Operations

Notifications & Alerting

Route important platform events to the teams that can actually act on them.

Channel types

Slack incoming webhooks

Microsoft Teams incoming webhooks

In-product alerts and dashboard indicators

Budget threshold events

Governance drift events

High-severity findings

Action lifecycle events

Operational anomalies

Region policy exceptions

FinOps channel

Budget thresholds, commitment opportunities, rightsizing regressions and spend anomalies.

Security channel

Critical exposure findings, unauthorized regions, public access changes and policy exceptions.

Platform channel

Scan failures, integration health changes, queue delays and action execution failures.

Audit channel

Evidence bundle completion, export job failures and policy change notifications.

Critical

Route immediately to the owning team and keep the alert visible until acknowledged.

High

Route during business hours unless the event affects production, identity or internet exposure.

Medium

Batch into daily triage where possible to avoid alert fatigue.

Low

Keep in product dashboards unless a team explicitly asks for notifications.

Next: configure routing in How to configure alerts routing and validate prerequisites in Integrations.