Skip to content

Commit c1d6611

Browse files
committed
Use placeholders
1 parent 80ba73e commit c1d6611

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

troubleshoot/ingest/opentelemetry/429-errors-motlp.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -16,9 +16,9 @@ products:
1616

1717
# 429 errors when using the Elastic Cloud Managed OTLP Endpoint
1818

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.
2020

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.
2222

2323
## Symptoms
2424

@@ -51,7 +51,7 @@ A 429 status means that the rate of requests sent to the Managed OTLP endpoint h
5151
Refer to the [Rate limiting section](opentelemetry://reference/motlp.md#rate-limiting) in the mOTLP reference documentation for details.
5252

5353
* 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).
5555
* Multiple Collectors or SDKs are sending data concurrently without load balancing or backoff mechanisms.
5656

5757
## Resolution
@@ -62,7 +62,7 @@ To resolve 429 errors, identify whether the bottleneck is caused by ingest limit
6262

6363
If you’ve confirmed that your ingest configuration is stable but still encounter 429 errors:
6464

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.
6666
* {{ech}} (ECH): Increase your {{es}} capacity by scaling or resizing your deployment:
6767
* [Scaling considerations](../../../deploy-manage/production-guidance/scaling-considerations.md)
6868
* [Resize deployment](../../../deploy-manage/deploy/cloud-enterprise/resize-deployment.md)

0 commit comments

Comments
 (0)