docs: add data format consequences to OTel ingest path descriptions - #8237
Draft
alexandra5000 wants to merge 1 commit into
Draft
docs: add data format consequences to OTel ingest path descriptions#8237alexandra5000 wants to merge 1 commit into
alexandra5000 wants to merge 1 commit into
Conversation
alexandra5000
marked this pull request as draft
September 8, 2026 13:24
Contributor
Elastic Docs AI PR menuCheck the box to run an AI review for this pull request.
Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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
Closes #6569.
The docs listed all the destinations an OTLP source can send data to, but never said that the destination determines the data format. The companion PR elastic/opentelemetry#668 adds a canonical diagram and table to
opentelemetry://reference/compatibility/data-streams.md. This PR adds the supporting text changes in docs-content.Merge after elastic/opentelemetry#668 — the cross-repo anchor linked from these pages won't resolve until that PR is merged.