starred/uptime-kuma

Fork 0

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

[Feature] Combined Monitors #522

New issue

Closed

opened 2026-02-28 01:49:23 -05:00 by deekerman · 5 comments

deekerman commented

2026-02-28 01:49:23 -05:00

Owner

Originally created by @Horstexplorer on GitHub (Nov 3, 2021).

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

I checked and didn't find similar feature request

🏷️ Feature Request Type

UI Feature

🔖 Feature description

Id like to see a way in which we could not just organize monitors to named but also logical groups.

✔️ Solution

Currently, we can group the monitors on the status page, which unfortunately is only possible on a single level.
This does not allow us to adequately display clusters running in high availability configurations.
Example: Consider a set of web servers that provide redundancy for their application. Each of these web servers would have its own monitor.
I would like to have a way to display the availability of this application as a sum of the individual monitors of these web servers, preferably with more detail than just up or down (like degraded or critical; depending on how many of the monitors are down).

❓ Alternatives

No response

📝 Additional Context

No response

Originally created by @Horstexplorer on GitHub (Nov 3, 2021). ### ⚠️ Please verify that this feature request has NOT been suggested before. - [X] I checked and didn't find similar feature request ### 🏷️ Feature Request Type UI Feature ### 🔖 Feature description Id like to see a way in which we could not just organize monitors to named but also logical groups. ### ✔️ Solution Currently, we can group the monitors on the status page, which unfortunately is only possible on a single level. This does not allow us to adequately display clusters running in high availability configurations. Example: Consider a set of web servers that provide redundancy for their application. Each of these web servers would have its own monitor. I would like to have a way to display the availability of this application as a sum of the individual monitors of these web servers, preferably with more detail than just up or down (like degraded or critical; depending on how many of the monitors are down). ### ❓ Alternatives _No response_ ### 📝 Additional Context _No response_

deekerman

2026-02-28 01:49:23 -05:00

closed this issue
added the
feature-request

A:monitor

type:new
labels

deekerman commented

2026-02-28 01:49:27 -05:00

Author

Owner

@deefdragon commented on GitHub (Nov 3, 2021):

duplicate of #468 et. all.

@deefdragon commented on GitHub (Nov 3, 2021): duplicate of #468 et. all.

deekerman commented

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

Author

Owner

@Horstexplorer commented on GitHub (Nov 3, 2021):

Not everything which involves groups is automatically a duplicate of something that involves groups.
This is a pretty rude and inappropriate response.

@Horstexplorer commented on GitHub (Nov 3, 2021): Not everything which involves groups is automatically a duplicate of something that involves groups. This is a pretty rude and inappropriate response.

deekerman commented

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

Author

Owner

@chakflying commented on GitHub (Nov 3, 2021):

Thanks for your suggestion, but grouping really has been discussed many times before, I think your use case is already covered by #639 and I don't think there is a reason to have another issue open about it.

@chakflying commented on GitHub (Nov 3, 2021): Thanks for your suggestion, but grouping really has been discussed many times before, I think your use case is already covered by #639 and I don't think there is a reason to have another issue open about it.

deekerman commented

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

Author

Owner

@deefdragon commented on GitHub (Nov 3, 2021):

Grouping of notifications is one of THE most requested features. The reason that there are so many other issues referenced to, and referencing 468, is because of this.

Different people want different things in regards to grouping. It's MUCH easier for work to be done on it when all the potential aspects of that feature are all in one location. Then the trade-offs of different methods of implementation, what should be focused on, how to display it, what to work on first vs what to push to the future etc. can be discussed in one location.

While it looks like a bit of a mess as a result until someone takes on the task of sorting it all, its better than missing something in the feature request log. As such, this is better as a comment/addition to 468.

@deefdragon commented on GitHub (Nov 3, 2021): Grouping of notifications is one of THE most requested features. The reason that there are so many other issues referenced to, and referencing 468, is because of this. Different people want different things in regards to grouping. It's MUCH easier for work to be done on it when all the potential aspects of that feature are all in one location. Then the trade-offs of different methods of implementation, what should be focused on, how to display it, what to work on first vs what to push to the future etc. can be discussed in one location. While it looks like a bit of a mess as a result until someone takes on the task of sorting it all, its better than missing something in the feature request log. As such, this is better as a comment/addition to 468.

deekerman commented

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

Author

Owner

@louislam commented on GitHub (Nov 3, 2021):

Thanks for your suggestion, but grouping really has been discussed many times before, I think your use case is already covered by #639 and I don't think there is a reason to have another issue open about it.

Duplicate of #639

@louislam commented on GitHub (Nov 3, 2021): > Thanks for your suggestion, but grouping really has been discussed many times before, I think your use case is already covered by #639 and I don't think there is a reason to have another issue open about it. Duplicate of #639