<?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: Syslogging via tailing a logfile in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Syslogging-via-tailing-a-logfile/m-p/67497#M13591</link>
    <description>&lt;P&gt;That would involve installing the forwarder on every host we use. Our hosts are already set up to forward local syslogged events to be indexed by Splunk, and I am trying to leverage that mechanism.&lt;/P&gt;</description>
    <pubDate>Sat, 12 Jan 2013 01:19:16 GMT</pubDate>
    <dc:creator>NK_1</dc:creator>
    <dc:date>2013-01-12T01:19:16Z</dc:date>
    <item>
      <title>Syslogging via tailing a logfile</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Syslogging-via-tailing-a-logfile/m-p/67495#M13589</link>
      <description>&lt;P&gt;Ideally, we'd like to modify the application to syslog directly for indexing by Splunk.&lt;BR /&gt;
In the meantime, is there any adverse effect to tailing the last line of the log, and invoking logger to syslog?&lt;BR /&gt;
&lt;PRE&gt;&lt;CODE&gt;&lt;BR /&gt;
#!/bin/bash&lt;BR /&gt;
tail -n1 -F -q MyLogFile.log | \&lt;BR /&gt;
while read -r line ; do&lt;BR /&gt;
   # send to local syslog&lt;BR /&gt;
   logger -t MyAppTag -p local1.info `echo "$line"`&lt;BR /&gt;
done&lt;BR /&gt;
&lt;/CODE&gt;&lt;/PRE&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Sep 2012 20:55:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Syslogging-via-tailing-a-logfile/m-p/67495#M13589</guid>
      <dc:creator>NK_1</dc:creator>
      <dc:date>2012-09-21T20:55:59Z</dc:date>
    </item>
    <item>
      <title>Re: Syslogging via tailing a logfile</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Syslogging-via-tailing-a-logfile/m-p/67496#M13590</link>
      <description>&lt;P&gt;I'm curious, why not have splunkforwarder just monitor the logfile directly?&lt;/P&gt;</description>
      <pubDate>Sat, 12 Jan 2013 00:56:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Syslogging-via-tailing-a-logfile/m-p/67496#M13590</guid>
      <dc:creator>numentajpb</dc:creator>
      <dc:date>2013-01-12T00:56:17Z</dc:date>
    </item>
    <item>
      <title>Re: Syslogging via tailing a logfile</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Syslogging-via-tailing-a-logfile/m-p/67497#M13591</link>
      <description>&lt;P&gt;That would involve installing the forwarder on every host we use. Our hosts are already set up to forward local syslogged events to be indexed by Splunk, and I am trying to leverage that mechanism.&lt;/P&gt;</description>
      <pubDate>Sat, 12 Jan 2013 01:19:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Syslogging-via-tailing-a-logfile/m-p/67497#M13591</guid>
      <dc:creator>NK_1</dc:creator>
      <dc:date>2013-01-12T01:19:16Z</dc:date>
    </item>
    <item>
      <title>Re: Syslogging via tailing a logfile</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Syslogging-via-tailing-a-logfile/m-p/67498#M13592</link>
      <description>&lt;P&gt;We replace syslog with rsyslog, which can send arbitrary files to syslog.&lt;/P&gt;

&lt;P&gt;&lt;A href="http://www.rsyslog.com/doc/imfile.html"&gt;rsyslog imfile&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 13 Jan 2013 18:56:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Syslogging-via-tailing-a-logfile/m-p/67498#M13592</guid>
      <dc:creator>Linegod</dc:creator>
      <dc:date>2013-01-13T18:56:42Z</dc:date>
    </item>
  </channel>
</rss>

