Getting Data In

Details on disabled flag in inputs.conf?

Jordan_Brough
Path Finder

In many examples (on splunk.com, in training class slides, and elsewhere) I see a "disabled = false" setting in many inputs.conf [monitor] stanzas. However, the only documentation I see for this setting is on http://docs.splunk.com/Documentation/Splunk/latest/admin/inputsconf and it doesn't list what the default is, for example. Are there other docs with more details on the setting, what the default is, and why it is included in many example stanzas but not all? In particular, do I need to be adding this setting to all my [monitor] stanzas?

Tags (2)
1 Solution

Ayn
Legend

Default is false, meaning inputs will by default be enabled unless anything else is specified. I include it out of habit, and because it provides a simple way for people doing changes to see where they can change if they want to disable an input. But, other than for brevity, there's no real reason to include disabled = false for an input that's supposed to be enabled (that I know of that is).

View solution in original post

Ayn
Legend

Default is false, meaning inputs will by default be enabled unless anything else is specified. I include it out of habit, and because it provides a simple way for people doing changes to see where they can change if they want to disable an input. But, other than for brevity, there's no real reason to include disabled = false for an input that's supposed to be enabled (that I know of that is).

Get Updates on the Splunk Community!

Application management with Targeted Application Install for Victoria Experience

  Experience a new era of flexibility in managing your Splunk Cloud Platform apps! With Targeted Application ...

Index This | What goes up and never comes down?

January 2026 Edition  Hayyy Splunk Education Enthusiasts and the Eternally Curious!   We’re back with this ...

Splunkers, Pack Your Bags: Why Cisco Live EMEA is Your Next Big Destination

The Power of Two: Splunk + Cisco at "Ludicrous Scale"   You know Splunk. You know Cisco. But have you seen ...