Dashboard & Metrics
Orchestra exposes operational and AI consumption metrics at two levels: an in-app dashboard for a live operational overview, and the .NET Aspire dashboard for deep infrastructure and OpenTelemetry telemetry.
Dashboard
The Dashboard is the first screen after entering a workspace. It provides a high-level snapshot of everything happening across agents, tickets, and jobs — without navigating away.
Operations
The Operations row surfaces the most time-critical numbers at a glance:
| Metric | Description |
|---|---|
| Active Agents | Currently busy agents out of total configured agents (e.g. 0 / 10) |
| Jobs Today | Number of jobs started within the current calendar day |
| Success Rate (7d) | Percentage of completed jobs over the last 7 days, with a completed / failed breakdown |
| Jobs In Progress | Jobs currently in a Running or Waiting state right now |
Tickets
| Metric | Description |
|---|---|
| Total Tickets | All tickets currently synced across every connected integration (Jira, GitHub, GitLab) |
| Resolved by Agents (7d) | Unique tickets that an agent successfully acted on in the last 7 days |
Code Impact CLI agents only
Tracks the concrete code changes produced by CLI-type agents (Coding Agent, Agentic Search Agent):
| Metric | Description |
|---|---|
| Lines Added | Cumulative lines of code added by CLI agents over the selected period |
| Lines Removed | Cumulative lines of code removed by CLI agents |
| Files Changed | Total distinct files modified across all CLI agent job runs |
AI Consumption (7d)
A compact summary of AI API usage for the workspace, with a link to the full AI Usage page:
Combined input + output tokens consumed by all agents in the last 7 days.
Total number of model inference requests made across all agents and jobs.
System
A quick inventory of the workspace configuration — how many agents, skills, and workflows are set up:
| Metric | Description |
|---|---|
| Agents | Number of agents configured in this workspace |
| Skills | Number of skill folders created |
| Workflows | Number of automation workflows defined |
Charts
A bar chart showing daily job volume over the last 7 days, helping you spot activity spikes or quiet periods.
A live list of the most recently run jobs with status badges and direct links to their detail views.
AI Usage
The AI Usage page gives a detailed breakdown of model consumption across the workspace. Navigate here from the Dashboard via View AI Usage → or through the workspace navigation.
Summary Cards
The top row provides workspace-wide totals for the selected time window (24h / 7d / 30d / 90d / All):
| Card | Description |
|---|---|
| Total Tokens | Combined input + output token count for the period |
| Input Tokens | Tokens sent to the model (prompts, context, tool schemas) |
| Output Tokens | Tokens generated by the model (responses, tool call arguments) |
| API Calls | Total number of model inference requests made in the period |
| Lines Added | Lines of code added by CLI agents during the period |
| Lines Removed | Lines of code removed by CLI agents during the period |
Filters
Narrow the data to a specific subset using the filter bar:
Filter metrics by AI provider — Azure OpenAI, Ollama, or GitHub Copilot CLI — to compare cost profiles side by side.
Drill into a specific model deployment (e.g. claude-haiku-4.5, gpt-4o-mini) to see its individual consumption share.
Charts
A bar chart grouping total token usage by model. Quickly identify which model is responsible for the bulk of consumption.
A line chart showing token throughput over the selected period. Useful for identifying peak usage windows and correlating spikes with specific jobs.
Time window selector: Use the 24h / 7d / 30d / 90d / All buttons in the top-right corner of the AI Usage page to change the reporting window. All summary cards and charts update in sync.
Aspire Dashboard & OpenTelemetry
In addition to the built-in metrics pages, Orchestra ships full OpenTelemetry instrumentation for every .NET service. When running under .NET Aspire, all telemetry is automatically routed to the Aspire dashboard.
The .NET Aspire dashboard surfaces AI usage metrics — token counts, model latency, and request volume — collected via OpenTelemetry from the API and Worker services.
End-to-end traces span from the API through the Worker service and into external AI provider calls, making it straightforward to diagnose slow or failing agent executions.
All services emit structured logs captured by the Aspire dashboard, searchable and filterable by service, severity, and trace ID.
Container health, port bindings, environment variables, and resource graphs for every service — API, Worker, PostgreSQL, Redis, and Node.js services — are visible in the Aspire console.
Accessing the Aspire dashboard: When you run aspire run, the Aspire dashboard starts automatically. The URL is printed in the console output (typically http://localhost:15888). No additional configuration is needed — all services register with the Aspire telemetry collector automatically.