Skip to main content
When you run a team in Agno, the response you get (TeamRunOutput) includes detailed metrics about the run. These metrics help you understand resource usage (like token usage and time), performance, and other aspects of the model and tool calls across both the team leader and team members. Metrics are available at multiple levels:
  • Per-message: Each message (assistant, tool, etc.) has its own metrics.
  • Per-member run: Each team member run has its own metrics. You can make member runs available on the TeamRunOutput by setting store_member_responses=True,
  • Team-level: The TeamRunOutput aggregates metrics across all team leader and team member messages.
  • Session-level: Aggregated metrics across all runs in the session, for both the team leader and all team members.

Example Usage

Suppose you have a team that performs some tasks and you want to analyze the metrics after running it. Here’s how you can access and print the metrics:
You’ll see the outputs with following information:
  • input_tokens: The number of tokens sent to the model.
  • output_tokens: The number of tokens received from the model.
  • total_tokens: The sum of input_tokens and output_tokens.
  • audio_input_tokens: The number of tokens sent to the model for audio input.
  • audio_output_tokens: The number of tokens received from the model for audio output.
  • audio_total_tokens: The sum of audio_input_tokens and audio_output_tokens.
  • cache_read_tokens: The number of tokens read from the cache.
  • cache_write_tokens: The number of tokens written to the cache.
  • reasoning_tokens: The number of tokens used for reasoning.
  • duration: The duration of the run in seconds.
  • time_to_first_token: The time taken until the first token was generated.
  • provider_metrics: Any provider-specific metrics.

Developer Resources