Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
OSEE/ReqAndDesign
< OSEE
Revision as of 15:19, 28 October 2013 by Ryan.d.brooks.boeing.com (Talk | contribs) (→Requirements)
Logging
Requirements
- 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)
Design
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
http://www.precisejava.com/javaperf/j2ee/JDBC.htm#JDBC104
-7 is used for duration on instantaneous events otherwise the actual duration in ms is updated upon completion (in the meantime -1 is used)