DevOps Interview DropAdvanced TierScenario+50 XP on read
How do you investigate a latency spike that lasted only five minutes?
#Observability#Debugging#Performance#Incident
Core Summary
A latency spike that self-heals is usually a transient event: a brief resource spike (GC pause, momentary CPU burst), a traffic pattern (a batch job, a cache miss thundering herd), or a brief dependency issue. The challenge is that by the time you start investigating, it is gone. So you have to know what to capture in real time and look backward.
Hints
Hint 1: Self-healing usually means the problem was transient or self-correcting
Hint 2: Capture traces during the spike; investigate after
Hint 3: Check: GC pauses, CPU bursts, traffic shape, dependency health
Reported in interviews at Google, Meta, Amazon