<?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: Where does HEC push come in from? in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Where-does-HEC-push-come-in-from/m-p/411060#M118599</link>
    <description>&lt;P&gt;Just the messenger here &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt; The docs say:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;* Specifies the host if an event doesn't have a host set.
 * "ip" sets the host to the IP address of the system sending the data.
 * "dns" sets the host to the reverse DNS entry for IP address of the system
   sending the data.
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;It is most likely true, because the default for &lt;CODE&gt;connection_host&lt;/CODE&gt; is empty and therefore you would get the hostname of the instance running the HEC input. &lt;BR /&gt;
I never used this setting nor had to &lt;EM&gt;play&lt;/EM&gt; with it, because we use dedicated HEC inputs and also only have one sender for each HEC input.&lt;/P&gt;

&lt;P&gt;cheers, MuS&lt;/P&gt;</description>
    <pubDate>Wed, 12 Jun 2019 20:23:45 GMT</pubDate>
    <dc:creator>MuS</dc:creator>
    <dc:date>2019-06-12T20:23:45Z</dc:date>
    <item>
      <title>Where does HEC push come in from?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Where-does-HEC-push-come-in-from/m-p/411047#M118586</link>
      <description>&lt;P&gt;A customer is asking:&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;&lt;EM&gt;"How can we tell where an HEC push is actually coming in from? or is that just not logged anywhere?"&lt;/EM&gt;&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 08 Jun 2019 21:54:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Where-does-HEC-push-come-in-from/m-p/411047#M118586</guid>
      <dc:creator>ddrillic</dc:creator>
      <dc:date>2019-06-08T21:54:01Z</dc:date>
    </item>
    <item>
      <title>Re: Where does HEC push come in from?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Where-does-HEC-push-come-in-from/m-p/411048#M118587</link>
      <description>&lt;P&gt;@ddrillic &lt;/P&gt;

&lt;P&gt;I think you want to understand the working of HEC. The easiest way to understand HEC is that consider it as rest-endpoint. &lt;BR /&gt;
Just like rest-endpoint, it is always in listening mode as and when someone tries to access it will respond. In case of HEC when someone sends an event, HEC receives as a request and get the parameters from it and stores those as an event in Splunk.&lt;/P&gt;

&lt;P&gt;I hope you understand what I'm trying to say.&lt;/P&gt;</description>
      <pubDate>Sun, 09 Jun 2019 05:08:04 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Where-does-HEC-push-come-in-from/m-p/411048#M118587</guid>
      <dc:creator>VatsalJagani</dc:creator>
      <dc:date>2019-06-09T05:08:04Z</dc:date>
    </item>
    <item>
      <title>Re: Where does HEC push come in from?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Where-does-HEC-push-come-in-from/m-p/411049#M118588</link>
      <description>&lt;P&gt;Fair enough, the question is whether any data about the sender is stored somewhere... &lt;/P&gt;</description>
      <pubDate>Sun, 09 Jun 2019 23:17:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Where-does-HEC-push-come-in-from/m-p/411049#M118588</guid>
      <dc:creator>ddrillic</dc:creator>
      <dc:date>2019-06-09T23:17:39Z</dc:date>
    </item>
    <item>
      <title>Re: Where does HEC push come in from?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Where-does-HEC-push-come-in-from/m-p/411050#M118589</link>
      <description>&lt;P&gt;Not sure about sendor as if two sendor is using same token then they are considered to be same in Splunk. But for debugging purpose you can use  &lt;CODE&gt;index="_introspection" sourcetype=http_event_collector_metrics&lt;/CODE&gt;.&lt;/P&gt;</description>
      <pubDate>Mon, 10 Jun 2019 06:59:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Where-does-HEC-push-come-in-from/m-p/411050#M118589</guid>
      <dc:creator>VatsalJagani</dc:creator>
      <dc:date>2019-06-10T06:59:44Z</dc:date>
    </item>
    <item>
      <title>Re: Where does HEC push come in from?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Where-does-HEC-push-come-in-from/m-p/411051#M118590</link>
      <description>&lt;P&gt;Great. &lt;CODE&gt;index="_internal" &amp;lt;HEC Key&amp;gt;&lt;/CODE&gt; was also useful ; -)&lt;/P&gt;</description>
      <pubDate>Mon, 10 Jun 2019 18:20:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Where-does-HEC-push-come-in-from/m-p/411051#M118590</guid>
      <dc:creator>ddrillic</dc:creator>
      <dc:date>2019-06-10T18:20:37Z</dc:date>
    </item>
    <item>
      <title>Re: Where does HEC push come in from?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Where-does-HEC-push-come-in-from/m-p/411052#M118591</link>
      <description>&lt;P&gt;Did you create multiple tokens and want to find out which token is sending in the logs or do you want to know from which host you are receiving logs from? &lt;/P&gt;</description>
      <pubDate>Mon, 10 Jun 2019 18:31:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Where-does-HEC-push-come-in-from/m-p/411052#M118591</guid>
      <dc:creator>Eldenhanjoel</dc:creator>
      <dc:date>2019-06-10T18:31:16Z</dc:date>
    </item>
    <item>
      <title>Re: Where does HEC push come in from?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Where-does-HEC-push-come-in-from/m-p/411053#M118592</link>
      <description>&lt;P&gt;The second -  from which host you are receiving logs from? &lt;/P&gt;</description>
      <pubDate>Mon, 10 Jun 2019 18:34:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Where-does-HEC-push-come-in-from/m-p/411053#M118592</guid>
      <dc:creator>ddrillic</dc:creator>
      <dc:date>2019-06-10T18:34:59Z</dc:date>
    </item>
    <item>
      <title>Re: Where does HEC push come in from?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Where-does-HEC-push-come-in-from/m-p/411054#M118593</link>
      <description>&lt;P&gt;| tstats count where index=* sourcetype=X by host&lt;BR /&gt;
 | sort 0 -count&lt;/P&gt;</description>
      <pubDate>Mon, 10 Jun 2019 18:44:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Where-does-HEC-push-come-in-from/m-p/411054#M118593</guid>
      <dc:creator>Eldenhanjoel</dc:creator>
      <dc:date>2019-06-10T18:44:39Z</dc:date>
    </item>
    <item>
      <title>Re: Where does HEC push come in from?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Where-does-HEC-push-come-in-from/m-p/411055#M118594</link>
      <description>&lt;P&gt;Hi ddrillic,&lt;/P&gt;

&lt;P&gt;I started to use a props.conf, transforms.conf setting to work around exactly this issue. It will add a meta data field containing the host that parsed the event therefore you will always know which Splunk instance parsed the events or where it came from.&lt;/P&gt;

&lt;P&gt;Here is my config:&lt;BR /&gt;
props.conf&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[default]
TRANSFORMS-000-add-relay-info-to-meta = add-relay-info-to-meta
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;transforms.conf&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[add-relay-info-to-meta]
FORMAT = splunk_hwf::&amp;lt;hostNameHere&amp;gt;
REGEX = .
WRITE_META = true
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;You can then search for &lt;CODE&gt;index=_internal splunk_hwf::*&lt;/CODE&gt; to see the Splunk instance that pared the events.&lt;BR /&gt;
The down side is that the hostname value needs to be hard coded, but I have an app that works around this as well &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/P&gt;

&lt;P&gt;Also be aware this will only work on non- &lt;CODE&gt;INDEXED_EXTRACTIONS&lt;/CODE&gt; events, if you use a default parsing pipeline setup.&lt;/P&gt;

&lt;P&gt;Hope this helps ...&lt;/P&gt;

&lt;P&gt;cheers, MuS&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;UPDATE&lt;/STRONG&gt;&lt;/P&gt;

&lt;P&gt;The correct answer would be changing the &lt;CODE&gt;connection_host&lt;/CODE&gt; in inputs.conf for the according &lt;CODE&gt;[http...]&lt;/CODE&gt; stanza&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;connection_host = [ip|dns|proxied_ip|none]
* Specifies the host if an event doesn't have a host set.
* "ip" sets the host to the IP address of the system sending the data.
* "dns" sets the host to the reverse DNS entry for IP address of the system
  sending the data.
* "proxied_ip" checks whether an X-Forwarded-For header was sent
  (presumably by a proxy server) and if so, sets the host to that value.
  Otherwise, the IP address of the system sending the data is used.
* "none" leaves the host as specified in the HTTP header.
* No default.
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Mon, 10 Jun 2019 21:08:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Where-does-HEC-push-come-in-from/m-p/411055#M118594</guid>
      <dc:creator>MuS</dc:creator>
      <dc:date>2019-06-10T21:08:21Z</dc:date>
    </item>
    <item>
      <title>Re: Where does HEC push come in from?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Where-does-HEC-push-come-in-from/m-p/411056#M118595</link>
      <description>&lt;P&gt;Update ping - I misunderstood the question, but this will give you a two in one answer/solution &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 10 Jun 2019 21:18:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Where-does-HEC-push-come-in-from/m-p/411056#M118595</guid>
      <dc:creator>MuS</dc:creator>
      <dc:date>2019-06-10T21:18:22Z</dc:date>
    </item>
    <item>
      <title>Re: Where does HEC push come in from?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Where-does-HEC-push-come-in-from/m-p/411057#M118596</link>
      <description>&lt;P&gt;Very interesting information as always @MuS.&lt;/P&gt;</description>
      <pubDate>Mon, 10 Jun 2019 23:54:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Where-does-HEC-push-come-in-from/m-p/411057#M118596</guid>
      <dc:creator>ddrillic</dc:creator>
      <dc:date>2019-06-10T23:54:54Z</dc:date>
    </item>
    <item>
      <title>Re: Where does HEC push come in from?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Where-does-HEC-push-come-in-from/m-p/411058#M118597</link>
      <description>&lt;P&gt;Hey right, thanks for sharing this information.&lt;/P&gt;</description>
      <pubDate>Tue, 11 Jun 2019 12:33:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Where-does-HEC-push-come-in-from/m-p/411058#M118597</guid>
      <dc:creator>VatsalJagani</dc:creator>
      <dc:date>2019-06-11T12:33:55Z</dc:date>
    </item>
    <item>
      <title>Re: Where does HEC push come in from?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Where-does-HEC-push-come-in-from/m-p/411059#M118598</link>
      <description>&lt;P&gt;@Mus, my buddy says -&lt;/P&gt;

&lt;P&gt;-- If the host isn't specified for data that is coming through HEC, then it takes the VIP/HF hostname…which is what we don't want. &lt;/P&gt;

&lt;P&gt;Is it right?&lt;/P&gt;</description>
      <pubDate>Wed, 12 Jun 2019 14:38:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Where-does-HEC-push-come-in-from/m-p/411059#M118598</guid>
      <dc:creator>ddrillic</dc:creator>
      <dc:date>2019-06-12T14:38:00Z</dc:date>
    </item>
    <item>
      <title>Re: Where does HEC push come in from?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Where-does-HEC-push-come-in-from/m-p/411060#M118599</link>
      <description>&lt;P&gt;Just the messenger here &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt; The docs say:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;* Specifies the host if an event doesn't have a host set.
 * "ip" sets the host to the IP address of the system sending the data.
 * "dns" sets the host to the reverse DNS entry for IP address of the system
   sending the data.
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;It is most likely true, because the default for &lt;CODE&gt;connection_host&lt;/CODE&gt; is empty and therefore you would get the hostname of the instance running the HEC input. &lt;BR /&gt;
I never used this setting nor had to &lt;EM&gt;play&lt;/EM&gt; with it, because we use dedicated HEC inputs and also only have one sender for each HEC input.&lt;/P&gt;

&lt;P&gt;cheers, MuS&lt;/P&gt;</description>
      <pubDate>Wed, 12 Jun 2019 20:23:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Where-does-HEC-push-come-in-from/m-p/411060#M118599</guid>
      <dc:creator>MuS</dc:creator>
      <dc:date>2019-06-12T20:23:45Z</dc:date>
    </item>
    <item>
      <title>Re: Where does HEC push come in from?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Where-does-HEC-push-come-in-from/m-p/411061#M118600</link>
      <description>&lt;P&gt;@MuS - we don't set the &lt;CODE&gt;connection_host&lt;/CODE&gt; parameter and the host field ends up to be one of the indexers, but let me check....&lt;/P&gt;</description>
      <pubDate>Wed, 12 Jun 2019 21:28:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Where-does-HEC-push-come-in-from/m-p/411061#M118600</guid>
      <dc:creator>ddrillic</dc:creator>
      <dc:date>2019-06-12T21:28:07Z</dc:date>
    </item>
  </channel>
</rss>

