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
Metric | Unit | Tier | Description | Minor1 | Critical1 threshold | Editable | Platform | Vendor |
---|---|---|---|---|---|---|---|---|
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 | 25 | 35 | No | Java and .NET | None |
Operation latency on the database | % | Database | Percentage of database requests that cross the latency threshold | 5 | 10 | Yes | Java and .NET | .NET: MS SQL 2005 and 2008, Oracle 10 and 11 |
Operations with errors on the database | % | Database | Percentage of database requests with errors | 5 | 10 | Yes | Java and .NET | .NET: MS SQL 2005 and 2008, Oracle 10 and 11 |
Deadlock | # of threads | Web and Business | Average number of threads in a deadlock state | 5 | 10 | No | Java | None |
Memory pages per second | pages/sec | Web and Business | Rate of paging memory to and from the server | 100 | 200 | No | .NET | None |
Memory usage | % | Web and Business | Java: Average percentage of memory marked as used by all heap pools .NET: Average percentage of the average values of virtual and private memory used by all traced ASP.NET worker processes. The values are defined in the agent policy file. Note: 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. | 75 | 90 | No | Java and .NET | None |
Processor queue length | # of threads | Web and Business | Number of ready (not running) threads in the processor queue | 800 | 1000 | No | .NET | None |
Requests queued | # of requests | Web and Business | Average number of ASP.NET requests waiting to be processed | 500 | 750 | No | .NET | None |
Thread count | # of threads | Web and Business | Java: Average number of threads used by the JVM process .NET: Average number of threads used by all traced ASP.NET worker processes | 500 | 750 | No | Java and .NET | None |
Percent of thread pool used | % | Web and Business | Percentage of the thread pool that is used | 80 | 90 | No | Java | WebSphere, WebLogic |
Transactions with errors on the server | % | Web and Business | Percentage of the transactions with errors | 5 | 10 | Yes | Java and .NET | None |
Transaction latency on the server | % | Web and Business | Percentage of the transactions that cross the latency threshold | 5 | 10 | Yes | Java and .NET | None |
Users experiencing slow operations | % | User | Percentage of users experiencing operations that cross the latency threshold | 5 | 10 | Yes | Not applicable | None |
Users experiencing operations with errors | % | User | Percentage of users experiencing operations with errors | 5 | 10 | Yes | Not applicable | None |
Users experiencing slow network time | % | Network | Percentage of users experiencing operations time that cross the latency threshold | 5 | 10 | Yes | Not applicable | None |
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
Configuring event thresholds (SLAs) for automatically discovered applications
2 Comments
Sandy Reid
Sara Kamen