Files
zooqueen 75c4f1f641 One product answers with one name, route, command and docs page
The CLI lines on the product pages were written from the product name -- hanzo
dns zones, hanzo kms keys -- and several were not commands the binary has. So the
command moves into lib/product.ts, which assembles the rest from what is already
stated: the catalog names the product and its route, pages.json names what the
catalog does not carry, and products-metadata answers for docs, where null means
docs publishes nothing and the link drops.

Every CLI line in that table was run against the binary. A product absent from it
has no command and its page prints none; nothing composes a verb out of a name.
Both blocks that draw it import the Product type rather than declaring their own,
which leaves the table the only place a command can be written.

The catalog also moves out of package.json into pnpm-workspace.yaml, where pnpm
reads it, so the versions are stated once.
2026-09-06 23:18:24 -07:00

80 lines
3.5 KiB
TypeScript

'use client'
import { ArrowRight, BarChart3, Clock, Database, Gauge, Layers, Search, Zap } from 'lucide-react'
import { ProductLanding } from '@/components/product/ProductLanding'
import { ProductFooter } from '@/components/products/ProductFooter'
/**
* Hanzo Metrics, through the ONE product kit.
*
* The largest cluster left: TWELVE pages — engine, gateway, guard, ingress,
* jin, metrics, o11y, operator, sentinel, skills, telemetry, visor — at 85%+
* identical className sets, each a hero, a six-card grid and a call to action
* written out again. All twelve pass one typed props object to
* `ProductLanding`. See LLM.md, "Tailwind is NOT gone".
*
* EVERY WORD IS THE ONE THAT WAS HERE. ProductFooter came out of the final
* card's `max-w-3xl` wrapper, where it had been rendering narrower than on
* every other product page.
*/
export default function HanzoMetricsPage() {
return (
<>
<ProductLanding
badge={"metrics.hanzo.ai"}
badgeIcon={BarChart3}
title={"Hanzo Metrics"}
tagline={"The metrics half of Hanzo O11y"}
lede={"Metrics used to be its own database here. It is now a subsystem of Hanzo O11y, which serves metrics, logs and traces from one column store — so a counter and the trace that incremented it are one query. Reach for this page when the question is a number over time; the rest of O11y is where that number leads."}
ctas={[
{ label: "View on GitHub", href: "https://github.com/hanzoai/metrics" },
]}
what={{
title: "What a metric is here",
sub: "A row in a column store rather than a series in a store of its own.",
pillars: [
{
icon: Database,
title: "One store, not four",
body: "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.",
},
{
icon: Search,
title: "PromQL, or the builder",
body: "Bring the PromQL you already wrote, or assemble the query in the UI without learning it. Both compile to the same thing.",
},
{
icon: Zap,
title: "Labels you would not dare add",
body: "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.",
},
{
icon: Layers,
title: "The number leads somewhere",
body: "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.",
},
{
icon: Gauge,
title: "Alerts are saved queries",
body: "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.",
},
{
icon: Clock,
title: "Scoped to your org",
body: "Every query carries the org from your token, so one deployment serves many tenants and no panel can read across them.",
},
],
}}
finalCta={{
title: "Send a metric, then follow it",
buttons: [
{ label: "View on GitHub", href: "https://github.com/hanzoai/metrics" },
],
}}
/>
<ProductFooter slug={"metrics"} name={"Metrics"} />
</>
)
}