<?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 will followTail=1 work on a symlink that keeps changing in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-will-followTail-1-work-on-a-symlink-that-keeps-changing/m-p/86453#M17973</link>
    <description>&lt;P&gt;Thanks Simeon, that is exactly how we would expect the system to operate and it's great to have confirmation of that behavior.&lt;/P&gt;</description>
    <pubDate>Wed, 07 Mar 2012 20:11:27 GMT</pubDate>
    <dc:creator>beaumaris</dc:creator>
    <dc:date>2012-03-07T20:11:27Z</dc:date>
    <item>
      <title>How will followTail=1 work on a symlink that keeps changing</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-will-followTail-1-work-on-a-symlink-that-keeps-changing/m-p/86449#M17969</link>
      <description>&lt;P&gt;We are trying to monitor logs in a directory that are created by an application that does the following&lt;/P&gt;

&lt;OL&gt;
&lt;LI&gt;Creates a new filename that has a date/time stamp in the file name&lt;/LI&gt;
&lt;LI&gt;Points a symbol link (filename working.log) to the newly created file&lt;/LI&gt;
&lt;LI&gt;At regular intervals (a period of minutes) it repeats steps 1 and 2&lt;/LI&gt;
&lt;/OL&gt;

&lt;P&gt;In essence we have two options for monitoring here: we can monitor the directory, which detects the newly created files, waits for the end of file to not change and then uploads the file contents; or we can use followTail=1 on the working.log file and not worry about all the individually-named files.  For the second option, we're assuming that Splunk will be able to follow the "end" of the working.log file even as the symlink is changed from one physical file to the next.  If Splunk does correctly follow the end of the working.log file, then the expectation is that this will reduce the time it takes to upload the logged data since we won't have to wait for the "end of file" to be detected.&lt;/P&gt;

&lt;P&gt;Will Splunk work correctly on a symlink that is changes the target file every few minutes?&lt;/P&gt;</description>
      <pubDate>Wed, 07 Mar 2012 14:48:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-will-followTail-1-work-on-a-symlink-that-keeps-changing/m-p/86449#M17969</guid>
      <dc:creator>beaumaris</dc:creator>
      <dc:date>2012-03-07T14:48:21Z</dc:date>
    </item>
    <item>
      <title>Re: How will followTail=1 work on a symlink that keeps changing</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-will-followTail-1-work-on-a-symlink-that-keeps-changing/m-p/86450#M17970</link>
      <description>&lt;P&gt;What is the purpose of the symlink?   Splunk should automatically handle the new file unless all of the events are the same as the previous file.&lt;/P&gt;</description>
      <pubDate>Wed, 07 Mar 2012 16:52:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-will-followTail-1-work-on-a-symlink-that-keeps-changing/m-p/86450#M17970</guid>
      <dc:creator>Simeon</dc:creator>
      <dc:date>2012-03-07T16:52:42Z</dc:date>
    </item>
    <item>
      <title>Re: How will followTail=1 work on a symlink that keeps changing</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-will-followTail-1-work-on-a-symlink-that-keeps-changing/m-p/86451#M17971</link>
      <description>&lt;P&gt;The log files and the symlink are being managed by a 3rd party application, so it is unclear to us why they take this approach.  However, given that the symlink exists, the thinking is that if Splunk does follow the symlink as it gets set to different targets, then we can use followTail=1 on the working.log file and the events will be delivered sooner, since they will be detected as soon as they are written to disk rather than waiting for Splunk to determine that the file is no longer being written to which can take many seconds.&lt;/P&gt;</description>
      <pubDate>Wed, 07 Mar 2012 17:07:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-will-followTail-1-work-on-a-symlink-that-keeps-changing/m-p/86451#M17971</guid>
      <dc:creator>beaumaris</dc:creator>
      <dc:date>2012-03-07T17:07:08Z</dc:date>
    </item>
    <item>
      <title>Re: How will followTail=1 work on a symlink that keeps changing</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-will-followTail-1-work-on-a-symlink-that-keeps-changing/m-p/86452#M17972</link>
      <description>&lt;P&gt;Splunk should follow the symlink once the timestamp/modtime is updated.  So in your case, you can point Splunk at the file which the app is updating.  &lt;/P&gt;</description>
      <pubDate>Wed, 07 Mar 2012 19:24:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-will-followTail-1-work-on-a-symlink-that-keeps-changing/m-p/86452#M17972</guid>
      <dc:creator>Simeon</dc:creator>
      <dc:date>2012-03-07T19:24:19Z</dc:date>
    </item>
    <item>
      <title>Re: How will followTail=1 work on a symlink that keeps changing</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-will-followTail-1-work-on-a-symlink-that-keeps-changing/m-p/86453#M17973</link>
      <description>&lt;P&gt;Thanks Simeon, that is exactly how we would expect the system to operate and it's great to have confirmation of that behavior.&lt;/P&gt;</description>
      <pubDate>Wed, 07 Mar 2012 20:11:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-will-followTail-1-work-on-a-symlink-that-keeps-changing/m-p/86453#M17973</guid>
      <dc:creator>beaumaris</dc:creator>
      <dc:date>2012-03-07T20:11:27Z</dc:date>
    </item>
  </channel>
</rss>

