Skip to content

Case study: Metrics monitoring and alerting

Design a planet-scale time-series metrics and alerting system with Gorilla chunk compression, cardinality protection, and resilient alerting.

35 min9 steps

By the end you can
  • Estimate active time-series cardinality, sample ingestion rate, and storage savings from Gorilla delta-of-delta and XOR compression
  • Explain why label cardinality — not sample rate — is the primary scaling limit of a time-series database
  • Design a decoupled ingestion, in-memory head chunk, and step-aligned query caching pipeline
  • Predict how the monitoring and alerting pipeline survives incident query storms, ingester restarts, and alert flapping

Pin down what a metrics system must survive

Features

  • 10 s samples; label/range queries; rollups; alert ticks 15-30 s

Targets

  • 85-95% writes; millions samples/s; query p99 <500 ms

Isolation

  • Never block production; alerts survive dashboard storms

What distinguishes a time-series metric from a structured log event?

Answer this step to continue.