<?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: Ingesting file data in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Ingesting-file-data/m-p/81646#M16841</link>
    <description>&lt;P&gt;Change the &lt;CODE&gt;CHECK_METHOD&lt;/CODE&gt; for the file in props.conf.  Any other than the default method will cause Splunk to index the entire file if it's changed. From the docs:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;CHECK_METHOD = [endpoint_md5|entire_md5|modtime]
* Set CHECK_METHOD endpoint_md5 to have Splunk checksum of the first and last 256 bytes of a
  file. When it finds matches, Splunk lists the file as already indexed and indexes only new
  data, or ignores it if there is no new data.
* Set CHECK_METHOD = entire_md5 to use the checksum of the entire file.
* Set CHECK_METHOD = modtime to check only the modification time of the file.
* Settings other than endpoint_md5 cause Splunk to index the entire file for each detected
  change.
* Defaults to endpoint_md5.
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;So, you should do something like:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[source::&amp;lt;yoursource&amp;gt;]
CHECK_METHOD = modtime
&lt;/CODE&gt;&lt;/PRE&gt;</description>
    <pubDate>Thu, 03 Oct 2013 19:03:48 GMT</pubDate>
    <dc:creator>Ayn</dc:creator>
    <dc:date>2013-10-03T19:03:48Z</dc:date>
    <item>
      <title>Ingesting file data</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Ingesting-file-data/m-p/81645#M16840</link>
      <description>&lt;P&gt;I have a Powershell script that is writing data about sessions for an application to a file every 5 minutes so the file timestamp is changing, but Splunk only pulls in changed or new sessions. I was hoping Splunk would pull in all the data every 5 minutes so that I could get a good point-in-time count of the number of sessions and what they looked like at that time. Does anyone know if I can force Splunk to ingest the entire file when it changes? Here is the code I use to write a powershell object to a Splunk friendly file in case anyone is interested. "Id" is where the line break should be.&lt;/P&gt;

&lt;P&gt;($obj | fl | Out-String).Trim() -replace "&lt;CODE&gt;n&lt;/CODE&gt;r&lt;CODE&gt;n","" -replace "&lt;/CODE&gt;r&lt;CODE&gt;n","," -replace " :","=" -replace " +"," " -replace "(?m)^Id","&lt;/CODE&gt;nId" | Set-Content $file&lt;/P&gt;</description>
      <pubDate>Thu, 03 Oct 2013 18:44:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Ingesting-file-data/m-p/81645#M16840</guid>
      <dc:creator>bcross64</dc:creator>
      <dc:date>2013-10-03T18:44:48Z</dc:date>
    </item>
    <item>
      <title>Re: Ingesting file data</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Ingesting-file-data/m-p/81646#M16841</link>
      <description>&lt;P&gt;Change the &lt;CODE&gt;CHECK_METHOD&lt;/CODE&gt; for the file in props.conf.  Any other than the default method will cause Splunk to index the entire file if it's changed. From the docs:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;CHECK_METHOD = [endpoint_md5|entire_md5|modtime]
* Set CHECK_METHOD endpoint_md5 to have Splunk checksum of the first and last 256 bytes of a
  file. When it finds matches, Splunk lists the file as already indexed and indexes only new
  data, or ignores it if there is no new data.
* Set CHECK_METHOD = entire_md5 to use the checksum of the entire file.
* Set CHECK_METHOD = modtime to check only the modification time of the file.
* Settings other than endpoint_md5 cause Splunk to index the entire file for each detected
  change.
* Defaults to endpoint_md5.
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;So, you should do something like:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[source::&amp;lt;yoursource&amp;gt;]
CHECK_METHOD = modtime
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Thu, 03 Oct 2013 19:03:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Ingesting-file-data/m-p/81646#M16841</guid>
      <dc:creator>Ayn</dc:creator>
      <dc:date>2013-10-03T19:03:48Z</dc:date>
    </item>
  </channel>
</rss>

