Docs / Monitoring / Notification Routing by Channel

Notification Routing by Channel

Published · Last updated: May 2026 · 3 min read

Who this is for

Anyone who wants to control which alerts go to which notification channels (email, Slack, Telegram, etc.).

What you will complete

Understand how alert notifications are routed to notification channels, and how to configure your channels for the right alert coverage.

Before you begin

  • At least one notification channel must be configured under Settings → Notification Channels.
  • Alert rules must be created under Alerts → Rules.

How routing works

CloudAIPilot sends alert notifications to all active notification channels in your organization when an alert fires. There is no per-rule channel routing at this time — all channels receive all alerts.

What this means in practice:

  • If you have Slack and email both configured, a firing CPU alert sends to both.
  • To receive different alerts in different places, configure channels based on who should be notified, not by alert type.
  • To silence all notifications for a specific alert temporarily, snooze the alert (see KB-06-05).

Alert notification contents

When an alert fires, the notification sent to each channel includes:

  • Alert name / rule description — what condition was met (e.g., "CPU Usage > 85% on server-name")
  • Severity level — Critical, Warning, or Info
  • Server name — which server the alert applies to
  • Current metric value — the value that triggered the alert (e.g., "CPU: 92%")
  • Time — when the alert fired
  • Link to dashboard — direct link to the Alerts page in your dashboard

When an alert resolves, a separate "resolved" notification is sent with the same information.

Configuring which events trigger notifications

You can control which notification events your channels receive using the Notification Preferences page.

  1. Go to Settings → Notification Preferences.
  2. For each event type (alert fired, alert resolved, backup completed, deployment failed, etc.), toggle which channels receive the notification.
  3. Save preferences.

This lets you, for example, send alert notifications to Slack but send backup failure notifications only to email.

Recommended channel setup for alerts

For small teams (1–3 people):

  • One email channel (for all alerts, as a reliable fallback)
  • One Slack channel (for real-time visibility)

For larger teams:

  • A team Slack channel for Warning alerts (visible to everyone)
  • An email or PagerDuty channel for Critical alerts (to reach on-call)
  • Telegram for personal mobile notifications

For production systems:

  • Always have at least two channels active, so that if one fails, alerts still reach you.

Testing your alert notification routing

  1. Go to Settings → Notification Channels.
  2. Find your configured channel and click Test or Send Test Notification.
  3. Verify the test message arrives in the channel.
  4. To verify an actual alert triggers the channel: create a temporary rule with an artificially low threshold (e.g., CPU > 1%), wait for it to fire, confirm the notification arrives, then delete the test rule.

Common errors and fixes

"My alert fired but I did not receive a notification" Cause (1): No notification channel is configured. Fix: Go to Settings → Notification Channels and add at least one channel.

Cause (2): The notification channel has an error (webhook URL changed, email bouncing, etc.). Fix: Go to Settings → Notification Channels, click Test on the channel, and diagnose the delivery error.

Cause (3): The alert was in Snoozed state when it would have re-notified. Fix: Check the alert status in Alerts → Events.

"I am receiving too many notifications for every alert" Fix: Configure Notification Preferences to limit which event types trigger each channel. Alternatively, raise alert thresholds or add duration requirements to reduce firing frequency.

Related articles