What a metric is here
A row in a column store rather than a series in a store of its own.
rate(http_requests_total[5m])a spike is the start of a question
A row in a column store rather than a series in a store of its own.
01 / 06
Metrics go where the logs and traces already are — Hanzo Datastore, a column store. Nothing to run beside it and nothing to keep in sync with it.
02 / 06
Bring the PromQL you already wrote, or assemble the query in the UI without learning it. Both compile to the same thing.
03 / 06
Per-model, per-route, per-tenant. A column store counts distinct values for a living, so a label that would multiply series in a time-series database is just another column here.
04 / 06
A spike on a chart is the start of a question, not the end. Click it and you are in the traces for that window, because they were never in a different system.
05 / 06
You write the query, look at it, then keep it as a rule. What pages you is something you have already seen return the answer you expected.
06 / 06
Every query carries the org from your token, so one deployment serves many tenants and no panel can read across them.
rate(http_requests_total[5m])onequeryPaste and ship
Paste this into any agent. It reads the skill manifest and calls Metrics from there.
Read https://hanzo.ai/skill.md and use Hanzo Metrics in my project. Start with: hanzo metrics queryThe service the session above is changing.
A build is running from the last commit on main.
Static, published by the same pipeline as the rest.
traces for that window · gateway
Example project. Every name in it is one you would give your own.