Acknowledge timeout
Acknowledge timeout automatically moves an acknowledged incident back to triggered state if it isn't resolved within a set time.
Last updated
Acknowledge timeout automatically moves an acknowledged incident back to triggered state if it isn't resolved within a set time.
Acknowledge timeout is a time limit you set on an integration. If an acknowledged incident isn't resolved within that window, Spike moves it back to triggered state and resumes alerting. This is useful when someone acknowledges an incident but gets pulled into other work before resolving it.

It depends on how critical the integration is. A shorter timeout means faster re-alerting on unresolved incidents.
Critical integrations — 20 minutes
Severe but non-critical integrations — 60 minutes
Non-critical integrations — leave it blank
You don't need a timeout on every integration.
Avoid short timeouts like 5 or 10 minutes. They generate more alerts than your team can act on and increase alert fatigue.
Last updated