The log message file name is passed as the first parameter to all NEH handlers. It consists of a list of value pairs named:
NotificationDetailFieldName – a string identifying the parameter
and
NotificationDetailFieldValue – a value for the parameter
By reading these name-value pairs, the handler is able to analyze the log entry that caused it to be invoked and respond accordingly.
Log message files have a variable number of fields and can contain additional fields, such as a SessionID or a Data Source. The following table lists common fields.
|
Immutable |
The log message will not be cleared when erasing the logs. |
|
SequenceNumber |
All logs have an ascending sequence number. |
|
MasterDate |
A 32 bit timestamp of when the master received the log message. |
|
LocalDate |
A 32 bit timestamp of when the log message was sent. |
|
Source |
The node from which the log message originated. |
|
Category |
The log message category. |
|
Level |
A value between 1 and 4 with 1 being Detail and 4 being Error. |
|
Attachments |
The text of any attachment to the log message. |
|
Log |
The body of the log message. |
|
Acked |
Indicates if the log message is acknowledged (0 or 1). |
|
BuildNumber |
The version of Ops Center Protector on the node that sent the log message. |