Cardinality Governance
Purpose
How the platform governs cardinality — the primary cost and stability risk.
Rules
- Any new metric/label/trace attribute ships with a cardinality estimate in the PR.
- Default to drop/hash before keep when source cardinality is unbounded.
- High-churn values (IDs, raw timestamps) are an automatic stop → logs/traces/exemplars.
Gate
Reach for the Cardinality Budget Calculator skill before adding labels to any production-bound Alloy/Prometheus/OTel config.
Top contributors (rolling)
[stub: cardinality-top-contributors]— fill this in. Greppable doc-debt marker.
Related
Local graph
Linked from 7 notes
5 — Label & Attribute Schema Design
Cardinality budget, naming conventions, and the high-churn label traps that turn a cheap metric into a production incident — the design discipline for the labels semantic conventions don't already cover for you.
Metrics Instrumentation Guide
How to instrument a service for **metrics** on the ShipSolid observability platform.
Naming & Label Schema
The canonical label and resource-attribute schema every signal must follow.
Signal Catalog
Canonical catalog of the signals the platform supports and the golden signals every service should
Onboarding Checklist
The definitive checklist for taking a service from zero to fully observable.
07 — Cost & Governance
Keeping the platform affordable and well-governed: budgets, cardinality, vendors.
Ingest Budget by Team
Ingest budget allocation per team and current consumption.
Related notes
Ingest Budget by Team
Ingest budget allocation per team and current consumption.
Integration Specifications
Specifications for integrations between the platform and external systems (IRM, BigPanda, SNOW,
Monthly Cost Reports
Monthly observability cost reports.
07 — Cost & Governance
Keeping the platform affordable and well-governed: budgets, cardinality, vendors.