Notifications only work when they land with the right context. Use this playbook to keep FinOps signals high-signal and low-friction.

Channel cheat sheet

Recommended JSON payload

{
  "type": "anomaly",
  "team": "platform",
  "target": {
    "channel": "#gcp-spend",
    "provider": "slack"
  },
  "budgetImpact": 3400,
  "link": "/spending/projects?project=payments-prod",
  "notes": "Spend is +27% WoW after the batch import launch."
}

Implementation steps

1. Open frontend-user/src/components/AlertsPanel.tsx.
2. Map severity -> destination (PagerDuty for high, Slack for everything else).
3. Use Chakra Badge colors to mirror severity (green/yellow/red).
4. Add the docs link https://stackdyno.dev/docs/alerts-routing so recipients can self-serve context.

Measuring success

• Track mean time to acknowledge (MTTA) and mean time to resolve (MTTR) inside PagerDuty.
• Look for week-over-week reductions in ignored notifications.
• When in doubt, hide alerts rather than tuning teams out—doc updates are cheaper than trust rebuilds.

Once alerted teams know where to go for context, they start asking for more automation instead of muting it.