Unable to ingest performance metrics from the Splunk Add-on for Microsoft Windows

Available Languages

Updated:September 29, 2026

Document ID:SPLK047349

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Applicability

Splunk Cloud Splunk Enterprise Splunk Apps & Add-ons Splunk Add-on for Microsoft Windows

Description

The Splunk Add-on for Microsoft Windows is having trouble ingesting Perfmon data, such as CPU, logical disk, memory, and physical disk metrics.

Investigation

Search below SPL in the Search and Reporting App.

index="_internal" "*splunk-perfmon*" sourcetype="splunkd"

ExecProcessor [12424 ExecProcessor] - message from ""C:\Program Files\SplunkUniversalForwarder\bin\splunk-perfmon.exe"" 
splunk-perfmon - PerfMonitor::init: Failed to configure Performance Monitor

The error occurs when the Windows Performance Monitor on the host machine is not working properly, preventing Splunk-perfmon from connecting to it via the splunk-perfmon.exe script.

Resolution

To resolve this issue, please follow these steps:

1. Open CMD as Administrator on Windows instance.
2. Type the command: lodctr /R
3. Wait for the output of the above command.
4. Restart the splunkd service.

The expected output of the lodctr /R command:

The lodctr /R command reloads the performance counter library files and refreshes the registry settings for performance counters, which can resolve issues with corrupted or missing performance counter data.

Note: Additionally, please verify if the Search Head is labeled as ITE/ITSI. If yes, then install SA-IndexCreation app on forwarder.

SA-IndexCreation contains the transforms for the PerfmonMetrics:* sourcetypes and is therefore needed on the system that does event parsing too (the HF in this case).
This sourcetype is used by the built-in Windows entity types and goes to a metric index.
SA-IndexCreation is required on HF to make PerfmonMetrics:* sourcetype work. Heavy forwarder is responsible for event parsing and without the SA-IndexCreation, the perfmonMetrics:* sourcetype will not function properly.