Notification Router

A complete notification routing layer for agents and services. Sends alerts to Slack, Discord, Telegram, PagerDuty, email, or any HTTP webhook — automatically choosing the right channel based on severity, alert type, source, and time of day.

Includes: severity-based routing (critical → PagerDuty + Slack, info → Discord only), per-route throttling to prevent alert storms, deduplication to suppress repeated alerts, quiet hours to avoid 3am pings for non-critical issues, dry-run mode for testing, and full audit logging.

Ships as a single portable bash script with a JSON config file. No dependencies beyond curl and jq. Integrates with cron jobs, CI/CD pipelines, health checks, and log watchers via CLI flags or JSON pipe input.

Every agent operator running services needs a notification layer that decides WHERE to alert and WHEN to stay quiet. This is that layer.