Splunk universal forwarder 'splunkd' process consuming high CPU intermittently

Available Languages

Updated:September 29, 2026
Document ID:SPLK046143

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 Enterprise Windows

Description

Splunk universal forwarder's 'splunkd' process consumes high CPU usage on the Windows server intermittently.
 


Investigation

Splunk Add-on for Windows consumes high CPU usage because the disabled modular inputs (disabled = 1) continue to run in the background and consume system resources. 
 

Resolution

Disabled modular inputs from the Splunk Add-on for Windows continue to execute at regular intervals which continue to consume system resources. The recommendation is set the polling interval to -1 to force the scripted inputs to run only once.

Here is the workaround solution:

1. Backup the existing $SPLUNK_HOME/etc/apps/Splunk_TA_windows/local/inputs.conf.


2. Set interval = -1  for those disabled inputs: 

[WinHostMon://Application]
disabled = 1
interval = -1

3. Restart the Splunk universal forwarder.
 

Revision History

Revision Publish Date Comments
1.0
29-Sep-2026
Initial Release

Was this Document Helpful?

FeedbackFeedback

Contact Cisco

This Document Applies to These Products