Designing and Managing Behavior Models - Alarm Actions - EventLog -
Delete Node      Fire Trigger

EventLog

The EventLog alarm action writes information about an alarm transition to the Windows Application event log or a UNIX system log file. On Solaris the system log file is /var/adm/messages, and on HP-UX it is /var/adm/syslog/syslog.log.

 
  To add an EventLog action to a transition:

  1. From the Transition Definition window, select the New Action button.

    A pop-up menu listing all the alarm actions is displayed.

  2. Select EventLog from the pop-up menu.

    The Event Log Action dialog is displayed.

    eventLogAction

    This dialog provides default values for the three standard event log parameters -- Source, Type, and Event -- and allows you to change them.

  3. Leave the default value in the Source text field, or type in a new registered source.

    In the Windows environment, use the default value (NerveCenter) for the Source unless you are familiar with the intricacies of the event log and have created another registered source. The source is the program generating the log entry.

  4. Select one of the standard event log types from the Type drop-down list.

    Select the most appropriate option for the situation your alarm transition detects. The options are Error, Warning, Informational, Audit Success, and Audit Failed.

  5. Leave the default event ID in the Event field, or type a new one.

    Under Windows, use the default value (3221356553) in the Event field unless you're familiar with the inner workings of the event log, have changed your Source value from the default, and have defined an associated ID. The event log uses this event ID to find the text message format for the log entry.

  6. Select the OK button in the Event Log Action dialog.
  7. Select the OK button in the Transition Definition window.
  8. Select the Save button in the Alarm Definition window.

A sample event log entry is shown in Event Detail.

Event Detail

eventDetail

Fields in Log Entry or Mail Message lists the fields in a NerveCenter log entry or mail message and discusses the value of each field.

Fields in Log Entry or Mail Message

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.

Severity

The severity of the transition's destination state.

PropertyGroup

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

Node

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

Alarm

Name of the alarm.

Ostate

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

Trigger

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

Nstate

State of the alarm after the logged transition occurs.

TrapTime

The contents of a trap's timestamp field. Used only when the transition was caused by a trap-mask trigger.

GenericTrapNumber

The contents of a trap's generic-trap field. Used only when the transition was caused by a trap-mask trigger.

Enterprise

The contents of a trap's enterprise field. Used only when the transition was caused by a trap-mask trigger.

SpecificTrapNumber

The contents of a trap's specific-trap field. Used only when the transition was caused by a trap-mask trigger.

Instance

The specific base object instance for which the transition occurred.

Object

The base object associated with the transition.

Attribute ...

The variable bindings of the trigger that caused the transition. Each variable binding is printed in the format Attribute attribute=value.



Delete Node Fire Trigger
29 July 2003