ems log dump value
An event producer recognizes the existence of an event and generates an event indication.
An event consumer describes events that it wants to receive based on filtering information within the event indication (type of message, contents within message).
The EMS engine receives indications from event producers and forwards to event consumers based on filtering descriptions.
EMS supports the following event consumers:
The logging consumer receives events from the engine and writes out event indication descriptions using a generic text-based log format.
The syslog consumer receives events from the engine and forwards to the kernel syslog facility.
The SNMP trap consumer receives events from the engine and forwards to the kernel SNMP trap genera_tor.
An EMS event has a name, typically expressed in a dotnotation format, and a collection of named attributes. Attribute values are either strings or integers. An EMS event has a priority associated with it. The following priority levels are defined:
node_fault A data corruption has been detected or the node is unable to provide client service.
svc_error A software error has been detected which is not immediately fatal.
log status
Return the status of the EMS log.
event status
Return the status describing events that have been
processed by the EMS engine.
status Return a terse version of the EMS engine status.
Rotated log files are identified by an integer suffix. For example, the first rotated file would normally be /etc/ems/log.0, the second /etc/ems/log.1, and so on.
The log file format is based on Extensible Markup Language (XML) fragments and contains information describing all of the data associated with the event indication. The following is an example log record associated with an event describing a state transition in the cluster monitor:
The format of the EMS log file is subject to change in a future release.
To get event processing information, the ems status event command is issued. Here is an example of its output:
Current time: 26May1999 03:58:14 Engine status: indications 28, drops 0 Event Indications Drops Last Time cf.fsm.stateTransit 1 0 26May1999 03:58:07 ems.asup.change 2 0 26May1999 03:58:06 ems.log.change 2 0 26May1999 03:58:06 ems.snmp.change 1 0 26May1999 03:58:06 kern.syslog.msg 22 0 26May1999 03:58:14
Event The name of the event.
Indications
The number of event indications of this type that
have been received.
Drops The number of times an event indication of this type was dropped due to resource constraints.
Last Time
This field contains timestamp header information
associated with the last event received of this
type. A value of local indicates that the event
was received by EMS on behalf of the local node. A
value of partner indicates that the event was
received by EMS on behalf of a cluster partner
node.
To get log status, the ems log status command is issued. Here is an example of its output:
EMS log data:
Current time: 25May1999 01:43:20
[LOG_default]
save 5, rotate weekly, size 8244
file /etc/log
level debug
indications 23, drops 0
last update: 25May1999 01:41:03
size The amount of data written to the currently active log file.
indications
Number of event indications received.
drops The number of events that were dropped due to resource constraints.
last update
The time at which the last event indication was
processed.
Remaining fields contain data associated with the last event indication.