<?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: Using props.conf and transforms.conf to exclude 'USERID' events in Palo Alto logs in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Using-props-conf-and-transforms-conf-to-exclude-USERID-events-in/m-p/518267#M87635</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/205842"&gt;@km1986&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;it's difficoult to see you regex: please use the "Insert/Edit Code Sample" button when you have code:&lt;/P&gt;&lt;P&gt;Anyway, the problem is that all the logs are filtered, is it correct?&lt;/P&gt;&lt;P&gt;you could try using a simpler regex&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;REGEX = USERID&lt;/LI-CODE&gt;&lt;P&gt;and&lt;/P&gt;&lt;P&gt;a more complete props and transforms:&lt;/P&gt;&lt;P&gt;pros.conf:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[pan:traffic]
TRANSFORMS-set= setparsing,setnull&lt;/LI-CODE&gt;&lt;P&gt;transforms.conf&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[setnull]
REGEX = USERID
DEST_KEY = queue
FORMAT = nullQueue

[setparsing]
REGEX = .
DEST_KEY = queue
FORMAT = indexQueue&lt;/LI-CODE&gt;&lt;P&gt;Then I see that the host override is missing of a command:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[paloalto-host]
REGEX = .
FORMAT = host::$1
DEST_KEY = MetaData:Host&lt;/LI-CODE&gt;&lt;P&gt;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;</description>
    <pubDate>Mon, 07 Sep 2020 15:22:12 GMT</pubDate>
    <dc:creator>gcusello</dc:creator>
    <dc:date>2020-09-07T15:22:12Z</dc:date>
    <item>
      <title>Using props.conf and transforms.conf to exclude 'USERID' events in Palo Alto logs</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Using-props-conf-and-transforms-conf-to-exclude-USERID-events-in/m-p/518253#M87632</link>
      <description>&lt;P&gt;Hello All, I'm trying to prevent the 'USERID' events from getting indexed by making the following changes on my Heavy Forwarder. However, after adding the TRANSFORMS-null statement and the [setnull] stanza in transforms.conf, I'm not seeing any logs getting indexed at all. Any guidance is appreciated&lt;/P&gt;&lt;P&gt;inputs.conf&lt;/P&gt;&lt;P&gt;[monitor:///var/log/palo]&lt;BR /&gt;disabled = false&lt;BR /&gt;sourcetype = pan:traffic&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;props.conf&lt;/P&gt;&lt;P&gt;[pan:traffic]&lt;BR /&gt;TRANSFORMS-null = setnull&lt;BR /&gt;TZ = America/New_York&lt;BR /&gt;TRANSFORMS-host = paloalto-host&lt;BR /&gt;DATETIME_CONFIG =&lt;BR /&gt;LINE_BREAKER = ([\r\n]+)&lt;BR /&gt;NO_BINARY_CHECK = true&lt;BR /&gt;SHOULD_LINEMERGE = true&lt;BR /&gt;disabled = false&lt;BR /&gt;pulldown_type = true&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;transforms.conf&lt;/P&gt;&lt;P&gt;[paloalto-host]&lt;BR /&gt;SOURCE_KEY = _raw&lt;BR /&gt;FORMAT = host::$1&lt;BR /&gt;DEST_KEY = MetaData:Host&lt;/P&gt;&lt;P&gt;[setnull]&lt;BR /&gt;REGEX = ^(?:[^,\n]*,){3}USERID&lt;BR /&gt;DEST_KEY = queue&lt;BR /&gt;FORMAT = nullQueue&lt;/P&gt;</description>
      <pubDate>Mon, 07 Sep 2020 14:29:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Using-props-conf-and-transforms-conf-to-exclude-USERID-events-in/m-p/518253#M87632</guid>
      <dc:creator>km1986</dc:creator>
      <dc:date>2020-09-07T14:29:22Z</dc:date>
    </item>
    <item>
      <title>Re: Using props.conf and transforms.conf to exclude 'USERID' events in Palo Alto logs</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Using-props-conf-and-transforms-conf-to-exclude-USERID-events-in/m-p/518258#M87633</link>
      <description>&lt;P&gt;HBi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/205842"&gt;@km1986&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;wher do you located the files?&lt;/P&gt;&lt;P&gt;thet must stay on the Indexers or (when present) on Heavy Forwarders.&lt;/P&gt;&lt;P&gt;Are you sure about the regex? if you share a sample of your logs&amp;nbsp; I could help you in this check..&amp;nbsp;&lt;/P&gt;&lt;P&gt;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;</description>
      <pubDate>Mon, 07 Sep 2020 14:43:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Using-props-conf-and-transforms-conf-to-exclude-USERID-events-in/m-p/518258#M87633</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2020-09-07T14:43:51Z</dc:date>
    </item>
    <item>
      <title>Re: Using props.conf and transforms.conf to exclude 'USERID' events in Palo Alto logs</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Using-props-conf-and-transforms-conf-to-exclude-USERID-events-in/m-p/518264#M87634</link>
      <description>&lt;P&gt;Hey&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/161352"&gt;@gcusello&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The files are located on the Heavy Forwarder (/var/log/palo). I have double-checked the regex, it seems to be fine. None of the logs are getting indexed at all, even the ones not of 'USERID' type, which is why I was thinking if something is wrong in the props/transforms?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Below is a sample:&lt;/P&gt;&lt;P&gt;Sep 7 03:29:28 ttt-tt-ttt-9 1,2020/09/07 03:29:28,000000000000000,USERID,end,2304,2020/09/07 03:29:18,172.17.132.5,172.17.130.68,0.0.0.0,0.0.0.0,tttttt-tttttttt,,,dns,vsys1,trust,trust,ethernet1/2,ethernet1/2,default,2020/09/07 03:29:18,386215,1,50473,53,0,0,0x64,udp,allow,260,102,158,2,202 0/09/07 03:28:47,0,any,0,10906416,0x8000000000000000,ttt-tt-ttttt-ttttt,ttt-tt-ttttt-ttttt,0,1,1,aged-out,324,327,0,0,,tttttttttttt,from-policy,,,0,,0,,N/A,0,0,0,0,tttttttt-tttt-tttt-tttt-tttttttttttt,0&lt;/P&gt;</description>
      <pubDate>Mon, 07 Sep 2020 15:01:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Using-props-conf-and-transforms-conf-to-exclude-USERID-events-in/m-p/518264#M87634</guid>
      <dc:creator>km1986</dc:creator>
      <dc:date>2020-09-07T15:01:16Z</dc:date>
    </item>
    <item>
      <title>Re: Using props.conf and transforms.conf to exclude 'USERID' events in Palo Alto logs</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Using-props-conf-and-transforms-conf-to-exclude-USERID-events-in/m-p/518267#M87635</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/205842"&gt;@km1986&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;it's difficoult to see you regex: please use the "Insert/Edit Code Sample" button when you have code:&lt;/P&gt;&lt;P&gt;Anyway, the problem is that all the logs are filtered, is it correct?&lt;/P&gt;&lt;P&gt;you could try using a simpler regex&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;REGEX = USERID&lt;/LI-CODE&gt;&lt;P&gt;and&lt;/P&gt;&lt;P&gt;a more complete props and transforms:&lt;/P&gt;&lt;P&gt;pros.conf:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[pan:traffic]
TRANSFORMS-set= setparsing,setnull&lt;/LI-CODE&gt;&lt;P&gt;transforms.conf&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[setnull]
REGEX = USERID
DEST_KEY = queue
FORMAT = nullQueue

[setparsing]
REGEX = .
DEST_KEY = queue
FORMAT = indexQueue&lt;/LI-CODE&gt;&lt;P&gt;Then I see that the host override is missing of a command:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[paloalto-host]
REGEX = .
FORMAT = host::$1
DEST_KEY = MetaData:Host&lt;/LI-CODE&gt;&lt;P&gt;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;</description>
      <pubDate>Mon, 07 Sep 2020 15:22:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Using-props-conf-and-transforms-conf-to-exclude-USERID-events-in/m-p/518267#M87635</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2020-09-07T15:22:12Z</dc:date>
    </item>
    <item>
      <title>Re: Using props.conf and transforms.conf to exclude 'USERID' events in Palo Alto logs</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Using-props-conf-and-transforms-conf-to-exclude-USERID-events-in/m-p/521328#M88095</link>
      <description>&lt;P&gt;Thanks&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/161352"&gt;@gcusello&lt;/a&gt;,&amp;nbsp;this worked. I think I had an issue with the splunk test instance which was not indexing logs properly since I was seeing issues with some other logs as well.&lt;/P&gt;&lt;P&gt;I spun up a fresh instance and tried it and it worked.&lt;/P&gt;</description>
      <pubDate>Thu, 24 Sep 2020 16:41:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Using-props-conf-and-transforms-conf-to-exclude-USERID-events-in/m-p/521328#M88095</guid>
      <dc:creator>km1986</dc:creator>
      <dc:date>2020-09-24T16:41:46Z</dc:date>
    </item>
    <item>
      <title>Re: Using props.conf and transforms.conf to exclude 'USERID' events in Palo Alto logs</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Using-props-conf-and-transforms-conf-to-exclude-USERID-events-in/m-p/521403#M88103</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/205842"&gt;@km1986&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;Good for you.&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>Fri, 25 Sep 2020 06:40:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Using-props-conf-and-transforms-conf-to-exclude-USERID-events-in/m-p/521403#M88103</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2020-09-25T06:40:51Z</dc:date>
    </item>
    <item>
      <title>Re: Using props.conf and transforms.conf to exclude 'USERID' events in Palo Alto logs</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Using-props-conf-and-transforms-conf-to-exclude-USERID-events-in/m-p/711779#M117556</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/161352"&gt;@gcusello&lt;/a&gt;&amp;nbsp;- Will this work if we give some more values to be considered for indexing in transforms.conf?&lt;/P&gt;&lt;P&gt;[setparsing]&lt;BR /&gt;REGEX = systemd | auditd | CROND&lt;BR /&gt;DEST_KEY = queue&lt;BR /&gt;FORMAT = indexQueue&lt;/P&gt;&lt;P&gt;[setnull]&lt;BR /&gt;REGEX = .&lt;BR /&gt;DEST_KEY = queue&lt;BR /&gt;FORMAT = nullQueue&lt;/P&gt;</description>
      <pubDate>Mon, 17 Feb 2025 06:06:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Using-props-conf-and-transforms-conf-to-exclude-USERID-events-in/m-p/711779#M117556</guid>
      <dc:creator>sureshkumaar</dc:creator>
      <dc:date>2025-02-17T06:06:46Z</dc:date>
    </item>
    <item>
      <title>Re: Using props.conf and transforms.conf to exclude 'USERID' events in Palo Alto logs</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Using-props-conf-and-transforms-conf-to-exclude-USERID-events-in/m-p/711793#M117557</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/206567"&gt;@sureshkumaar&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;it isn't a good idea to attach a new question to a closed question, even if on the same topic: it's always better to open a new one to have a surely faster and probably better answer to your question.&lt;/P&gt;&lt;P&gt;Anyway,&amp;nbsp;if the regex that you're using matches all the events to filter, it's correct and you can use it.&lt;/P&gt;&lt;P&gt;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;</description>
      <pubDate>Mon, 17 Feb 2025 08:21:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Using-props-conf-and-transforms-conf-to-exclude-USERID-events-in/m-p/711793#M117557</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2025-02-17T08:21:55Z</dc:date>
    </item>
  </channel>
</rss>

