Sun Microsystems Sun Java System Web Server 7.0, Manual

Page: 23 / 132

Because using the Administration Server takes computing resources, the command-line
interface and the Admin Console are the most costly monitoring methods.
For more information on these monitoring methods, see the following sections:
■
“About Statistics” on page 23
■
“Monitoring Current Activity Using the Admin Console” on page 25
■
“Monitoring Current Activity Using the CLI” on page 26
■
“Monitoring Current Activity Using stats.xml” on page 29
■
“Monitoring Current Activity Using perfdump” on page 31
■
“Monitoring Current Activity Using the Java ES Monitoring Console” on page 37
About Statistics
You can monitor many performance statistics through the Admin Console user interface,
through the command-line interface, through the
stats-xml
URI, and through
perfdump
. For
all these monitoring methods, the server uses statistics it collects. None of these monitoring
methods will work if statistics are not collected.
The statistics give you information at the configuration level, the server instance level, or the
virtual server level. The statistics are broken up into functional areas.
For the configuration, statistics are available in the following areas:
■
Requests
■
Errors
■
Response Time
For the server instance, statistics are available in the following areas:
■
Requests
■
Errors
■
Response Time
■
General
■
Java Virtual Machine (JVM
TM
)
■
Connection Queue
■
Keep Alive
■
DNS
■
File Cache
■
Thread Pools
■
Session Replication
■
Session Threads, including Profiling data (available if profiling is enabled)
Monitoring Server Performance
Chapter 1 • Performance and Monitoring Overview 23