Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "OSEE/ReqAndDesign"
< OSEE
(→Requirements) |
|||
| Line 5: | Line 5: | ||
* entries shall be accessible (especially) when an application server is unresponsive | * 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) | * entries shall be available until they are deleted by an admin or admin policy (applied by server automatically) | ||
| − | + | * at run-time logging shall be enabled/disabled based on any combination of user, source, and type | |
=== Design === | === Design === | ||
| − | id, | + | id, timestamp, user, source, type_id, duration, status, details (maybe in JSON format) |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| + | log entry types are defined as tokens with a long and name (which is not in db) | ||
http://www.precisejava.com/javaperf/j2ee/JDBC.htm#JDBC104 | http://www.precisejava.com/javaperf/j2ee/JDBC.htm#JDBC104 | ||
| − | |||
-7 is used for duration on instantaneous events | -7 is used for duration on instantaneous events | ||
otherwise the actual duration in ms is updated upon completion (in the meantime -1 is used) | otherwise the actual duration in ms is updated upon completion (in the meantime -1 is used) | ||
| − | |||
== Exception Handeling == | == Exception Handeling == | ||
=== Requirements === | === Requirements === | ||
=== Design === | === Design === | ||
Revision as of 15:30, 28 October 2013
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)
- at run-time logging shall be enabled/disabled based on any combination of user, source, and type
Design
id, timestamp, user, source, type_id, duration, status, details (maybe in JSON format)
log entry types are defined as tokens with a long and name (which is not in db) 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)