[Feature Request] Add option to select different notifications for DOWN
and UP
#4470
Labels
area:notifications
Everything related to notifications
feature-request
Request for new features to be added
π I have found these related issues/pull requests
#1953: Pushover different sound for up/down
#1582: Selecting notifications to send
π·οΈ Feature Request Type
Settings
π Feature description
It should be possible to optionally select a different notification for the
UP
message.Use cases:
DOWN
orUP
events respectively.βοΈ Solution
UP
message" should be added to the notification settings of each monitor. If enabled, the notification methods select above would only be used forDOWN
messages.UP
messages.DOWN
events and omit information about changes back toUP
status.β Alternatives
Alternatives to the UI changes suggested above:
DOWN
andUP
messages above the list of notification providers.| Notification | Use for
DOWN
| Use forUP
|| - | - | - |
| Provider 1 | [x] | [ ] |
| Provider 2 | [ ] | [x] |
| Provider 3 | [x] | [x] |
Alternatives to this implementation in general
π Additional Context
The idea behind all of this is that I want to hear an alarm and have a different vibration pattern for the notifications on my phone depending on wether a service goes down or comes back up. I want to be sure to receive the
DOWN
notification, but I don't care if only way later I see that the service isUP
again.Therefore, I would add the same notification provider twice (e.g. Telegram and Ntfy in my case). The one named "Ntfy - UP", for example, would just receive Priority 3 or 4 (medium / high). Then I'd add another instance of this provider, call it "Ntfy - DOWN" and set the priority to 5 (max). I can then configure my phone to treat those messages in a certain way.
This general approach using the monitor settings instead of making changes to the notification provider itself would allow for a more flexible and fine-grained approach, as one could use it with every notification provider available and mix and match as required.
The text was updated successfully, but these errors were encountered: