In Part 2 of this series, we learned how to access IIS metrics and logs using Windows tools. In this post, we’ll show you a more comprehensive approach to IIS monitoring, one that brings together out-of-the-box dashboards, automated alerts, and log analytics, all in a single platform.
In this post, we’ll show you how to use built-in IIS monitoring tools to access and graph performance counters, configure logging in IIS, and query your logs with Microsoft’s Log Parser Studio. We’ll also explain how to use a diagnostic tool to investigate memory leaks and high CPU utilization in your application pools and worker processes.
Microsoft’s Internet Information Services (IIS) is a web server that has traditionally come bundled with Windows (e.g., versions 5.0, 6.0, and beyond). IIS has numerous extensibility features. Swappable interfaces like ISAPI and FastCGI make it possible to use IIS with a variety of backend technologies, from micro-frameworks like Flask to runtimes like Node.js, along with technologies you’d expect to find within a Windows-based production environment (e.g., ASP.NET).
July brought you new releases for our monitoring core and web frameworks: Icinga 2.9 and Icinga Web 2.6. Both major versions add more awesome features to your monitoring stack. Icinga 2.9.1 was already pushed fixing a problem with non-Systemd platforms, Icinga Web 2.6.1 is coming later this week fixing a regression.
Yes, you heard it right. They both happened on the same day. I had no idea about WebGazer a few months ago, and now I am a part of it! It all started when a friend of mine texted me that he wanted some help. I said okay, but honestly, I did not think that it would become my new job.