CloudInfraOS

Notification Channels

Notification channels deliver alerts and runbook events to your team. Configure email, Slack, and webhook channels to ensure the right people get the right information at the right time.

Channel Types

Email Notifications

Email is always available out of the box. Alert emails include:

  • The alert name, severity, and trigger condition
  • The affected resource or cost data that triggered the alert
  • A direct link to the relevant page in CloudInfraOS
  • Timestamp and suggested next steps

Emails are sent to the address associated with your CloudInfraOS account. Additional recipients can be added from the notification settings page.

Slack Notifications

Send alerts and runbook execution updates to a Slack channel. To set up:

  1. Create a Slack app with incoming webhook permissions
  2. Generate a webhook URL for your target channel
  3. In CloudInfraOS, navigate to Settings → Notifications
  4. Add the webhook URL and select which events to forward

Webhook Notifications

Send event payloads to any HTTP endpoint. Use this for custom integrations — forward alerts to PagerDuty, Opsgenie, Discord, Microsoft Teams, or your own internal tools.

Each webhook delivery includes a JSON payload with the event type, affected resources, alert severity, and a signature header for verification. See Webhooks API for the full payload schema.

Notification Preferences

From the Settings → Notifications page, you can:

  • Toggle individual notification channels on or off
  • Set per-channel preferences (which alert severities to send, quiet hours)
  • Add multiple recipients to email channels
  • Test each channel with a sample notification

Notification Routing

Different alert severities can be routed to different channels. For example:

  • Critical — email + Slack + webhook (PagerDuty)
  • Warning — Slack only
  • Info — no notification (dashboard only)

Configure routing per alert rule or set organization-wide defaults from the notification settings page.