Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Option to send only one notification if entire host goes down (Conditional/Dependent Notifications) #5452

Closed
zwimer opened this issue Dec 19, 2024 · 1 comment
Labels
feature-request Request for new features to be added

Comments

@zwimer
Copy link

zwimer commented Dec 19, 2024

πŸ“‘ I have found these related issues/pull requests

🏷️ Feature Request Type

Settings, Other

πŸ”– Feature description

If I have monitors set up like this:

Host1
    Host1_Ping
    Host1_Service1
    Host1_Service2
    ...
    Host1_Service48

If Host1 looses internet or is shutdown or something, it's very likely that none of those services will be up. If each has notifications enabled, then this will result in a flood of like 50 notifications all at once.

βœ”οΈ Solution

It would be nice if uptime kuma could detect that every single child went down and just send a single notifcation stating 'Host1 and dependent services are down'.

❓ Alternatives

Group notifications so that instead of 50 individual simultaneous notifications, I get one large notification.

πŸ“ Additional Context

Notification grouping is likely the more-preferred solution here (if we can only have one), but there already exists an issue for that: #1137

@zwimer zwimer added the feature-request Request for new features to be added label Dec 19, 2024
@CommanderStorm
Copy link
Collaborator

Duplicate of the issues you linked => closing as a duplicate

@CommanderStorm CommanderStorm closed this as not planned Won't fix, can't repro, duplicate, stale Dec 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request Request for new features to be added
Projects
None yet
Development

No branches or pull requests

2 participants