Dashboards & Visualizations

HEC Continues to get 404 errors when sending webhooks

jnalewak_chef
Engager

I am trying to send notifications to an HEC in Splunk Cloud (self-service) using a json webhook from Chef Automate v2. The token I use is valid and I get success when using curl with an authentication header but not when using the following URL from Automate (actual info replaced with <> placeholders): <protocol>://input-<splunk_cloud_instance>.cloud.splunk.com:8088/services/collector/<token>

The error shows: "failed to post. Code 404. Body: {"text":"The requested URL was not found on this server.","code":404}"

Is there something different I need to do in the URL to get the message to post properly?

Tags (2)
0 Karma

jnalewak_chef
Engager

I found the issue. By default query strings are disabled for auth with HEC in Splunk Cloud. The documentation tells me to submit a ticket to an admin to get add allowQueryStringAuth=true to my token in the file: $SPLUNK_HOME/etc/apps/splunk_httpinput/local/inputs.conf. The problem is that I am using Splunk Cloud free to do testing for integration with Chef products and so I can't submit a ticket. Is there a way to do this without buying a support contract? (especially when you are just doing integration testing 🙂

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...

Modernize your Splunk Apps – Introducing Python 3.13 in Splunk

We are excited to announce that the upcoming releases of Splunk Enterprise 10.2.x and Splunk Cloud Platform ...

Step into “Hunt the Insider: An Splunk ES Premier Mystery” to catch a cybercriminal ...

After a whole week of being on call, you fell asleep on your keyboard, and you hit a sequence of buttons that ...