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

Filter Alerts for Notification #3585

Closed
1 task done
btmolloy opened this issue Aug 16, 2023 · 5 comments
Closed
1 task done

Filter Alerts for Notification #3585

btmolloy opened this issue Aug 16, 2023 · 5 comments
Labels
area:notifications Everything related to notifications feature-request Request for new features to be added

Comments

@btmolloy
Copy link

⚠️ 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, Other

🔖 Feature description

Uptime Kuma is an amazing replacement for Uptime Robot as Kuma excels in places Uptime Robot can not. However, there are a few features that I really wish Kuma had, such as filtering of alerts. What I mean by this is the ability to filter what alerts are sent on a notification type. For example, I have a ton of sites that I like to monitor with Kuma, and Id love to be able to send SSL/Cert Alerts to one google chat, and the rest of the alerts to another chat. This would allow more organization of messages and allow a more efficient workflow. My current fix for this is very much a duck tape type fix where I essentially duplicated the google chat notification code and made one of them have server logic that only allows SSL messages to be sent and the other does the opposite.

✔️ Solution

A perfect solution for this would be some sort of checkbox or drop down on the Notification Setup menu that would allow for more configuration of what alerts will be sent through the notification method, (i.e. All, SSL/CERT ONLY, KEYWORD ONLY, 503 ERROR?).
Screenshot 2023-08-16 at 10 46 37 AM

❓ Alternatives

Im not sure of any alternative solutions for this issue. I have a duck tape type fix right now which can be seen in the attached image. I am NOT at all suggesting this is a viable solution, this is only what I had time for.
Screenshot 2023-08-16 at 10 52 26 AM

📝 Additional Context

No response

@btmolloy btmolloy added the feature-request Request for new features to be added label Aug 16, 2023
@btmolloy btmolloy changed the title Filter For alerts Filter Alerts for Notification Aug 16, 2023
@CommanderStorm
Copy link
Collaborator

An alternative is to use Grafana Oncall for your escalation needs (see #2783 => this will probably be avaliable in v2.0)

Oncall includes fully customisable routing of allerts
image

@btmolloy
Copy link
Author

Thank you for this alternative solution, Im going to look into this, although I'm curious if there is a more simple or primitive solution here. Louislam is the one who determines if suggested feature ideas are going to be looked into any further right?

@CommanderStorm
Copy link
Collaborator

I'm curious if there is a more simple or primitive solution here

Currently not, but that is why you opened the feature-request. ^^

Louislam is the one who determines if suggested feature ideas are going to be looked into any further right?

Yes, Louis has the final say on what gets merged.
If you'd like to implement such a feature, please

  1. device a plan what should be changed how to achieve the goal of an escalation system
    (filtering alerts to different channels is essentially a basic building block of an escalation system)
  2. discuss said plan as laid out here: https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md
    (rationale: saving time on your + Louis end)
  3. Change what needs to be changed
  4. Wait for a review + merge/revisiting of missed topics

tldr: Reasonable implementations of reasonable features are likely to get merged.

@CommanderStorm
Copy link
Collaborator

CommanderStorm commented Aug 16, 2023

Related #1315

Note that this feature-request is also a duplicate of #1233 / #1562 and partially #1137

@CommanderStorm
Copy link
Collaborator

@btmolloy
We are consolidating duplicate issues a bit to make issue management easier.
I think, we should track this issue in #1233 as there is real functional difference.
Both issues target the ability to filter alerts.
⇒ I am going to close this as a duplicate.

@CommanderStorm CommanderStorm closed this as not planned Won't fix, can't repro, duplicate, stale Dec 4, 2023
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

2 participants