Splunk Enterprise

HTTP event collector: Channel identifiers, what do they identify

mneergaa
Engager

Quote from event collector docs:

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.

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...

  • One per client software, Linux and Windows?
  • One per released version of the softwares?
  • One per actual client running the software?

Does the channel parameter actually impact indexing or queries in any way? I don't understand why it's required at all.

Durgapk
Explorer

Can we use one channel identifier for multiple clients through Splunk HEC to enable indexer acknowledgement

0 Karma

shandr
Path Finder
0 Karma

Durgapk
Explorer

Can we use one channel identifier for multiple clients through Splunk HEC to enable indexer acknowledgement

Tags (1)
0 Karma

sni_splunk
Splunk Employee
Splunk Employee

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:
http://dev.splunk.com/view/event-collector/SP-CAAAE8X#aboutchannels

0 Karma

Durgapk
Explorer

Can we use one channel identifier for multiple clients through Splunk HEC to enable indexer acknowledgement

Tags (1)
0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Level Up Your .conf25: Splunk Arcade Comes to Boston

With .conf25 right around the corner in Boston, there’s a lot to look forward to — inspiring keynotes, ...

Manual Instrumentation with Splunk Observability Cloud: How to Instrument Frontend ...

Although it might seem daunting, as we’ve seen in this series, manual instrumentation can be straightforward ...

Take Action Automatically on Splunk Alerts with Red Hat Ansible Automation Platform

Ready to make your IT operations smarter and more efficient? Discover how to automate Splunk alerts with Red ...