Repository navigation
feat(schema): add conversation.id field to gen_ai schema - #2697
Conversation
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
🤖 GitHub commentsJust comment with:
|
🔍 Preview links for changed docs |
✅ 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. |
|
@Mikaayenson FYI |
|
@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. |
|
@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 |
1. What does this PR do?
Add
conversation.idfield to thegen_aischema 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.idSee 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