Source
Data scrubbing, retention & volume control — found from sitemap — Elastic Observability APM
Checked for Elastic Observability APM on 17 Nov 2026
- Page
- https://www.elastic.co/docs/reference/managed-inputs/rate-limiting
- Checked
- 17 Nov 2026, 13:07 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:c3f5541e0f6a101d9f126ba6ebc611c0d734ed7fa00fe550b9218b65cd7186a2
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Rate limiting behavior Report an error
“Rate limiting occurs when a managed input receives data faster than it can process and index into Elasticsearch. The endpoint responds with HTTP 429 errors until the data volume is reduced.”
-
Rate limiting ech behavior Report an error
“Elastic Cloud Hosted: Rate limits depend on your Elasticsearch cluster capacity. If your cluster can't keep up with incoming data, the endpoint starts rejecting requests with 429 errors.”
-
Rate limiting serverless behavior Report an error
“Elastic Cloud Serverless: Elastic manages scaling automatically. Rate limiting is rare and typically indicates a temporary event to protect our system.”
-
Rate limiting identification Report an error
“When rate limiting occurs, the managed input responds with an HTTP 429 Too Many Requests status code.”
-
Otlp rate limit error message Report an error
“For the Managed OTLP Endpoint, a log message similar to this can appear in the OpenTelemetry Collector's output:”
-
Shipper auto retry Report an error
“Elasticsearch output shippers such as Beats, Elastic Agent, and Logstash typically retry 429 responses automatically with backoff. Configure your shipper to queue data so transient rejections don't lose data.”
-
Ech latency threshold Report an error
“When Elasticsearch latency exceeds 6 seconds, managed inputs reduce concurrency and return HTTP 429 errors.”
-
Autoops diagnostics Report an error
“If AutoOps is available in your region, use it to check latency, CPU utilization, index queue depth, and node load to confirm whether your cluster is under-resourced.”
-
Ech undersized cluster Report an error
“If AutoOps is not available in your region, contact Elastic Support.”
-
Scaling options Report an error
“Resize deployment Autoscaling in ECE and ECH”
-
Serverless persistent 429 Report an error
“If you experience persistent 429 errors, contact Elastic Support.”
-
Free trial Report an error
“Get started free 14-day free trial All features included No setup required”
Scores citing this record
- The Agency Tech Lead Alerting, integrations & developer workflow
- The Agency Tech Lead Data scrubbing, retention & volume control
- The Data Protection Officer Data scrubbing, retention & volume control
- The Mobile Team Lead APM, tracing & profiling
- The Mobile Team Lead Data scrubbing, retention & volume control
- The SaaS CTO Data scrubbing, retention & volume control
- The Skeptic Data scrubbing, retention & volume control
- The Site Reliability Engineer Data scrubbing, retention & volume control