Docs/Alerts & Routing

How to

How to configure anomaly and region alert routing

Route critical FinOps and Security events to the right channel and ensure responders can act quickly.

Back to How To Guides

Priority Events

  • Burn-rate anomaly.
  • Unauthorized region deployment.
  • Carbon spike anomaly.
  • `budget.forecast.exceeded` forecast overrun event.

Channel Setup

  1. 1. Open `Integrations > Notifications`.
  2. 2. Create webhook channels by incident type or team.
  3. 3. Map high-priority events to dedicated channels.
  4. 4. Configure fallback channel for failed delivery scenarios.

Validation

  • Use test delivery action for each channel.
  • Trigger sample events from scanner or policy checks.
  • Confirm links route responders directly to relevant dashboard context.

Response Workflow

Route high-severity events to ticketing escalation (Jira or ServiceNow) when required by policy. Keep incident SLA ownership explicit per team.

Get started

Find recoverable spend before the next invoice lands.

Connect one AWS, Azure or GCP scope, approve the safest savings actions, and give finance a receipt when the savings verify.

Read-only scan first. Approval gates before remediation.