Repository navigation
RFC 0058: Add gen_ai.conversation.id - #2696
Merged
taylor-swanson merged 1 commit intoSep 21, 2026
Merged
Conversation
Contributor
🤖 GitHub commentsJust comment with:
|
trisch-me
approved these changes
Sep 21, 2026
taylor-swanson
approved these changes
Sep 21, 2026
3 tasks
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
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
Proposal RFC to add
gen_ai.conversation.id(keyword, extended, beta) to the existinggen_aifieldset, matching the OpenTelemetry GenAI attribute of the same name.This is a documentation-only Proposal PR per rfcs/PROCESS.md: rationale + field YAML + example events. Schema application to
schemas/gen_ai.ymlfollows after acceptance.Changes
rfcs/text/0058-gen_ai-conversation-id.md— Proposal RFCrfcs/text/0058/gen_ai.yaml— proposed field definitionWhy
Needed to correlate multi-turn GenAI sessions (detections, Agent Builder / assistant traces, OTel spans) without inventing a custom field. Adjacent ids (
gen_ai.agent.id,gen_ai.response.id) are already in ECS; conversation id was the missing session key.Test plan
schemas/gen_ai.yml(or rely on post-merge automation when available)