Splunk Cloud Platform

HTTP Event Collector- Is there something wrong with this curl command?

andrew15
Loves-to-Learn Lots

Currently trying to test an HTTP event collector token by directly sending events to the cloud before we use the HEC for a OpenTelemetry Connector, but we are getting stuck at 403 Forbidden error. I can see the successful request going through our firewall. Is there something wrong with this curl command? 

Not sure if it affects anything but we are still on the Splunk Cloud Classic, not Victoria. 

Screenshots attached, appreciate any help we can get!

andrew15_1-1684954283713.pngandrew15_1-1684954283713.png

andrew15_2-1684954360716.pngandrew15_2-1684954360716.png

 

 

 

 

Labels (2)
0 Karma

rnowitzki
Builder

Hi @andrew15 ,

Are you sure about the port (443)?  Usually it's 8088, I guess also for Splunk Cloud (Classic).
There are some Examples in the Docs.

Ralph

 

 

--
Karma and/or Solution tagging appreciated.
0 Karma
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!

SOC4Kafka - New Kafka Connector Powered by OpenTelemetry

The new SOC4Kafka connector, built on OpenTelemetry, enables the collection of Kafka messages and forwards ...

Rounding off the Splunk Dashboard Contest

What does a contest-winning Splunk dashboard look like? In this case, it isn't in a browser tab at all. It ...

A Four Part Event Series: AI + Observability: AI Agents, LLMs, Apps, & Infrastructure

AI + Observability: AI Agents, LLMs, Apps, & Infrastructure The rapid evolution of artificial intelligence ...