Agno instrumentation #1050
Merged
Agno instrumentation #1050
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
Codecov ReportAttention: Patch coverage is 📢 Thoughts on this report? Let us know! |
tcdent
previously requested changes
Jun 6, 2025
…/agentops into agno_instrumentation
dot-agi
approved these changes
Jun 12, 2025
Member
dot-agi
left a comment
dot-agi
left a comment
There was a problem hiding this comment.
One more in the sack, thanks to @fenilfaldu 🚀
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
📥 Pull Request
#790 #994
📘 Description
Streaming Context Management
Implemented a StreamingContextManager to handle long-running streaming operations where traditional span management doesn't work
Maintains active span contexts across streaming iterations, ensuring child operations (like LLM calls) remain properly nested
Automatically cleans up contexts when streaming completes
Hierarchical Trace Context Propagation
Team → Agent → Tool hierarchy: Team operations create parent spans that encompass all agent activities
Agent → LLM context linking: Agent contexts are preserved and propagated to LLM instrumentation through session ID mapping
Instrumented Components
Agent Operations: run/arun methods for synchronous and asynchronous agent execution
Team Workflows: Team collaboration with proper parent-child relationships
Tool Execution: Function calls maintain context from their calling agent
Metrics Collection: Token usage and timing metrics with proper attribution
🧪 Testing
Example