Latency SLOs Done Right
Talkat SREcon19 Europe/Middle East/Africa · on Wednesday, 2019-10-02· at 11:30· Track 1: The Liffey B·
summary
Claim: percentiles alone mislead when aggregating across nodes and long windows, producing huge errors (example: ~68% error from naive averaging). Practical alternatives are three methods: keep raw logs (accurate but costly), use counter metrics that count requests below a chosen threshold (cheap, requires fixed thresholds), or store HDR histograms/DDSketch-style summaries for efficient, aggregatable distributions. Benchmarks show sketches and HDR implementations achieve ~0.01–0.25% accuracy and performant aggregation; Circonus’s histogram tooling demonstrates this works in production.
AI-written summary · about
chapters (9)
- 0:00Start
- 4:40What is an SLO?
- 13:34Latency SLOs via Log Data
- 15:13Latency SLOs with Counter Metrics
- 16:16(2) Latency SLOs via Counter Metrics
- 18:38HDR Histograms
- 19:40HDR Histogram Data Structures
- 22:01HDR Histogram Metric
- 22:16Latency SLOs with Histograms
related talks
31mLatency SLOs Done Right
32mSoftware Performance: A Shape Not a Number
36mHow to Include Latency in SLO-based Alerting
30mTechniques for SLOs and Error Budgets at Scale
39mThe Many Ways Your Monitoring Is Lying to You
37mLies, Damn Lies, and Metrics
38mTechniques and Tools for a Coherent Discussion about Performance in Complex...
43mFinding the Golden Signals with Prometheus
