Codestin Search App

Thanks to visit codestin.com
Credit goes to monops.dev

Deploy an agent

Incident lifecycle

One incident, start to signed-off.

Six stages in one system. Four of them run without anyone watching; two are deliberately yours. Pick any stage for what it actually does and the defaults it ships with.

The engine sees it first

detect · engine

Risk crosses a floor, or an endpoint check fails twice in a row. Either way the state machine moves with nobody watching.

failures to open: 2
risk floors: 35 / 60 / 82

One incident, not forty

A fingerprint of the failure signature dedupes the alert, and flap suppression holds the line so a bouncing machine never becomes a page storm.

dedupe: signature fingerprint
flap window: 300s

L1 to L3 without a second vendor

escalate · policy

No acknowledgement inside the timeout and the policy climbs a level by itself, routing to the next rotation on call.

timeout per level: 300s
ceiling: L3

The evidence is already attached

diagnose · engine

The flight recorder window is flushed, the guilty process tree resolved, and cluster events from the same minutes joined to the incident automatically.

recorder window: 5 min · 300 frames
process tree: up to 32 levels

Closed when the signal says so

resolve · your team

Recovery has to hold across successive sweeps before the incident closes, so a half-healed machine never gets marked green.

sweeps to confirm: 4
stale incidents reaped: 600s

Written while it is still true

post-mortem · your team

A timeline assembled from the evidence, carrying the verdict on the prediction itself: called or missed, and by how much warning.

verdict: called / missed + lead
evidence retained: 90 days

Stages 01 to 04 run with nobody watching. Stages 05 and 06 are where your team decides what it meant.

Deploy an agent→