[GH-ISSUE #983] Feature request: High-Availability #689

New issue

Closed

opened 2026-02-25 23:43:17 +03:00 by kerem · 2 comments

kerem commented

2026-02-25 23:43:17 +03:00

Owner

Originally created by @nh2 on GitHub (Apr 1, 2024).
Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/983

Hi,

I'm looking for an alternative to the abandoned https://github.com/AcalephStorage/consul-alerts

Does healthchecks have any form of high-availability (HA) feature currently?

With HA I mean that you can run a cluster of machines, all running healthchecks, and if one goes down, the others will still alert you of failed health checks.

From a first look, it seems healthchecks is a plain single-server Django app without any dependency on a highly available database package like consul or etcd.

Of course one can HA the underlying DB, such as postgres, but it would still require that healthchecks actually supports running multiple healthchecks instances on different servers against the underlying HA database.

Is that supported?

if not, consider this a feature request -- i think it makes sense that the software that watches my HA software for uptime is also HA itself :)

Thanks!

Originally created by @nh2 on GitHub (Apr 1, 2024). Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/983 Hi, I'm looking for an alternative to the abandoned https://github.com/AcalephStorage/consul-alerts Does `healthchecks` have any form of high-availability (HA) feature currently? With HA I mean that you can run a cluster of machines, all running `healthchecks`, and if one goes down, the others will still alert you of failed health checks. From a first look, it seems `healthchecks` is a plain single-server Django app without any dependency on a highly available database package like `consul` or `etcd`. Of course one can HA the underlying DB, such as postgres, but it would still require that `healthchecks` actually supports running multiple `healthchecks` instances on different servers against the underlying HA database. Is that supported? if not, consider this a feature request -- i think it makes sense that the software that watches my HA software for uptime is also HA itself :) Thanks!

kerem closed this issue

2026-02-25 23:43:17 +03:00

kerem commented

2026-02-25 23:43:17 +03:00

Author

Owner

@cuu508 commented on GitHub (Apr 2, 2024):

Of course one can HA the underlying DB, such as postgres, but it would still require that healthchecks actually supports running multiple healthchecks instances on different servers against the underlying HA database.

Yes, that is supported. You can run multiple (probably load-balanced) Healthchecks web servers against a single database. The manage.py sendalerts command, which is in charge of sending out notifications, can also be run concurrently on multiple servers.

@cuu508 commented on GitHub (Apr 2, 2024): > Of course one can HA the underlying DB, such as postgres, but it would still require that healthchecks actually supports running multiple healthchecks instances on different servers against the underlying HA database. Yes, that is supported. You can run multiple (probably load-balanced) Healthchecks web servers against a single database. The `manage.py sendalerts` command, which is in charge of sending out notifications, can also be run concurrently on multiple servers.

kerem commented

2026-02-25 23:43:17 +03:00

Author

Owner

@nh2 commented on GitHub (Apr 10, 2024):

Thank you!

@nh2 commented on GitHub (Apr 10, 2024): Thank you!