Add info for EDOT SDKs supported telemetry configuration #4303
+32
−14
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
Contributor
Contributor
Vale Linting ResultsSummary: 1 suggestion found 💡 Suggestions (1)
|
2 tasks
bmorelli25
reviewed
Dec 12, 2025
solutions/observability/get-started/quickstart-monitor-your-application-performance.md
Outdated
Show resolved
Hide resolved
bmorelli25
reviewed
Dec 12, 2025
...ckstart-unified-kubernetes-observability-with-elastic-distributions-of-opentelemetry-edot.md
Outdated
Show resolved
Hide resolved
bmorelli25
reviewed
Dec 12, 2025
bmorelli25
requested changes
Dec 12, 2025
Member
bmorelli25
left a comment
bmorelli25
left a comment
There was a problem hiding this comment.
I think we need to rethink how we communicate this limitation to users.
- I don't think this is necessary in our quickstarts
- I don't think a Tip at the top of all of our troubleshooting guides is the right place or way to explain this
Some ideas:
- You could add a "Supported architectures" or similar section under each "General troubleshooting" headings. We could call out this support/limitation as regular text there.
- What about this page? https://www.elastic.co/docs/reference/opentelemetry/architecture. There should definitely be a warning that sending to APM Server OTel intake is not supported on this page
- This page too should definitely have something on it: https://www.elastic.co/docs/solutions/observability/apm/opentelemetry-intake-api
- Should a limitation be listed here? https://www.elastic.co/docs/solutions/observability/apm/opentelemetry/limitations
Contributor
Author
|
Hey hey @bmorelli25 I moved the information a bit. Also check out the elastic/opentelemetry sister PR for this issue: elastic/opentelemetry#510 |
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.
Summary
This PR updates the EDOT SDK documentation to make support boundaries explicit.
EDOT SDKs are supported only when they send telemetry to:
Sending EDOT SDK data directly to APM Server’s OpenTelemetry intake endpoint is not supported.
Closes #4168
Related PR in the elastic/opentelemetry repo: #510
Generative AI disclosure
To help us ensure compliance with the Elastic open source and documentation guidelines, please answer the following:
Tool(s) and model(s) used: Claude Sonnet 4.5 via Cursor