Getting a Quick Start with NerveCenter
-
Monitoring Alarms - Reading Logged Data -
This section describes how to examine the log file that the IfData_LogToFile alarm creates.
Sample Entry from Ifdata.log shows a sample entry from a log file. Each entry in the ifdata.log file refers to a single interface on a node.
Fields in a Log Entry explains what information the fields in this report contain. Refer to Sample Entry from Ifdata.log when reading the field descriptions.
Field | Contains |
---|---|
Date and time the record was logged. The format of the time is mm/dd/yyyy hh:mm:ss day (for example, 10/29/1997 14:32:22 Sat). | |
Identification number of the log entry. NerveCenter assigns a sequential number to each log entry. | |
Severity of the transition's destination state. The severity in the sample illustration is Normal. | |
Property group of the node that caused the alarm to change states. | |
Name of the alarm. The alarm triggered in the previous sample illustration is IfData_LogToFile. | |
Name of the state from which the alarm moves when the logged transition occurs. | |
Name of the trigger that causes the alarm to move from the Ostate to the Nstate. | |
The specific base object instance for which the transition occurred. | |
The attribute values of the node that caused the transition. Each is printed in the format |
When you later create and customize alarms, you'll be able to specify precisely what data you want logged. This versatility can help you monitor specific information about certain types of nodes. NerveCenter can also log alarm information to a Windows Event log or a UNIX system log. On Windows, alarms can log data directly into the NerveCenter database.
Analyzing Historical Detail for an Alarm Instance | Resetting and Disabling Alarms |
29 July 2003 |