Open MadsRC opened 1 year ago
I can confirm that Splunk HEC is documented to take in those parameters from the query parameters (examples 3 and 4) and that our source only looks at the channel
parameter.
I am a little confused what you are saying about the channel=
prefix, though. In the example shown above, the query parameter includes an extraneous channel=
(note: …/raw?channel=channel=00872DC6-AC83-4EDE-8AFE-8413C3825C4C&…
) but the linked examples don't show this. Is that a typo?
I can confirm that Splunk HEC is documented to take in those parameters from the query parameters (examples 3 and 4) and that our source only looks at the
channel
parameter.I am a little confused what you are saying about the
channel=
prefix, though. In the example shown above, the query parameter includes an extraneouschannel=
(note:…/raw?channel=channel=00872DC6-AC83-4EDE-8AFE-8413C3825C4C&…
) but the linked examples don't show this. Is that a typo?
You are absolutely correct, that was a typo - I've been awake for too long...
I've fixed the description to not include the channel part.
A note for the community
Problem
When sending data to Splunk via the HTTP Event Collector (HEC), one can provide certain metadata, in addition to the event payload. The metadata usually associated with HEC traffic is
index
,sourcetype
,source
andchannel
.When sending to the
/services/collector/event
or/services/collector
endpoint, all this metadata, except forchannel
is provided in JSON payload of the HTTP body. An example would be:When sending such an event, the fields will be available in the event. Fields such as
source
will havesplunk_
prepended (this is undocumented in the Splunk HEC source documentation).For example, when sending the data to Vector's splunk HEC input like this:
the resulting event will look like this:
When sending data to the
/services/collector/raw
endpoint of the Splunk HEC source, the HTTP body is used as a raw event. If one wishes to provide metadata, this has to be done via query parameters. Unfortunately, only thechannel
query parameter is extracted.When sending an event to the Splunk HEC source like this:
the following event is generated:
Notice the lack of
splunk_source
andsplunk_sourcetype
fields.Expected behaviour would be:
splunk_
to the metadata fields should be documented/services/collector/raw
endpoint,index
,source
andsourcetype
should be extracted from query parametersConfiguration
No response
Version
0.27.1-debian
Debug Output
No response
Example Data
No response
Additional Context
No response
References
No response