> ## Documentation Index
> Fetch the complete documentation index at: https://docs.duvo.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Understanding Metrics

> Definitions for the agent, user, and source metrics shown in Team Insights, plus how to interpret trends.

## Introduction

This page explains the metrics available in Team Insights and how to interpret them for your organization.

***

## Agent Metrics

### Total Runs

The total number of times agents have been executed in the selected time period.

**What it tells you:**

* Overall automation activity level
* Whether usage is growing or declining
* Comparison baseline for different periods

### Completed Runs

Runs that finished successfully without errors or interruptions.

**What it tells you:**

* Reliability of your agents
* Success rate of your automation
* Whether agents are working as expected

**Healthy target:** Aim for 90%+ completion rate. Lower rates may indicate issues with Connections, AOPs, or edge cases.

### Active Agents

Agents that have had at least one run in the selected period.

**What it tells you:**

* How many agents are actually being used
* Breadth of automation across your workflows
* Whether some agents are unused and could be retired

***

## User Metrics

### Active Users

Team members who have run at least one agent in the period.

**What it tells you:**

* Adoption rate across your team
* Whether automation is spreading or concentrated
* Opportunities to improve adoption

### Runs Per User

Average number of runs initiated by each active user.

**What it tells you:**

* Engagement depth with automation
* Power users vs casual users
* Potential for expanding usage

***

## Source Metrics

### Manual Runs

Runs triggered by users clicking the Run button.

**Typical patterns:**

* Higher for new agents being tested
* Common for ad-hoc tasks
* May indicate scheduling opportunities

### Scheduled Runs

Runs triggered automatically by schedules.

**Typical patterns:**

* Indicates mature, trusted agents
* Represents true automation value
* Should grow as agents prove reliable

### Slack Runs

Runs triggered through Slack connection.

**Typical patterns:**

* Shows collaboration and accessibility
* Common for team-facing agents
* Indicates good connection with daily workflows

***

## Interpreting Trends

### Growing Usage

Increasing runs and active users indicates:

* Successful adoption of automation
* Value being recognized by the team
* Opportunity to expand to new use cases

### Declining Usage

Decreasing activity might mean:

* Initial excitement wearing off
* Agents not meeting needs
* Process changes making agents obsolete
* Team members may need more support or better agents

### Steady Usage

Consistent activity suggests:

* Stable, reliable automation
* Agents well-matched to workflows
* Opportunity to optimize or expand

***

## Benchmarking

While every organization is different, consider these general benchmarks:

| Metric              | Starting Out  | Maturing | Advanced |
| ------------------- | ------------- | -------- | -------- |
| Completion Rate     | 70-80%        | 85-95%   | 95%+     |
| Scheduled vs Manual | 20/80         | 50/50    | 70/30    |
| Active Users        | \<25% of team | 25-50%   | 50%+     |

***

## Things to Know

* Metrics reflect activity within the selected time period
* Compare similar time periods for meaningful trends
* Seasonal variations may affect some metrics
* Focus on trends rather than absolute numbers