Add semantic conventions for GenAI agent planning operation#3594
Open
Krishnachaitanyakc wants to merge 1 commit intoopen-telemetry:mainfrom
Open
Add semantic conventions for GenAI agent planning operation#3594Krishnachaitanyakc wants to merge 1 commit intoopen-telemetry:mainfrom
Krishnachaitanyakc wants to merge 1 commit intoopen-telemetry:mainfrom
Conversation
lmolkova
moved this from Untriaged
to Awaiting codeowners approval
in Semantic Conventions Triage
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
3 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.
Partially addresses #2664
area:gen-ai
Summary
Clarify
planspan naming based on the immediate parent span.For
span.gen_ai.plan.internal, this change specifies that the span name SHOULD be:plan {gen_ai.agent.name}when the parent isinvoke_agentplan {gen_ai.workflow.name}when the parent isinvoke_workflowplanotherwiseRationale
This removes ambiguity when both
gen_ai.agent.nameandgen_ai.workflow.nameare available, and makes span naming more consistent across instrumentations.Scope
Updates the normative guidance in
model/gen-ai/spans.yamland the generated GenAI agent span documentation.No new attributes or operations are introduced.