Documentation: v4.3.1 - kuvasz-uptime.dev
docker pull kuvaszmonitoring/kuvasz:4.3.1
Important
There is a short questionnaire about Kuvasz in general, which you can fill out anonymously. It takes only a few minutes, and your feedback is highly appreciated as it helps me to focus on the most important features and improvements in the future. You can find it here.
Thanks, Adam
Fixes
- Push monitors burned through their failure count threshold in seconds: a missed heartbeat was counted as a new failure on every check, and since Kuvasz evaluates the push monitors every 5 seconds, a failure count threshold higher than 1 only delayed the alert by a few seconds, instead of tolerating as many missed heartbeats as it was set to. From now on every missed heartbeat counts only once.
- Push monitors could go down right after a maintenance window or a restart: the deadline of the next countable missed heartbeat was calculated from the last heartbeat only, so whenever that heartbeat was already long overdue - after a maintenance window of the monitor, after a restart or a longer downtime of Kuvasz itself, or after a monitor was paused for a while - the checks credited all the heartbeats missed in the meantime at once, burning through the whole failure count threshold within seconds. A missed heartbeat is now counted at most once per heartbeat interval, no matter how far behind the last heartbeat is.
- Changing the failure counting of a push monitor resets its pending failures: the failures recorded so far were counted against the monitor's previous settings, so they weren't comparable to the updated ones - lowering the failure count threshold below the number of already recorded failures even left behind a counter that nothing consumed any more, delaying the detection of the next outage. Updating the heartbeat interval, the grace period or the failure count threshold of a monitor now clears them, and its failure counting starts from scratch. Every other setting (its name or integrations, for example) leaves the already recorded failures intact, so editing a monitor during an outage doesn't delay its alert.
Full Changelog: 4.3.0...4.3.1