starred/uptime-kuma

Fork 0

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

Stop notifications if specific monitor is down #1248

New issue

Closed

opened 2026-02-28 02:14:56 -05:00 by deekerman · 8 comments

deekerman commented

2026-02-28 02:14:56 -05:00

Owner

Originally created by @Vecsy on GitHub (Jul 12, 2022).

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

I checked and didn't find similar feature request

🏷️ Feature Request Type

New Notification

🔖 Feature description

The option to stop all notifications only if a specific monitor goes down/offline. This would prevent a user receiving a lot of down/up emails/other notifications.

✔️ Solution

Here is my case example: I host an ESXi server. If the ESXi server is offline, do not send down notifications for WebServer1, WebServer2, WebServer3, MailServer1, MailServer2 etc etc.

❓ Alternatives

No response

📝 Additional Context

No response

Originally created by @Vecsy on GitHub (Jul 12, 2022). ### ⚠️ Please verify that this feature request has NOT been suggested before. - [X] I checked and didn't find similar feature request ### 🏷️ Feature Request Type New Notification ### 🔖 Feature description The option to stop all notifications only if a specific monitor goes down/offline. This would prevent a user receiving a lot of down/up emails/other notifications. ### ✔️ Solution Here is my case example: I host an ESXi server. If the ESXi server is offline, do not send down notifications for WebServer1, WebServer2, WebServer3, MailServer1, MailServer2 etc etc. ### ❓ Alternatives _No response_ ### 📝 Additional Context _No response_

deekerman

2026-02-28 02:14:56 -05:00

closed this issue
added the
feature-request
label

deekerman commented

2026-02-28 02:15:00 -05:00

Author

Owner

@ouuan commented on GitHub (Nov 27, 2022):

I also want to request a similar but different feature: an option to stop all notifications when all monitors are down, or for example when 90% of the monitors are down. This can prevent receiving tons of notifications when there are network issues with the Uptime Kuma server itself.

@ouuan commented on GitHub (Nov 27, 2022): I also want to request a similar but different feature: an option to stop all notifications when all monitors are down, or for example when 90% of the monitors are down. This can prevent receiving tons of notifications when there are network issues with the Uptime Kuma server itself.

deekerman commented

2026-02-28 02:15:01 -05:00

Author

Owner

@cris1 commented on GitHub (Jul 19, 2023):

I have a device that I want to monitor on general behaviour .. It comes up for 1 minute and sleeps 5 minutes.. I don't want to see notifications (desktop notifications) for this device.. its ok just to monitor it and I can watch the graphs to see if it still behaves as expected.

@cris1 commented on GitHub (Jul 19, 2023): I have a device that I want to monitor on general behaviour .. It comes up for 1 minute and sleeps 5 minutes.. I don't want to see notifications (desktop notifications) for this device.. its ok just to monitor it and I can watch the graphs to see if it still behaves as expected.

deekerman commented

2026-02-28 02:15:01 -05:00

Author

Owner

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

Is this one of the duplicates linked to https://github.com/louislam/uptime-kuma/pull/1236?

@CommanderStorm commented on GitHub (Jul 19, 2023): Is this one of the duplicates linked to https://github.com/louislam/uptime-kuma/pull/1236?

deekerman commented

2026-02-28 02:15:01 -05:00

Author

Owner

@cris1 commented on GitHub (Jul 19, 2023):

Is this one of the duplicates linked to #1236?

For me it's not a dependency issue. It's more like : Yes i want to monitor it, but no it's not relevant enough to notify me with any notifications.

@cris1 commented on GitHub (Jul 19, 2023): > Is this one of the duplicates linked to #1236? For me it's not a dependency issue. It's more like : Yes i want to monitor it, but no it's not relevant enough to notify me with any notifications.

deekerman commented

2026-02-28 02:15:01 -05:00

Author

Owner

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

Yes i want to monitor it, but no it's not relevant enough to notify me with any notifications.

You could just disable the notifiations for said monitor. Am I missing something?

@CommanderStorm commented on GitHub (Jul 19, 2023): > Yes i want to monitor it, but no it's not relevant enough to notify me with any notifications. You could just disable the notifiations for said monitor. Am I missing something? ![image](https://github.com/louislam/uptime-kuma/assets/26258709/3bb39bf0-3d4a-418e-8e5f-0f4a828f3a92)

deekerman commented

2026-02-28 02:15:01 -05:00

Author

Owner

@cris1 commented on GitHub (Jul 19, 2023):

As far as I can see this doesn't apply for the desktop notifications.
As a (workable) workaround I increased the Retries to 60, so before it will send a notification, the device was up again.

@cris1 commented on GitHub (Jul 19, 2023): As far as I can see this doesn't apply for the desktop notifications. As a (workable) workaround I increased the Retries to 60, so before it will send a notification, the device was up again. ![image](https://github.com/louislam/uptime-kuma/assets/666701/d4921568-8ad2-425b-850e-24da34ddf614)

deekerman commented

2026-02-28 02:15:01 -05:00

Author

Owner

@ouuan commented on GitHub (Jul 19, 2023):

@cris1 Whatever, it seems that your request is irrelevant to this issue.

@ouuan commented on GitHub (Jul 19, 2023): @cris1 Whatever, it seems that your request is irrelevant to this issue.

deekerman commented

2026-02-28 02:15:01 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Dec 1, 2023):

@Vecsy
We are consolidating duplicate issues a bit to make issue management easier.
I think, we should track this issue in https://github.com/louislam/uptime-kuma/issues/1089 and as there is no functional difference (maybe just small naming differences, but nothing that would require a different issue imo)
=> I am going to close this as a duplicate

@CommanderStorm commented on GitHub (Dec 1, 2023): @Vecsy We are consolidating duplicate issues a bit to make issue management easier. I think, we should track this issue in https://github.com/louislam/uptime-kuma/issues/1089 and as there is no functional difference (maybe just small naming differences, but nothing that would require a different issue imo) => I am going to close this as a duplicate