Monitoring Your Network
-
Monitoring Alarms - Reading Logged Data -
As was mentioned in the section Viewing an Alarm Instance's History, NerveCenter does not maintain a lot of historical information about network conditions. It remembers the last twenty transitions for each current alarm instance; however, when that alarm instance is deleted (when it returns to Ground), even that history is lost.
To preserve historical information about a network problem, a behavior model must log data about alarm transitions to a file, the system log (UNIX), Event Log (Windows), or to the NerveCenter database (Windows only). To take advantage of this logged data, all you need to know is where the data is being logged and how to interpret the logged data.
You can also manage the size of logs as well as the length of time they are stored by setting parameters in NerveCenter Administrator. For more information, see the book Managing NerveCenterNerveCenter and refer to NerveCenter Administrator help.
For more information about where NerveCenter writes log data and how you should interpret this data, see the following subsections:
To determine whether an alarm logs data about any of its transitions and, if so, where it logs that data, you should look at the alarm's notes using the NerveCenter Client.
From the NerveCenter Client's
Admin
menu, choose Alarm Definition List
.
The Alarm Definition List window is displayed.
Notes
button.The Alarm Notes and Associations dialog displays.
This dialog contains documentation for the alarm you selected and describes, among other things, any logging actions. For a Log to File action, the notes specify the log file to which data is written. An EventLog action causes NerveCenter to log data to one of the following locations:
A Log to Database action causes NerveCenter to log to the NerveCenter database (Windows only).
Using the NerveCenter Client | How to Interpret Logged Data |
29 July 2003 |