<?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 Blacklist audit.log from inputs.conf in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Blacklist-audit-log-from-inputs-conf/m-p/697103#M115644</link>
    <description>&lt;P&gt;I want to block the&amp;nbsp;audit.log file from a particular instance sending logs to splunk, is the stanza sufficient to accomplish that?&lt;/P&gt;&lt;P&gt;Per matching a file:&lt;/P&gt;&lt;PRE&gt;blacklist = &amp;lt;regular expression&amp;gt;
* If set, files from this input are NOT monitored if their path matches the
  specified regex.
* Takes precedence over the deprecated '_blacklist' setting, which functions
  the same way.
* If a file matches the regexes in both the deny list and allow list settings,
  the file is NOT monitored. Deny lists take precedence over allow lists.
* No default.&lt;/PRE&gt;&lt;LI-CODE lang="css"&gt;[monitor:///logs/incoming/file.com/all-messages.log]
sourcetype = something
index = something_platform
disabled = 0
blacklist = audit.log&lt;/LI-CODE&gt;</description>
    <pubDate>Thu, 22 Aug 2024 21:34:37 GMT</pubDate>
    <dc:creator>rickymckenzie10</dc:creator>
    <dc:date>2024-08-22T21:34:37Z</dc:date>
    <item>
      <title>Blacklist audit.log from inputs.conf</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Blacklist-audit-log-from-inputs-conf/m-p/697103#M115644</link>
      <description>&lt;P&gt;I want to block the&amp;nbsp;audit.log file from a particular instance sending logs to splunk, is the stanza sufficient to accomplish that?&lt;/P&gt;&lt;P&gt;Per matching a file:&lt;/P&gt;&lt;PRE&gt;blacklist = &amp;lt;regular expression&amp;gt;
* If set, files from this input are NOT monitored if their path matches the
  specified regex.
* Takes precedence over the deprecated '_blacklist' setting, which functions
  the same way.
* If a file matches the regexes in both the deny list and allow list settings,
  the file is NOT monitored. Deny lists take precedence over allow lists.
* No default.&lt;/PRE&gt;&lt;LI-CODE lang="css"&gt;[monitor:///logs/incoming/file.com/all-messages.log]
sourcetype = something
index = something_platform
disabled = 0
blacklist = audit.log&lt;/LI-CODE&gt;</description>
      <pubDate>Thu, 22 Aug 2024 21:34:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Blacklist-audit-log-from-inputs-conf/m-p/697103#M115644</guid>
      <dc:creator>rickymckenzie10</dc:creator>
      <dc:date>2024-08-22T21:34:37Z</dc:date>
    </item>
    <item>
      <title>Re: Blacklist audit.log from inputs.conf</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Blacklist-audit-log-from-inputs-conf/m-p/697114#M115647</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/265393"&gt;@rickymckenzie10&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;yes it's possible to filter audit logs from some servers but your approach isn't correct:&lt;/P&gt;&lt;P&gt;the blacklist option is to not index files not some events from a file.&lt;/P&gt;&lt;P&gt;If you don't want only events read from the same file, the only solution is filter logs on Indexers before indexing (&amp;nbsp;&lt;A href="https://docs.splunk.com/Documentation/SplunkCloud/9.2.2403/Forwarding/Routeandfilterdatad#Filter_event_data_and_send_to_queues" target="_blank"&gt;https://docs.splunk.com/Documentation/SplunkCloud/9.2.2403/Forwarding/Routeandfilterdatad#Filter_event_data_and_send_to_queues&lt;/A&gt;&amp;nbsp;).&lt;/P&gt;&lt;P&gt;In other words, filtering isn't possible on Forwarders.&lt;/P&gt;&lt;P&gt;The only logs that's possible to filter on Forwarders are WinEventLogs but it isn't your case.&lt;/P&gt;&lt;P&gt;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;</description>
      <pubDate>Fri, 23 Aug 2024 06:50:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Blacklist-audit-log-from-inputs-conf/m-p/697114#M115647</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2024-08-23T06:50:51Z</dc:date>
    </item>
    <item>
      <title>Re: Blacklist audit.log from inputs.conf</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Blacklist-audit-log-from-inputs-conf/m-p/705860#M116740</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/265393"&gt;@rickymckenzie10&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;good for you, see next time!&lt;/P&gt;&lt;P&gt;Ciao and happy splunking&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;&lt;P&gt;P.S.: Karma Points are appreciated &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 03 Dec 2024 16:31:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Blacklist-audit-log-from-inputs-conf/m-p/705860#M116740</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2024-12-03T16:31:37Z</dc:date>
    </item>
    <item>
      <title>Re: Blacklist audit.log from inputs.conf</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Blacklist-audit-log-from-inputs-conf/m-p/705862#M116742</link>
      <description>&lt;P&gt;Sure:&amp;nbsp;&lt;A href="https://community.splunk.com/t5/Getting-Data-In/Rolling-upgrade-vs-Maintenance-mode-commands-on-cluster-manager/td-p/705861" target="_blank"&gt;https://community.splunk.com/t5/Getting-Data-In/Rolling-upgrade-vs-Maintenance-mode-commands-on-cluster-manager/td-p/705861&lt;/A&gt;&amp;nbsp;&lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 03 Dec 2024 16:40:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Blacklist-audit-log-from-inputs-conf/m-p/705862#M116742</guid>
      <dc:creator>rickymckenzie10</dc:creator>
      <dc:date>2024-12-03T16:40:28Z</dc:date>
    </item>
  </channel>
</rss>

