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

Support other notification types #106

Open
1 of 3 tasks
julianbrost opened this issue Oct 5, 2023 · 4 comments · May be fixed by #188
Open
1 of 3 tasks

Support other notification types #106

julianbrost opened this issue Oct 5, 2023 · 4 comments · May be fixed by #188
Assignees
Labels
enhancement New feature or request

Comments

@julianbrost
Copy link
Collaborator

julianbrost commented Oct 5, 2023

At the moment, pretty much only state notifications are sent. We also have to allow sending other notifications.

For example, in case of Icinga 2, the available notification types are:

  • DowntimeStart
  • DowntimeEnd
  • DowntimeRemoved
  • Custom
  • Acknowledgement
  • Problem
  • Recovery
  • FlappingStart
  • FlappingEnd

Also, there are events within an incident that could be worth an extra notification, for example:

  • Incident (un)managed / manager(s) changed
  • Incident escalated

Suggestion for moving forward (1. should be pretty straight forward, the others probably need a bit more discussion about the details)

  • Just send all of these non-state notifications to all incident recipients. As the very first step without any new configuration options. If there's an open incident, it sounds like a reasonable default to get notified about everything that's related to the incident if someone is involved in the incident.
  • It should also be possible to receive those notifications without an incident. For this, an option would be to have something like second part in the rules next to (on a logical level, not on the representation in the rule editor) the escalations where one can configure which event types should be routed to which recipients.
  • There should probably be the possibility to limit the types from 1., maybe with something like allowing to exclude certain types in the event rule per recipient.
@yhabteab yhabteab added the enhancement New feature or request label Oct 10, 2023
@yhabteab yhabteab self-assigned this Oct 10, 2023
@yhabteab
Copy link
Member

Currently, the following rough idea exists: In event rules, the escalation stages get an extra option to restrict notification types

Don't we also want to allow to restrict notifications at contacts level, just like in Icinga 2?

@julianbrost
Copy link
Collaborator Author

Not for now, but quite possibly at a later stage, similar to per-contact time restrictions for example.

@julianbrost
Copy link
Collaborator Author

@nilmerg I've updated the issue description after our discussion today. Please have a look.

@julianbrost julianbrost assigned nilmerg and unassigned yhabteab Nov 14, 2023
@nilmerg
Copy link
Member

nilmerg commented Nov 15, 2023

Looks fine

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
4 participants