Organizations seeking to monitor the status (running/stopped) of Windows Services in Splunk Observability Cloud must transition from the deprecated Smart Agent to the Splunk Distribution of the OpenTelemetry Collector (OTEL Collector). This article explains the steps to enable Windows Services monitoring, clarifies agent/component requirements, and provides a sample configuration. Screenshots and code snippets are included for clarity.
Common symptoms:
Follow these steps to determine if your current environment is affected and to prepare for OTEL-based monitoring:
telegrafreceiver.Error: failed to start receiver "telegraf": invalid configuration for win_services input
Follow the steps below to configure Windows Services monitoring using the Splunk OTEL Collector (agent mode):
Download the latest Splunk Distribution of the OpenTelemetry Collector for Windows from:
Splunk OTEL Collector Releases
Follow installation steps as described in:
Get started with the Splunk Distribution of the OpenTelemetry Collector
agent_config.yaml or otelcol-config.yaml):receivers:
telegraf:
plugins:
- name: inputs.win_services
service_names:
- "wuauserv"
- "Spooler"
# Optionally specify state filters (e.g., running, stopped)
states:
- "running"
- "stopped"exporters:
signalfx:
access_token: "<YOUR_SPLUNK_ACCESS_TOKEN>"
realm: "<YOUR_REALM>"service:
pipelines:
metrics:
receivers: [telegraf]
exporters: [signalfx]
<YOUR_SPLUNK_ACCESS_TOKEN> and <YOUR_REALM> with appropriate values.service_names.net stop splunk-otel-collector
net start splunk-otel-collector
sc query splunk-otel-collector
C:\Program Files\Splunk\OpenTelemetry Collector\logs\otelcol.log
| Revision | Publish Date | Comments |
|---|---|---|
1.0 |
01-Oct-2026
|
Initial Release |