Monitoring overall system health
Monitoring overall system health is important to ensure that your system is performing well. Monitoring should include, web servers, application servers, databases, back-end systems, and any other systems critical to running your website.
Before you begin
About this task
Metric | Meaning |
---|---|
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 WebSphere Application Server 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 WebSphere Application Server, helping you to determine the capacity that you must 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 Java™ virtual machine (JVM) heap available. |
![]() ![]() |
![]() ![]() |
![]() ![]() |
|
Database and connection pool size | |
Java virtual memory (JVM) | Use JVM metrics to understand the JVM heap dynamics, including the frequency of garbage collection. This data can help setting the optimal heap size. In addition, use the metric to identify potential memory leaks. |
CPU | Observe these metrics to know whether you are at or near the maximum capacity of your system resources. |
I/O | |
System paging |
WebSphere Application Server
for z/OS® relies on WLM services to collect some
of the accounting and performance data.
Resource Measurement Facility (RMF™) and RMF-written System Management Facility (SMF) records
present performance and accounting information to the WebSphere Application Server. In addition, the WebSphere
Application Server for z/OS has SMF records that collect extra domain-specific information
Turn off the SMF records or RMF data by using the administrative console and the SMFPRMxx
parmlib member if you do not need the information. Use the SMFPRMxx parmlib member to control the
detail of the WebSphere Application Server for z/OS SMF records. If you need SMF information, review the SMF records to
ensure that you are collecting only the record types and details that you need.
Setting up your workload manager goals and filtering criteria is beyond the scope
of this topic. You can classify work into service classes based on user ID and server name. Classify
the control regions as reasonably high-performing system tasks
Procedure
- Enable PMI through the administrative console to begin data collection.
- Use Tivoli Performance Viewer or other performance monitoring and management solutions to monitor performance.
- Extend monitoring capabilities by developing your own monitoring applications or extending PMI.