<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Details on disabled flag in inputs.conf? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Details-on-disabled-flag-in-inputs-conf/m-p/97164#M20259</link>
    <description>&lt;P&gt;Default is &lt;CODE&gt;false&lt;/CODE&gt;, 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 &lt;CODE&gt;disabled = false&lt;/CODE&gt; for an input that's supposed to be enabled (that I know of that is).&lt;/P&gt;</description>
    <pubDate>Thu, 12 Jul 2012 17:55:44 GMT</pubDate>
    <dc:creator>Ayn</dc:creator>
    <dc:date>2012-07-12T17:55:44Z</dc:date>
    <item>
      <title>Details on disabled flag in inputs.conf?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Details-on-disabled-flag-in-inputs-conf/m-p/97163#M20258</link>
      <description>&lt;P&gt;In many examples (on splunk.com, in training class slides, and elsewhere) I see a "disabled = false" setting in many inputs.conf &lt;CODE&gt;[monitor]&lt;/CODE&gt; stanzas.  However, the only documentation I see for this setting is on &lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/admin/inputsconf"&gt;http://docs.splunk.com/Documentation/Splunk/latest/admin/inputsconf&lt;/A&gt; 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?&lt;/P&gt;</description>
      <pubDate>Thu, 12 Jul 2012 16:42:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Details-on-disabled-flag-in-inputs-conf/m-p/97163#M20258</guid>
      <dc:creator>Jordan_Brough</dc:creator>
      <dc:date>2012-07-12T16:42:32Z</dc:date>
    </item>
    <item>
      <title>Re: Details on disabled flag in inputs.conf?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Details-on-disabled-flag-in-inputs-conf/m-p/97164#M20259</link>
      <description>&lt;P&gt;Default is &lt;CODE&gt;false&lt;/CODE&gt;, 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 &lt;CODE&gt;disabled = false&lt;/CODE&gt; for an input that's supposed to be enabled (that I know of that is).&lt;/P&gt;</description>
      <pubDate>Thu, 12 Jul 2012 17:55:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Details-on-disabled-flag-in-inputs-conf/m-p/97164#M20259</guid>
      <dc:creator>Ayn</dc:creator>
      <dc:date>2012-07-12T17:55:44Z</dc:date>
    </item>
  </channel>
</rss>

