Add EDOT data streams documentation and clarify exporter/storage behavior #504
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 adds a new documentation page titled “EDOT data streams”, addressing recurring user questions.
The new page explains:
Why EDOT configurations sometimes include two exporters (
otelandecs)Which data streams are populated by EDOT in OTel-native and ECS/APM-compatible modes
Differences in data streams between mOTLP and local EDOT deployments
Why some fields appear duplicated
Which storage engines are used (TSDB, LogsDB)
Closes #3501
Generative AI disclosure
Did you use a generative AI (GenAI) tool to assist in creating this contribution?
If you answered "Yes" to the previous question, please specify the tool(s) and model(s) used (e.g., Google Gemini, OpenAI ChatGPT-4, etc.).
Tool(s) and model(s) used:
Claude 4.5 Sonnet via Cursor