Data Monitoring / Alerting & Observability Design
Observability: Threshold hysteresis
A metric oscillates around its threshold and repeatedly opens and closes incidents. Plot the boundary crossings and current recovery criteria.
Environment and inputs: Platform-neutral monitoring design with Prometheus and OpenTelemetry examples; syntax and signal availability depend on the deployed stack.
Failure scenario
A metric oscillates around its threshold and repeatedly opens and closes incidents. Confirm the cause before choosing a fix.
Evidence to collect
Plot the boundary crossings and current recovery criteria. Record the time, affected scope and a healthy comparison interval.
Fix the confirmed cause
Use appropriate sustained conditions or separate recovery thresholds and verify detection delay remains acceptable. Write the expected result first. Change one relevant setting at a time.
Check the result and hand over
Repeat the check for threshold hysteresis using the same scope and a representative interval. Check that the symptom is resolved, expected records are present and downstream results are correct. If coverage, correctness or latency worsens, restore the recorded configuration through the agreed rollback process.
Scope and precautions
Prefer read-only access and limit queries to the relevant period or dataset. This example has not been tested on your systems. Test changes in an approved environment. Keep credentials and sensitive data out of shared evidence.