Add troubleshooting guide for 429 errors when using the Elastic Cloud Managed OTLP Endpoint #3669
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
🔍 Preview links for changed docs |
theletterf
approved these changes
Oct 28, 2025
simitt
reviewed
Oct 28, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds a new troubleshooting topic under that explains how to diagnose and resolve HTTP 429 Too Many Requests errors when sending data to the mOTLP endpoint in both Elastic Cloud Serverless and Elastic Cloud Hosted environments.
Also includes an update to the mOTLP quickstart page that replaces the inline “Error: too many requests” section with a link to this troubleshooting guide.
Closes #6054