Becauseusing the Administration Server takes computing resources, the command-line
interfaceand the Admin Console are the most costly monitoring methods.
Formore information on these monitoring methods, see the following sections:
■“AboutStatistics” on page 23
■“MonitoringCurrent Activity Using the Admin Console” on page 25
■“MonitoringCurrent Activity Using the CLI” on page 26
■“MonitoringCurrent Activity Using stats.xml” on page 29
■“MonitoringCurrent Activity Using perfdump” on page 31
■“MonitoringCurrent Activity Using the Java ES MonitoringC onsole” on page 37
About Statistics
Youcan monitor many performance statistics through the Admin Console user interface,
throughthe command-line interface, through the stats-xml URI, and through perfdump.For
allthese monitoring methods, the server uses statistics it collects. None of these monitoring
methodswill work if statistics are not collected.
Thestatistics give you information at the conguration level, the server instance level, or the
virtualserver level. The statistics are broken up into functional areas.
Forthe conguration, statistics are available in the following areas:
■Requests
■Errors
■ResponseTime
Forthe server instance, statistics are available in the following areas:
■Requests
■Errors
■ResponseTime
■General
■JavaVirtual Machine (JVMTM)
■ConnectionQueue
■KeepAlive
■DNS
■FileCache
■ThreadPools
■SessionReplication
■SessionThreads, including Proling data (available if proling is enabled)
MonitoringServer Performance
Chapter1 • Performance and Monitoring Overview 23