<?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: Force splunk to poll files more quickly? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Force-splunk-to-poll-files-more-quickly/m-p/40761#M7563</link>
    <description>&lt;P&gt;The only time I've seen this an issue with data taking too long to get there was with previous versions and trying to monitor a directory with too many files/subdirectories.  Is your monitor stanza set overly broad then trying to whitelist down?&lt;/P&gt;</description>
    <pubDate>Mon, 11 Jul 2011 16:15:25 GMT</pubDate>
    <dc:creator>mikelanghorst</dc:creator>
    <dc:date>2011-07-11T16:15:25Z</dc:date>
    <item>
      <title>Force splunk to poll files more quickly?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Force-splunk-to-poll-files-more-quickly/m-p/40759#M7561</link>
      <description>&lt;P&gt;For testing purposes, I would really really like to force splunk to poll files in a monitor:// directory structure (and index changes) more quickly - at least temporarily. Is there some way I can force splunk to do this, overriding the default check-backoff behavior?&lt;/P&gt;</description>
      <pubDate>Mon, 11 Jul 2011 15:43:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Force-splunk-to-poll-files-more-quickly/m-p/40759#M7561</guid>
      <dc:creator>sconover</dc:creator>
      <dc:date>2011-07-11T15:43:47Z</dc:date>
    </item>
    <item>
      <title>Re: Force splunk to poll files more quickly?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Force-splunk-to-poll-files-more-quickly/m-p/40760#M7562</link>
      <description>&lt;P&gt;There isn't a user configurable monitor interval setting which can be used to gain this kind of control over monitor stanzas. Generally speaking, I haven't seen the need for this though, as I see files indexed with almost no delay at all between when the files are updated and when the updates come into Splunk. &lt;/P&gt;</description>
      <pubDate>Mon, 11 Jul 2011 16:12:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Force-splunk-to-poll-files-more-quickly/m-p/40760#M7562</guid>
      <dc:creator>jbsplunk</dc:creator>
      <dc:date>2011-07-11T16:12:31Z</dc:date>
    </item>
    <item>
      <title>Re: Force splunk to poll files more quickly?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Force-splunk-to-poll-files-more-quickly/m-p/40761#M7563</link>
      <description>&lt;P&gt;The only time I've seen this an issue with data taking too long to get there was with previous versions and trying to monitor a directory with too many files/subdirectories.  Is your monitor stanza set overly broad then trying to whitelist down?&lt;/P&gt;</description>
      <pubDate>Mon, 11 Jul 2011 16:15:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Force-splunk-to-poll-files-more-quickly/m-p/40761#M7563</guid>
      <dc:creator>mikelanghorst</dc:creator>
      <dc:date>2011-07-11T16:15:25Z</dc:date>
    </item>
    <item>
      <title>Re: Force splunk to poll files more quickly?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Force-splunk-to-poll-files-more-quickly/m-p/40762#M7564</link>
      <description>&lt;PRE&gt;&lt;CODE&gt;"Generally speaking, I haven't seen the need for this though, as I see files indexed with almost no delay at all between when the files are updated and when the updates come into Splunk."
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;My experiments show that there's anywhere from a zero to 15 second delay in indexing, which seems to match up well with the answer to this post:&lt;/P&gt;

&lt;P&gt;&lt;A href="http://splunk-base.splunk.com/answers/6693/how-to-force-splunk-to-index-new-files-quickly"&gt;http://splunk-base.splunk.com/answers/6693/how-to-force-splunk-to-index-new-files-quickly&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;I've since found a solution for what I want to happen - use oneshot:&lt;/P&gt;

&lt;P&gt;&lt;A href="http://splunk-base.splunk.com/answers/684/after-fixing-propsconf-how-to-re-index-the-same-files-using-the-new-settings"&gt;http://splunk-base.splunk.com/answers/684/after-fixing-propsconf-how-to-re-index-the-same-files-using-the-new-settings&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;which converts indexing from async to blocking - more appropriate for my usage scenario.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Jul 2011 20:54:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Force-splunk-to-poll-files-more-quickly/m-p/40762#M7564</guid>
      <dc:creator>sconover</dc:creator>
      <dc:date>2011-07-11T20:54:44Z</dc:date>
    </item>
  </channel>
</rss>

