DevOpsInterviewPrep logo
← Observability, SLOs & Reliability / 32
mediumNewRazorpaySwiggyDatadog

We can't afford full logging on our hottest service. Sample the logs or filter aggressively, and what do we lose?

Sampling keeps proportions and loses rare individuals; filtering keeps chosen classes complete and loses whatever you misclassified. Decide retention at write time, keep counters always, rehydrate the rest.

Updated Sep 2026 · Grounded in researched DevOps, SRE and platform engineering interview loops, written to a senior-engineer editorial bar, and never padded to hit a word count.

Sampling keeps proportions and loses rare individuals; filtering keeps chosen classes complete and loses whatever you misclassified. Decide retention at write time, keep counters always, rehydrate the rest.

20 answers per topic instead of 10, and your progress kept · no cardor unlock all 390 remaining answers · ₹2,000 / $25
UP NEXT ON YOUR JOURNEY
Next in this trackCould we use distributed traces as regression tests for request flows, not just for debugging?Next in this trackWho monitors the monitoring? Design meta-monitoring so a dead collector never hides an outage.Next in this trackYour severity matrix looked tidy until a real incident. How do you define severities people actually apply?
DISCUSSION · 0

Nothing here yet. Say how you would answer it.