Documentation / Alerting

Alerting

Define delivery channels — email, Microsoft Teams, Slack, or your own webhook endpoint — once for the whole organisation, then route platform events to them with scoped rules.

Cirrova's alerting subsystem is built around two concepts: channels (where notifications go) and rules (which events route to which channels). Both live on a single page — Organisation Settings → Alerting — so every recipient and every routing decision sits in one place rather than being scattered across tenants and budgets.

EVENTS RULES CHANNELS Anomaly detected Anomaly resolved Budget threshold Snapshot failed Rule A Anomaly · prod tenant Rule B Budget · all Email Microsoft Teams Slack Custom webhook
An event matches one or more rules; each matched rule fans out to its configured channels. A channel (here, Slack) can be attached to multiple rules.

A channel is a named delivery endpoint — a Slack workspace webhook, a list of email recipients, an HTTPS endpoint of your own, and so on. A rule says "when an event of type X happens within scope Y, deliver to channels Z". Channels and rules are independent: one channel can be reused across many rules, and one rule can fan out to many channels.

Splitting routing from delivery makes the common patterns straightforward — production anomalies into a war-room Slack and on-call email; budget alerts to finance; everything mirrored to your own webhook for archiving — without duplicating recipient lists across budgets or tenants.

Centralised alerting requires a Control plan or above. The page is read-only on lower tiers. See Pricing for a full feature comparison.

In this section

Channels
Named delivery endpoints — Email, Microsoft Teams, Slack, or Custom webhook. How to configure each type, send a test, and enable or disable without breaking rules.
Rules
Match platform events to channels with optional scope filters. Covers the four event types, scoping by tenant / subscription / resource group / tag / budget, and the per-rule delivery history view.
Custom webhooks
Full integration spec for the Custom webhook channel: request headers, HMAC-SHA256 signature verification, retry schedule, payload structure, and per-event payload schemas.
Related reading
Anomaly Detection → Notifications covers how anomaly events are raised. Budgets → Alert thresholds covers how budget threshold events are raised.

Permissions

Channels and rules are organisation-wide settings, so management is gated at organisation level.

  • Organisation owners can create, edit, and delete channels and rules, and view delivery history.
  • Other roles (including tenant admins) cannot manage alerting configuration. They can still trigger events that fire rules, and they receive deliveries via channels they're recipients on, but the page itself is read-only.

Anomaly sensitivity is a separate per-tenant setting and is still managed under Organisation Settings → Tenants → tenant → Cost tracking by tenant admins. Sensitivity controls which events are raised; alerting rules control where raised events are delivered.

Previous Budgets First article Channels