adding support for grouping and sub-grouping #2103

Closed
opened 2026-02-28 02:43:05 -05:00 by deekerman · 5 comments
Owner

Originally created by @macaty on GitHub (Apr 13, 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

Uptime-kuma is an amazing project, and after my initial experience using it, I deeply appreciate its beauty. I would love to contribute some great ideas to this project and hope they can be accepted to make kuma even more perfect.

✔️ Solution

adding support for grouping and sub-grouping, which would allow users to easily categorize monitoring items and set alert notification recipients by group, or proxies setting

Alternatives

No response

📝 Additional Context

No response

Originally created by @macaty on GitHub (Apr 13, 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 Uptime-kuma is an amazing project, and after my initial experience using it, I deeply appreciate its beauty. I would love to contribute some great ideas to this project and hope they can be accepted to make kuma even more perfect. ### ✔️ Solution adding support for grouping and sub-grouping, which would allow users to easily categorize monitoring items and set alert notification recipients by group, or proxies setting ### ❓ Alternatives _No response_ ### 📝 Additional Context _No response_
deekerman 2026-02-28 02:43:05 -05:00
Author
Owner

@JackBailey commented on GitHub (May 12, 2023):

I'd love this feature too.
More context for maintainers:

Say I have 10 services on a server. One of which being a push.

I want to know when any of my services go down, but if the push monitor is down, the rest would be too. I don't need notifications for every all 10 services, just 1 for the push.

@JackBailey commented on GitHub (May 12, 2023): I'd love this feature too. More context for maintainers: Say I have 10 services on a server. One of which being a push. I want to know when _any_ of my services go down, but if the push monitor is down, the rest would be too. I don't need notifications for every all 10 services, just 1 for the push.
Author
Owner

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

@macaty
is this one of the PRs, which will be resolved once https://github.com/louislam/uptime-kuma/pull/2693 is merged in the next release?
If yes, could you please cose this issue, as this is one of the duplicates mentioned in the above's issue?
If no, could you please rephrase your issue to make it more distinct?

@CommanderStorm commented on GitHub (Jun 4, 2023): @macaty is this one of the PRs, which will be resolved once https://github.com/louislam/uptime-kuma/pull/2693 is merged in the next release? If yes, could you please cose this issue, as this is one of the duplicates mentioned in the above's issue? If no, could you please rephrase your issue to make it more distinct?
Author
Owner

@rwjack commented on GitHub (Jun 21, 2023):

To add a user story to this:

I monitor a couple of services through a VPN.
If the VPN network connection goes out, I get notified that all of those checks are down.
It would make more sense to get a single notification, such as: "VPN Group is Down (5/5)" - as in 5 out of 5 checks are down.

Which can also be used to group notifications in general:
"DMZ Services Down (7/20)" - 7 out of 20 checks down

@rwjack commented on GitHub (Jun 21, 2023): To add a user story to this: I monitor a couple of services through a VPN. If the VPN network connection goes out, I get notified that all of those checks are down. It would make more sense to get a single notification, such as: "VPN Group is Down (5/5)" - as in 5 out of 5 checks are down. Which can also be used to group notifications in general: "DMZ Services Down (7/20)" - 7 out of 20 checks down
Author
Owner

@CommanderStorm commented on GitHub (Jun 21, 2023):

@rwjack
I don't the intention of your comment.
Grouping is in the current beta.

If you'd like an enhancement of said feature, please post a separate issue. Like this, this is not managable.

@CommanderStorm commented on GitHub (Jun 21, 2023): @rwjack I don't the intention of your comment. Grouping is in the [current beta](https://github.com/louislam/uptime-kuma/releases/tag/1.22.0-beta.0). If you'd like an enhancement of said feature, please post a separate issue. Like this, this is not managable.
Author
Owner

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

This issue was partially resolved in https://github.com/louislam/uptime-kuma/pull/2693 and is available since v1.22.0.
The remaining issues of this project are tracked in different issues:

  • @JackBailey

    I want to know when any of my services go down

    This is tracked in #1089 and related duplicates

  • @macaty

    adding support for grouping and sub-grouping, which would allow users to [...] set [...] proxies setting [by group]

    This is tracked in #1097

=> closing as resolved

@CommanderStorm commented on GitHub (Dec 3, 2023): This issue was partially resolved in https://github.com/louislam/uptime-kuma/pull/2693 and is available since `v1.22.0`. The remaining issues of this project are tracked in different issues: - @JackBailey > I want to know when any of my services go down This is tracked in #1089 and related duplicates - @macaty > adding support for grouping and sub-grouping, which would allow users to [...] set [...] proxies setting [by group] This is tracked in #1097 => closing as resolved
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/uptime-kuma#2103
No description provided.