# Hanzo Dashboards — Hanzo AI

> Grafana-compatible dashboards for infrastructure, application, and business metrics.

Traces · observations · scores

# Hanzo Dashboards

A dashboard is a saved query

[GitHub](https://github.com/hanzoai/dashboards)

Dashboards — Hanzo

[Logs](https://hanzo.ai/cloud/logs)[Metrics](https://hanzo.ai/metrics)[Dashboards](https://hanzo.ai/dashboards)[O11y](https://hanzo.ai/o11y)[AI Metrics](https://hanzo.ai/cloud/ai-metrics)[Billing](https://hanzo.ai/billing)[Plans & Pricing](https://hanzo.ai/cloud/plans)[Sessions](https://hanzo.ai/cloud/sessions)

- gatewayReady
- payments-apiReady
- checkout-webBuilding
- docs-siteReady

Every request enters here, so the limiter does too.

`api.hanzo.ai/v1/o11y/dashboards`[Open in the console](https://hanzo.ai/home)

Example project. Every name in it is one you would give your own.

Paste and ship

Paste this into any agent. It reads the skill manifest and calls Dashboards from there.

Agent promptapi /v1/o11y/dashboardsCopy

```
Read https://hanzo.ai/skill.md and use Hanzo Dashboards in my project. Start with: hanzo o11y dashboards list
```

## What a dashboard is made of

Widgets, monitors, saved views and score configs — all of them queries over one store.

01

### Widgets over your own data

A widget names what to select and how to group it. Because it queries the store that already holds your traces, a chart cannot drift from what happened.

02

### Monitors

A saved query you want watched rather than looked at. Same definition as the widget beside it, kept in one place so the alert and the chart cannot disagree.

03

### One store, not two

Traces, observations and scores live in the service that serves the dashboards. There is no export step, no second database to keep in sync, and nothing to reconcile after an outage.

04

### Saved table views

The columns, filters and sort you arrived at are a preset you can name and return to. Presets belong to the project, so a colleague opens the view you meant.

05

### Scores are yours to define

Score configs say what good means for your application — a rating, a label, a number from an evaluator. Dashboards then aggregate the thing you actually care about.

06

### Permission per category

Access is granted by category rather than per object, and the boundary is the organization on your token. Reading somebody else's project is not a URL away.

TracesThe thing being queried

ScoresYours to define

MonitorsSaved and watched

SSOIAM login

Open source royalty

### 20% to the author of the code that runs

Verify that you own a repository, and every org that deploys a project built from it pays you 20% of its metered spend, accrued each period.

[How authors are paid](https://hanzo.ai/oss)[Our repositories](https://hanzo.ai/open-source)

## Start from a trace

Send traces from your application, then build the view that answers the question you keep asking about them.

[View on GitHub](https://github.com/hanzoai/dashboards)

Related capabilities

[LogsSearch every line](https://hanzo.ai/cloud/logs)[MetricsTime series & SLOs](https://hanzo.ai/metrics)[O11y](https://hanzo.ai/o11y)

## Get Dashboards

Composable dashboards

License: Apache-2.0[hanzoai/dashboards](https://github.com/hanzoai/dashboards)

[Deploy to Cloud](https://platform.hanzo.ai/deploy)