notification-routing

Route agent notifications by defining channel mappings in a JSON configuration file and tagging outputs with channel types. A dispatcher then sends notifications to appropriate destinations based on those tags, preventing important alerts from being buried in a single channel.

Organize team notifications using topic-based routing. By configuring custom channel mappings for notification types, agents tag messages with specific channel types, ensuring alerts are categorized and delivered to the correct destinations instead of overwhelming a single feed.

Configure custom channel mappings by defining the relationships between notification types and channel identifiers in your configuration file. Agents use these mappings to tag notifications, allowing the dispatcher to accurately route alerts to the appropriate configured channels.

The notification routing dispatcher supports multiple platforms through a provider-agnostic adapter system. Platform-specific adapters are used to handle flexible routing options, allowing the dispatcher to send notifications to various destinations across your team environment.

Agents tag notifications by including specific channel type tags in their outputs. The dispatcher reads these tags, matches them against the configured channel mappings, and routes the notification to the correct destination, ensuring alerts are sent to the right place.

Use a dedicated routing dispatcher when team notifications overwhelm a single channel and cause alert fatigue. It is optimized for environments where routine notifications bury important alerts, ensuring critical messages reach specific, targeted channels.