Situation Status Log attributes
The Situation Status attributes collect status information on started situations and policies. You can apply any of the predefined queries for this group (in the Query editor underCloud Pak System Software Monitoring Server → Situation Status Log) to charts and tables; you cannot use these attributes in situations.
Display Item Attribute to further qualify the situation. With a display item set for a multiple-row attribute group, the situation continues to look at the other rows in the sampling and opens more events if other rows qualify. This optional addition to a situation also enables you to quickly distinguish events in the message log and event console views. The display item is designated in the Situation editor (Formula tab, click Advanced).
Full Name The name given to the situation or policy.
Global Timestamp The time the event was recorded by the hubCloud Pak System Software Monitoring Server. The format is MM/DD/YY HH:MM:SS.
Local Timestamp The time the event occurred or the condition was observed by the originating managed system. The format is MM/DD/YY HH:MM:SS, as in 07/23/09 04:45:35 for July 23,2009 at 4:45:35 a.m.
Name The unique identifier given to the situation or policy.
Node The name of the monitoring server where the situation is running.
Origin Node The name of the managed system where the situation is being monitored.
Owner The user ID of the person who acknowledged the event.
Sound File The name of the sound file associated with the Navigator item for this situation.
Status The status of the situation. The possible values are listed in the following table:
| Status | Value | Description |
|---|---|---|
|
|
A |
The situation event has been acknowledged. |
|
|
D |
The situation has been deleted. |
|
|
X |
The situation is in a problem state. |
|
|
F |
The acknowledgment has expired and the situation is still true. |
|
|
Y |
The situation is running and is true. |
|
|
N |
The situation is running, has been true, and is now false. |
|
|
E |
The acknowledgment was removed before it had expired and the situation is still true. |
|
|
L |
The situation is being started. |
|
|
P |
The situation has been stopped. |
| Not Available | <null> | The status for the situation is not being returned. To investigate, set
this client trace: error (unit:Managed detail) |
Acknowledged
Deleted
Problem
Expired
Open
Closed
Reopened
Started
StoppedTo determine why the status is set as it is, the following
client trace will help: error (unit:Managed detail).
Type The event is either pure (unsolicited notification; the situation has no sampling interval) or sampled (the situation is sampled at intervals).
- Sampled
-
Sampled events happen when a situation becomes true. Situations sample data at regular intervals. When the situation is true, it causes an event, which gets closed automatically when the situation goes back to false (or you can close it manually if you stop the situation).
- Pure
- Pure events are unsolicited notifications. Examples of pure events
are an out-of-paper condition on a printer and an occurrence that
adds an entry to the Windows System Log. Some monitoring agents have
attributes that report pure events, such as the Windows Event Log
and Windows File Change attribute groups. A situation using one of
these attributes can monitor for pure events. Because of the nature
of pure events and the fact that a situation created with pure event
attributes does not have a sampling interval, they are not closed
automatically like sampled events; you must close the event manually
or through an UNTIL clause.
Note: If you create a query and apply a column function to the Type attribute, pure events will not be included in the AVG, COUNT, MAX, MIN or SUM calculation.