Monitor overall system health

WAS v8.5 > Monitoring
Monitor overall system health

Overall system health monitoring includes web servers, application servers, databases, LDAPs, back-end systems, and any other systems critical to running the site. WAS provides PMI data to provide statistics on WAS resources, application resources, and system metrics.

Metric Description
Average response time Include statistics, for example, servlet or enterprise beans response time. Response time statistics indicate how much time is spent in various parts of WAS and might quickly indicate where the problem is (for example, the servlet or the enterprise beans).
Number of requests (transactions) Enables you to look at how much traffic is processed by WAS, helping you to determine the capacity that we have to manage. As the number of transactions increase, the response time of your system might be increasing, showing the need for more system resources or the need to retune your system to handle increased traffic.
Number of live HTTP sessions The number of live HTTP sessions reflects the concurrent usage of your site. The more concurrent live sessions, the more memory is required. As the number of live sessions increase, you might adjust the session time-out values or the JVM heap available.
Web server thread pools Interpret web server thread pools, web container thread pools, ORB thread pools, and data source or connection pool size. These thread pools might constrain performance due to their size. The thread pools setting can be too small or too large, therefore causing performance problems. Setting the thread pools too large impacts the amount of memory needed on a system or might cause too much work to flow downstream if downstream resources cannot handle a high influx of work. Setting thread pools too small might also cause bottlenecks if the downstream resource can handle an increase in workload.
The web and EJB thread pools
Database and connection pool size
JVM JVM heap dynamics, including the frequency of garbage page. This data can assist in setting the optimal heap size. In addition, use the metric to identify potential memory leaks.
CPU System resources.
I/O
System paging

To monitor several of these statistics, WAS provides the PMI to obtain the data, and provides the Tivoli Performance Viewer in the dmgr console to view this data.
To monitor several of these statistics, WAS provides the PMI to obtain the data, and provides the Tivoli Performance Viewer and the optional IBM Tivoli Composite Application Manager for WAS in the dmgr console to view this data.

Enable PMI through the dmgr console to begin data collection.
Use Tivoli Performance Viewer or IBM Tivoli Optimizer
Use Tivoli Performance Viewer or ITCAM to monitor performance.
Extend monitoring capabilities by developing our own monitoring applications or extending PMI.

Subtopics

PMI
Custom PMI API
Enable PMI data page
Develop custom PMI monitoring applications
Monitoring performance with Tivoli Performance Viewer
Third-party performance monitoring and management solutions
Monitoring performance with ITCAM for WAS
SNMP based performance monitoring for WAS

+
Search Tips | Advanced Search

Metric	Description
Average response time	Include statistics, for example, servlet or enterprise beans response time. Response time statistics indicate how much time is spent in various parts of WAS and might quickly indicate where the problem is (for example, the servlet or the enterprise beans).
Number of requests (transactions)	Enables you to look at how much traffic is processed by WAS, helping you to determine the capacity that we have to manage. As the number of transactions increase, the response time of your system might be increasing, showing the need for more system resources or the need to retune your system to handle increased traffic.
Number of live HTTP sessions	The number of live HTTP sessions reflects the concurrent usage of your site. The more concurrent live sessions, the more memory is required. As the number of live sessions increase, you might adjust the session time-out values or the JVM heap available.
Web server thread pools	Interpret web server thread pools, web container thread pools, ORB thread pools, and data source or connection pool size. These thread pools might constrain performance due to their size. The thread pools setting can be too small or too large, therefore causing performance problems. Setting the thread pools too large impacts the amount of memory needed on a system or might cause too much work to flow downstream if downstream resources cannot handle a high influx of work. Setting thread pools too small might also cause bottlenecks if the downstream resource can handle an increase in workload.
The web and EJB thread pools
Database and connection pool size
JVM	JVM heap dynamics, including the frequency of garbage page. This data can assist in setting the optimal heap size. In addition, use the metric to identify potential memory leaks.
CPU	System resources.
I/O
System paging