eG Help

The Windows Process Activation Service (WAS) manages application pool configuration and the creation and lifetime of worker processes for HTTP and other protocols. The World Wide Web Publishing Service (W3SVC) and other services depend on WAS.

This test monitors the Windows Process Activation Service and reports useful statistics revealing how well the service manages the worker processes and how healthy these worker processes are.

Measurement	Description	Measurement Unit	Interpretation
Active_Listener_Channels	Indicates the number of currently active listener channels in the worker process.	Number
Active_Protocol_Handlers	Indicates the number of currently active protocol handlers in the worker process.	Number
Health_Ping_Reply_Latenc	Indicates the average time taken by the worker process to reply to last health ping.	MSecs	You can monitor and improve application pool health by having the Windows Process Activation Service (WAS) ping an application pool's worker process at set intervals. A delayed response from the worker process or the lack of any response might mean that the worker process does not have a thread to respond to the ping request, or that it is hanging for some other reason. Based on the results of the ping request, WAS can flag a worker process as unhealthy and shut it down. By default, worker process pinging is enabled. You may have to adjust the ping interval and the ping response time to gain access to timely information about application pool health without triggering false unhealthy conditions, for example, instability caused by an application.
Total_Requests_Served	Indicates the total number of requests served by the worker process.	Number	This counter is only meaningful when request based recycling is enabled for the application pool.