Situations
Predefined situations describe system conditions that you might want to monitor.
A situation is a logical expression involving one or more system conditions. When a condition matches the specified situation, the action specified in the situation occurs.
Use predefined situations to start monitoring quickly or as a template from which to create your own custom situations.
To display details about the Transaction Tracking predefined situations, select Transactions Reporter in the navigator in the Situation Editor.
- Parent_Sub_Transaction_Time_C
- Parent_Sub_Transaction_Time_M
- Parent_Sub_Transaction_Time_W
- Transaction_Rate_C
- Transaction_Rate_M
- Transaction_Rate_W
You can use default situations as templates for creating customized monitoring situations. You can also create new situations using Transaction Tracking attributes. When specifying a new situation, use the Aggregate Situations (TOAGGSIT) and Interaction Situations (TOINTSIT) tables to define situations that include both flexible context and flexible metrics. See Tivoli Monitoring for further information about creating situations.
Earlier predefined situations
In ITCAM for Transactions V7.2.0.2 and earlier, Transaction Tracking provided the following predefined situations. These situations are not associated by default and do not provide flexible context and flexible metrics:
- Failed_Transactions
The Failed_Transactions situation uses the Group Level and Percent Failed attributes and the KTO: REMEMBER AGGREGATE Take Action command (KTO: REMEMBER AGGREGATE &{Aggregates.Aggregate_ID} failed=1) to indicate a high failure rate for transactions within a topology. By using this situation, you can see the nodes with a high failure rate (more than 50%) in the topology workspaces and identify the transaction instances that are causing the problem. Hover the mouse over Transactions in the Navigator to display details of the situation, agent, date and time, and aggregate name for the transaction that has failed.
The situation causes the Transaction Reporter to obtain the instance for the aggregate that triggered the command by exceeding the condition. The Transaction Reporter performs a full instance trace and provides the Instance Rows and Instance Interaction Rows to the Tivoli Data Warehouse. This situation is run every 5 minutes by default.
- Slow_Transactions
The Slow_Transactions situation uses the Group Level and Response Time Deviation attributes and the KTO: REMEMBER AGGREGATE Take Action command (KTO: REMEMBER AGGREGATE &{Aggregates.Aggregate_ID} slow=1) to identify transactions that are slower than the baseline by 100% or more and store them in the Tivoli Data Warehouse. The baseline is determined by the average of the response times over the last 24 hours (or custom History setting). This situation is run every 5 minutes by default.
- KTU_Transport_Queue_Full
The KTU_Transport_Queue_Full situation is triggered whenever events are dropped because the number of events in the Transport Dispatch Queue for the Transaction Collector is exceeded. The situation generates an alert which is displayed for 5 minutes in the Transport Dispatch Queue Size column of the Collector Status pane in the Transaction Collector workspace.