Ops Center Protector maintains a list of log messages generated by the various subsystems running on Protector nodes. All log messages and are sent to and stored on the Master node, where they are made available via the user interface.
- A unique ID assigned to every log entry, useful when discussing logs with colleagues and support engineers.
- Audit Flag indicating a change to the system status. These cannot be modified or deleted, for compliance purposes. The identity of the user initiating the action is recorded.
- Date and time recording when the log was generated on the originating node and received by the master node.
- Level identifying the importance of the log entry.
- Attachment enabling additional context information to be attached to the log entry.
- An ID identifying the position within the Protector code where the message was generated. The ID can be used to reference an engineering support database that provides additional description and identifies possible causes and solutions.
Numerous filters can be applied to the displayed logs to enable the user to locate relevant entries.
Log entries that relate to a particular activity, such as a repository resynchronization, are marked with a session marker. This session marker can be used to filter the logs so that only the log entries relating to that activity are displayed.
Log entries can be acknowledged by the user and marked with a comment so that it is clear that the event has been noticed and addressed.
The entire log data-base can be exported in various file formats so that it can be analyzed offline or presented in a report.
If a specific event or set of events occurs in the logs then notifications can be generated via email, SNMP or the OS System Event Log.