We have updated our Terms of Service, Code of Conduct, and Addendum.

Unable to perform Destination test with Splunk HEC

Somnath Bhattacharya
Somnath Bhattacharya Posts: 1 ✭
in Stream

I am new to cribl and trying to setup Splunk HEC destination from cribl sanbox stream instance. I have provisioned a free splunk cloud instance and setup HEC. While I can send data via: curl -k "https://<host>:8088/services/collector" -H "Authorization: Splunk 38aa4a38-8fd5-4faa-afc4-9b3533ac39c7" -d "{"event": "Hello, world!", "sourcetype": "manual"}"

I am unable to run destination test from cribl with the exact endpoint or with /services/collector/event. Everytime the request time out with error:

2025-02-20T14:23:57.956αtime:2025-02-20T14:23:57.956Zαcid:w0αchannel:output:splunkαlevel:errorαmessage:error while flushingαioName:splunk_hecαioType:destination{}error:αmessage:request timeoutαstack:Error: request timeout at /opt/cribl/bin/cribl.js:15:9721630 at new Promise (<anonymous>) at p.doHttpRequest (/opt/cribl/bin/cribl.js:15:9721585) at runNextTicks (node:internal/process/task_queues:60:5) at process.processTimers (node:internal/timers:509:9) at async p.buildRecProm (/opt/cribl/bin/cribl.js:15:9718547)

Please guide, to fix the issue.

Tagged:

Answers

  • Jon Rust
    Jon Rust Posts: 507 mod

    I don't believe the sandbox instances can reach out to arbitrary destinations. Instead, set-up a Cribl Cloud instance (also free), and run your tests there.

Categories