[GH-ISSUE #316] Dependant Checks #243

New issue

Closed

opened 2026-02-25 23:41:44 +03:00 by kerem · 3 comments

kerem commented

2026-02-25 23:41:44 +03:00

Owner

Originally created by @adrianmace on GitHub (Dec 25, 2019).
Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/316

Firstly, I want to extend a massive thank you to the team behind this project. It is incredibly useful in my homelab where I want a simple and extensible way to monitor device health without exposing them out of the firewall/port forwarding!

Feature Request
I would like the ability to have checks that are only enabled once while other checks are healthy ie. if a simple check for the RUNNING status of docker.service fails, it would be great to automatically disable all checks configured for the containers (health, response time, batch jobs, etc).

This would also be useful in other situations; device uptime could be the parent of the running services, running service could be the parent of APM metrics or batch job statuses, etc.

Originally created by @adrianmace on GitHub (Dec 25, 2019). Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/316 _Firstly, I want to extend a massive thank you to the team behind this project. It is incredibly useful in my homelab where I want a simple and extensible way to monitor device health without exposing them out of the firewall/port forwarding!_ **Feature Request** I would like the ability to have checks that are only enabled once while other checks are healthy ie. if a simple check for the `RUNNING` status of `docker.service` fails, it would be great to automatically disable all checks configured for the containers (health, response time, batch jobs, etc). This would also be useful in other situations; device uptime could be the parent of the running services, running service could be the parent of APM metrics or batch job statuses, etc.

kerem

2026-02-25 23:41:44 +03:00

closed this issue
added the
feature
label

kerem commented

2026-02-25 23:41:45 +03:00

Author

Owner

@user655362020 commented on GitHub (Jun 6, 2020):

+1 for dependant checks. Useful for home users where computer does turns on for a long time.

@user655362020 commented on GitHub (Jun 6, 2020): +1 for dependant checks. Useful for home users where computer does turns on for a long time.

kerem commented

2026-02-25 23:41:45 +03:00

Author

Owner

@nbvcxz commented on GitHub (Feb 6, 2021):

This is exactly I'd love to see: It's like PRTG "parent" sensor. I thing about it in network context (I made some healthchecks at Mikrotik router and switches):
When Router is down, don't inform me Switches are also in down state - they just can't send ping to my healthchecks server. I hope it's rather easy to implement: «Parent» parameter for each sensor (blank as default). When «Parent» is defined, simple condition: don't put sensor in down state, disable it instead.

@nbvcxz commented on GitHub (Feb 6, 2021): This is exactly I'd love to see: It's like PRTG "parent" sensor. I thing about it in network context (I made some healthchecks at Mikrotik router and switches): When **Router is down**, don't inform me **Switches are also in down state** - they just can't send ping to my healthchecks server. I hope it's rather easy to implement: «Parent» parameter for each sensor (blank as default). When «Parent» is defined, simple condition: don't put sensor in down state, disable it instead.

kerem commented

2026-02-25 23:41:45 +03:00

Author

Owner

@cuu508 commented on GitHub (Nov 19, 2025):

Thanks for the comments. I am not planning to work on this. I'd like to keep Healthchecks lean and simple, and this feature is a little too niche for me.

@cuu508 commented on GitHub (Nov 19, 2025): Thanks for the comments. I am not planning to work on this. I'd like to keep Healthchecks lean and simple, and this feature is a little too niche for me.