Monitor Current Activity
Application Activity
The main screen of the Administrator displays a treeview on the left,
showing a parent for each registered WebApp and child nodes for
Sessions, Processes and the Event
Log. The right shows the application activity for the selected application.
Sessions
Sessions are mostly web services sessions of very short duration that
are activated as a call from a web application is made.
- Current Sessions
- The number of sessions currently
alive.
- Peak Sessions
- The highest number of concurrent
sessions since the WebApp was started.
- Total Sessions
- All sessions that have ever been since the WebApp was
started.
Processes
Processes are probably the most important metric from a system tuning
perspective.
- Current Processes
- The number of currently
active processes serving requests. Unless your application is
under load, this will be whatever your min pool is set to. If
the load starts to exceed what can be handled by your min pool,
new processes will be started (up to the max pool) and they will
stay around as long as the load requires them. Once the load drops,
those processes will stop and eventually go back down to the min
pool.
- Peak Processes
- Shows how high the load has ever forced the number of processes,
but will never exceed the max pool setting.
- Total Processes
- Shows the cumulative impact of the load as the process count
between min and max fluctuate.
Load
The server keeps track of the load by calculating the percentage of
time processes are in use over the last 30 seconds.
- Current Load
- The average of all running processes.
- Peak Load
- The highest load reached since the application was started.
Messages
- Client Messages
- The total number of client requests received.
- Server Messages
- The total number of server responses sent.
- Average Queue Time
- Average time sessions had to wait for an available process.
- Max Queue Time
- Maximum time a session had to wait for an available process.
- Average Queue Size
- Average number of requests that are waiting for an available
process when a request comes in.
- Max Queue Size
- Maximum number of requests that are waiting for an available
process when a request comes in.
Times
- Average Process Start Time
- The average time for processes to start. This includes the
min pool startup times and then the times any additional processes
(between min and max) that start based on load.
- Max Process Start Time
- The maximum time for a process to start.
- Average Response Time
- The average time for a completed request / response cycle.
- Max Response Time
- The maximum time for a completed request / response cycle.
- Time
- The total time the application has been running.
User
- Running as User
- The user account under which the application is running. The
default is the Windows System account.
In WebApps that use the Web Application Framework, most IIS sessions
happen in such a short time that they are rarely around long enough to
be seen. You will most likely see session information only for processes
like batch updates or reports.
Session ID
The ID of the session.
IP Address
The IP address of the client accessing the web application for this
session.
PID
The Windows Process ID of the WebApp process handling the request for
this session.
Client Messages
The number of requests and responses sent since the session was started.
Server Messages
The number of requests and responses sent since the session was started.
Time
This is how long the session has been running.
Slave Node
The IP address of the slave node handling this process (if Load
Balancing is in use).
Client Messages
The number of requests received by this process.
Server Messages
The number of responses sent by this process.
Time
How long the process has been running..
See Also
Using the Web
Application Administrator