topic Issues with HTTP Status for HEC token in Getting Data In

Issues with HTTP Status for HEC token

SplunkDash — Sun, 17 Nov 2024 19:23:12 GMT

Hey,

I am facing following issues when sending data using HEC token. Connection has been established with no issue but getting following error message with HEC. Any recommendations to resolve this issue will be highly appreciated. Thank you!

[http]
disabled = 0
enableSSL = 0

is also there.

Re: Issues with HTTP Status for HEC token

PickleRick — Sun, 17 Nov 2024 20:09:14 GMT

1. It's much more convenient (and lets people search the content later) if you copy-paste text instead of posting pictures (structured text is best pasted into a preformatted-style paragraph or a code block.

2. Here we only see the result of your action. We have no idea what exactly you did.

Re: Issues with HTTP Status for HEC token

SplunkDash — Sun, 17 Nov 2024 20:26:12 GMT

Hey @PickleRick

I was testing using this:

curl -k http://splunk-hf-1729440419.us-east-1.alb.amazonaws.com:8088/services/collector -H "Authorization: Splunk ad9fe08e-68fb-4b07-876b-94f00bdd0d91" -d '{"event": "Hec Splunk Test"}' -v

Re: Issues with HTTP Status for HEC token

dural_yyz — Mon, 18 Nov 2024 15:38:36 GMT

Your URL is short.

https://http-inputs-<customer>.splunkcloud.com/services/collector/raw
or
https://mysplunkserver.example.com:8088/services/collector/event

Re: Issues with HTTP Status for HEC token

isoutamo — Mon, 18 Nov 2024 17:03:51 GMT

After you have pasted whole url and token, please remove that token and generate a new one. Otherwise you could surprise how many will try it!
It’s best to anonymous both url (host part) and token before you post those to community.

Re: Issues with HTTP Status for HEC token

SplunkDash — Tue, 19 Nov 2024 00:45:13 GMT

Hey @isoutamo

Thank you for letting me know. But the token and the host URL provided are not the actual, I changed them a little. We should be fine. Thank you so much again.

Re: Issues with HTTP Status for HEC token

SplunkDash — Tue, 19 Nov 2024 00:44:27 GMT

Hello,

The issues got resolved. The port 8088 was used by other services causing that issue, had to kill that service to resolve that issue. Now working as expected. Thank you so much all.