Skip to content

feat(schema): add conversation.id field to gen_ai schema - #2697

Merged
taylor-swanson merged 2 commits into
elastic:mainfrom
taylor-swanson:feat/implement-rfc-0058
Sep 21, 2026
Merged

taylor-swanson merged 2 commits into
elastic:mainfrom
taylor-swanson:feat/implement-rfc-0058

Conversation

@taylor-swanson

Copy link
Copy Markdown
Contributor

1. What does this PR do?

Add conversation.id field to the gen_ai schema as a keyword field that is a unique identifier for a conversation. It is used to store and correlate messages within a conversation.

2. Which ECS fields are affected/introduced?

  • gen_ai.conversation.id

See RFC 0058

3. Why is this change necessary?

See RFC 0058

4. Have you added/updated documentation?

YES

5. Have you built ECS and committed any newly generated files?

YES

6. Have you run the ECS validation tests locally?

YES

7. Anything else for the reviewers?

N/A

Commit Message

feat(schema): add conversation.id field to gen_ai schema

Add `conversation.id` field to the `gen_ai` schema as a keyword
field that is a unique identifier for a conversation. It is used
to store and correlate messages within a conversation.

- Implements RFC 0058

Add `conversation.id` field to the `gen_ai` schema as a keyword
field that is a unique identifier for a conversation. It is used
to store and correlate messages within a conversation.

- Implements RFC 0058
@taylor-swanson taylor-swanson self-assigned this Sep 21, 2026
@taylor-swanson taylor-swanson added the enhancement New feature or request label Sep 21, 2026
@taylor-swanson
taylor-swanson requested a review from a team September 21, 2026 15:00
@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!)

@github-actions

github-actions Bot commented Sep 21, 2026 •

Copy link
Copy Markdown
Contributor

@github-actions

Copy link
Copy Markdown
Contributor

✅ Elastic Docs Style Checker (Vale)

No issues found on modified lines!


The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale.

@trisch-me

Copy link
Copy Markdown
Contributor

@Mikaayenson FYI

@trisch-me

Copy link
Copy Markdown
Contributor

@taylor-swanson do you know why docs are failing? is it temporary error?

@taylor-swanson

Copy link
Copy Markdown
Contributor Author

@taylor-swanson do you know why docs are failing? is it temporary error?

I'm not sure... it's unrelated to this PR, though. It looks like some external issue. The build, check, and match steps all passed for docs.

@taylor-swanson
taylor-swanson merged commit 9868ff5 into elastic:main Sep 21, 2026
7 of 8 checks passed
@taylor-swanson
taylor-swanson deleted the feat/implement-rfc-0058 branch September 21, 2026 16:39
@taylor-swanson

Copy link
Copy Markdown
Contributor Author

@Mikaayenson, this will be going into the next ECS release (probably 9.6.0), however, you can start using this field at any point. Since it is a keyword field, nothing extra needs to be done. As long as the incoming JSON type in the document is a string, then the dynamic ECS template will work as expected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants