Appears in: Telemetry Ingestion Pipeline — this is §8 of the full design, split into its own file so the root stays a table of contents.
8. Quick-Reference Cheat Sheet
Fan-in at scale → stateless gateway + persistent gRPC connections + connection pooling
Backpressure → gRPC RESOURCE_EXHAUSTED (429) → agent WAL absorbs burst
Burst absorption → Kafka between gateway and processor; 2-4h retention
Cardinality enforcement → approximate counting (HyperLogLog) at processor; reject early
Tail sampling → hash-partition by trace_id in Kafka; assemble per-partition
Multi-tenancy → enforce at: network / auth / gateway / processor / storage (all layers)
Deduplication → at-least-once + TSDB fingerprint dedup (metrics), hash dedup (logs)
Out-of-order samples → Mimir out-of-order ingestion window (up to 1h)
End-to-end SLO → synthetic canary batch every 60s through the full pipeline
Self-observability → consumer lag (Kafka) is the single most important operational metric
Delta vs cumulative → enforce cumulative at agent SDK; deltaToCumulative processor = stateful + restarts cause counter resets
k8s enrichment → enrich at agent (DaemonSet downward API); avoid per-span k8s API calls
Data tiering → ingester (hot, 2h) → object store (cold) → compactor (merge + dedup RF=3 blocks)
Global topology → regional writes + async replication → global query tier; never single global cluster at 10M agents
Kafka producer gotcha → max.message.bytes=1MB default; split large trace batches at gateway before produce
Local graph
Related notes
Chapter 1 — Telemetry Ingestion Pipeline
Principal/Staff-level design of a high-throughput telemetry ingestion pipeline — requirements, architecture, deep dives, and trade-offs at 10x scale.
Q1: 500M Samples/Sec, Zero Drop on Rolling Deploy
Full principal-level solution: design a telemetry ingestion pipeline for 500M metric samples/sec from 100K services globally with a zero-drop guarantee during rolling deployment of the ingestion tier.
Q10: Self-Service Tenant Onboarding With Zero Platform-Team Involvement
Full principal-level solution: design a self-service tenant onboarding API for a telemetry pipeline that protects shared infrastructure from a misbehaving new tenant on day one.
Q8: Counters Resetting to Zero After an OTel SDK Upgrade
Full principal-level solution: diagnose and fix a tenant's dashboards showing counters reset to zero every few minutes after an OTel SDK upgrade, without requiring instrumentation changes.