<?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: Custom audit path with rlog.sh in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/Custom-audit-path-with-rlog-sh/m-p/470435#M16423</link>
    <description>&lt;P&gt;Thanks.&lt;/P&gt;

&lt;P&gt;It's working!&lt;/P&gt;</description>
    <pubDate>Fri, 06 Sep 2019 01:57:40 GMT</pubDate>
    <dc:creator>payal23</dc:creator>
    <dc:date>2019-09-06T01:57:40Z</dc:date>
    <item>
      <title>Custom audit path with rlog.sh</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Custom-audit-path-with-rlog-sh/m-p/470433#M16421</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I have audit data coming from a port (UDP) to Heavy Forwarder[via syslog] and have to apply rlog.sh on the same.&lt;/P&gt;

&lt;P&gt;Just to start, I tried to monitor a custom path rather than the /var/log/audit/audit.log and used rlog.sh script.&lt;/P&gt;

&lt;P&gt;Something like this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[monitor:///vf/home/splunk/Audit_new.log]
[script:///opt/splunk/splunkforwarder/etc/apps/Splunk_TA_nix/bin/rlog.sh]
sourcetype = auditd_nix
interval = 1
index = vf_os
disabled = 0
passAuth = splunk
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Instead of indexing vf/home/splunk/Audit_new.log, SPLUNK indexed /var/log/audit/auditd.log with index=vf_os and sourcetype=auditd_nix and source=/opt/splunk/splunkforwarder/etc/apps/Splunk_TA_nix/bin/rlog.sh&lt;/P&gt;

&lt;P&gt;I want to index the sample file i placed under custom path vf/home/splunk/Audit_new.log with rlog.sh implemented. &lt;/P&gt;

&lt;P&gt;Thanks,&lt;BR /&gt;
Payal&lt;/P&gt;</description>
      <pubDate>Wed, 30 Sep 2020 02:02:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Custom-audit-path-with-rlog-sh/m-p/470433#M16421</guid>
      <dc:creator>payal23</dc:creator>
      <dc:date>2020-09-30T02:02:35Z</dc:date>
    </item>
    <item>
      <title>Re: Custom audit path with rlog.sh</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Custom-audit-path-with-rlog-sh/m-p/470434#M16422</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;If you want to monitor &lt;CODE&gt;audit.log&lt;/CODE&gt; from different path then you need to modify &lt;CODE&gt;rlog.sh&lt;/CODE&gt; and it is not best practice to modify script shipped with Add-on because when you will upgrade the Splunk Add-on for Linux and Unix it will overwrite &lt;CODE&gt;rlog.sh&lt;/CODE&gt; &amp;amp; due to this your monitoring will break.&lt;/P&gt;

&lt;P&gt;If you still want to achieve this using custom rlog.sh then change below config in &lt;STRONG&gt;rlog.sh&lt;/STRONG&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;From
AUDIT_FILE=/var/log/audit/audit.log

To
AUDIT_FILE=/vf/home/splunk/Audit_new.log
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;And remove &lt;CODE&gt;[monitor:///vf/home/splunk/Audit_new.log]&lt;/CODE&gt; from inputs.conf&lt;/P&gt;</description>
      <pubDate>Wed, 04 Sep 2019 10:19:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Custom-audit-path-with-rlog-sh/m-p/470434#M16422</guid>
      <dc:creator>harsmarvania57</dc:creator>
      <dc:date>2019-09-04T10:19:05Z</dc:date>
    </item>
    <item>
      <title>Re: Custom audit path with rlog.sh</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Custom-audit-path-with-rlog-sh/m-p/470435#M16423</link>
      <description>&lt;P&gt;Thanks.&lt;/P&gt;

&lt;P&gt;It's working!&lt;/P&gt;</description>
      <pubDate>Fri, 06 Sep 2019 01:57:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Custom-audit-path-with-rlog-sh/m-p/470435#M16423</guid>
      <dc:creator>payal23</dc:creator>
      <dc:date>2019-09-06T01:57:40Z</dc:date>
    </item>
    <item>
      <title>Re: Custom audit path with rlog.sh</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Custom-audit-path-with-rlog-sh/m-p/470436#M16424</link>
      <description>&lt;P&gt;As a follow up:&lt;/P&gt;

&lt;P&gt;Could you add a second&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;AUDIT_FILE=&amp;lt;PATH&amp;gt;
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;To index a second custom audit file path along with the default?&lt;/P&gt;</description>
      <pubDate>Thu, 20 Feb 2020 15:49:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Custom-audit-path-with-rlog-sh/m-p/470436#M16424</guid>
      <dc:creator>tkw03</dc:creator>
      <dc:date>2020-02-20T15:49:37Z</dc:date>
    </item>
  </channel>
</rss>

