CoreWeave Alerts is a new platform feature that delivers real-time notifications about your clusters, deployments, and operations. Alerts are managed in the Cloud Console across two pages. The Integrations page connects destinations, and the new Alert configuration page chooses which alerts your organization receives and which destinations each one goes to. You can view your full alert history in the Cloud Console.
In-app delivery is enabled by default for every organization, so alerts appear on the Alert history page. To send alerts to Slack or a webhook, connect the destination on the Integrations page and then opt alerts in to that destination on the Alert configuration page. Enabling an additional destination doesn’t disable in-app.
Alert configuration page
The new Alert configuration page lists every alert your organization can receive, grouped by category (such as Distributed File Storage, AI Object Storage, GPU (hardware health and runtime errors), and SUNK) and tagged with a severity of Critical, Warning, or Info. You can:
- Toggle delivery for a single alert per destination, including in-app.
- Use Configure all on a category to enable or disable an entire category across one or more channels at once.
For a walkthrough, see Configure alerts.
Destination types
Alerts can be delivered to four destination types: in-app (enabled by default), Slack OAuth, Slack webhook, and generic webhook. In Slack, alerts appear from the CoreWeave Mission Control app.
Slack OAuth integration
Connect the CoreWeave Mission Control app to your Enterprise Slack workspace through an OAuth authorization flow. This integration supports alert threading, message editing, and connecting multiple channels from a single authorization.
For setup instructions, see Slack OAuth integration.
Slack webhook integration
Connect CoreWeave Mission Control to a Slack channel using an incoming webhook URL. This is useful for teams that manage their own Slack app integrations or prefer a simpler setup without the OAuth authorization flow.
For setup instructions, see Webhook integrations.
Generic webhook integration
Use the CoreWeave Mission Control app to send alerts to any HTTPS endpoint, enabling integration with third-party tools, custom dashboards, or internal services. Optionally configure a signing secret to verify payload authenticity using the X-CoreWeave-Signature header.
For setup instructions, see Webhook integrations.
Destination limits
Your organization can have at most one Slack destination (either Slack OAuth or Slack webhook) and one generic webhook destination at a time. To switch types, you must delete the existing destination before creating a new one.
IAM access control
Access to alerts is split between two areas, each with its own IAM roles. Grant these through an IAM Access Policy.
| Task | Required role |
|---|
| View the Integrations page and the destinations list | Integrations Viewer (READ_INTEGRATIONS) |
| Create, update, or delete Slack and webhook destinations | Integrations Admin (WRITE_INTEGRATIONS) |
| View the Alert configuration and Alert history pages | Notifications Viewer (READ_NOTIFICATIONS) |
| Subscribe or unsubscribe alerts on the Alert configuration page | Notifications Admin (WRITE_NOTIFICATIONS) |
The legacy admin group doesn’t automatically include any of these roles. Administrators must create or update an IAM Access Policy to explicitly grant the appropriate roles to the users or groups that need them.
Destination type reference
| Destination type | Description |
|---|
| In-app | Default channel; alerts always appear on the Alert history page |
| Slack OAuth | Multi-step OAuth flow with alert threading and multi-channel support |
| Slack Webhook | Single-channel Slack delivery using an incoming webhook URL |
| Generic Webhook | HTTPS endpoint delivery with optional signature verification |
