Getting a Quick Start with NerveCenter - Monitoring Alarms - Reading Logged Data -
Previous: Analyzing Historical Detail for an Alarm Instance     Next: Resetting and Disabling Alarms

Reading Logged Data

This section describes how to examine the log file that the IfData_LogToFile alarm creates.

 
  To open the log file:

  1. Start a text editor or viewer on your system.
  2. Open the ifdata.log file:

The figure below shows a sample entry from a log file. Each entry in the ifdata.log file refers to a single interface on a node.

Sample Entry from Ifdata.log

ifdataLog.gif

Click the thumbnail above to view full-sized image.

The table below explains what information the fields in this report contain. Refer to the above illustration when reading the field descriptions.

Fields in a Log Entry

Field Contains

Time

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).

LogId

Identification number of the log entry. NerveCenter assigns a sequential number to each log entry.

DestStateSev

Severity of the transition's destination state. The severity in the sample illustration is Normal.

NodePropertyGroup

Property group of the node that caused the alarm to change states.

NodeName

Name of the node that caused the alarm to change states.

AlarmName

Name of the alarm. The alarm triggered in the previous sample illustration is IfData_LogToFile.

OrigState

Name of the state from which the alarm moves when the logged transition occurs.

TriggerName

Name of the trigger that causes the alarm to move from the Ostate to the Nstate.

DestState

State of the alarm after the logged transition occurs.

TriggerInstance

The specific base object instance for which the transition occurred.

TriggerBaseObject

The base object associated with the transition.

Attribute ...

The attribute values of the node that caused the transition. Each is printed in the format Attribute attribute.instance=value. For a description of the attributes logged by the ifData poll, see MIB Values Detected by the ifData Poll.

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 NT Event log or a UNIX system log. On Windows NT, alarms can log data directly into the NerveCenter database.

Previous: Analyzing Historical Detail for an Alarm Instance Next: Resetting and Disabling Alarms
Please send comments or corrections to Information Development
This file was last updated on 10 October 2000