Filter
Top Products
■
session-replication
■
thread
■
thread-pool
■
thread-pool-bucket (process-level)
■
virtual-server
■
web-app-bucket
▼
To View stats-xml Output from the CLI
In addition to a URI, you can also access stats-xml output through the command-line
interface. It is enabled by default. Unlike viewing stats-xml output through the URI, the
Administration Server must be running to view stats-xml output at the command-line.
However, if request processing threads are hanging in your server (for example, because they
are busy), and you cannot use the URI, you can still access stats-xml output through the CLI.
Toview the stats-xml output through the command-lineinterface,enter:
./wadm get-stats-xml --user=admin-user --password-file=admin-password-le
--config=cong-name --node=node-name
Monitoring Current Activity Using perfdump
perfdump is a Server Application Function (SAF) built into Web Server that collects various
pieces of performance data from the Web Server internal statistics and displays them in ASCII
text. The perfdump output does not display all the statistics available through the
command-line statistics or the Admin Console, but it can still be a useful tool. For example, you
can still use perfdump even if the Administration Server is not running. You can view the
perfdump output through the CLI, which is enabled by default, or you can view the perfdump
output through a URI, which you have to enable. If you enable the URI, you must control access
to the perfdump URI, otherwise it can be visible to users.
With perfdump, the statistics are unied. Rather than monitoring a single process, statistics are
multiplied by the number of processes, which gives you an accurate view of the server as a
whole.
For information on tuning the information displayed by perfdump, see
“Using Monitoring
Data to Tune Your Server” on page 48
.
▼
To Enable the perfdump URI from the Admin Console
You can enable perfdump URI for a virtual server through the Admin Console.
●
MonitoringServerPerformance
Chapter1 • Performanceand MonitoringOverview 31