Skip to content
Astera Technology

Distinguish consecutive bad samples from elapsed failure time

Apply a three-sample trigger without claiming three minutes of known failure.

Fix the sample-based trigger

Local synthetic rule triggers after three consecutive observed bad samples. Samples are every two minutes. A healthy observation resets the streak. Triggering records a sample condition; no event start or end between observations is known.

Streak state table
TimeSampleBad streak
10:00Bad1
10:02Bad2
10:04Healthy0
10:06 /10:08 /10:10Bad /bad /bad1 /2 /3
Download editable CSV ↓

Walk the streak state

  1. Read samples in order
  2. Reset on observed healthy
  3. Trigger when streak reaches three

A missing sample breaks the evidence of consecutiveness under this supplied rule.

When does the trigger occur, and what time span joins its bad points?

Show the worked answer

10:10. Its three bad points span four minutes from 10:06 to 10:10, not six minutes of proved continuous failure.

Keep duration uncertainty

Filled decision checks
CaseDecisionReason
Bad,bad,healthyNo triggerStreak resets
Bad,bad,bad at two-minute spacingTrigger on thirdThree samples span 4 min
Download editable CSV ↓

Keep sample timestamps and the trigger rule version. A duration-based alert would need a separate definition and observations.

Related resources