event status show

Description​

The event status show command summarizes information about occurrences of events. For detailed information about specific occurrences of events, use the event log show command.

Parameters​

{ [-fields <fieldname>, ...]

If you specify the -fields <fieldname>, ... parameter, the command output also includes the specified field or fields. You can use '-fields ?' to display the fields to specify.

| [-instance ]}

If you specify the -instance parameter, the command displays detailed information about all fields.

[-node {<nodename>|local}] - Node

Selects the event records that match this parameter value. Events are tracked on a node-by-node basis, rather than being rolled up cluster-wide.

[-message-name <Message Name>] - Message Name

Selects the event records that match this parameter value. The message name is a short descriptive string. Filtering output by message name displays messages of a specific type.

[-indications <integer>] - Number of Indications

Selects the event records that match this parameter value. This parameter is most useful when used with a range, such as using the range "more than 20" to display only events that have been posted more than 20 times.

[-drops <integer>] - Number of Drops

Selects the event records that match this parameter value.

[-last-time-occurred <MM/DD/YYYY HH:MM:SS>] - Last Indication Time

Selects the event records that match this parameter value.

[-last-time-dropped <MM/DD/YYYY HH:MM:SS>] - Last Suppressed Indication Time

Selects the event records that match this parameter value.

[-last-time-processed <MM/DD/YYYY HH:MM:SS>] - Last Processed Indication Time

Selects the event records that match this parameter value.

[-stat-starting-time <MM/DD/YYYY HH:MM:SS>] - Stat Starting Time

Selects the event records that match this parameter value.

[-last-hour-histogram <integer>, ...] - 60-minute Histogram (privilege: advanced)

Use this parameter with the -fields parameter to display the "last hour" histogram for each event type. The last hour histogram records the number of times each event occurred in the last hour. The histogram is divided into sixty buckets, and each bucket collects one minute's events. The buckets display with the most recent event first.

[-last-day-histogram <integer>, ...] - 24-hour Histogram (privilege: advanced)

Use this parameter with the -fields parameter to display the "last day" histogram for each event type. The last day histogram records the number of times each event occurred in the last day. The histogram is divided into 24 buckets, and each bucket collects one hour's events. The buckets display with the most recent event first.

[-last-week-histogram <integer>, ...] - 7-day Histogram (privilege: advanced)

Use this parameter with the -fields parameter to display the "last week" histogram for each event type. The last week histogram records the number of times each event occurred in the last week. The histogram is divided into 7 buckets, and each bucket collects one day's events. The buckets display with the most recent event first.

[-severity {NODE_FAULT|SVC_FAULT|NODE_ERROR|SVC_ERROR|WARNING|NOTICE|INFO|DEBUG|VAR}] - Severity

Selects events that have the event severity you specify. Severity levels sort with the most severe levels first. Severity levels:

• NODE_FAULT - The node has detected data corruption, or is unable to provide client service.

• SVC_FAULT - The node has detected a temporary loss of service. Typically, this is caused by a transient software fault.

• NODE_ERROR - The node has detected a hardware error that is not immediately fatal.

• SVC_ERROR - The node has detected a software error that is not immediately fatal.

• WARNING - A high-priority message that does not indicate a fault.

• NOTICE - A normal-priority message that does not indicate a fault.

• INFO - A low-priority message that does not indicate a fault.

• DEBUG - A debugging message. These messages are typically suppressed.

• VAR - These messages have variable severity. Severity level for these messages is selected at runtime.

The examples below illustrate how to query on severity.