Alerts now post to Slack

Send Cloud Intelligence™ alert notifications to the Slack channels that own each workload, alongside or instead of email.

An alert is only as good as the moment someone reads it. Cloud Intelligence™ Alerts have always been flexible on the trigger side: any scope, any metric, daily to yearly, with per-dimension evaluation. On the delivery side they had exactly one option, an email digest. That works for the person who created the alert. It does not work for the engineering team whose Compute Engine SKU just doubled, because that team lives in Slack and treats the FinOps inbox as an archive. So people forwarded emails by hand, or wired up CloudFlow flows, or just missed it.

What you get

When you create or edit an alert, the notifications step now has a Slack channel picker next to the email recipients. It is the same picker you already use for budget thresholds, so if your workspace is connected through the Cloud Intelligence™ app for Slack, your channels are already there. Add one channel or several. Each channel gets its own delivery, and retries are idempotent, so a slow Slack API or a retried job will not double-post into a channel.

Email keeps working exactly as before: same daily digest, same schedule, same recipients. Nothing you have set up changes unless you change it. Slack recipients are configured in the console for now; the Alerts API and Terraform provider do not expose them (yet).

Get started

1. Connect your Slack workspace through the Cloud Intelligence™ app for Slack, if you have not already. A Slack workspace admin needs to do this once.
2. Create an alert or open an existing one, and add Slack channels in the notifications step.
3. Keep the email digest for the people who want it. See Subscribe to alerts notifications for how subscriptions work.

If you route an alert into a channel where engineers actually act on it, tell us what the message is missing. That is the feedback that shapes what the Slack post looks like next.