You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: troubleshoot/ingest/opentelemetry/429-errors-motlp.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,9 +16,9 @@ products:
16
16
17
17
# 429 errors when using the Elastic Cloud Managed OTLP Endpoint
18
18
19
-
When sending telemetry data through the {{motlp}} (mOTLP), you might encounter HTTP `429 Too Many Requests` errors. These indicate that your ingest rate has temporarily exceeded the rate or burst limits configured for your Elastic Cloud project.
19
+
When sending telemetry data through the {{motlp}} (mOTLP), you might encounter HTTP `429 Too Many Requests` errors. These indicate that your ingest rate has temporarily exceeded the rate or burst limits configured for your {{ecloud}} project.
20
20
21
-
This issue can occur in both Elastic Cloud Serverless and {{ech}} (ECH) environments.
21
+
This issue can occur in both {{serverless-full}} and {{ech}} (ECH) environments.
22
22
23
23
## Symptoms
24
24
@@ -51,7 +51,7 @@ A 429 status means that the rate of requests sent to the Managed OTLP endpoint h
51
51
Refer to the [Rate limiting section](opentelemetry://reference/motlp.md#rate-limiting) in the mOTLP reference documentation for details.
52
52
53
53
* In {{ech}}, the {{es}} capacity for your deployment might be underscaled for the current ingest rate.
54
-
* In Elastic Cloud Serverless, rate limiting should not result from {{es}} capacity, since the platform automatically scales ingest capacity. If you suspect a scaling issue, [contact Elastic Support](contact-support.md).
54
+
* In {{serverless-full}}, rate limiting should not result from {{es}} capacity, since the platform automatically scales ingest capacity. If you suspect a scaling issue, [contact Elastic Support](contact-support.md).
55
55
* Multiple Collectors or SDKs are sending data concurrently without load balancing or backoff mechanisms.
56
56
57
57
## Resolution
@@ -62,7 +62,7 @@ To resolve 429 errors, identify whether the bottleneck is caused by ingest limit
62
62
63
63
If you’ve confirmed that your ingest configuration is stable but still encounter 429 errors:
64
64
65
-
*Elastic Cloud Serverless: [Contact Elastic Support](contact-support.md) to request an increase in ingest limits.
65
+
*{{serverless-full}}: [Contact Elastic Support](contact-support.md) to request an increase in ingest limits.
66
66
* {{ech}} (ECH): Increase your {{es}} capacity by scaling or resizing your deployment:
0 commit comments