<?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: Inputs.conf Monitoring 1 file 1 event in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Inputs-conf-Monitoring-1-file-1-event/m-p/130825#M26886</link>
    <description>&lt;P&gt;Have you looked into the batch command as opposed to monitor?&lt;/P&gt;</description>
    <pubDate>Sun, 06 Jul 2014 02:07:08 GMT</pubDate>
    <dc:creator>Runals</dc:creator>
    <dc:date>2014-07-06T02:07:08Z</dc:date>
    <item>
      <title>Inputs.conf Monitoring 1 file 1 event</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Inputs-conf-Monitoring-1-file-1-event/m-p/130821#M26882</link>
      <description>&lt;P&gt;I am monitoring the logs for an application that spits out 3 xml files per day that I want indexed to 1 event per entire file.  Everything is setup and working properly when the files are initially indexed because the files are already complete. &lt;/P&gt;

&lt;P&gt;The problem is when the application is actually building the file.&lt;BR /&gt;
 1. The application is creates the file&lt;BR /&gt;
 2. Splunk indexes what is created&lt;BR /&gt;
 3. the application adds to the file&lt;BR /&gt;
 4. splunk indexes the addition to another event&lt;BR /&gt;
 5. application adds more to the file&lt;BR /&gt;
 6. splunk indexes changes to another event.&lt;BR /&gt;
 7. so on and so forth.&lt;/P&gt;

&lt;P&gt;Since Monitor doesn't use Interval to index new files every however many seconds or via cron job I kinda at a loss.  I have tried setting the time_before_close=120 but that still indexes the file at creation and then will index the file modifications of the next 2 min in another event.  I am wanting 1 event per file.  This isn't a high demand application so indexing the files once a day would be acceptable.&lt;/P&gt;

&lt;P&gt;Here is my inputs and props which are pretty simple.&lt;/P&gt;

&lt;P&gt;[monitor://whatever]&lt;BR /&gt;
disabled=false&lt;BR /&gt;
index=data&lt;BR /&gt;
whitelist=.xml&lt;BR /&gt;
blacklist=garbage&lt;BR /&gt;
sourcetype=info&lt;BR /&gt;
time_before_close=120&lt;/P&gt;

&lt;P&gt;[info]&lt;BR /&gt;
break_only_before=GOBBLEDEEGOOP&lt;BR /&gt;
max_events=200000&lt;BR /&gt;
time_prefix=start-time&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 16:59:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Inputs-conf-Monitoring-1-file-1-event/m-p/130821#M26882</guid>
      <dc:creator>jeffflynn</dc:creator>
      <dc:date>2020-09-28T16:59:37Z</dc:date>
    </item>
    <item>
      <title>Re: Inputs.conf Monitoring 1 file 1 event</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Inputs-conf-Monitoring-1-file-1-event/m-p/130822#M26883</link>
      <description>&lt;P&gt;First of all, props.conf settings are case sensitive so "break_only_before" needs to be BREAK_ONLY_BEFORE, and so on.&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 16:59:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Inputs-conf-Monitoring-1-file-1-event/m-p/130822#M26883</guid>
      <dc:creator>Ayn</dc:creator>
      <dc:date>2020-09-28T16:59:39Z</dc:date>
    </item>
    <item>
      <title>Re: Inputs.conf Monitoring 1 file 1 event</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Inputs-conf-Monitoring-1-file-1-event/m-p/130823#M26884</link>
      <description>&lt;P&gt;yea. that just lazy typing on my part.  i have everything in caps in my props file&lt;/P&gt;</description>
      <pubDate>Thu, 03 Jul 2014 19:20:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Inputs-conf-Monitoring-1-file-1-event/m-p/130823#M26884</guid>
      <dc:creator>jeffflynn</dc:creator>
      <dc:date>2014-07-03T19:20:30Z</dc:date>
    </item>
    <item>
      <title>Re: Inputs.conf Monitoring 1 file 1 event</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Inputs-conf-Monitoring-1-file-1-event/m-p/130824#M26885</link>
      <description>&lt;P&gt;You may write a small script to read the file and setup a scripted data input to read script's output. &lt;BR /&gt;
&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.1.1/Data/Setupcustominputs"&gt;http://docs.splunk.com/Documentation/Splunk/6.1.1/Data/Setupcustominputs&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 03 Jul 2014 19:20:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Inputs-conf-Monitoring-1-file-1-event/m-p/130824#M26885</guid>
      <dc:creator>somesoni2</dc:creator>
      <dc:date>2014-07-03T19:20:33Z</dc:date>
    </item>
    <item>
      <title>Re: Inputs.conf Monitoring 1 file 1 event</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Inputs-conf-Monitoring-1-file-1-event/m-p/130825#M26886</link>
      <description>&lt;P&gt;Have you looked into the batch command as opposed to monitor?&lt;/P&gt;</description>
      <pubDate>Sun, 06 Jul 2014 02:07:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Inputs-conf-Monitoring-1-file-1-event/m-p/130825#M26886</guid>
      <dc:creator>Runals</dc:creator>
      <dc:date>2014-07-06T02:07:08Z</dc:date>
    </item>
    <item>
      <title>Re: Inputs.conf Monitoring 1 file 1 event</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Inputs-conf-Monitoring-1-file-1-event/m-p/130826#M26887</link>
      <description>&lt;P&gt;I think my best chance at getting what I need is to run a script every morning that will copy the new files to a subfolder.  Then index the files from the subfolder using a batch command instead of monitor.  &lt;/P&gt;</description>
      <pubDate>Mon, 07 Jul 2014 15:15:43 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Inputs-conf-Monitoring-1-file-1-event/m-p/130826#M26887</guid>
      <dc:creator>jeffflynn</dc:creator>
      <dc:date>2014-07-07T15:15:43Z</dc:date>
    </item>
  </channel>
</rss>

