Agent CheckAgent Check
IIS Graph


Collect IIS metrics aggregated across all of your sites, or on a per-site basis. The IIS Agent check collects metrics for active connections, bytes sent and received, request count by HTTP method, and more. It also sends a service check for each site, letting you know whether it’s up or down.



The IIS check is packaged with the Agent, so simply install the Agent on your IIS servers.

Also, your IIS servers must have the Win32_PerfFormattedData_W3SVC_WebService WMI class installed. You can check for this using the following command:

Get-WmiObject -List -Namespace root\cimv2 | select -Property name | where name -like "*Win32_PerfFormattedData_W3SVC*"

This class should be installed as part of the web-http-common Windows Feature:

PS C:\Users\vagrant> Get-WindowsFeature web-* | where installstate -eq installed | ft -AutoSize

Display Name                       Name               Install State
------------                       ----               -------------
[X] Web Server (IIS)               Web-Server             Installed
    [X] Web Server                 Web-WebServer          Installed
        [X] Common HTTP Features   Web-Common-Http        Installed
            [X] Default Document   Web-Default-Doc        Installed
            [X] Directory Browsing Web-Dir-Browsing       Installed
            [X] HTTP Errors        Web-Http-Errors        Installed
            [X] Static Content     Web-Static-Content     Installed

You can add the missing features with install-windowsfeature web-common-http, this will require a restart of the system to work properly.


Prepare IIS

On your IIS servers, first resync the WMI counters.

On Windows <= 2003 (or equivalent), run the following in cmd.exe:

C:/> winmgmt /clearadap
C:/> winmgmt /resyncperf

On Windows >= 2008 (or equivalent), instead run:

C:/> winmgmt /resyncperf

Connect the Agent

Create a file iis.yaml in the Agent’s conf.d directory. See the sample iis.yaml for all available configuration options:


  - host: . # "." means the current host
  # sites:  # to monitor specific sites, or to collect metrics on a per-site basis
  #   - example.com
  #   - dev.example.com

To collect metrics on a per-site basis, you must use the sites option. The Agent collects metrics for each site you list and tags them with the site name — iis.net.num_connections tagged with site:example.com, and iis.net.num_connections tagged with site:dev.example.com.

If you don’t configure sites, the Agent collects all the same metrics, but their values reflect totals across all sites — iis.net.num_connections is the total number of connections on the IIS server; you will not have visibility into per-site metrics.

You can also monitor sites on remote IIS servers. See the sample iis.conf for relevant configuration options. By default, this check runs against a single instance - the current machine that the Agent is running on. It will check the WMI performance counters for IIS on that machine.

If you want to check other remote machines as well, you can add one instance per host. Note: If you also want to check the counters on the current machine, you will haveto create an instance with empty params.

The optional provider parameter allows to specify a WMI provider (default to 32 on Datadog Agent 32-bit or 64). It is used to request WMI data from the non-default provider. Available options are: 32 or 64. For more information, review this MSDN article.

The sites parameter allows you to specify a list of sites you want to read metrics from. With sites specified, metrics will be tagged with the site name. If you don’t define any sites, the check will pull the aggregate values across all sites.

Here’s an example of configuration that would check the current machine and a remote machine called MYREMOTESERVER. For the remote host we are only pulling metrics from the default site.

- host: .
    - myapp1
    - Default Web Site
  username: MYREMOTESERVER\fred
  password: mysecretpassword
  is_2008: false
  • is_2008 (Optional) - NOTE: because of a typo in IIS6/7 (typically on W2K8) where perfmon reports TotalBytesTransferred as TotalBytesTransfered, you may have to enable this to grab the IIS metrics in that environment.

Restart the Agent to begin sending IIS metrics to Datadog.


Run the Agent’s info subcommand and look for iis under the Checks section:


      - instance #0 [OK]
      - Collected 26 metrics, 0 events & 1 service check


Data Collected


The amount of time the IIS server has been running
shown as second
The number of bytes served per second
shown as byte
The number of bytes received per second
shown as byte
The total number of bytes transferred per second
shown as byte
The number of active connections
shown as connection
The number of files sent per second
shown as file
The number of files received per second
shown as file
The number of connection attempts per second
shown as connection
The number of GET requests per second
shown as request
The number of POST requests per second
shown as request
The number of HEAD requests per second
shown as request
The number of PUT requests per second
shown as request
The number of DELETE requests per second
shown as request
The number of OPTIONS requests per second
shown as request
The number of TRACE requests per second
shown as request
The number of not found errors per second (typically reported as an HTTP 404 response code)
shown as error
The number of locked errors per second (typically reported as an HTTP 423 response code)
shown as error
The number of requests from users over an anonymous connection per second
shown as request
The number of requests from users over a non-anonymous connection per second
shown as request
The number of Common Gateway Interface requests executed per second
shown as request
The number of ISAPI requests executed per second
shown as request


The IIS check does not include any event at this time.

Service Checks


The Agent submits this service check for each configured site in iis.yaml. It returns Critical if the site’s uptime is zero, otherwise OK.


Need help? Contact Datadog Support.

Further Reading

Learn more about infrastructure monitoring and all our integrations on our blog