Page tree

Skip to end of metadata
Go to start of metadata

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 that are listed as editable in the Application Configuration page.

Tip

To expand the table for online reading, press the F key to turn the full screen view on or off.

Metrics for tiers in the Application View

MetricUnitTierDescription

Minor1
threshold

Critical1
threshold
EditablePlatform

Vendor
limitations

CPU usage

 
%

Web and Business

Java: Average percentage of CPU used by the JVM process.

NET: Average percentage of CPU used by all traced ASP.NET worker processes

2535

No

Java and .NETNone

Memory usage

MBWeb and Business

Java: Average consumed memory, consisting of heap and non-heap memory

.NET: Average values of virtual and private memory that are used by all traced ASP.NET worker processes

75% of total memory90% of total memoryNoJava and .NETNote: For WebSphere 7 application servers, the Memory Usage metrics sometimes display values greater than 100%. The value is displayed as it is received from WebSphere, and the same results are displayed in the JConsole tool.
Operation latency on the database%Database

Percentage of database requests that cross the latency threshold

510YesJava and .NET.NET: MS SQL 2005 and 2008, Oracle 10 and 11 
Operations with errors on the database%DatabasePercentage of database requests with errors510YesJava and .NET.NET: MS SQL 2005 and 2008, Oracle 10 and 11

Transaction latency on the server

%Web and BusinessPercentage of the transactions that cross the latency threshold510YesJava and .NETNone
Transactions with errors on the server%Web and BusinessPercentage of the transactions with errors510YesJava and .NETNone
Users experiencing operations with errors%UserPercentage of users experiencing operations with errors510YesNot applicableNone
Users experiencing slow network time%NetworkPercentage of users experiencing operations time that cross the latency threshold510YesNot applicableNone
Users experiencing slow operations%UserPercentage of users experiencing operations that cross the latency threshold510YesNot applicableNone
 

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

Related topics

Configuring event thresholds (SLAs) for automatically discovered applications

Monitoring applications

Event sources