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

Notification rules #3634

Closed
1 task done
JaJe92 opened this issue Aug 23, 2023 · 3 comments
Closed
1 task done

Notification rules #3634

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

Comments

@JaJe92
Copy link

JaJe92 commented Aug 23, 2023

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

If I have multiple networking devices such as switches or routers monitored, each of these have it's own devices that I also monitor, I want to setup a notification rules that whenever one of these switches or routers goes down, to notify me about these routers only and not get spammy notification that all devices behind that switch/router is not responding.

Why not, adding conditional notifications too, If x and y is true/false then notify, else ignore.

✔️ Solution

Select list of devices and add as 'child' to 'parent' device, so whenever the 'parent' device goes down, no notification needed to receive for 'child' devices too.

❓ Alternatives

No response

📝 Additional Context

No response

@JaJe92 JaJe92 added the feature-request Request for new features to be added label Aug 23, 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

Related #1315

I think this is a duplicate of #3585 / #1233 / #1562 and partially #1137
If you agree, could you please close this Issue, as duplicates only create immortal zombies and are really hard to issue-manage?
If not, what makes this issue unique enough to require an additional issue? (Could this be integrated into the issue linked above?) ^^

@stepech
Copy link

stepech commented Sep 10, 2023

Why is this issue mentioned in v1.23.1 release notes? @louislam perhaps a typo?

Edit: Yeah, should be #3643

@CommanderStorm CommanderStorm added the area:notifications Everything related to notifications label Dec 5, 2023
@CommanderStorm
Copy link
Collaborator

@JaJe92
We are consolidating duplicate issues a bit to make issue management easier.
I think, we should track this issue in #508 as there is no functional difference (maybe just small naming differences, but nothing that would require a different issue imo)
⇒ 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 8, 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

3 participants