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

# Incidents Digest

**Incidents Digest** lets you send a scheduled summary of incidents to your team in addition to real-time alerts. Your team receives a consolidated digest on a daily or weekly cadence covering the incidents that matter for that period — either only what changed since the last send, or a snapshot of still-open incidents over a lookback window.

This is useful for reducing noise, providing management-level visibility, or keeping stakeholders informed without overwhelming them with individual alerts.

![Incidents Digest tab in Alert Rules](https://mintcdn.com/elementary/g2yzs1TzUZKxy0TN/pics/cloud/incident_digest_list.png?fit=max\&auto=format\&n=g2yzs1TzUZKxy0TN\&q=85\&s=ab864bfc8a836fe8e482611739b935b3)

## How it works

Digest rules are configured under **Alert Rules → Incidents Digest** tab. Each rule defines:

* **When** to send the digest (cadence: daily or weekly, at a specific hour)
* **Which** incidents match (filters by tag, owner, status, model, or category)
* **What to include** (only what changed since the last send, or full incident status over a lookback window)
* **Where** to send it (one or more destinations such as a Slack channel or email)

At the scheduled time, Elementary collects the incidents that match the rule and delivers them as a single message.

![Incidents digest email](https://mintcdn.com/elementary/g2yzs1TzUZKxy0TN/pics/cloud/incident_digest_email.png?fit=max\&auto=format\&n=g2yzs1TzUZKxy0TN\&q=85\&s=bebe444cf0dac0de039713a769a030d1)

## Creating a digest rule

Navigate to **Alert Rules** in the left sidebar and select the **Incidents Digest** tab. Click **Create digest rule** to open the configuration drawer.

The filters, categories, and destinations are configured the same way as in [Alert Rules](https://docs.elementary-data.com/cloud/features/alerts-and-incidents/alert-rules.md). Unique to digest rules are **cadence** and **what to include**.

### Cadence

Choose how often the digest should be sent:

* **Daily** — sent once a day at the hour you choose.
* **Weekly** — sent once a week on the day and at the hour you choose.

The time is in UTC.

### What to include

Under **What to include**, choose how the digest selects incidents:

* **Only what changed** — incidents that opened, were acknowledged, or resolved since the previous report. Already-open incidents that failed again are not included.
* **Full incident status** — a snapshot of still-active incidents over a lookback window, plus anything that changed since the last report.

New rules default to **Full incident status** with a **3 day** lookback. Existing rules stay on **Only what changed** until you edit them.

![Digest schedule, what to include, and lookback](https://mintcdn.com/elementary/Uxl46T0pIuWHGtvM/pics/cloud/incident_digest_lookback.png?fit=max\&auto=format\&n=Uxl46T0pIuWHGtvM\&q=85\&s=cd976a404f4b10291a022e6a8abf1872)

#### Full incident status

When **Full incident status** is selected, set **Look back** to 1, 3, 7, 14, or 30 days. The digest then includes:

* **Open** — incidents that are still open and whose last failure is within the lookback window, including ones that opened earlier. This matches the [incidents page](https://docs.elementary-data.com/cloud/features/alerts-and-incidents/incidents.md) for the same window.
* **Acknowledged** — the same, for incidents you have already acknowledged.
* **Resolved since last report** — incidents that closed since the previous digest, so the report shows what got done without repeating everything resolved in the last N days.

Open and acknowledged incidents that are also new since the last report are marked with a **New** indicator.

Incidents that are still open but have not failed inside the lookback window are omitted. Cadence still controls when the digest is sent; lookback controls which open incidents appear in it.

> [!NOTE]
>
> To get a daily reminder of still-open incidents, edit the digest rule, select **Full incident status**, and set a lookback (for example 7 days). Leaving the rule on **Only what changed** continues to send only activity since the last report.

## Managing digest rules

Once created, digest rules appear as cards in the **Incidents Digest** tab. From each card you can:

* **Edit** the rule to change any configuration.
* **Activate / Deactivate** the rule without deleting it.
* **Delete** the rule.

![Digest rule action menu](https://mintcdn.com/elementary/g2yzs1TzUZKxy0TN/pics/cloud/incident_digest_rule_menu.png?fit=max\&auto=format\&n=g2yzs1TzUZKxy0TN\&q=85\&s=6c6a98943390365a3ce50a5c96dbb9b3)

## Relationship with alert rules

Digest rules are independent of [Alert Rules](https://docs.elementary-data.com/cloud/features/alerts-and-incidents/alert-rules.md). You can have both real-time alert rules and digest rules active at the same time — they are evaluated separately. A common pattern is to use real-time alert rules for critical on-call channels and digest rules for broader team summaries.


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