Application metrics and problems
The following table lists application server metrics that can be displayed in the Application View. 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
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
1 If you upgraded from an earlier version of BMC Application Diagnostics, the names of the properties appear in the Agent Policy files and use the terms tolerating and frustrated to represent warning and critical thresholds, respectively; for example:
global.error.tolerating.event.threshold=5
global.error.frustrated.event.threshold=10
The following example describes how the status is determined per transaction entry point, and how this can differ for the application or server status.
Metrics for tiers in the Application View, by request
The following metrics are not displayed by default; contact BMC Support to activate required metrics.
Related topics
Configuring-event-thresholds-SLAs-for-automatically-discovered-applications
Monitoring-applicationsEvent sources
Sending-App-Visibility-health-events-to-integrated-systems
Contact BMC support team