Docs » Supported integrations in Splunk Observability Cloud » Configure application exporters and receivers for monitoring » Windows Performance Counters (deprecated)

Windows Performance Counters (deprecated) πŸ”—

Caution

This integration is deprecated and will reach End of Support in a future release. During this period only critical security and bug fixes are provided. When End of Support is reached, the monitor will be removed and no longer be supported, and you won’t be able to use it to send data to Splunk Observability Cloud.

To forward metrics from Windows Performance Counters to Splunk Observability Cloud use the Windows Performance Counters receiver instead.

The Splunk Distribution of the OpenTelemetry Collector uses the Smart Agent receiver with the telegraf/win_perf_counters monitor type to receive metrics from Windows performance counters.

This monitor is available on Windows.

Benefits πŸ”—

After you configure the integration, you can access these features:

Installation πŸ”—

Follow these steps to deploy this integration:

  1. Deploy the Splunk Distribution of OpenTelemetry Collector to your host:

  2. Configure the monitor, as described in the Configuration section.

  3. Restart the Splunk Distribution of OpenTelemetry Collector.

Configuration πŸ”—

To use this integration of a Smart Agent monitor with the Collector:

  1. Include the Smart Agent receiver in your configuration file.

  2. Add the monitor type to the Collector configuration, both in the receiver and pipelines sections.

Example πŸ”—

To activate this integration, add the following to your Collector configuration:

receivers:
  smartagent/telegraf/win_perf_counters:
    type: telegraf/win_perf_counters
    ... # Additional config

The following snippet shows a sample configuration with counters and settings:

receivers:
 - type: telegraf/win_perf_counters
   printValid: true
   objects:
    - objectName: "Processor"
      instances:
       - "*"
      counters:
       - "% Idle Time"
       - "% Interrupt Time"
       - "% Privileged Time"
       - "% User Time"
       - "% Processor Time"
      includeTotal: true
      measurement: "win_cpu"

Next, add the monitor to the service.pipelines.metrics.receivers section of your configuration file:

service:
  pipelines:
    metrics:
      receivers: [smartagent/telegraf/win_perf_counters]

Configuration settings πŸ”—

The following table shows the configuration options for the telegraf/win_perf_counters receiver:

Option

Required

Type

Description

objects

No

list of objects (see below)

Contains the configuration of the monitor.

counterRefreshInterval

No

int64

Frequency of expansion of the counter paths and counter refresh.

The default value is 5s)

useWildCardExpansion

No

bool

If set to true, instance indexes are included in instance

names, and wildcards are expanded and localized when applicable. The default value is false.

printValid

No

bool

Print the configurations that match available performance

counters. The default value is false.

pcrMetricNames

No

bool

If true, metric names are emitted in the

PerfCounterReporter format. The default value is false.

The nested objects configuration object has the following fields:

Option

Required

Type

Description

objectName

No

string

The name of a Windows performance counter object.

counters

No

list of strings

The name of the counters to collect from the performance counter

object.

instances

No

list of strings

The Windows performance counter instances to retrieve for the

performance counter object.

measurement

No

string

The name of the Telegraf measurement to be used as a metric

name.

warnOnMissing

No

bool

Log a warning if the performance counter object is missing. The

default value is false.

failOnMissing

No

bool

Throws an error if the performance counter object is missing.

The default value is false.

includeTotal

No

bool

Include the total instance when collecting performance counter

metrics. The default value is false.

Metrics πŸ”—

The Splunk Distribution of the OpenTelemetry Collector doesn’t filter metrics for this receiver.

Troubleshooting πŸ”—

If you are a Splunk Observability Cloud customer and are not able to see your data in Splunk Observability Cloud, you can get help in the following ways.

Available to Splunk Observability Cloud customers

Available to prospective customers and free trial users

  • Ask a question and get answers through community support at Splunk Answers .

  • Join the Splunk #observability user group Slack channel to communicate with customers, partners, and Splunk employees worldwide. To join, see Chat groups in the Get Started with Splunk Community manual.

This page was last updated on Oct 21, 2024.