Difference between revisions of "OSEE/ReqAndDesign"

From Eclipsepedia

Jump to: navigation, search
(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, time, agent, source, type, details (maybe in json format), duration
+
id, timestamp, user, source, type_id, duration, status, details (maybe in JSON format)
 
+
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
+
  
 +
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

Contents

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)

Exception Handeling

Requirements

Design