<?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: How to drop data from a HEC Collector? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-to-drop-data-from-a-HEC-Collector/m-p/656949#M111247</link>
    <description>&lt;P&gt;In my case, yes. Check your props.conf, and try with [httpevent]&amp;nbsp; and see if that helps. I had to do a mixture of both to get it to work.&lt;/P&gt;</description>
    <pubDate>Thu, 07 Sep 2023 10:43:31 GMT</pubDate>
    <dc:creator>skirven</dc:creator>
    <dc:date>2023-09-07T10:43:31Z</dc:date>
    <item>
      <title>How to drop data from a HEC Collector?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-drop-data-from-a-HEC-Collector/m-p/596364#M104126</link>
      <description>&lt;P&gt;Hi,&amp;nbsp;&lt;BR /&gt;&amp;nbsp; &amp;nbsp;I'm trying to isolate why I'm not able to drop data from a HEC Collector endpoint. I have some docker logs I don't need to ingest. The Splunk HF is still on 7.3.8 for backwards compatibility, so I don't know if that's in play here. I checked with btool, and the files did load correctly.&lt;/P&gt;
&lt;P&gt;inputs.conf:&lt;BR /&gt;&amp;nbsp;- Sidenote here: When I set "source" value, it remained as "httpevent". But when I changed Sourcetype, the event changed correctly, which is odd.&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;[http://tpas_token]
disabled = 0
index = elm-tpas-spc
token = DD0D58D8-9F38-4A96-956C-XXXXXXXXXXXXXX
source = tpas-event
sourcetype = tpas-event&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;props.conf&lt;BR /&gt;&amp;nbsp;- Sidenote: I tried also [ tpas-event ], and that also did not work&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;[ source::tpas-event ]
TRANSFORMS-drop-handlers = drop-handlers&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;transforms.conf&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;[ drop-handlers ]
REGEX = handlers.py|connection.py
DEST_KEY = queue
FORMAT = nullQueue&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 04 May 2022 16:31:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-drop-data-from-a-HEC-Collector/m-p/596364#M104126</guid>
      <dc:creator>skirven</dc:creator>
      <dc:date>2022-05-04T16:31:35Z</dc:date>
    </item>
    <item>
      <title>Re: How to drop data from a HEC Collector?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-drop-data-from-a-HEC-Collector/m-p/656910#M111238</link>
      <description>&lt;P&gt;Hello , did you find a solution for this problem ?&lt;BR /&gt;I'm facing the same issue and the data coming from HEC is never dropped.&lt;/P&gt;</description>
      <pubDate>Thu, 07 Sep 2023 05:11:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-drop-data-from-a-HEC-Collector/m-p/656910#M111238</guid>
      <dc:creator>matthieup</dc:creator>
      <dc:date>2023-09-07T05:11:50Z</dc:date>
    </item>
    <item>
      <title>Re: How to drop data from a HEC Collector?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-drop-data-from-a-HEC-Collector/m-p/656948#M111246</link>
      <description>&lt;P&gt;The first question is - are your props/transforms on the same host as you're receiving data with your HEC input(s)? Or are you trying to receive HEC on HF and filter with props/transforms on indexers?&lt;/P&gt;</description>
      <pubDate>Thu, 07 Sep 2023 10:41:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-drop-data-from-a-HEC-Collector/m-p/656948#M111246</guid>
      <dc:creator>PickleRick</dc:creator>
      <dc:date>2023-09-07T10:41:53Z</dc:date>
    </item>
    <item>
      <title>Re: How to drop data from a HEC Collector?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-drop-data-from-a-HEC-Collector/m-p/656949#M111247</link>
      <description>&lt;P&gt;In my case, yes. Check your props.conf, and try with [httpevent]&amp;nbsp; and see if that helps. I had to do a mixture of both to get it to work.&lt;/P&gt;</description>
      <pubDate>Thu, 07 Sep 2023 10:43:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-drop-data-from-a-HEC-Collector/m-p/656949#M111247</guid>
      <dc:creator>skirven</dc:creator>
      <dc:date>2023-09-07T10:43:31Z</dc:date>
    </item>
    <item>
      <title>Re: How to drop data from a HEC Collector?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-drop-data-from-a-HEC-Collector/m-p/656951#M111249</link>
      <description>&lt;P&gt;I'm receiving the HEC directly on the search head and have the props/transforms setup on both the SH and the indexers.&lt;BR /&gt;The sourcetype is "jenkins_log" and the log I want to avoid has "DBCompilation" in the source field&lt;BR /&gt;&lt;BR /&gt;This is what I'm trying to achieve.&lt;BR /&gt;in props.conf:&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;[jenkins_log]
TRANSFORMS-override = ignore_jenkins_logs&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;BR /&gt;in transforms.conf&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[ignore_jenkins_logs]
SOURCE_KEY = fields:source
REGEX = DBCompilation
DEST_KEY = queue
FORMAT = nullQueue&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 07 Sep 2023 10:55:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-drop-data-from-a-HEC-Collector/m-p/656951#M111249</guid>
      <dc:creator>matthieup</dc:creator>
      <dc:date>2023-09-07T10:55:39Z</dc:date>
    </item>
    <item>
      <title>Re: How to drop data from a HEC Collector?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-drop-data-from-a-HEC-Collector/m-p/656954#M111250</link>
      <description>&lt;P&gt;Ugh. Using SH as an input collector is... kinda unusual. And not a very beautiful architecture.&lt;/P&gt;&lt;P&gt;Anyway, remember that your events are parsed and processed _only_ on the first "heavy" (based on the Splunk Enterprise install package; not UF) component in event's path (except ingest actions; those can happen on indexers even on parsed data). So if you're ingesting HEC on SH, you need those props/transforms on SH.&lt;/P&gt;&lt;P&gt;And in order to filter on the source field you need&lt;/P&gt;&lt;PRE&gt;MetaData:Source    &amp;nbsp;: The source associated with the event.
                      The value must be prefixed by "source::"&lt;/PRE&gt;</description>
      <pubDate>Thu, 07 Sep 2023 11:36:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-drop-data-from-a-HEC-Collector/m-p/656954#M111250</guid>
      <dc:creator>PickleRick</dc:creator>
      <dc:date>2023-09-07T11:36:00Z</dc:date>
    </item>
    <item>
      <title>Re: How to drop data from a HEC Collector?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-drop-data-from-a-HEC-Collector/m-p/656957#M111251</link>
      <description>&lt;P&gt;Noting your input on the SH being not the best option for the input collector of HEC.&lt;BR /&gt;&lt;BR /&gt;Anyway, your tip was the correct one and allowed to filter the data. You made my day, thanks !&lt;/P&gt;</description>
      <pubDate>Thu, 07 Sep 2023 11:56:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-drop-data-from-a-HEC-Collector/m-p/656957#M111251</guid>
      <dc:creator>matthieup</dc:creator>
      <dc:date>2023-09-07T11:56:20Z</dc:date>
    </item>
  </channel>
</rss>

