Splunk Observability Cloud

Trace REST API Throttling

euclidean
New Member

I am using the Splunk Observability REST API, specifically "/apm/trace" endpoint.  

I have following questions about throttling limits, which triggers HTTP code 429: 

- What is the limit?
- If this is configured anywhere within Splunk Observability?
- What types of throttling?  such as Hard, Soft, or Elastic / Dynamic
- Does it use fixed window or rolling window, with or without counters?

Thanks!

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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...