Enable PMI data collection
Overview
Performance Monitoring Infrastructure (PMI) must be enabled before collecting any performance data.
By default PMI is enabled
If PMI is enabled after the server is started, the server needs to be restarted to start the PMI.
The monitoring of individual components can be enabled or disabled dynamically.
Statistic sets
PMI provides four predefined statistic sets..
Statistics Description None All statistics are disabled. Basic Statistics specified in J2EE 1.4, as well as top statistics like...
- CPU usage
- Live HTTP sessions
Enabled out-of-the-box.
Extended Basic set plus key statistics from various WAS components like...
- Work load Management
- Dynamic caching
All All statistics are enabled. Custom Enable or disable individual statistics.
Custom setting
WAS v6.0 introduces fine-grained control to enable/disable statistics individually. The fine-grained control is available under the custom statistic set.
Though the v5.x monitoring levels {N, L, M, H, X} are deprecated in v6.0 and above, the 5.x PMI APIs are supported for backward compatibility. It is possible to use a v6.0 or later API to set the monitoring level and a v5.0 API to get the monitoring level. A new level - F - fine-grained - is introduced to indicate to the v5.x API that the fine-grained or v6.x monitoring spec is in effect. This new level - F - will be returned if a v5.x API is used to get the monitoring level from a server using v6.x monitoring specification.
In WAS v4.0 and v5.0, the statistics were enabled based on a monitoring/instrumentation level. The levels are None, Low, Medium, High and Max {N, L, M, H, X}. Enabling at a given level will include all the statistics at the given level plus counters from levels below the given level. So if we enable the Web Application module at level Medium {M} it enables all the counters at level M, plus all the Low {L} level counters. See PMI data collection for more information.
Sequential Update
In order to minimize the monitoring overhead, the updates to...
- CountStatistic
- AverageStatistic
- TimeStatistic
...are not synchronized.
Since these statistic types track total and average, the extra accuracy is generally not worth the performance cost. The RangeStatistic and BoundedRangeStatistic are very sensitive; therefore, they are always are synchronized. If needed, updates to all the statistic types can be synchronized by checking the box...
Use sequential update
Enable PMI using one of the following methods:
Related
Enable PMI
Enable PMI using wsadmin
Obtaining a list of performance counters from the command line
Enable the Java virtual machine profiler data
Enterprise bean counters
JDBC connection pool counters
J2C connection pool counters
Java virtual machine counters
Object Request Broker counters
Servlet session counters
Transaction counters
Thread pool counters
Web app counters
Workload Management counters
System counters
Dynamic cache counters
Web services gateway counters
Web services counters
Alarm Manager counters
Object Pool counters
Scheduler counters
High availability manager counters
Distribution and consistency services (DCS) stack counters
Extension registry counters