New workflow and step spans for agentic systems #3179
Conversation
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
adityamehra
reviewed
Dec 6, 2025
model/gen-ai/registry.yaml
Outdated
| - id: gen_ai.step.description | ||
| stability: development | ||
| type: string | ||
| brief: Name/identifier of the step. |
model/gen-ai/registry.yaml
Outdated
| - id: gen_ai.step.assigned_agents | ||
| stability: development | ||
| type: string | ||
| brief: Name/identifier of the step. |
There was a problem hiding this comment.
Name of agent/agents assigned to execute the step
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Fixes #
Changes
Added support for new workflow and step spans as described in this proposal.
Following shows
WorkflowandStepspans created for different agentic frameworks(opentelemetry-util-genaipackage extended with workflow and step span support(POC))LangGraph
CrewAI
OpenAI agents
Important
Pull requests acceptance are subject to the triage process as described in Issue and PR Triage Management.
PRs that do not follow the guidance above, may be automatically rejected and closed.
Merge requirement checklist
[chore]