From bca602f4b02fa56f83617f040f85df005f54e1c4 Mon Sep 17 00:00:00 2001 From: ZeinebMegaadi Date: Wed, 15 Apr 2026 15:13:35 +0100 Subject: [PATCH 1/2] docs: add monitor lifecycle explanation to README --- README.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/README.md b/README.md index 786e6102b..7d845ee5b 100644 --- a/README.md +++ b/README.md @@ -112,6 +112,15 @@ Feel free to ask questions or share your ideas - we'd love to hear from you! If you would like to sponsor an additional feature, [see this page](https://checkmate.so/sponsored-features). +## Monitor Lifecycle + +1. A monitor executes a check (HTTP / ping / port / hardware via Capture agent) +2. The result is stored (success/failure + response time) +3. The system evaluates recent checks to determine status (up/down) +4. If failure threshold is reached, the monitor becomes "down" +5. If it stays down, an incident is created automatically +6. Notifications are triggered based on configuration + ## Screenshots

From d532d133716b9264e0cdaf795e57e356c000693e Mon Sep 17 00:00:00 2001 From: ZeinebMegaadi Date: Thu, 16 Apr 2026 18:33:44 +0100 Subject: [PATCH 2/2] fix(lifecycle updated) --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 7d845ee5b..2180e35b4 100644 --- a/README.md +++ b/README.md @@ -116,9 +116,9 @@ If you would like to sponsor an additional feature, [see this page](https://chec 1. A monitor executes a check (HTTP / ping / port / hardware via Capture agent) 2. The result is stored (success/failure + response time) -3. The system evaluates recent checks to determine status (up/down) -4. If failure threshold is reached, the monitor becomes "down" -5. If it stays down, an incident is created automatically +3. Recent check results are evaluated against the monitor's configured status change threshold +4. If the monitor's status change threshold is met and the current status is not equal to the previous status, the monitor's state changes (e.g. `initializing`, `up`, `down`, `breached`) +5. Upon a state change: an incident is either created or resolved, depending on the monitor's current status 6. Notifications are triggered based on configuration ## Screenshots