<?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: Null filtering not working with props and transforms in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Null-filtering-not-working-with-props-and-transforms/m-p/575764#M101776</link>
    <description>&lt;P&gt;Typically, PaloAlto logs aren’t ingested as pan:traffic directly, but rather as pan:log (or older as pan_log)&lt;/P&gt;&lt;P&gt;this gets changed into pan:traffic (and pan:other-log-types) during the transforms step assuming you have the Pan-TA:&amp;nbsp;&lt;A href="https://github.com/PaloAltoNetworks/Splunk-Apps/blob/develop/Splunk_TA_paloalto/default/props.conf" target="_blank"&gt;https://github.com/PaloAltoNetworks/Splunk-Apps/blob/develop/Splunk_TA_paloalto/default/props.conf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;So you likely need [pan:log] or [pan_log] in your props instead of [pan:traffic] depending on what your inputs look like on your forwarders&lt;/P&gt;&lt;P&gt;Secondly you mention this is on your indexers. Are your PAN logs being ingested by Universal Forwarders or Heavy Forwarders? If they are Heavy Forwarders, or you are sending through &amp;nbsp;intermediate Heavy Forwarders, then parsing is already complete by the time you reach your indexers, and your props and transforms need to be on a different system (the first HF in the path from your syslog servers to your indexers)&lt;/P&gt;&lt;P&gt;Hope this helps&lt;/P&gt;</description>
    <pubDate>Sat, 20 Nov 2021 14:13:02 GMT</pubDate>
    <dc:creator>acharlieh</dc:creator>
    <dc:date>2021-11-20T14:13:02Z</dc:date>
    <item>
      <title>Null filtering not working with props and transforms</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Null-filtering-not-working-with-props-and-transforms/m-p/575757#M101775</link>
      <description>&lt;P&gt;I have the following conf file configs to drop any event that contains the verbiage, "Allow all zones to query DNS anycast address", in Palo logs:&lt;/P&gt;&lt;PRE&gt;props.conf
[pan:traffic]
TRANSFORMS-paloanycast = paloruledrop
 
transforms.conf
[paloruledrop]
REGEX = Allow all zones to query DNS anycast address
DEST_KEY = queue
FORMAT = nullQueue&lt;/PRE&gt;&lt;P&gt;Snippet of event&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;Nov 20 07:11:00 firewall,2021/11/20 07:10:59,010701010006,TRAFFIC,end,2305,2021/11/20 07:10:59,x.x.x.x,y.y.y.y,0.0.0.0,0.0.0.0,Allow all zones to query DNS anycast address,,,dns,vsys7,vrf,xxx-xx-x,xxx.xxx,xxx.xxx,data-data-data,2021/11/20...&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Applied the&amp;nbsp; changes to my cluster master and pushed to the indexers (verified the indexers got the config), but these&amp;nbsp;"Allow all zones to query DNS anycast address" events are not being dropped.&lt;/P&gt;&lt;P&gt;I verified the regex on&amp;nbsp;regex101.com&lt;/P&gt;&lt;P&gt;Any help would be appreciated&lt;/P&gt;&lt;P&gt;Thx&lt;/P&gt;</description>
      <pubDate>Sat, 20 Nov 2021 17:08:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Null-filtering-not-working-with-props-and-transforms/m-p/575757#M101775</guid>
      <dc:creator>jwalzerpitt</dc:creator>
      <dc:date>2021-11-20T17:08:48Z</dc:date>
    </item>
    <item>
      <title>Re: Null filtering not working with props and transforms</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Null-filtering-not-working-with-props-and-transforms/m-p/575764#M101776</link>
      <description>&lt;P&gt;Typically, PaloAlto logs aren’t ingested as pan:traffic directly, but rather as pan:log (or older as pan_log)&lt;/P&gt;&lt;P&gt;this gets changed into pan:traffic (and pan:other-log-types) during the transforms step assuming you have the Pan-TA:&amp;nbsp;&lt;A href="https://github.com/PaloAltoNetworks/Splunk-Apps/blob/develop/Splunk_TA_paloalto/default/props.conf" target="_blank"&gt;https://github.com/PaloAltoNetworks/Splunk-Apps/blob/develop/Splunk_TA_paloalto/default/props.conf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;So you likely need [pan:log] or [pan_log] in your props instead of [pan:traffic] depending on what your inputs look like on your forwarders&lt;/P&gt;&lt;P&gt;Secondly you mention this is on your indexers. Are your PAN logs being ingested by Universal Forwarders or Heavy Forwarders? If they are Heavy Forwarders, or you are sending through &amp;nbsp;intermediate Heavy Forwarders, then parsing is already complete by the time you reach your indexers, and your props and transforms need to be on a different system (the first HF in the path from your syslog servers to your indexers)&lt;/P&gt;&lt;P&gt;Hope this helps&lt;/P&gt;</description>
      <pubDate>Sat, 20 Nov 2021 14:13:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Null-filtering-not-working-with-props-and-transforms/m-p/575764#M101776</guid>
      <dc:creator>acharlieh</dc:creator>
      <dc:date>2021-11-20T14:13:02Z</dc:date>
    </item>
    <item>
      <title>Re: Null filtering not working with props and transforms</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Null-filtering-not-working-with-props-and-transforms/m-p/575770#M101777</link>
      <description>&lt;P&gt;Thx for the reply&lt;/P&gt;&lt;P&gt;I am using the Palo TA and ingesting the logs via HF with the sourcetype set to&amp;nbsp;&lt;SPAN&gt;pan:traffic&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 20 Nov 2021 17:07:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Null-filtering-not-working-with-props-and-transforms/m-p/575770#M101777</guid>
      <dc:creator>jwalzerpitt</dc:creator>
      <dc:date>2021-11-20T17:07:38Z</dc:date>
    </item>
  </channel>
</rss>

