starred/uptime-kuma

Fork 0

mirror of https://github.com/louislam/uptime-kuma.git synced 2026-03-02 22:57:00 -05:00

Master Monitor over other Monitors #1856

New issue

Closed

opened 2026-02-28 02:35:04 -05:00 by deekerman · 5 comments

deekerman commented

2026-02-28 02:35:04 -05:00

Owner

Originally created by @maxwai on GitHub (Feb 6, 2023).

⚠️ Please verify that this feature request has NOT been suggested before.

I checked and didn't find similar feature request

🏷️ Feature Request Type

Other

🔖 Feature description

Be able to set a kind of "Master" Monitor. So when this "Master" Monitor (this could be for example the Server itself where the Services are running) goes down, the other Monitors that depend on this "Master" Monitor go down as well.

This would allow to avoid sending multiple Notifications when the "Master" Monitor is down, since currently one would get a Notification for every Service that goes down and the Server itself.

This can be quite useful for people that want to check the individual Services (so to check if a docker goes down for example) but also to quickly see that the Server itself has a Problem (has crashed or doesn't have an Internet connection anymore).

Here is an example how this could look like: (ignore the Services in Maintenance)

Here the all Services (called "Dienste" here) are living on the Server so if the first Monitor goes down, all Services should also be marked as down immediately and only one Notification should be send instead of 6

✔️ Solution

Add a way to link multiple Monitors to a single Monitor that acts like a "Master Switch"

❓ Alternatives

No response

📝 Additional Context

No response

Originally created by @maxwai on GitHub (Feb 6, 2023). ### ⚠️ Please verify that this feature request has NOT been suggested before. - [X] I checked and didn't find similar feature request ### 🏷️ Feature Request Type Other ### 🔖 Feature description Be able to set a kind of "Master" Monitor. So when this "Master" Monitor (this could be for example the Server itself where the Services are running) goes down, the other Monitors that depend on this "Master" Monitor go down as well. This would allow to avoid sending multiple Notifications when the "Master" Monitor is down, since currently one would get a Notification for every Service that goes down and the Server itself. This can be quite useful for people that want to check the individual Services (so to check if a docker goes down for example) but also to quickly see that the Server itself has a Problem (has crashed or doesn't have an Internet connection anymore). Here is an example how this could look like: (ignore the Services in Maintenance) ![image](https://user-images.githubusercontent.com/44324946/216930635-81073cb2-5b3a-4fd6-bf83-de5a25a3467b.png) Here the all Services (called "Dienste" here) are living on the Server so if the first Monitor goes down, all Services should also be marked as down immediately and only one Notification should be send instead of 6 ### ✔️ Solution Add a way to link multiple Monitors to a single Monitor that acts like a "Master Switch" ### ❓ Alternatives _No response_ ### 📝 Additional Context _No response_

deekerman

2026-02-28 02:35:04 -05:00

closed this issue
added the
feature-request
label

deekerman commented

2026-02-28 02:35:09 -05:00

Author

Owner

@drewlsvern commented on GitHub (Mar 15, 2023):

I am also looking for a feature similar to this. I would be willing to contribute towards this feature. I would love to gather some thoughts from others on this before starting though.

I have used Nagios before so my mind immediately kind of jumped to how I used it. You have a host and then you have a bunch of services that belong to that host.

I'm wondering if it might be easiest to automatically setup a master host to ping and then any sub monitors could be anything else.

In terms of the UI, my thought is to have an accordion and then any sub monitors would be visible by expanding the accordion.

@drewlsvern commented on GitHub (Mar 15, 2023): I am also looking for a feature similar to this. I would be willing to contribute towards this feature. I would love to gather some thoughts from others on this before starting though. I have used Nagios before so my mind immediately kind of jumped to how I used it. You have a host and then you have a bunch of services that belong to that host. I'm wondering if it might be easiest to automatically setup a master host to ping and then any sub monitors could be anything else. In terms of the UI, my thought is to have an accordion and then any sub monitors would be visible by expanding the accordion.

deekerman commented

2026-02-28 02:35:10 -05:00

Author

Owner

@uptimejeff commented on GitHub (May 8, 2023):

If internet is down for the uptimekuma host, I'd like it to pause all notifications until internet is restored.
Example: ping a known host which ALL checks depend on (ping an upstream router or 8.8.8.8) or two hosts (1.1.1.1/8.8.8.8), if unreachable, pause all checks/notification until service restored.

@uptimejeff commented on GitHub (May 8, 2023): If internet is down for the uptimekuma host, I'd like it to pause all notifications until internet is restored. Example: ping a known host which ALL checks depend on (ping an upstream router or 8.8.8.8) or two hosts (1.1.1.1/8.8.8.8), if unreachable, pause all checks/notification until service restored.

deekerman commented

2026-02-28 02:35:10 -05:00

Author

Owner

@feofan69 commented on GitHub (May 9, 2023):

If internet is down for the uptimekuma host, I'd like it to pause all notifications until internet is restored. Example: ping a known host which ALL checks depend on (ping an upstream router or 8.8.8.8) or two hosts (1.1.1.1/8.8.8.8), if unreachable, pause all checks/notification until service restored.

How to make pause all monitors?

@feofan69 commented on GitHub (May 9, 2023): > If internet is down for the uptimekuma host, I'd like it to pause all notifications until internet is restored. Example: ping a known host which ALL checks depend on (ping an upstream router or 8.8.8.8) or two hosts (1.1.1.1/8.8.8.8), if unreachable, pause all checks/notification until service restored. How to make pause all monitors?

deekerman commented

2026-02-28 02:35:10 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Jul 26, 2023):

@maxwai
I think this is a duplicate of https://github.com/louislam/uptime-kuma/issues/2487 or https://github.com/louislam/uptime-kuma/pull/1236
If you agree, could you please close this Issue, as duplicates only create immortal zombies and are really hard to issue-manage?
If not, what makes this issue unique enough to require an additional issue? (Could this be integrated into the issue linked above?) ^^

@CommanderStorm commented on GitHub (Jul 26, 2023): @maxwai I think this is a duplicate of https://github.com/louislam/uptime-kuma/issues/2487 or https://github.com/louislam/uptime-kuma/pull/1236 If you agree, could you please close this Issue, as duplicates only create immortal zombies and are really hard to issue-manage? If not, what makes this issue unique enough to require an additional issue? (Could this be integrated into the issue linked above?) ^^

deekerman commented

2026-02-28 02:35:10 -05:00

Author

Owner

@maxwai commented on GitHub (Jul 27, 2023):

@CommanderStorm
I looked at the issued, and you are right, this is a duplicate of #1236 . Sorry, didn't see that one.

@maxwai commented on GitHub (Jul 27, 2023): @CommanderStorm I looked at the issued, and you are right, this is a duplicate of #1236 . Sorry, didn't see that one.