Writing a situation with multiple results

Body

Writing a situation with multiple results

The results of a situation sometimes gives more than one result.

for example NT_Disk_Space_low  could give back the results for more than one disk on the machine.

If the situation is to fire on each result then Display Item has to be selected.

Definition of Display Item:
Normally, when a situation encounters a value in a row that meets the condition, it opens an event and no more happens until the event has been closed and then opened again.
With a key attribute set as the display item 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.
Only certain attributes can be designated as display items.

The Display Item option can be selected from the Advanced Situation Options in the GUI:

However not all attributes have this option and sometimes it is not available on a situation that will give a multiple row result.

For example with the UX OS agent there is an option to monitor Solaris zones.

However when this is tried, it will tell you that the display item option is not available for any of the Solaris zone parameters.

In these cases there is two options that can used:

1) Individual situations are written for each  result value,

for example  The Zone_Id is a number  so:

Solaris_Zones.Zone_ID == 1 AND *VALUE Solaris_Zones.Status *EQ Running

then another situation is written for the zone_id  2;

Solaris_Zones.Zone_ID == 2 AND *VALUE Solaris_Zones.Status *EQ Running

until the number of zones are covered and these are then distributed.

2) It is possible to change the dockpc file on the TEPS so that it will use display item.

HOWEVER it should be noted that this is a local workaround:
This is an unsupported change and it is therefore at your own risk, if there are any issues then you will requested to change the file back to the standard installed file.
If the agent is upgraded at any point the file may be overwritten and this change will have to be added to the new file as well, if it is not added if there is a upgrade the situation will fail.

Before anything is done, take a copy of the file to safe place, so it can be restored if there are any issues.

The change is done to the dockpc file (where pc is the agent code) on the TEPS.

So for this example it is the dockux file.

These files can have more than one section, and the attribute can be defined in each section.

The sections (there is often more than one) in the file that describe the attribute has to have the line

*ATOMIZE:

added and the TEPS then needs to be reconfigured for the change to be picked up.

for example to allow the Zone_ID on Solaris zones to be able to have display item set :

The change is done to the dockux file on the TEPS

The line:
*ATOMIZE:
needs to be added to the attribute definition.

Edit the file and locate the lines of:
*ATTR: Zone_ID

There are three cases for this: one in System, one in Process and one in Solaris_Zones

add the *ATOMIZE: line as below:

*ATTR: Zone_ID
*CAPTION: Zone ID
*COLUMN: ZID
*TYPE: I,4
*PRINTF: "%d"
*OPTION: PRIMARYKEY=0
*ENUM: Value_Exceeds_Maximum=2147483647
*ENUM: Value_Exceeds_Minimum=-2147483648
*ENUM: Not_Available=-1
*ENUM: Not_Collected=-2
*AGIENUMS:
*OPTION: SORTBYINTERNAL
*TEXT: The numeric ID the system assigned to a zone.
*ATOMIZE:

The TEPS then needs to be reconfigured for the change to be picked up.

Once that is done you will be able to select Display Item for the Zone_Id and the situation will fire on all Zone_Id

Subscribe and follow us for all the latest information directly on your social feeds: