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
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
| Metric | Unit | Tier | Description | Minor | Critical 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 | 75 | 85 | Java and .NET | None | |
Memory usage | % | Web and Business | Java: Average percentage of consumed memory, consisting of heap and non-heap memory .NET: Average percentage values of virtual and private memory that are used by all traced ASP.NET worker processes | 85 | 95 | Contact BMC support | Java and .NET | 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. |
| 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 |
Transaction latency on the server | % | Web and Business | Percentage of executions for each transaction entry point that crosses the latency threshold That is, the value represents the violation rate of each transaction entry point. | 5 | 10 | Yes | Java and .NET | None |
| Transactions with errors on the server | % | Web and Business | Percentage of executions for each transaction entry point with HTTP errors That is, the value represents the error rate of each transaction entry point. | 5 | 10 | Yes | Java and .NET | 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 |
| Users experiencing slow operations | % | User | Percentage of users experiencing operations that cross the latency threshold | 5 | 10 | Yes | Not applicable | None |
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 requestThe following metrics are not displayed by default; contact BMC Support to activate required metrics.
| Metric | Unit | Tier | Description | Platform | Vendor limitations |
|---|---|---|---|---|---|
Deadlock | # of threads | Web and Business | Average number of threads in a deadlock state | Java | None |
Memory pages per second | pages/sec | Web and Business | Rate of paging memory to and from the server | .NET | None |
Garbage collection count | # of GC cycles | Java: Sum of garbage collection (GC) cycles invoked by all GC algorithms .NET: Sum of the number of generation 0 calls Note: For WebSphere 8.5 application servers, the Garbage Collection Count metric and event displays a value that is different from the value displayed in the JConsole tool. The value in BMC Application Diagnostics is displayed as it is received from WebSphere. Metric not displayed by default. | Java and .NET | None | |
Garbage collection time | ms | Java: Sum of the time spent on GC cycles by all GC algorithms .NET: Sum of the time spent on generation 0 calls | Java and .NET | None | |
Heap size - committed | MB | Java: Sum of committed memory in all heap pools, measured after GC and as reported by JVM .NET: Amount of virtual memory currently committed by the GC Metric not displayed by default. | Java and .NET | None | |
Heap size used | MB | Java: Sum of committed memory in all heap pools, measured after GC and as reported by JVM .NET: Amount of virtual memory currently committed by the GC Metric not displayed by default. | Java and .NET | None | |
| Percent of thread pool used | % | Web and Business | Percentage of the thread pool that is used | Java | WebSphere, WebLogic |
Permanent generation - used | MB | Memory used for the Permanent Generation pool Metric not displayed by default. | Java | None | |
| Permanent generation - maximum | MB | Maximum memory used for the Permanent Generation pool Metric not displayed by default. | Java | None | |
Processor queue length | # of threads | Web and Business | Number of ready (not running) threads in the processor queue | .NET | None |
Processor time | % | Percentage of elapsed time for all processes of the OS that the processor spends to execute a nonidle thread Metric not displayed by default. | .NET | None | |
Requests queued | # of requests | Web and Business | Average number of ASP.NET requests waiting to be processed | .NET | None |
Restarted application pools | # of processes | Sum of all restarted worker processes in all of the application pools Metric not displayed by default. | .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 | Java and .NET | None |
| Web services duration - average | ms | Average time spent on web service exits, as measured on sampled requests, that are marked as exit points and as tier "w_s" in the recording profile | .NET | None |
Comments
Log in or register to comment.