DevOpsInterviewPrep logo
← Observability, SLOs & Reliability / 40
hardNewDatadogGoogleUber

Latency regressed 30 percent and traces show the time is inside one service. Now what?

Tracing tells you which service and which span. It stops at the function boundary, and that is exactly where a CPU regression lives. Continuous profiling is the layer most teams do not have when they need it.

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.

Tracing tells you which service and which span. It stops at the function boundary, and that is exactly where a CPU regression lives. Continuous profiling is the layer most teams do not have when they need it.

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 trackYour architecture is queues and consumers. The golden signals assume request and response. Now what?Next in this trackYour OTLP endpoint returns HTTP 200, but spans are missing. Should the Collector retry the batch?Popular right nowWhat happens at the kernel level on SIGTERM versus SIGKILL, and why might a container ignore SIGTERM?
DISCUSSION · 0

Nothing here yet. Say how you would answer it.