A daily dose of software engineering wisdom - inspiring, thought provoking, and sometimes just plain dangerous.

Tags: logging

Logging:

Ability to turn on / off logging at runtime and switch verbosity of it is very valuable. log4j does this.

Log entries should include the date / time and user performing the action.
We should log all interactions with the outside world:

- Front end: Every controller (AddUser, UpdatePrice, etc) should log that it has run.
- Back end: SQL, HTTP connections, calls to external systems / APIs, etc.

Things are most likely to go wrong at the boundary between systems, and our UnitTesting don't verify those, so we need lots of visibility.

Also of course log all errros with full stack trace.

Last published: Monday 5th April 2010

<<Previous     Next>>

carriagereturn.org home