StackState Self-hosted v5.1.x
Collect telemetry information with Windows Management Instrumentation (WMI) from Windows applications and servers.
StackState Agent for Windows collects telemetry information from Windows by querying WMI. Metrics obtained from the defined WMI queries are collected periodically. Multiple WMI queries can be defined. Collected WMI metrics are sent to StackState and can be used as metric streams.
After installing StackState Agent V2 for Windows, the integration can be configured. The integration is included in StackState Agent V2 for Windows, no additional installation steps are required. The WMI integration has to be configured.
The WMI integration can be enabled and configured via the StackState Agent Manager. Opening the StackState Agent Manager can be done by, in PowerShell:
PS> & 'C:\Program Files\StackState\StackState Agent\embedded\agent.exe' launch-gui
The integration can be enabled via the StackState Agent Manager:
- 2.select in the drop-down
Add a check,
After the integration is enabled WMI queries can be defined in the integrations configuration yaml file, i.e.
wmi_check.d/conf.yaml. Multiple WMI queries can be configured. In the configuration file, an instance can be configured which represents a WMI query. An instance is defined by the following fields:
- # min_collection_interval: 120 # use in place of collection_interval for Agent V2.14.x or earlier
- [ActiveTransactions, sql.server.connections.active, gauge]
- Name: test_db
Restart StackState Agent V2 after making changes to the WMI integration's configuration.
Reference: the integration's configuration file is located at
Statuspage in the StackState Agent Manager provides insight into the operational status of the configurated WMI queries/instances.
It's possible to invoke the WMI integration to verify whether the configured WMI queries/instances telemetry is being retrieved and collected by StackState Agent V2 for Windows. To invoke, in PowerShell:
PS> & 'C:\Program Files\StackState\StackState Agent\embedded\agent.exe' check wmi_check
Refer to the log file for more information. The log file is located at