Monitoring scenarios

This topic outlines the following different scenarios where TrueSight Middleware and Transaction Monitor helps solve, prevent or automatically handle specific problems:

Monitor the performance of specific technologies

TrueSight Middleware and Transaction Monitor monitors the technologies through which the transactions you are interested in flow. TrueSight Middleware and Transaction Monitor can monitor and tell you whether:

• There are problems in your environment and where they are.
• Your infrastructure is performing as expected. You can monitor the speed and latency of your applications.
• You need to re-engineer your applications or infrastructure to better handle your current or future needs. By isolating sources of real system inadequacies, you can plan appropriately using facts based on real numbers in your environment.

Find bottlenecks in your transaction pathway

TrueSight Middleware and Transaction Monitor can identify bottlenecks in your transaction pathway.

You can start with a simple transaction pathway and collect statistics for how long it takes a transaction to traverse the transaction pathway. You can add activities to different parts of your transaction pathway to expose more details of your business process. The additional information, such has how long a transaction takes to get from point A to point B can reveal bottlenecks. TrueSight Middleware and Transaction Monitor can also reveal how long a particular application takes to process a transaction. Your transportation layer could be operating efficiently, while your application is the bottleneck.

Transaction assurance and service level agreements

A record of the transaction might be stored in history from where it can be retrieved should it need to be reviewed or some proof of its completion is necessary.

Using SLA templates allows you to be notified pro-actively via event actions when your transaction pathway is performing badly or has SLA excursions. A SLA excursion is a transaction that has exceeded your defined thresholds for the duration of a transaction. You might be notified that any number of transactions have had SLA excursions during an interval and then query that period of time for those transactions or you may be notified of each transaction. Generally the first might be a human oriented event action like an email where the second might be done with a log to file action. Refer to Transaction Pathway View for more details on querying transactions from history.

A simple two-activity transaction pathway in TrueSight Middleware and Transaction Monitor can show when a transaction arrives at and leaves the company borders. The time that it takes a transaction to travel between two points can be calculated and used to produce reports that show whether any service level agreements are fulfilled or not.

Monitor high-value transactions

Using payload data, TrueSight Middleware and Transaction Monitor allows you to monitor and quickly identify high-value transactions by content.

For example, assume three transactions in a financial institution are processed with values of $1,000, $10,000, and $1,000,000 respectively. Failure in any of these transactions is not acceptable but the ability to identify the value of the failed transaction can decide how important a resolution becomes.