> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cube.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Alerts

> Set up email alerts for API outages, database timeouts, pre-aggregation failures, and build completions in Cube.

Alerts notify you by email when something happens in your account: an API goes
down, a database stops responding in time, a pre-aggregation build fails, or a
build finishes.

> [!NOTE]
>
> Available on [Premium and above plans](https://cube.dev/pricing).

## Manage alerts

Click **Alerts** in the sidebar to see every alert configured on the account. Click
**Create alert** to add one, or use the edit and delete icons on a row to change or remove
an existing alert.

On plans below [Enterprise](https://cube.dev/pricing), only account administrators can
manage alerts. On the Enterprise plan, access also follows the `AlertsCreate`,
`AlertsRead`, `AlertsUpdate`, and `AlertsDelete` actions. Administrators always have
access, and the built-in Developer and AIBI Developer roles carry all four. The same four
actions also govern [budgets](https://docs.cube.dev/admin/account-billing/budgets).

> [!NOTE]
>
> These four actions are not among the ones you can pick when you build a \[custom
> role]\[ref-custom-roles]. To grant them, assign a built-in Developer or AIBI Developer
> role.

## Event types

Each alert watches a single event type:

| Event type | What it detects | Resolved email |
| - | - | - |
| **API outages** | The API stops responding | Yes |
| **Database response timeouts** | The database takes too long to answer | Yes |
| **Pre-aggregation build failures** | A [pre-aggregation](https://docs.cube.dev/admin/monitoring/pre-aggregations.md) build fails | Yes |
| **Build completed** | A build reaches a terminal state | No |
| **All** | Every event type above | Per event type |

The first three are conditions: Cube emails you when the condition starts, then emails
you again with a `Resolved —` subject prefix when it clears. While a condition persists,
Cube does not re-send the same alert for a while — 1 hour for API outages and database
response timeouts, 3 hours for pre-aggregation build failures.

> [!WARNING]
>
> **Build completed** fires when a build finishes, whether it succeeded or failed. The
> subject line reads `Build finished with status: <status>`. It is a point-in-time event,
> so it has no resolved email.

## Deployments

An alert applies either to **All** deployments in the account, or to a **Specific** set
you pick. Choosing **Specific** requires at least one deployment.

## Recipients

Under **Send alerts to**, pick who receives the alert:

* **All users on this account** — every user receives it. Use the **Also send to** field
  to add email addresses of people outside the account.
* **Specific users** — use the **Recipients** field to search for users on the account,
  or type any email address. Add at least one recipient, a user or an address.

If you type the email address of a user on the account, Cube adds that user instead, so
nobody receives the same alert twice.

> [!NOTE]
>
> **All users on this account** only reaches users who have signed in at least once. Users
> who were invited but never signed in do not receive alerts.

## Delivery

Alerts are delivered by email — there is no Slack, webhook, or PagerDuty delivery.
[Dashboard deliveries and their alerts](https://docs.cube.dev/docs/explore-analyze/dashboard-deliveries.md),
which send dashboards and alert on their numbers, are a separate feature with
their own delivery channels.

Recipients who are Cube users also get each alert, and its resolution, in their
[inbox](https://docs.cube.dev/docs/inbox.md).

To alert from your own observability stack instead, export telemetry with [monitoring
integrations](https://docs.cube.dev/admin/monitoring/monitoring-integrations).

[ref-custom-roles]: https://docs.cube.dev/admin/users-and-permissions/custom-roles.md


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.