This help page is for version 8.0. The latest available help is for version 8.3.
How to monitor Internet Information Services (IIS)
Listed below are some of the recommendations for monitoring the Internet Information Services (IIS) counters and services.
Monitoring services is very important in case of business critical applications and IIS is one of those critical services that should be monitored. An IIS failure can be the root cause for other applications failing and the cause of many hours looking in log files for the cause of the failures. Below are three important IIS services that should be monitored.
Services to Monitor
|Application Host Helper Service||AppHostSvc|
|Windows Process Activation Service*||WAS|
|World Wide Web Publishing Service||W3SVC|
* The Windows Process Activation Service also has some Event IDs that should be monitored as well. The Event Source for the following Event IDs is the Microsoft-Windows-WAS log file. The Event Log Monitor is ideal for this task.
- 5144 - (Error): WAS is not able to enable application pool.
- 5002 - (Error): Application pool is being automatically disabled.
- 5059 - (Error): WAS encountered a failure when it started a worker process to save the application pool. The application pool has been disabled.
- 5117 - (Warning): A worker process serving application pool has requested a recycle because it reached its private bytes memory limit.
- 5077 - (Warning): A worker process serving application pool has requested a recycle because it reached its virtual memory limit.
- 5009 - (Warning): A process serving application pool terminated unexpectedly.
Internet Information Services (IIS) has many counters that can be monitored on a running. Each of the following counters below are counters that are recommended to be monitored for the performance of your IIS process.
Performance Counters to Watch
|Memory\Pages/sec||0 - 20|
|Memory\Available Bytes||10% of physical memory|
|Memory\Committed Bytes||75% of physical memory|
|Memory\Pool||Nonpaged Bytes A steady value. (A slow rise might indicate a memory leak.)|
|Processor\% Processor Time||< 75%|
|Processor\System Processor Queue Length||< 2|
|LogicalDisk\% Disk Time||As low as possible|
|LogicalDisk\Avg. Disk Queue Length||< 2|
|LogicalDisk\Avg. Disk Bytes/Transfer||As high as possible|
|Web Service\Bytes Total/sec||As high as possible|
|Active Server Pages\Request Wait Time||As low as possible|
|Active Server Pages\Requests Queued||As low as possible|
|Active Server Pages\Transactions/sec||As high as possible**|
** ASP transactions degrade overall server performance because each transaction requires interaction with a database. If you are concerned about server performance, use ASP transactions sparingly.