Add a possibility to make groups and priority's #1761

New issue

Closed

opened 2026-02-28 02:31:43 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-28 02:31:43 -05:00

Owner

Originally created by @vslinuxdotnet on GitHub (Jan 11, 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

Create groups names and priority number by machine, if a machine in a group fails first, don't try others in same group because all will be down. Example: 100 alerts will be send at the moment in one gateway fails...

✔️ Solution

If one machine with priority 0 in same group fails don't try to check if others with priority 1,2,3 are alive.
Only one alert is send inform that groups name, machine is down.

❓ Alternatives

No response

📝 Additional Context

No response

Originally created by @vslinuxdotnet on GitHub (Jan 11, 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 Create groups names and priority number by machine, if a machine in a group fails first, don't try others in same group because all will be down. Example: 100 alerts will be send at the moment in one gateway fails... ### ✔️ Solution If one machine with priority 0 in same group fails don't try to check if others with priority 1,2,3 are alive. Only one alert is send inform that groups name, machine is down. ### ❓ Alternatives _No response_ ### 📝 Additional Context _No response_

deekerman

2026-02-28 02:31:43 -05:00

closed this issue
added the
feature-request

A:monitor
labels

deekerman commented

2026-02-28 02:31:49 -05:00

Author

Owner

@chakflying commented on GitHub (Jan 11, 2023):

#1236 will basically meet your needs.

@chakflying commented on GitHub (Jan 11, 2023): #1236 will basically meet your needs.

deekerman commented

2026-02-28 02:31:50 -05:00

Author

Owner

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

@vslinuxdotnet https://github.com/louislam/uptime-kuma/pull/2693 has been merged and is avaliable in 1.22.
I think this issue is resolved. Could you close this issue?

@CommanderStorm commented on GitHub (Jul 4, 2023): @vslinuxdotnet https://github.com/louislam/uptime-kuma/pull/2693 has been merged and is avaliable in `1.22`. I think this issue is resolved. Could you close this issue?

deekerman commented

2026-02-28 02:31:50 -05:00

Author

Owner

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

@
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/pull/2693 https://github.com/louislam/uptime-kuma/issues/1089 https://github.com/louislam/uptime-kuma/issues/2487 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 7, 2023): @ 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/pull/2693 https://github.com/louislam/uptime-kuma/issues/1089 https://github.com/louislam/uptime-kuma/issues/2487 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.