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

Feature Req: Ability to selectively configure data to send via notification on a per service (or even per class within a service) #1959

Open
taw123 opened this issue Apr 5, 2024 · 0 comments

Comments

@taw123
Copy link

taw123 commented Apr 5, 2024

Is your feature request related to a problem? Please describe.

Different Watchtower events/messages have very different types of priority and thus require different types of notification based upon that type.

Currently, all defined notifications sent via ANY notification service will ALL contain the SAME user selected/configured content.

Describe the solution you'd like

At a minimum I would like to send notification-report via email, and register for notification with a DIFFERENT service (aka Pushover) for error/faults. Would seem like a common senerio where differing types of events call for different types of notification.

Ideally it would be nice to extend the concept to include the ability to send notifications (again customized by type- Reports vs error/faults) with different priorities/recipients as most notification APIs support the concept of event priority. As such using "normal" events or even silent notification for status reports, and high priority for events like failures and faults.

Current design does allow for multiple notification services, but no method for differentiating content between services or even between multiple definitions of the SAME service with differing delivery recipients/or priority.

If this isn't clear please let me know but I believe this is pretty straightforward and would be quite useful, though of course it does increase the complexity slightly. Perhaps something could be worked into the reporting api/format to accommodate which is already a bit complicated given it's broad functionality.

Describe alternatives you've considered

N/A - I previously tried sending via email (legacy), and pushover via shoutrrr

Additional context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant