Custom Dashboards
Custom dashboards give every team a live view of the signals they need to operate AI systems: traces, evals, cost, latency, model health, tool behavior, workflow status, and business KPIs.
What Dashboards Do
Dashboards combine widgets such as time series, tables, scorecards, histograms, heatmaps, trace lists, eval scorecards, cost views, and process-unit status panels.
When To Use Them
Use dashboards when you need a repeatable view for:
- Agent reliability.
- Model latency and quality.
- Token spend and cost attribution.
- Eval score trends.
- Workflow health and SLA status.
- Customer or product outcome monitoring.
Prerequisites
- Send data through a concrete integration path: OpenTelemetry, REST/HTTP events, JavaScript or pixel tracking, Claude Code, OpenAI Agents, or another ingestion method.
- Include stable dimensions such as
workflow,agent,model,team,customer_tier, orbusiness_unit. - Decide who the dashboard is for: engineering, product, support, executives, or ML teams.
Step-By-Step Setup
- Open Dashboards.
- Create a dashboard or duplicate an existing template.
- Add widgets for the core question you want to answer.
- Filter by workflow, model, team, or environment.
- Add drill-down links to traces, evals, alerts, or process units.
- Save and share with the owning team.
Example Widget Definition
What Appears In The Console
Dashboards show live widgets with drill-down paths into the trace, model, eval, alert, pipeline, and process-unit records behind each metric.
Common Mistakes
- Building one large dashboard for every persona.
- Showing infrastructure health without AI quality or business impact.
- Missing drill-downs from KPI to trace.
- Grouping by fields that are unstable or missing.