High cardinality

Prometheus pays for high cardinality metrics at write time. ClickHouse pays at query time. Neither solves it : they fail differently. Here's how to choose.

What actually breaks when teams add high cardinality metrics and why those failures are hard to avoid unless the system is built for it.

High cardinality in time-series databases can slow queries, increase storage costs, and strain indexing. Here’s how it impacts performance and scaling.

High cardinality data can quietly drive up storage costs and slow down performance. Here’s why it happens and what you can do to fix it.

High cardinality can overwhelm monitoring systems, leading to slow queries and blind spots. Here’s why it matters and how to handle it effectively.

The software monitoring world is broken because of a TSDB. We deserve a TSDW

Ths single most important thing to get better at your software monitoring journey

Dissecting the RCA of Alerting - Reliability, Correlations, Actionability

If you want to bring down your monitoring costs, you need to shake up a decision paralysis in engineering

Fulfill all your food delivery orders this December 31st by taming High Cardinality data with Levitate 😉

What is a Time Series Data Warehouse? How does it help in your monitoring journey? How does it differ from a Time Series Database? That and more

Report from SRE Day 2023, where Piyush Verma - CTO Last9, gave a talk on Unwiring High Cardinality

Using 'Sharding' to tame High Cardinality data for Levitate - Our Time Series Data Warehouse

Engineering innovation to solve high cardinality with Levitate - a multi-part series