IIS Web Server Monitoring: Best Practices

If you’re running a Windows environment, chances are you’re using Microsoft IIS as your Web server to run your Web applications. Your IIS Web server is a critical component of your IT infrastructure. Services such as SharePoint, Outlook, and your Web presence are dependent on its availability. If it’s going to take a long time to access a Web application or website, you will likely end up leaving the site or raise a help desk ticket.

When you have different Web applications for different user groups, you should monitor the performance of the Web server because a Web server issue can cause application downtime which can impact business services. To address this issue, it’s a good idea to tune your Web servers from time to time. By doing so, you can make sure the effects are showing positive growth in application performance and availability.

Like any other Web server in the network, IIS is prone to performance issues. Monitoring IIS server is useful for improving server performance, identifying performance bottlenecks, increasing throughput, and identifying connectivity issues. To successfully achieve optimum server performance, you should consider the following best practices:

  • Application pools provide a convenient way to manage a set of websites, applications, and their parallel worker processes. You'll want to start by monitoring your app pool's memory usage. If you find that the app pool is utilizing high memory, recycle it for optimum performance.
  • Monitor the number of client connections to the worldwide web service. This will help you have a better understanding of the load on the server. As the number of client connections increases, you should consider load balancing across multiple Web servers.
  • Monitoring data downloaded or uploaded to the WWW service helps you have a better understanding of the data traffic on your server, which allows you to make informed decisions on bandwidth allocation.
  • If you detect that the IIS server is too busy when monitoring incoming sessions, start by increasing the connection count or if the server is too overloaded, load balance across multiple Web servers.
  • As with any application, you will need to monitor basic metrics, such as CPU usage, physical memory, virtual memory, I/O read/write and so on.

Watch this video and find out how you can improve the health of your IIS Web server.

  • IIS is a web server that lets you share information with users on the internet, intranet, or the extranet and so monitoring of its performance and response time is critical to its users. Applications Manager's IIS Monitor helps in proactively monitoring the IIS performance metrics.

    - India Access web hosting and development

  • Bookmarked this for future reference.

  • Great info, my biggest issue in Solarwinds pre 11.5 is the db structure being what it is and we poll for some mass tables - every now and again the connection to the db resets causing the web page to fail.

  • My personal experience, monitoring IIS app pool memory has been the most common performance issue by far. Understanding that App pools were designed to help ensure that in a multi-website hosted environment that one site crashing should not effect another site. The biggest issues of course being that if one of the app pools take up more then it share of memory. This can also be true when the server also performs multiple functions which is now common with virtual servers where we can allocate more and more resources.

    Monitoring the number of client connections is intriguing to me, I have done so through services link google analytical or piwik, which also gathers other statistical information. Would like to see how application monitoring will compare the counts to these tools.

Thwack - Symbolize TM, R, and C