If something goes wrong at 8:29:23, see everything that
happened at that time. If a SAN has a disk failure, causing a
database server to reboot, which gives connection errors for
the front end server, and slowness for the client, you can see
the whole picture at once.
Extra detail for ploddle-enabled languages:
Source code file and line number
Link it in with your source code management
Process name / ID
Thread name / ID
Exception stack traces
Any application-specific data you want to add :-)
Username, actions taken, SCM revision IDs, ...
Use your current logging infrastructure
Syslog for system-level events
Python Logging for application-level
Extra data is sent as JSON, so adding support
for your language / logging library of choice
should be simple.