Application metrics and problems

TrueSight App Visibility Manager monitors the following list of application server metrics, which can help you correlate application issues with server issues. If a metric exceeds a threshold, the tier in the Application View changes color, and the problem is displayed on the Problems tab for the tier member.

Example of the Web tier, Problems tab

appvis_problems_tab.png

Related topics

Configuring-event-thresholds-SLAs-for-automatically-discovered-applications

Monitoring-applications

App-Visibility-end-user-monitoring
Event sources

Sending-App-Visibility-health-events-to-integrated-systems

Some metrics are platform dependent (Java servers or .NET servers), but most are from both platforms.

You can configure threshold values listed as editable in the Application Configuration page.

Metrics for tiers in the Application View


The following example describes how the status is determined per transaction entry point, and how this can differ for the application or server status.

Example of server status and transaction status

In a five-minute period, a server has 25 transactions without any latency violations or availability errors, and 1 transaction entry point, login.jsp, that has an exception error.

The statuses of the application and server are Critical, even though fewer than 5% of all the transactions that were executed have issues. (That is, with the default settings of 5% for Minor, 10% for Critical.)

When you drill down to the login.jsp transaction, you see the status of the transaction is Critical because it ran once and had an exception error. That is, every time the transaction ran (once) it had an error, so the percentage of transaction executions with errors for this entry point is 100%.

Metrics for tiers in the Application View, by request

The following metrics are not displayed by default; contact BMC Support to activate required metrics.


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*