Monitoring Your Network - Monitoring Alarms - Reading Logged Data -
Previous: Using the NerveCenter Client     Next: Determining Where Data is Being Logged

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 NT), or to the NerveCenter database (Windows NT 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 NerveCenter 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:

• Determining Where Data is Being Logged
• How to Interpret Logged Data