Monitor overall system health

Use PMI data to monitor overall system health

+
Search Tips | Advanced Search

To monitor PMI statistics...

Enable PMI
Monitor system using TPV or some other 3rd-party performance monitoring solution.

Metrics to monitor include...

Metric Meaning
Average response time Include statistics for servlet and EJB response time.
Number of requests (transactions) As transactions increase, response time increases.
Number of live HTTP sessions Reflects concurrent usage. The more live sessions, the more memory is required.
As number increases, consider increasing...

session time-out values
JVM heap

Web server thread pools Interpret Web server, Web container, ORB, data source pools together.
Setting too large impacts the amount of memory that is required and might cause too much work to flow downstream if downstream resources cannot handle a high influx of work.
Setting too small might cause bottlenecks if the downstream resource is able handle an increase in workload.
Java virtual memory Look for frequency of garbage collection. This data can assist in setting the optimal heap size. In addition, use the metric to identify potential memory leaks.
A possible goal is to make the heap large enough to make the GC interval longer than 10 seconds, but small enough so the duration is only 1 to 2 seconds.
CPU You must observe these system resources to ensure that we have enough system resources, for example, CPU, I/O, and paging, to handle the workload capacity.
I/O System paging

PMI
Custom PMI API
Enable PMI data collection
Develop your own monitoring applications
Monitor performance with Tivoli Performance Viewer
Third-party performance monitoring
Monitor performance with ITCAM for WAS

Metric	Meaning
Average response time	Include statistics for servlet and EJB response time.
Number of requests (transactions)	As transactions increase, response time increases.
Number of live HTTP sessions	Reflects concurrent usage. The more live sessions, the more memory is required. As number increases, consider increasing... session time-out values JVM heap
Web server thread pools	Interpret Web server, Web container, ORB, data source pools together. Setting too large impacts the amount of memory that is required and might cause too much work to flow downstream if downstream resources cannot handle a high influx of work. Setting too small might cause bottlenecks if the downstream resource is able handle an increase in workload.
Java virtual memory	Look for frequency of garbage collection. This data can assist in setting the optimal heap size. In addition, use the metric to identify potential memory leaks. A possible goal is to make the heap large enough to make the GC interval longer than 10 seconds, but small enough so the duration is only 1 to 2 seconds.
CPU	You must observe these system resources to ensure that we have enough system resources, for example, CPU, I/O, and paging, to handle the workload capacity.
I/O	System paging