Skip to content

RFC 0058: Add gen_ai.conversation.id - #2696

Merged
taylor-swanson merged 1 commit into
elastic:mainfrom
Mikaayenson:rfc-0058-gen-ai-conversation-id
Sep 21, 2026
Merged

taylor-swanson merged 1 commit into
elastic:mainfrom
Mikaayenson:rfc-0058-gen-ai-conversation-id

Conversation

@Mikaayenson

Copy link
Copy Markdown
Contributor

Summary

Proposal RFC to add gen_ai.conversation.id (keyword, extended, beta) to the existing gen_ai fieldset, 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.yml follows after acceptance.

Changes

  • rfcs/text/0058-gen_ai-conversation-id.md — Proposal RFC
  • rfcs/text/0058/gen_ai.yaml — proposed field definition

Why

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

  • ECS team reviews Proposal (maturity: beta)
  • On merge, add field to schemas/gen_ai.yml (or rely on post-merge automation when available)

@Mikaayenson
Mikaayenson requested a review from a team September 21, 2026 13:56
@github-actions

Copy link
Copy Markdown
Contributor

🤖 GitHub comments

Just comment with:

  • run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

@taylor-swanson
taylor-swanson merged commit 4e46202 into elastic:main Sep 21, 2026
11 of 12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants