Allow tag-based notification routing for webhooks and email per host and service #998
Description
Is your feature request related to a problem? Please describe.
Currently, notifications (webhooks and email) in Pulse can only be defined globally. It's not possible to route notifications with fine granularity to different channels based on server or service context.
Describe the solution you'd like
It would be a significant improvement if notification routing could be managed using tags assigned to servers and/or services. For example, if every server or service could be tagged (e.g. according to customer, environment, or responsibility), each notification configuration (such as a webhook or email setup) could then specify exactly which tags it applies to.
This would make it possible to easily define rules like:
- All servers tagged with "customer:alpha" use email configuration 1 and webhook 1
- All services tagged with "critical" and "customer:beta" use webhook 2 and email 2
- Future servers/services just need to be tagged appropriately, and the notification logic would adapt automatically
This kind of tag-based routing would give much more flexibility and scalability, especially for teams managing many different servers, customers, or service types.
Describe alternatives you've considered
- Continue with global notification configuration (current approach), which is inflexible for different notification needs.
- Manually assign notification settings per server or service, which quickly becomes unmanageable at scale.
Additional context
Tag-based notification routing would let users easily express business logic and organizational structure, making it much easier to keep notification settings maintainable and relevant as the infrastructure evolves.