You can further restrict your definition of unavailability by creating a similar situation that is triggered when a particular fault code or fault string is observed in the message. An example of a situation definition that uses the Fault Code and Fault String attributes in the Fault Log_610 attribute group to specify a particular fault that triggers the situation is displayed inFigure 1.
When this fault code and fault string is observed in the message, the situation is triggered and displayed in the Tivoli Enterprise Portal.
From the flyover window about the triggered situation, follow the link to the Situation Event Results workspace to see what caused the situation to be triggered, and the affected operation. Then, assuming that you created links to the Operational Flow workspace for this situation in the Situation Event Results workspace, you can take that link to the associated Operational Flow workspace to see the topology view.
Displaying the accompanying topology view displays a Critical status indicator on the affected operation aggregate. Double-clicking the operation aggregate displays the specific operation instance affected by the situation in the Interaction Detail portion of the view. The flyover window on the operation instance includes the details about the specific situation that is triggered.
Metrics in the Fault Log table are not accumulated over the entire Tivoli Enterprise Monitoring Agent monitoring interval. Therefore, the situations that are written against this table are triggered when the situation sampling interval expires and there is a matching entry in the Fault Log table. A row can remain in the Fault Log table for up to 10 minutes. Therefore, the situation does not close until the row that matches the situation condition is removed.