Getting Data In

Error while sending data via SplunkHECExporter

Av2
Observer

I using the OpenTelemetry Collector to receive and export logs to my Splunk Cloud Instance.
I have a AWS lambda which polls data and runs a OpenTelemetry Lambda layer which receives the logs in the OTLP format and exports it to Splunk cloud Instance using HEC exporter. Below is the configurations for otel

receivers:
otlp:
protocols:
http:
exporters:
splunk_hec:
token: ${SPLUNK_TOKEN}
endpoint: ${HEC_ENDPOINT}
# Source. See https://docs.splunk.com/Splexicon:Source
source: "otel"
# Source type. See https://docs.splunk.com/Splexicon:Sourcetype
sourcetype: "otel"
service:
pipelines:
logs:
receivers: [otlp]
exporters: [splunk_hec]



Now, the problem is the splunk_hec exporter fails to send the logs to my splunk cloud Instance.
I get the below errors

max elapsed time expired Post "https://inputs.prd-p-gxyqz.splunkcloud.com:8088/services/collector/event": EOF


max elapsed time expired Post "https://inputs.prd-p-gxyqz.splunkcloud.com:8088/services/collector/event": context deadline exceeded



Now can you please help me identify the issue.
Also, what exactly should be my HEC Endpoint URL? The documentation says the format should be

<protocol>://http-inputs-<host>.splunkcloud.com:<port>/<endpoint>


But the above format doesn't work.

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!

Vibe-coding, AI, and Splunkcraft: Highlights from the .conf26 Builder Bar

If you stopped by the Builder Bar at .conf26, thank you! This year, we brought ...

Thanks for the Memories: .conf26 Took Learning to New Heights

Thank you, Splunk Community, for making .conf26 in Denver one for the books. From packed Splunk University ...

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...