Skip to main content

Routes & Channels

Routes and channels define where alerts go and how they are delivered.

Use this guide to explore how routes and channels determine where monitoring alerts are sent based on severity, environment, application, and ownership.

Routes​

Routes are trees of matching rules that decide:

  • Which alerts go to which teams or destinations.
  • How severity, environment, or application affect routing.
  • How to handle default or “catch‑all” cases.

Example patterns:

  • Route prod / critical alerts for a specific application to that team’s on‑call rotation.
  • Route dev or stage alerts primarily to Slack channels for faster iteration.
  • Route infrastructure‑level alerts (for example, Zabbix host down) to a central NOC.

Channels​

Channels are the concrete destinations for notifications, such as:

  • Email distribution lists.
  • Slack channels.
  • PagerDuty or other incident‑management platforms.
  • Generic webhooks to SIEM/SOAR or ticketing systems (e.g., Jira).

Configure these channels using relevant Cloudaware integration guides (for example, PagerDuty, Slack, Jira, SIEM/SOAR, Webhooks).

Design Tips​

  • Use CMDB attributes like application, environment, and owner when building routing rules.
  • Keep the routing tree as simple as possible while still reflecting your organization's structure.
  • Periodically review routes to ensure they still match how teams are organized and how services are owned.