You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
New Feature: Agent Names captured in traces and logs to aggregate per agent stats #10174
Including the agent-id along with the name may be something to consider. Name is optional, but Id is required. Name is also not enforced as unique. May want to revisit the Python changes as well.
Activity
sphenry commentedon Jan 21, 2025
Adding Dmytro Struk (@dmytrostruk) , it might make sense that this should be at the Kernel level
markwallace-microsoft commentedon Jan 22, 2025
Dmytro Struk (@dmytrostruk) can you handle making the equivalent .NET changes
Python: Add agent invocation spans (#10255)
TaoChenOSU commentedon Jan 22, 2025
Reopening for .Net
Dmytro Struk (@dmytrostruk) We may need to similar sample in .Net to verify the feature: #10184
Please let me know if you want to split the work or have a discussion.
crickman commentedon Jan 27, 2025
Including the agent-id along with the name may be something to consider. Name is optional, but Id is required. Name is also not enforced as unique. May want to revisit the Python changes as well.
.Net: Updated agent logs to include agent name (#10330)
.Net: Added traces for Agent invocations (#10387)
Python: Add agent invocation spans (microsoft#10255)
.Net: Updated agent logs to include agent name (microsoft#10330)
.Net: Added traces for Agent invocations (microsoft#10387)