Skip to content

Intermittent Failure Capture

Capture evidence during irregular failure episodes so elusive problems can be diagnosed after the episode disappears.

The Diagnostic Story

Symptom: The failure appears, the system is checked, the failure has disappeared. The investigation finds nothing because the failure state was erased by recovery, cleanup, or the simple passage of time. Anecdotal episode reports accumulate but diagnosis never advances because no two descriptions quite match and there is no evidence from the actual failure moment. The same unknown root cause recurs at irregular intervals with no path to resolution.

Pivot: Instrument the system, process, or human reporting workflow so that when an intermittent episode occurs, the relevant state, context, sequence, and traces are captured inside a protected window before evidence disappears, then routed into a diagnostic follow-up path that persists after normal operation resumes.

Resolution: Episodes become diagnosable because the evidence survives the failure, and root cause ambiguity decreases as captured context links state to sequence. Corrective action becomes possible and better calibrated because it is based on observed failure conditions rather than reconstructed guesses. Diagnosis is less disruptive because the capture mechanism does the work during the episode rather than requiring a recreation attempt later.

Reach for this when you hear…

[automotive engineering] “The check engine light comes on during the commute and goes off before I reach the dealer — we need a freeze-frame capture in the ECU so the code is still there when we plug in the scanner.”

[site reliability engineering] “The error rate spike lasts four minutes and our metrics retention is five-minute rollups — we're throwing away the exact window we need to diagnose it.”

[clinical neurology] “The patient's seizures happen twice a month for thirty seconds — we need a wearable EEG that records continuously and flags the episode, because they'll never be seizing in my office.”

Mechanisms / Implementations

  • Automatic Diagnostic Capture
  • Black Box Log
  • Flight Recorder
  • Incident Snapshot
  • Post-Episode Evidence Review
  • Rare Event Monitor
  • Symptom Diary
  • Trigger-Based Debug Trace

Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.

Built directly on (2)

Also references 11 related abstractions

Variants

Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.

Trigger-Based Diagnostic Capture · recognized

Episodic Symptom Capture · recognized

Flight-Recorder Failure Capture · recognized

Rare Event Evidence Capture · recognized