OKI Common Services Logging Service API.

The logging service definition specifies a set of interfaces (API) that abstracts logging in any system.

Purpose of the Logging Service: To support logging throughout the system for diagnostic, performance: metrics, tuning, benchmarking, monitoring, security, performance, data collection, usage or trend analysis, forecasting, and statistics.

Salient Features of the OKI Logging Common Service API

What the Logging Service Might Support

1. Output to a variety of output devices for presentation, including memory (circular) buffers, consoles, log files (automatic versioning options), network sockets / listeners, PDAs, beepers, smart devices, GUI text areas, and so on.

An application monitoring logs can relay salient information to system management frameworks such as SNMP alerts and traps.

2. Reliable and unreliable delivery mechanisms depending on need.

3. Multiple output formats: Generate output in a number of different formats, including XML.
4. Protocol-independence, possibly distributed.
5. Timestamps will be maintained by the server and used for log entries. The server can use the services of a timeserver, NIST, or other synchronization server as necessary. Moreover, it is often required only to track the time interval between events, so for many purposes such as performance tracking a less accurate time source will suffice.

6. Facilitate query of log and/or report generation from UI.

7. Support a flexible configuration policy, can be turned off or reconfigured at runtime, fine granularity.     

8. Should not interfere with normal operation, be loosely coupled with the rest of the system, and have minimal impact on performance.