Alerts
Detect, group, route, treat, suppress, and measure operational cost and usage signals.
What this product area is for
Alerts is the operational center for signals. It turns noisy detections into cases, routes notifications, supports incident escalation, manages noise control, connects runbooks, and measures alert quality.
Who uses it
- FinOps operators
- Platform teams
- Support teams
- Admins
Core workflows
- Triage cases.
- Inspect individual alerts.
- Declare and update incidents.
- Configure routing and escalation.
- Suppress or snooze noisy signals.
- Attach runbooks.
- Measure alert quality and response performance.
What Alerts owns
- Cases, individual alerts, incidents, routing, escalation, noise control, runbooks, and alert analytics.
What Alerts does not own
- Approvals, caps, policies, exceptions, and audit, which belong in Guardrails.
- Optimization workflow, which belongs in Optimizations.
- Cost dashboards, which belong in Costs.
- Slack OAuth and webhook setup, which belong in Integrations.
Tabs in this area
- Overview — Understand the Alerts operating model.
- Cases — Group related alerts into operational work items.
- Alerts — Inspect individual alert signals.
- Incidents — Escalate critical cases into incident workflow.
- Routing & Escalation — Configure how alerts notify teams and escalate over time.
- Noise Control — Manage suppressions, snoozes, maintenance windows, and muted cases.
- Runbooks — Guide repeatable operational responses.
- Analytics — Measure alert quality, response performance, routing reliability, and noise.
Recommended operating model
- Start from the overview to identify the most important signal.
- Open the tab that owns the workflow.
- Use filters to narrow the scope before taking action.
- Open detail drawers before changing sensitive configuration.
- Use related links instead of duplicating workflows across product areas.
- Confirm sensitive actions such as rotation, deletion, approval, payment changes, or revocation.
- Preserve request IDs, trace IDs, run IDs, and audit IDs when escalating.
Product boundaries
Kadryn keeps each product area focused. Alerts should provide enough context to understand the situation, but ownership of related workflows stays with the product area that is responsible for them.
For example, a page may show linked alerts, approvals, reports, integrations, or recommendations, but the full administration of those objects remains in their owning menu.
Related docs
Use the related links panel to continue into concepts, developer setup, troubleshooting, or security guidance.