This check monitors the state of any Windows Service and submits a service check to Datadog.
The Windows Service check is included in the Datadog Agent package, so you don’t need to install anything else on your Windows hosts.
windows_service.d/conf.yaml file in the
conf.d/ folder at the root of your Agent’s configuration directory. See the sample windows_service.d/conf.yaml for all available configuration options:
init_config: instances: ## @param services - list of strings - required ## List of services to monitor e.g. Dnscache, wmiApSrv, etc. ## ## If any service is set to `ALL`, all services registered with the SCM will be monitored. ## ## This matches all services starting with service, as if service.* is configured. ## For an exact match, use ^service$ # - services: - <SERVICE_NAME_1> - <SERVICE_NAME_2> ## @param tags - list of key:value element - optional ## List of tags to attach to every service check emitted by this integration. ## ## Learn more about tagging at https://docs.datadoghq.com/tagging # # tags: # - <KEY_1>:<VALUE_1> # - <KEY_2>:<VALUE_2>
Provide service names as they appear in services.msc’s properties field (e.g.
wmiApSrv), NOT the display name (e.g.
WMI Performance Adapter). For names with spaces: enclose the whole name in double quotation marks (e.g. “Bonjour Service”).
Note: spaces are replaced by underscores in Datadog.
Restart the Agent to start monitoring the services and sending service checks to Datadog.
Run the Agent’s
status subcommand and look for
windows_service under the Checks section.
The Windows Service check does not include any metrics.
The Windows Service check does not include any events.
The Agent submits this service check for each Windows service configured in
services, tagging the service check with ‘service:
Need help? Contact Datadog support.
Mistake in the docs? Feel free to contribute!