Jump to: navigation, search




  • shall handle thousands of log entries per second
  • log entries shall be quickly accessible based on any combination of server, user, timestamp, log type, duration, status
  • entries shall be accessible (especially) when an application server is unresponsive
  • entries shall be available until they are deleted by an admin or admin policy (applied by server automatically)


id, time, agent, source, type, details (maybe in json format), duration

log event are defined as tokens with long and name (which is not in db)

at runtime enable/disable logging by agent, source, and type even progress is reported using logger

need to see what is still running even if server is unresponsive need to to cross server analysis


-7 is used for duration on instantaneous events otherwise the actual duration in ms is updated upon completion (in the meantime -1 is used)

Exception Handeling