Push every 24 hours · Issue #6069 · louislam/uptime-kuma · GitHub
For your use case, I use Healthchecks.io. This service, which you can also self-host, allows you to send a start signal, for example, when a backup begins, and a success signal at the end of the process. This start signal initially confirms that the process is started on time.
Additionally, you can define a grace period. With a sent start signal, this period defines the maximum expected runtime of the process. As long as the success signal is sent within this period, the check is successful. This should better represent your use case.
(But to be honest, I don’t know how Healthchecks.io behaves if the grace period is longer than the check period.)
Furthermore, the start-success mechanism provides a runtime determination for the processes.
Uptime Kuma and Healthchecks.io have overlapping functions for push monitors. For some use cases, one product or the other has the edge.