<?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: how  to 'tail' the input that is being sent to indexer in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/how-to-tail-the-input-that-is-being-sent-to-indexer/m-p/54391#M96839</link>
    <description>&lt;P&gt;Your best bet would be to use a scripted input to run tail manually for the last 700 lines, something like tail blah -n 700 (double check the syntax). &lt;BR /&gt;
The only issue would be duplication if you don't have 700 new events in between readings.&lt;/P&gt;</description>
    <pubDate>Fri, 07 Sep 2012 14:57:13 GMT</pubDate>
    <dc:creator>Drainy</dc:creator>
    <dc:date>2012-09-07T14:57:13Z</dc:date>
    <item>
      <title>how  to 'tail' the input that is being sent to indexer</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/how-to-tail-the-input-that-is-being-sent-to-indexer/m-p/54390#M96838</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;

&lt;P&gt;Is it possible to tail the log files and send to indexer rather than sending one file as such.&lt;/P&gt;

&lt;P&gt;To make it clear - We have some log files of huge size for which we cannot do log rotation for some reason and the file has got entry from last year which I dont want to monitor through splunk.&lt;BR /&gt;
So is it possible to tail the last 600-700 lines of that file alone and send it to indexer -not the whole file?&lt;/P&gt;

&lt;P&gt;Every update to those 700 lines should be sent to indexer on regular basis&lt;/P&gt;

&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Fri, 07 Sep 2012 14:44:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/how-to-tail-the-input-that-is-being-sent-to-indexer/m-p/54390#M96838</guid>
      <dc:creator>splunker_123</dc:creator>
      <dc:date>2012-09-07T14:44:32Z</dc:date>
    </item>
    <item>
      <title>Re: how  to 'tail' the input that is being sent to indexer</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/how-to-tail-the-input-that-is-being-sent-to-indexer/m-p/54391#M96839</link>
      <description>&lt;P&gt;Your best bet would be to use a scripted input to run tail manually for the last 700 lines, something like tail blah -n 700 (double check the syntax). &lt;BR /&gt;
The only issue would be duplication if you don't have 700 new events in between readings.&lt;/P&gt;</description>
      <pubDate>Fri, 07 Sep 2012 14:57:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/how-to-tail-the-input-that-is-being-sent-to-indexer/m-p/54391#M96839</guid>
      <dc:creator>Drainy</dc:creator>
      <dc:date>2012-09-07T14:57:13Z</dc:date>
    </item>
    <item>
      <title>Re: how  to 'tail' the input that is being sent to indexer</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/how-to-tail-the-input-that-is-being-sent-to-indexer/m-p/54392#M96840</link>
      <description>&lt;P&gt;Syntax is correct :-)... or you could do &lt;CODE&gt;tail -n 700 blah&lt;/CODE&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 07 Sep 2012 15:07:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/how-to-tail-the-input-that-is-being-sent-to-indexer/m-p/54392#M96840</guid>
      <dc:creator>MHibbin</dc:creator>
      <dc:date>2012-09-07T15:07:10Z</dc:date>
    </item>
    <item>
      <title>Re: how  to 'tail' the input that is being sent to indexer</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/how-to-tail-the-input-that-is-being-sent-to-indexer/m-p/54393#M96841</link>
      <description>&lt;P&gt;You must have your reasons but I think it would be much easier to just index the whole file and then have Splunk follow the tail. You can always use time range picker or &lt;CODE&gt;earliest|latest&lt;/CODE&gt; in your search to filter out older results. Or you could "&lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/SearchReference/Delete"&gt;&lt;CODE&gt;delete&lt;/CODE&gt;&lt;/A&gt;" events older than your selected age.&lt;/P&gt;</description>
      <pubDate>Fri, 07 Sep 2012 15:14:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/how-to-tail-the-input-that-is-being-sent-to-indexer/m-p/54393#M96841</guid>
      <dc:creator>MHibbin</dc:creator>
      <dc:date>2012-09-07T15:14:25Z</dc:date>
    </item>
    <item>
      <title>Re: how  to 'tail' the input that is being sent to indexer</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/how-to-tail-the-input-that-is-being-sent-to-indexer/m-p/54394#M96842</link>
      <description>&lt;P&gt;The reason I ruled out option of indexing the whole file is due to license limitation.We are allowed to index till 10GB perday&lt;BR /&gt;
these files as a whole had grown up to 13GB now&lt;/P&gt;

&lt;P&gt;so if I index whole file then ,at least for the first time when the whole file is indexed it will cross 10 GB?(as per my understanding)&lt;/P&gt;</description>
      <pubDate>Fri, 07 Sep 2012 15:47:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/how-to-tail-the-input-that-is-being-sent-to-indexer/m-p/54394#M96842</guid>
      <dc:creator>splunker_123</dc:creator>
      <dc:date>2012-09-07T15:47:27Z</dc:date>
    </item>
    <item>
      <title>Re: how  to 'tail' the input that is being sent to indexer</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/how-to-tail-the-input-that-is-being-sent-to-indexer/m-p/54395#M96843</link>
      <description>&lt;P&gt;It will cross your limit and register a violation but on an Enterprise licence Splunk will allow you up to 5 violations in a 30 day rolling window. So as long as you then spend the next 30 days without a single violation you will have a clean licence again &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; Splunk uses this model as it allows for scenarios like this and for companys to do monthly dumps of batch files and the like.&lt;/P&gt;</description>
      <pubDate>Fri, 07 Sep 2012 15:49:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/how-to-tail-the-input-that-is-being-sent-to-indexer/m-p/54395#M96843</guid>
      <dc:creator>Drainy</dc:creator>
      <dc:date>2012-09-07T15:49:21Z</dc:date>
    </item>
    <item>
      <title>Re: how  to 'tail' the input that is being sent to indexer</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/how-to-tail-the-input-that-is-being-sent-to-indexer/m-p/54396#M96844</link>
      <description>&lt;P&gt;How about the ignoreOlderThan option? Or will this just work for the files itself and not the content of it?&lt;/P&gt;</description>
      <pubDate>Fri, 07 Sep 2012 16:35:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/how-to-tail-the-input-that-is-being-sent-to-indexer/m-p/54396#M96844</guid>
      <dc:creator>MuS</dc:creator>
      <dc:date>2012-09-07T16:35:09Z</dc:date>
    </item>
    <item>
      <title>Re: how  to 'tail' the input that is being sent to indexer</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/how-to-tail-the-input-that-is-being-sent-to-indexer/m-p/54397#M96845</link>
      <description>&lt;P&gt;That's just based on the modification time of the files. Monitor statements are all about the file, props are about the content &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 07 Sep 2012 18:45:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/how-to-tail-the-input-that-is-being-sent-to-indexer/m-p/54397#M96845</guid>
      <dc:creator>Drainy</dc:creator>
      <dc:date>2012-09-07T18:45:42Z</dc:date>
    </item>
  </channel>
</rss>

