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

Group / Collate / Aggregate notifications #1137

Open
1 task done
tomlawesome opened this issue Jan 7, 2022 · 8 comments
Open
1 task done

Group / Collate / Aggregate notifications #1137

tomlawesome opened this issue Jan 7, 2022 · 8 comments
Labels
area:notifications Everything related to notifications feature-request Request for new features to be added

Comments

@tomlawesome
Copy link

tomlawesome commented Jan 7, 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

For someone using Uptime Kuma to monitor plenty of items (~50) Uptime Kuma can spam notification emails when there is internet connectivity/networking problems.

I usually get 50 when it's down, and 50 again when it comes back up.

✔️ Solution

Allow Uptime Kuma to list ALL services that down, or ALL services that are up and then send them in a single email as a list after a configurable timeout.

❓ Alternatives

Some other kind of notification, filtering emails.
Different email inbox.

I would rather not do any of these because I will not notice them as quickly as an email to my personal mail. I also don't like these options as they (for email) create a lot of storage need for no reason.

📝 Additional Context

No response

@tomlawesome tomlawesome added the feature-request Request for new features to be added label Jan 7, 2022
@Furrypaw
Copy link

Furrypaw commented Jan 9, 2022

Would be nice to have some hierarchy so if the main host goes down / internet then only the main notification is sent instead of all the services that are being monitored.

@stelle007

This comment was marked as spam.

@DusterTheFirst
Copy link

I can see this being made possible by allowing users to group monitors together. If one monitor of a group starts alerting, the other monitors will block the notification for the whole group until they update their status. This will let users group together related failures and it can help reduce the spam notifications received from an outage of related monitors.

@Robin-Sch

This comment was marked as resolved.

@github0004

This comment was marked as off-topic.

@CommanderStorm CommanderStorm added the area:notifications Everything related to notifications label Dec 4, 2023
@CommanderStorm CommanderStorm changed the title Group / Collate / Aggregate notification emails & choose only up/down notification, or both. Group / Collate / Aggregate notification emails Dec 4, 2023
@CommanderStorm
Copy link
Collaborator

@tomlawesome
I have removed the alert filtering from your issue as I think tracking this in a distinct issue like #1233 is a better call

@CommanderStorm CommanderStorm changed the title Group / Collate / Aggregate notification emails Group / Collate / Aggregate notifications Dec 14, 2023
@alkcbs
Copy link

alkcbs commented Jun 7, 2024

To pull my thoughts from 4829 here, I'd love to see nested items within a group being able to have individual notifications off, while notifications for the group is on, and if something goes down, the group notification would specify what went down rather than just saying "child inaccessible." This would be for situations such as:

-Location (group)
--Server1 (child)
--Server2 (child)
--Firewall (child)

If one server goes down, one notification at the Location level, saying which server is down. If the firewall goes down (taking the servers with it), one notification at the Location level, listing all 3 children as down. As it sits, these would generate 2 and 4 emails for the scenarios if all alerts are enabled.

@zwimer
Copy link

zwimer commented Dec 19, 2024

Small note in case someone implements this, some services (like Telegram) have character limits, so grouped notifications may have to be split into parts at that limit to avoid being truncated or anything like that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:notifications Everything related to notifications feature-request Request for new features to be added
Projects
None yet
Development

No branches or pull requests

9 participants