I know this is on the roadmap, but found no feature request tracking it. https://updown.io/doc/how-pulse-cron-monitoring-works states:
At a later time it'll be possible to specify a string to expect in this body and consider the check as DOWN if a pulse was received without the configured string. For example in addition to detecting missing pulse, you could indicate if the task terminated "sucessfully" or with warnings/errors, and ask updown to match on the presence of the "successfully" string. This way you also get alerts and can check the body for controlled failure cases.
This would be incredibly useful. I currently use pulses to monitor the health of my Proxmox cluster. Each member of the cluster sends a pulse if a series of checks are OK. With the current implementation I can not differentiate between an unhealthy member, and offline member. Being able to consider the check as down if the body was missing a configured string would make that possible.
3 Comments
Indeed that is in my internal todo list which contains a lot more than the public suggestion board ^^
Thanks for posting it here and giving your feedback, I've bumped the priority a bit and will update here where there are news.
Perfect!
I just had a thought, related to our discussion on the uptime timeline vs. apdex bars. Maybe the uptime timeline could continue to show that a pulse was received, and the bars show the status of the pulse content?
Well the last 5 checks/pulse results are already displayed on the left (near the current status), and I don't store more history/details when all is well so that would not be an option. Even if it would, I don't really like having the same UI used for totally different meanings & timeframes.
Sign in to comment