<?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: Monitor File Size in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Monitor-File-Size/m-p/93441#M19432</link>
    <description>&lt;P&gt;Using a fschange input might be helpful here. By monitoring the file, and setting the option "sendEventMaxSize = N" then when the input checks the file, it will only send the contents of the file upto N bytes. If no content is sent, then you have progress. Not exactly what you are looking for, but without a perl/bash/python/etc script, I don't think it's possible. That is the other option, by the way. Write a scripted input to output the filesize of the file, and perform your search on that input.&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/5.0/Data/Monitorchangestoyourfilesystem" target="test_blank"&gt;http://docs.splunk.com/Documentation/Splunk/5.0/Data/Monitorchangestoyourfilesystem&lt;/A&gt;&lt;/CODE&gt;&lt;BR /&gt;
&lt;CODE&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/5.0/admin/inputsconf" target="test_blank"&gt;http://docs.splunk.com/Documentation/Splunk/5.0/admin/inputsconf&lt;/A&gt;&lt;/CODE&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 17 Oct 2012 16:42:46 GMT</pubDate>
    <dc:creator>alacercogitatus</dc:creator>
    <dc:date>2012-10-17T16:42:46Z</dc:date>
    <item>
      <title>Monitor File Size</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Monitor-File-Size/m-p/93440#M19431</link>
      <description>&lt;P&gt;My IDS system uses a file called snort.u2.xxxx.&lt;BR /&gt;
this file roles over every night during a service restart and starts at 0 size after the restart of the service.&lt;BR /&gt;
I have had a problem when the Snort service restarts that sometimes this file hangs.&lt;/P&gt;

&lt;P&gt;I want to be alerted if this file does not grow beyond a certain size in a given time.&lt;BR /&gt;
Then I want the alert to restart the Snortd service and monitor again for a given time and size.&lt;/P&gt;

&lt;P&gt;Anyone have any ideas how I can do this&lt;/P&gt;</description>
      <pubDate>Wed, 17 Oct 2012 16:20:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Monitor-File-Size/m-p/93440#M19431</guid>
      <dc:creator>hartfoml</dc:creator>
      <dc:date>2012-10-17T16:20:03Z</dc:date>
    </item>
    <item>
      <title>Re: Monitor File Size</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Monitor-File-Size/m-p/93441#M19432</link>
      <description>&lt;P&gt;Using a fschange input might be helpful here. By monitoring the file, and setting the option "sendEventMaxSize = N" then when the input checks the file, it will only send the contents of the file upto N bytes. If no content is sent, then you have progress. Not exactly what you are looking for, but without a perl/bash/python/etc script, I don't think it's possible. That is the other option, by the way. Write a scripted input to output the filesize of the file, and perform your search on that input.&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/5.0/Data/Monitorchangestoyourfilesystem" target="test_blank"&gt;http://docs.splunk.com/Documentation/Splunk/5.0/Data/Monitorchangestoyourfilesystem&lt;/A&gt;&lt;/CODE&gt;&lt;BR /&gt;
&lt;CODE&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/5.0/admin/inputsconf" target="test_blank"&gt;http://docs.splunk.com/Documentation/Splunk/5.0/admin/inputsconf&lt;/A&gt;&lt;/CODE&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 17 Oct 2012 16:42:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Monitor-File-Size/m-p/93441#M19432</guid>
      <dc:creator>alacercogitatus</dc:creator>
      <dc:date>2012-10-17T16:42:46Z</dc:date>
    </item>
  </channel>
</rss>

