Stackstate-WMI Integration


Get metrics from your Windows applications/servers with Windows Management Instrumentation (WMI) in real time to

  • Visualize their performance.
  • Correlate their activity with the rest of your applications.

For more details about configuring this integration refer to the following file(s) on GitHub:


If you are only collecting standard metrics from Microsoft Windows and other packaged applications, there are no installation steps. If you need to define new metrics to collect from your application, then you have a few options:

  1. Submit perfomance counters using System.Diagnostics in .NET, then access them via WMI.
  2. Implement a COM-based WMI provider for your application. You would typically only do this if you are using a non-.NET language.

To learn more about using System.Diagnostics, refer to the MSDN documentation here. After adding your metric you should be able to find it in WMI. To browse the WMI namespaces you may find this tool useful: WMI Explorer. You can find the same information with Powershell here.

If you assign the new metric a category of My_New_Metric, the WMI path will be \\<ComputerName>\ROOT\CIMV2:Win32_PerfFormattedData_My_New_Metric

If the metric isn’t showing up in WMI, try running winmgmt /resyncperf to force the computer to reregister the performance libraries with WMI.


  1. Open the Stackstate Agent Manager on the Windows server.
  2. Edit the Wmi Check configuration.

      - class: Win32_OperatingSystem
          - [NumberOfProcesses, system.proc.count, gauge]
          - [NumberOfUsers, system.users.count, gauge]
      - class: Win32_PerfFormattedData_PerfProc_Process
          - [ThreadCount, proc.threads.count, gauge]
          - [VirtualBytes, proc.mem.virtual, gauge]
          - [PercentProcessorTime, proc.cpu_pct, gauge]
        tag_by: Name
      - class: Win32_PerfFormattedData_PerfProc_Process
          - [IOReadBytesPerSec,, gauge]
        tag_by: Name
          - [IDProcess, Win32_Process, Handle, CommandLine]

    Note that the default configuration uses the filter clause to limit the metrics pulled. Either set the filters to valid values or remove them as shown above to collect the metrics.

    The metrics definitions include three components: class property in WMI, metric name as it appears in Stackstate, and the metric type.

  3. Restart the agent.

Configuration Options

Each WMI query has 2 required options, class and metrics and six optional options, host, namespace, filters, provider, tag_by, constant_tags and tag_queries.

class is the name of the WMI class, for example Win32_OperatingSystem or Win32_PerfFormattedData_PerfProc_Process. You can find many of the standard class names on the MSDN docs. The Win32_FormattedData_* classes provide many useful performance counters by default.

metrics is a list of metrics you want to capture, with each item in the list being a set of [WMI property name, metric name, metric type].

  • The property name is something like NumberOfUsers or ThreadCount. The standard properties are also available on the MSDN docs for each class.

  • The metric name is the name you want to show up in Stackstate.

  • The metric type is from the standard choices for all agent checks, such as gauge, rate, histogram or counter.

host is the optional target of the WMI query, localhost is assumed by default. If you set this option, make sure that Remote Management is enabled on the target host see here for more information.

namespace is the optionnal WMI namespace to connect to (default to cimv2).

filters is a list of filters on the WMI query you may want. For example, for a process-based WMI class you may want metrics for only certain processes running on your machine, so you could add a filter for each process name. You can also use the ‘%’ character as a wildcard.

provider is the optional WMI provider (default to 32 on Stackstate Agent 32-bit or 64). It is used to request WMI data from the non-default provider. Available options are: 32 or 64. See MSDN for more information.

tag_by optionally lets you tag each metric with a property from the WMI class you’re using. This is only useful when you will have multiple values for your WMI query. The examples below show how you can tag your process metrics with the process name (giving a tag of “name:app_name”).

constant_tags optionally lets you tag each metric with a set of fixed values.

tag_queries optionally lets you specify a list of queries, to tag metrics with a target class property. Each item in the list is a set of [link source property, target class, link target class property, target property] where:

  • ‘link source property’ contains the link value

  • ‘target class’ is the class to link to

  • ‘link target class property’ is the target class property to link to

  • ‘target property’ contains the value to tag with

It translates to a WMI query:

SELECT 'target property' FROM 'target class' WHERE 'link target class property' = 'link source property'

Note: setting this will cause any instance number to be removed from tag_by values i.e. name:process#1 => name:process

This feature is available starting with version 5.3 of the agent


To validate your installation and configuration, click the Agent Status menu from the Logs and Status button. The output should contain a section similar to the following: