<?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: HTTP event collector: Channel identifiers, what do they identify in Splunk Enterprise</title>
    <link>https://community.splunk.com/t5/Splunk-Enterprise/HTTP-event-collector-Channel-identifiers-what-do-they-identify/m-p/533944#M7361</link>
    <description>&lt;P&gt;Can we use one channel identifier for multiple clients through Splunk HEC to enable indexer acknowledgement&lt;/P&gt;</description>
    <pubDate>Wed, 23 Dec 2020 12:23:27 GMT</pubDate>
    <dc:creator>Durgapk</dc:creator>
    <dc:date>2020-12-23T12:23:27Z</dc:date>
    <item>
      <title>HTTP event collector: Channel identifiers, what do they identify</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/HTTP-event-collector-Channel-identifiers-what-do-they-identify/m-p/360197#M7356</link>
      <description>&lt;P&gt;Quote from &lt;A href="http://dev.splunk.com/view/event-collector/SP-CAAAE8X#aboutchannels"&gt;event collector docs&lt;/A&gt;:&lt;/P&gt;

&lt;BLOCKQUOTE&gt;
&lt;P&gt;Channels are designed so that you assign a unique channel to each client that sends data to HEC. Each channel has a channel identifier (ID), which must be a GUID but can be randomly generated. You assign channel IDs simply by including them in requests as shown in the examples above. When the Splunk server sees a new channel identifier, it creates a new channel.&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;

&lt;P&gt;What does this mean, exactly? If I have four different pieces of software, e.g. a Linux client program and a Windows client program, each of which log to Splunk, how many channel identifiers should I generate? The word “client” is quite ambiguous here...&lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;One per client software, Linux and Windows?&lt;/LI&gt;
&lt;LI&gt;One per released version of the softwares?&lt;/LI&gt;
&lt;LI&gt;One per actual client running the software?&lt;/LI&gt;
&lt;/UL&gt;

&lt;P&gt;Does the channel parameter actually impact indexing or queries in any way? I don't understand why it's required at all.&lt;/P&gt;</description>
      <pubDate>Wed, 09 Aug 2017 12:35:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/HTTP-event-collector-Channel-identifiers-what-do-they-identify/m-p/360197#M7356</guid>
      <dc:creator>mneergaa</dc:creator>
      <dc:date>2017-08-09T12:35:16Z</dc:date>
    </item>
    <item>
      <title>Re: HTTP event collector: Channel identifiers, what do they identify</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/HTTP-event-collector-Channel-identifiers-what-do-they-identify/m-p/360198#M7357</link>
      <description>&lt;P&gt;According to what I understand, it means the third meaning you mentioned, "one per actual client running the software". I think this is only needed if you use the indexer acknowledge, and you can read more details from here:&lt;BR /&gt;
&lt;A href="http://dev.splunk.com/view/event-collector/SP-CAAAE8X#aboutchannels"&gt;http://dev.splunk.com/view/event-collector/SP-CAAAE8X#aboutchannels&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 29 Apr 2018 08:54:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/HTTP-event-collector-Channel-identifiers-what-do-they-identify/m-p/360198#M7357</guid>
      <dc:creator>sni_splunk</dc:creator>
      <dc:date>2018-04-29T08:54:10Z</dc:date>
    </item>
    <item>
      <title>Re: HTTP event collector: Channel identifiers, what do they identify</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/HTTP-event-collector-Channel-identifiers-what-do-they-identify/m-p/360199#M7358</link>
      <description>&lt;P&gt;The new links are below.&lt;/P&gt;

&lt;OL&gt;
&lt;LI&gt;&lt;A href="https://docs.splunk.com/Documentation/Splunk/7.1.2/Data/FormateventsforHTTPEventCollector#Channel_identifier_header"&gt;https://docs.splunk.com/Documentation/Splunk/7.1.2/Data/FormateventsforHTTPEventCollector#Channel_identifier_header&lt;/A&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;A href="https://docs.splunk.com/Documentation/Splunk/7.1.2/RESTREF/RESTinput#services.2Fcollector.2Fraw"&gt;https://docs.splunk.com/Documentation/Splunk/7.1.2/RESTREF/RESTinput#services.2Fcollector.2Fraw&lt;/A&gt;&lt;/LI&gt;
&lt;/OL&gt;

&lt;P&gt;Be sure to select your Splunk version from that page (see URL).&lt;/P&gt;</description>
      <pubDate>Tue, 12 May 2020 23:50:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/HTTP-event-collector-Channel-identifiers-what-do-they-identify/m-p/360199#M7358</guid>
      <dc:creator>shandr</dc:creator>
      <dc:date>2020-05-12T23:50:05Z</dc:date>
    </item>
    <item>
      <title>Re: HTTP event collector: Channel identifiers, what do they identify</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/HTTP-event-collector-Channel-identifiers-what-do-they-identify/m-p/533942#M7359</link>
      <description>&lt;P&gt;Can we use one channel identifier for multiple clients through Splunk HEC to enable indexer acknowledgement&lt;/P&gt;</description>
      <pubDate>Wed, 23 Dec 2020 12:15:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/HTTP-event-collector-Channel-identifiers-what-do-they-identify/m-p/533942#M7359</guid>
      <dc:creator>Durgapk</dc:creator>
      <dc:date>2020-12-23T12:15:03Z</dc:date>
    </item>
    <item>
      <title>Re: HTTP event collector: Channel identifiers, what do they identify</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/HTTP-event-collector-Channel-identifiers-what-do-they-identify/m-p/533943#M7360</link>
      <description>&lt;P&gt;Can we use one channel identifier for multiple clients through Splunk HEC to enable indexer acknowledgement&lt;/P&gt;</description>
      <pubDate>Wed, 23 Dec 2020 12:16:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/HTTP-event-collector-Channel-identifiers-what-do-they-identify/m-p/533943#M7360</guid>
      <dc:creator>Durgapk</dc:creator>
      <dc:date>2020-12-23T12:16:01Z</dc:date>
    </item>
    <item>
      <title>Re: HTTP event collector: Channel identifiers, what do they identify</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/HTTP-event-collector-Channel-identifiers-what-do-they-identify/m-p/533944#M7361</link>
      <description>&lt;P&gt;Can we use one channel identifier for multiple clients through Splunk HEC to enable indexer acknowledgement&lt;/P&gt;</description>
      <pubDate>Wed, 23 Dec 2020 12:23:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/HTTP-event-collector-Channel-identifiers-what-do-they-identify/m-p/533944#M7361</guid>
      <dc:creator>Durgapk</dc:creator>
      <dc:date>2020-12-23T12:23:27Z</dc:date>
    </item>
  </channel>
</rss>

