Observability Practical By Samson Tanimawo, PhD Published May 3, 2026 4 min read

The Cardinality-By-Team Dashboard

Surface cardinality contributions per team. The dashboard, the conversation it triggers, and the savings teams typically achieve.

Panels

Per-team total cardinality. Time series count by team.

Top contributing metrics per team. The optimisation candidates.

Trend over 90 days. Growth visible; spikes investigated.

The conversation it triggers

Teams compare. Outliers ask questions; learnings spread.

Healthy competition: teams optimise to lower their cardinality.

Unhealthy: cardinality becomes status. Avoid the optimisation-for-show pattern.

Typical savings

Visibility alone produces 20-30% reduction in the first quarter.

Teams identify and remove unused metrics. Stale labels removed.

Compounding: year-over-year, the dashboard pays back in observability cost.

Operating the dashboard

Auto-refresh weekly. Trends visible without manual queries.

Per-team owner. Surfacing happens; teams own remediation.

Quarterly review with finance and engineering leadership.