hanzo-dev
a0f35ec7b5
The README already said "archived, superseded by hanzoai/o11y". That is where
the repository went; it is not where the ROUTES went, and a caller of
/v1/metrics/batch reading it learns nothing actionable.
NOTICE says the rest. The three probes kept their addresses and moved into
hanzoai/cloud's o11y package (apps/o11y/signals.go), each now naming the durable
store that holds its signal. The other eight — the ingest and query doors for
all three signals — are retired rather than ported, because they were a second
way to write and read what hanzoai/o11y already stores on its columnar plane,
and o11y ingests the SAME luxfi/metric MetricBatch wire, so no producer has a
shape to change, only an address.
It records what was MEASURED before deleting them, because "nobody uses it" is
the claim that is wrong most often: production reported records=0, spans=0 and
count=0 from every query door, and a git-grep sweep of every repository in the
hanzo, lux and zoo orgs found no caller outside this module and three derived
copies of the API document. Zero producers, zero consumers, zero rows.
And it closes out the last commit written here, which could never be pushed
because an archived repository is read-only. GET /v1/traces/{id} does not need a
home: hanzoai/o11y has served GET /v1/o11y/traces/{traceId} all along, over the
durable store, with the waterfall beside it. Obsolete, not pending — the word
matters, because "pending" is a debt and this is not one.
hanzoai/cloud was the only importer and no longer imports it. The remaining
go.mod lines across the estate are all // indirect.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Archived. Hanzo Metrics is superseded by hanzoai/o11y, which serves metrics, logs and traces from one subsystem at
/v1/o11y/*. Nothing new should depend on this repository; it is kept read-only for history. What follows describes the retired product.NOTICE says where each of the eleven routes went, what was measured before the eight duplicate doors were deleted, and why the last commit written here is obsolete rather than pending.
hanzoai/cloudwas the only importer and no longer imports it.
Hanzo Metrics
High-performance time-series metrics database.
Overview
Hanzo Metrics is a fast, cost-effective time-series database optimized for monitoring AI infrastructure. Store billions of data points with excellent compression and query performance for your observability needs.
Features
- High Performance: Fast ingestion and queries
- Efficient Storage: 10x compression vs alternatives
- PromQL Compatible: Use familiar Prometheus queries
- Long-term Storage: Cost-effective retention
- High Availability: Clustering and replication
- Multi-tenancy: Isolated tenant data
Quick Start
docker run -p 8428:8428 hanzo/metrics
Documentation
See the documentation for detailed guides and API reference.
License
MIT License - see LICENSE for details.