Getting Data In

Will the HTTP Event Collector respond with any error if it can't keep up with event volume?

sandeep23
Engager

I am planning to use HEC on heavy forwarder(s) which will forward to the indexer(s).

My question: Is HEC designed to return any error(s) to the sender if it can't keep up with volume of input? Does in-memory input queue configuration have any impact on response?

0 Karma
1 Solution

ineeman
Splunk Employee
Splunk Employee

Yes - if we fail to enqueue events into the queues (in memory or persistent) we will give you back an error (and a 502 response code) to say the service is too busy to handle requests.

View solution in original post

ineeman
Splunk Employee
Splunk Employee

Yes - if we fail to enqueue events into the queues (in memory or persistent) we will give you back an error (and a 502 response code) to say the service is too busy to handle requests.

gaarti
New Member

@ineeman
How should we make sure that we don't hit this issue? I keep getting this 503 Server busy error when I have seen a large volume of events getting posted to HEC.

Thanks much!

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!

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...

All Work and No Play? Not at .conf26! Unwind at These Evening Events

Between hands-on technical sessions, keynote reveals, and diving into live architectures, .conf26 is packed ...

Join the Hackathon at .conf26 and build a No-Code AI agent

Join us for the AI Agent Buildathon, an in-person, three-hour hands-on Hackathon where you’ll use Splunk Agent ...