<?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: Trying to drop events using inputs.conf in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-to-drop-events-using-inputs-conf/m-p/604858#M105164</link>
    <description>&lt;P&gt;Yes. You're missing one important thing. Blacklisting events on input works for windows event log input only. It doesn't even work for windows events pulled with WMI. And definitely does not work with file monitor input.&lt;/P&gt;&lt;P&gt;You have to filter your events in props/transforms on the first "heavy" component - HF or indexer - in event's path.&lt;/P&gt;</description>
    <pubDate>Thu, 07 Jul 2022 20:41:56 GMT</pubDate>
    <dc:creator>PickleRick</dc:creator>
    <dc:date>2022-07-07T20:41:56Z</dc:date>
    <item>
      <title>How to drop events using inputs.conf?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-drop-events-using-inputs-conf/m-p/604856#M105163</link>
      <description>&lt;P&gt;We have a Syslog server collecting data from Meraki Wireless devices.&amp;nbsp; There is a UF installed on the Syslog server sending data to Splunk.&amp;nbsp; I have been trying to use Blacklist to filter out the ICMP protocol events which we don't need and I have been unable to drop them.&amp;nbsp; The entry in my inputs.conf file for this are:&lt;/P&gt;
&lt;P&gt;[monitor:///syslog0/syslog/meraki/*/*.log]&lt;BR /&gt;disabled=0&lt;BR /&gt;host_segment = 4&lt;/P&gt;
&lt;P&gt;blacklist1 = protocol=icmp&lt;BR /&gt;blacklist2 = "(?192.\168.\30.\143.)"&lt;BR /&gt;blacklist3 = 10.\12.\239.\7&lt;BR /&gt;index = network&lt;BR /&gt;sourcetype = meraki&lt;/P&gt;
&lt;P&gt;I have tried a number of variations and have been unable to get the "protocol=icmp" to drop.&amp;nbsp; Is there something obvious that I am missing?&lt;/P&gt;
&lt;P&gt;Thanks in advance for any suggestions.&lt;/P&gt;</description>
      <pubDate>Thu, 07 Jul 2022 21:32:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-drop-events-using-inputs-conf/m-p/604856#M105163</guid>
      <dc:creator>leejones4</dc:creator>
      <dc:date>2022-07-07T21:32:32Z</dc:date>
    </item>
    <item>
      <title>Re: Trying to drop events using inputs.conf</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-drop-events-using-inputs-conf/m-p/604858#M105164</link>
      <description>&lt;P&gt;Yes. You're missing one important thing. Blacklisting events on input works for windows event log input only. It doesn't even work for windows events pulled with WMI. And definitely does not work with file monitor input.&lt;/P&gt;&lt;P&gt;You have to filter your events in props/transforms on the first "heavy" component - HF or indexer - in event's path.&lt;/P&gt;</description>
      <pubDate>Thu, 07 Jul 2022 20:41:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-drop-events-using-inputs-conf/m-p/604858#M105164</guid>
      <dc:creator>PickleRick</dc:creator>
      <dc:date>2022-07-07T20:41:56Z</dc:date>
    </item>
    <item>
      <title>Re: Trying to drop events using inputs.conf</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-drop-events-using-inputs-conf/m-p/604860#M105165</link>
      <description>&lt;P&gt;That was what I was wondering.&amp;nbsp; Thank you for pointing it out, now I can move on and try the props.conf and the transforms.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 07 Jul 2022 21:00:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-drop-events-using-inputs-conf/m-p/604860#M105165</guid>
      <dc:creator>leejones4</dc:creator>
      <dc:date>2022-07-07T21:00:13Z</dc:date>
    </item>
  </channel>
</rss>

