Add troubleshooting guide for OTel connectivity issues #3030
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
reviewed
Sep 19, 2025
hegerchr
reviewed
Oct 2, 2025
There was a problem hiding this comment.
@alexandra5000 thank you for putting this together. I left comments as suggestions.
florianl
reviewed
Oct 2, 2025
florianl
approved these changes
Oct 6, 2025
hegerchr
approved these changes
Oct 14, 2025
theletterf
approved these changes
Oct 14, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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 page covering connectivity issues between OpenTelemetry SDKs, the Collector, and Elastic endpoints.
The page includes:
Common error symptoms
Differentiation of root causes (firewall, endpoint errors, proxy misconfiguration, SDK vs Collector failures)
Step-by-step resolution checks (DNS, reachability, port testing, TLS validation)
Links to related existing pages (proxy settings, debug logging)
This content is intended to help users diagnose networking problems even when proxy settings appear correct but ports or firewalls block traffic.
Resolves #2351