ITCAM for Transactions 7.x: Robotic Response Time agent playback status and availability
KevinBaldwin 100000EDTY Comments (3) Visits (12798)
IBM Tivoli Composite Application Manager for Transactions
|Complete||The script started and completed playback|
The script failed to execute
This status will generate a Critical alert for the RRT_Playback_Failed situation
Robotic Response Time exceeds the timeout period specified for this script in the
corresponding AMCE profile
This status will generate a Warning alert for the RRT_
The script execution time is longer than the playback interval specified for this script in
the corresponding AMCE profile
This status generates a Warning alert for the RRT_
2. Robotic Script Verification Point Failures
This view is seen in the Robotic Response Time > Playback Status workspace:
Entries seen in this view are the result of failed verification points defined in robotic scripts or a "timeout".
If Verification Points are not defined in robotic scripts, Event Types such as HTTP Return Code Failure, Page Title Failure, URL Unavailable will not be reported.
3. Percent Good / Percent Failed / Percent Slow / Percent Available
These "Percentage" columns are seen in various Robotic Response Time > Application and Transaction workspace table views displaying aggregate data.
The percentage of transactions with a transaction status of Good or Slow
but not Failed.
The sum of this value and Percent Failed should total 100 percent.
Any failure is considered important, so the table cell for this attribute is
displayed in the TEP with a green background only when the value for
Percent Available is 100 percent.
Any value less than 100 percent is displayed in the TEP with a red
The percentage of transactions whose requests were marked as Slow.
Requests are marked as Slow if the transaction response time exceeds the
Minimum Response Time Threshold specified in the corresponding profile
This value is calculated by dividing Slow Requests by Total Requests and
multiplying by 100%.
The sum of this value and the Percent Good value should equal Percent
Any value that is greater than 0 percent is displayed with a yellow
background in the TEP.
The percentage of transactions whose requests were marked as Failed.
Requests are marked as Failed if:
Verification Points are needed for ARM_FAIL to be returned when failures
The percentage of transactions whose requests were marked as Good.
This is calculated by dividing Good Requests by Total Requests and
multiplying by 100%.
The sum of this value and the Percent Slow value should equal the Percent
Percentages are based on the number of requests in a 5 minute aggregate period. Therefore, if a script runs every 5 minutes and you are using the default aggregation period of 5 minutes, the different percentages will normally have values of 0 or 100.
4. Situation Event Console
The Situation Event Console can be viewed at the Enterprise level or the agent level in the Robotic Response Time workspace as seen here:
This view shows events triggered by the situations used on this agent.
Events relate to conditions that you want to examine to determine if a potential problem exists in the systems and resources you are monitoring.
Robotic Response Time includes the following default situations:
** If Verification Points are not defined these situations cannot trigger events.
These situations are explained in more detail in the ITCAM for Transactions Users Guide:
Visit the ITCA