--- title: "Microsoft IIS integration | Grafana Cloud documentation" description: "Learn about Microsoft IIS Grafana Cloud integration." --- > For a curated documentation index, see [llms.txt](/llms.txt). For the complete documentation index, see [llms-full.txt](/llms-full.txt). # Microsoft IIS integration for Grafana Cloud Microsoft IIS is a web server that can host and manage web apps on Windows servers. This integration for Grafana Cloud allows users to collect metrics and access logs for monitoring a Microsoft IIS instance. This integration supports Microsoft IIS 10.0 onwards. This integration includes 5 useful alerts and 3 pre-built dashboards to help monitor and visualize Microsoft IIS metrics and logs. ## Before you begin In order for the integration to properly work, you must configure Microsoft IIS with the following: Performance Counters need to be enabled 1. Start [Server Manager](https://storage.googleapis.com/grafanalabs-integration-assets/iis/screenshots/preinstructions-step-1.png) 2. Navigate to the [Local Server tab](https://storage.googleapis.com/grafanalabs-integration-assets/iis/screenshots/preinstructions-step-2.png) 3. Scroll down to the [Performance section](https://storage.googleapis.com/grafanalabs-integration-assets/iis/screenshots/preinstructions-step-3.png) 4. Right click the server and select `Start Performance Counters` You will also need to have a site running on your IIS instance to see some of the metrics. ## Install Microsoft IIS integration for Grafana Cloud 1. In your Grafana Cloud stack, click **Connections** in the left-hand menu. 2. Find **Microsoft IIS** and click its tile to open the integration. 3. Review the prerequisites in the **Configuration Details** tab and set up Grafana Alloy to send Microsoft IIS metrics and logs to your Grafana Cloud instance. 4. Click **Install** to add this integration’s pre-built dashboards and alerts to your Grafana Cloud instance, and you can start monitoring your Microsoft IIS setup. ## Configuration snippets for Grafana Alloy ### Simple mode These snippets are configured to scrape a single Microsoft IIS instance running locally with default ports. First, **manually** copy and append the following snippets into your alloy configuration file. ### Integrations snippets Alloy ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```alloy prometheus.exporter.windows "integrations_windows_exporter" { enabled_collectors = ["iis"] dfsr { sources_enabled = [""] } exchange { enabled_list = [""] } mssql { enabled_classes = [""] } } discovery.relabel "integrations_windows_exporter" { targets = prometheus.exporter.windows.integrations_windows_exporter.targets rule { target_label = "job" replacement = "integrations/iis" } rule { target_label = "instance" replacement = constants.hostname } } prometheus.scrape "integrations_windows_exporter" { targets = discovery.relabel.integrations_windows_exporter.output forward_to = [prometheus.remote_write.metrics_service.receiver] job_name = "integrations/windows_exporter" } ``` ### Advanced mode The following snippets provide examples to guide you through the configuration process. To instruct Grafana Alloy to scrape your Microsoft IIS instances, **manually** copy and append the snippets to your alloy configuration file, then follow subsequent instructions. ### Advanced integrations snippets Alloy ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```alloy prometheus.exporter.windows "integrations_windows_exporter" { enabled_collectors = ["iis"] dfsr { sources_enabled = [""] } exchange { enabled_list = [""] } mssql { enabled_classes = [""] } } discovery.relabel "integrations_windows_exporter" { targets = prometheus.exporter.windows.integrations_windows_exporter.targets rule { target_label = "job" replacement = "integrations/iis" } rule { target_label = "instance" replacement = constants.hostname } } prometheus.scrape "integrations_windows_exporter" { targets = discovery.relabel.integrations_windows_exporter.output forward_to = [prometheus.remote_write.metrics_service.receiver] job_name = "integrations/windows_exporter" } ``` This integrations uses the [prometheus.exporter.windows](/docs/alloy/latest/reference/components/prometheus.exporter.windows/) component to generate metrics from a Microsoft IIS instance. For the full array of configuration options, refer to the [prometheus.exporter.windows](/docs/alloy/latest/reference/components/prometheus.exporter.windows/) component reference documentation. This exporter must be linked with a [discovery.relabel](/docs/alloy/latest/reference/components/discovery.relabel/) component to apply the necessary relabelings. For each Microsoft IIS instance to be monitored you must create a pair of these components. Configure the following properties within each `discovery.relabel` component: - `instance` label: `constants.hostname` sets the `instance` label to your Grafana Alloy server hostname. If that is not suitable, change it to a value uniquely identifies this Microsoft IIS instance. Make sure this label value is the same for all telemetry data collected for this instance. You can then scrape them by including each `discovery.relabel` under `targets` within the [prometheus.scrape](/docs/alloy/latest/reference/components/prometheus.scrape/) component. ### Advanced logs snippets #### windows Alloy ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```alloy local.file_match "logs_integrations_integrations_iis" { path_targets = [{ __address__ = "localhost", __path__ = "/inetpub/logs/LogFiles/W3SVC/u_ex*.log", instance = constants.hostname, job = "integrations/iis", site = "", }] } loki.process "logs_integrations_integrations_iis" { forward_to = [loki.write.grafana_cloud_loki.receiver] stage.match { selector = "{job=\"integrations/iis\"} |~ \"^#\"" action = "drop" drop_counter_reason = "iis_comment_line" } } loki.source.file "logs_integrations_integrations_iis" { targets = local.file_match.logs_integrations_integrations_iis.targets forward_to = [loki.process.logs_integrations_integrations_iis.receiver] } ``` To monitor your Microsoft IIS instance logs, you will use a combination of the following components: - [local.file\_match](/docs/alloy/latest/reference/components/local.file_match) defines where to find the log file to be scraped. Change the following properties according to your environment: - `__address__`: The Microsoft IIS instance address - `__path__`: The path to the log file. - `instance` label: `constants.hostname` sets the `instance` label to your Grafana Alloy server hostname. If that is not suitable, change it to a value uniquely identifies this Microsoft IIS instance. Make sure this label value is the same for all telemetry data collected for this instance. - `site` label must be set to the website name that corresponds to the log path label `__path__`, which will contain a corresponding `siteID`. The `siteID` needs to bet set to a matching ID of the `site` label in the `__path__`. For example, a site name might be `Default Website` and its site ID might be `1`. This would result in `site: Default Website` and `__path__: /inetpub/logs/LogFiles/W3SVC1/u_ex*.log`. For each site, a new static config must be appended to the list under `static_configs` in order to filter logs by their site `labels`. - [loki.process](/docs/alloy/latest/reference/components/loki.process) defines how to process logs before sending it to Loki. - [loki.source.file](/docs/alloy/latest/reference/components/loki.source.file) sends logs to Loki. ## Dashboards The Microsoft IIS integration installs the following dashboards in your Grafana Cloud instance to help monitor your system. - Microsoft IIS applications - Microsoft IIS logs - Microsoft IIS overview **Microsoft IIS overview** **Microsoft IIS overview (Traffic)** **Microsoft IIS applications** ## Alerts The Microsoft IIS integration includes the following useful alerts: Expand table | Alert | Description | |-------------------------------------|-------------------------------------------------------------------------------------| | MicrosoftIISRejectedAsyncIORequests | Warning: There are a high number of rejected async I/O requests for a site. | | MicrosoftIIS5xxRequestErrors | Critical: There are a high number of 5xx request errors for an application. | | MicrosoftIISSuccessRateForWebsocket | Critical: There is a low success rate for websocket connections for an application. | | MicrosoftIISThreadpoolUtilization | Critical: The thread pool utilization is nearing max capacity. | | MicrosoftIISWorkerProcessFailures | Warning: There are a high number of worker process failures for an application. | ## Metrics The most important metrics provided by the Microsoft IIS integration, which are used on the pre-built dashboards and Prometheus alerts, are as follows: - up - windows\_iis\_blocked\_async\_io\_requests\_total - windows\_iis\_connection\_attempts\_all\_instances\_total - windows\_iis\_current\_application\_pool\_state - windows\_iis\_current\_connections - windows\_iis\_current\_worker\_processes - windows\_iis\_files\_received\_total - windows\_iis\_files\_sent\_total - windows\_iis\_locked\_errors\_total - windows\_iis\_not\_found\_errors\_total - windows\_iis\_received\_bytes\_total - windows\_iis\_rejected\_async\_io\_requests\_total - windows\_iis\_requests\_total - windows\_iis\_sent\_bytes\_total - windows\_iis\_server\_file\_cache\_hits\_total - windows\_iis\_server\_file\_cache\_queries\_total - windows\_iis\_server\_metadata\_cache\_hits\_total - windows\_iis\_server\_metadata\_cache\_queries\_total - windows\_iis\_server\_output\_cache\_hits\_total - windows\_iis\_server\_output\_cache\_queries\_total - windows\_iis\_server\_uri\_cache\_hits\_total - windows\_iis\_server\_uri\_cache\_queries\_total - windows\_iis\_total\_worker\_process\_failures - windows\_iis\_total\_worker\_process\_ping\_failures - windows\_iis\_total\_worker\_process\_shutdown\_failures - windows\_iis\_total\_worker\_process\_startup\_failures - windows\_iis\_worker\_file\_cache\_hits\_total - windows\_iis\_worker\_file\_cache\_queries\_total - windows\_iis\_worker\_max\_threads - windows\_iis\_worker\_metadata\_cache\_hits\_total - windows\_iis\_worker\_metadata\_cache\_queries\_total - windows\_iis\_worker\_output\_cache\_hits\_total - windows\_iis\_worker\_output\_queries\_total - windows\_iis\_worker\_request\_errors\_total - windows\_iis\_worker\_requests\_total - windows\_iis\_worker\_threads - windows\_iis\_worker\_uri\_cache\_hits\_total - windows\_iis\_worker\_uri\_cache\_queries\_total - windows\_iis\_worker\_websocket\_connection\_accepted\_total - windows\_iis\_worker\_websocket\_connection\_attempts\_total ## Changelog md ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```md # 1.1.0 - April 2026 * Updated dashboards to follow new stylistic standards # 1.0.0 - December 2025 * Chore: Fix incorrect semver to 1.0.0. No further changes # 0.0.3 - September 2023 * New Filter Metrics option for configuring the Grafana Agent, which saves on metrics cost by dropping any metric not used by this integration. Beware that anything custom built using metrics that are not on the snippet will stop working. * New hostname relabel option, which applies the instance name you write on the text box to the Grafana Agent configuration snippets, making it easier and less error prone to configure this mandatory label. # 0.0.2 - August 2023 * Add regex filter for logs datasource # 0.0.1 - April 2023 * Initial release ``` ## Cost By connecting your Microsoft IIS instance to Grafana Cloud, you might incur charges. To view information on the number of active series that your Grafana Cloud account uses for metrics included in each Cloud tier, see [Active series and dpm usage](/docs/grafana-cloud/fundamentals/active-series-and-dpm/) and [Cloud tier pricing](/products/cloud/pricing/).