Skip to content

New Feature: Agent Names captured in traces and logs to aggregate per agent stats #10174

Description


name: Feature request
about: Tracing agent names

For the internal audit I would like to be able to trace agent token usage statistics.

  • Invocation within a chat
  • Within the chat across multiple invocations
  • Across multiple chats and invocations

I am OK to rely on Kusto SQL, but I need the agent names to be captured in traces and logs automatically.

Activity

  1. sphenry commented on Jan 21, 2025

    @sphenry
    Contributor

    Adding Dmytro Struk (@dmytrostruk) , it might make sense that this should be at the Kernel level

  2. markwallace-microsoft commented on Jan 22, 2025

    @markwallace-microsoft
    Contributor

    Dmytro Struk (@dmytrostruk) can you handle making the equivalent .NET changes

  3. TaoChenOSU commented on Jan 22, 2025

    @TaoChenOSU
    Contributor

    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.

  4. moved this from Sprint: Planned to Sprint: In Progress in Semantic Kernelon Jan 23, 2025
  5. crickman commented on Jan 27, 2025

    @crickman
    Contributor

    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.

  6. moved this from Sprint: In Progress to Sprint: In Review in Semantic Kernelon Feb 4, 2025
  7. moved this from Sprint: In Review to Sprint: Done in Semantic Kernelon Feb 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

agentsexperimentalAssociated with an experimental feature

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions