Consistent mapping for OTel log and event bodies#120547
Merged
felixbarny merged 4 commits intoelastic:mainfrom Jan 22, 2025
Merged
Consistent mapping for OTel log and event bodies#120547felixbarny merged 4 commits intoelastic:mainfrom
felixbarny merged 4 commits intoelastic:mainfrom
Conversation
felixbarny
added
>enhancement
:StorageEngine/Data streams
elasticsearchmachine
added
v9.0.0
external-contributor
Collaborator
|
Pinging @elastic/es-data-management (Team:Data Management) |
Collaborator
|
Hi @felixbarny, I've created a changelog YAML for you. |
axw
approved these changes
Jan 22, 2025
Member
axw
left a comment
axw
left a comment
There was a problem hiding this comment.
LGTM. Should we bump the version in resources.yaml?
gregkalapos
approved these changes
Jan 22, 2025
felixbarny
added
auto-backport
Collaborator
💚 Backport successful
|
elasticsearchmachine
pushed a commit
that referenced
this pull request
Jan 22, 2025
andrzej-stencel
pushed a commit
to open-telemetry/opentelemetry-collector-contrib
that referenced
this pull request
Jan 24, 2025
…s and events in `otel` mode (#37387) The OTel community has reached a consensus that all structured data for events defined by semantic conventions should be stored in attributes (open-telemetry/semantic-conventions#1651 (comment)). The body for events may contain opaque/external data, which sounds like a job for the flattened field type. Therefore, it no longer makes sense to map the body for logs and events differently. The corresponding Elasticsearch mapping change has been merged already: elastic/elasticsearch#120547 --------- Co-authored-by: Carson Ip <carsonip@users.noreply.github.com>
chengchuanpeng
pushed a commit
to chengchuanpeng/opentelemetry-collector-contrib
that referenced
this pull request
Jan 26, 2025
…s and events in `otel` mode (open-telemetry#37387) The OTel community has reached a consensus that all structured data for events defined by semantic conventions should be stored in attributes (open-telemetry/semantic-conventions#1651 (comment)). The body for events may contain opaque/external data, which sounds like a job for the flattened field type. Therefore, it no longer makes sense to map the body for logs and events differently. The corresponding Elasticsearch mapping change has been merged already: elastic/elasticsearch#120547 --------- Co-authored-by: Carson Ip <carsonip@users.noreply.github.com>
zeck-ops
pushed a commit
to zeck-ops/opentelemetry-collector-contrib
that referenced
this pull request
Apr 23, 2025
…s and events in `otel` mode (open-telemetry#37387) The OTel community has reached a consensus that all structured data for events defined by semantic conventions should be stored in attributes (open-telemetry/semantic-conventions#1651 (comment)). The body for events may contain opaque/external data, which sounds like a job for the flattened field type. Therefore, it no longer makes sense to map the body for logs and events differently. The corresponding Elasticsearch mapping change has been merged already: elastic/elasticsearch#120547 --------- Co-authored-by: Carson Ip <carsonip@users.noreply.github.com>
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
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.
No description provided.