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

# Observe alerts

> Create Observe alert rules that notify the bell or a Slack channel when matching events reach a count in a window, or when none arrive; enable, disable and delete your own rules.

**Observe → Alerts** (`/observe/alerts`) lists the observability alert rules in your org unit. A rule counts matching events in a time window and pages a bell notification or a Slack channel when the count trips, or, as a deadman rule, when no events match at all. A rule created from a saved view on Events matches that view's filter; one created here matches all events. These rules are separate from the metric-threshold rules in [Analytics alerts](https://docs.gloo.com/forge/console/analytics/alerts.md). Reading the list needs `workflows:read`.

![Alert rules (light)](https://mintcdn.com/gloo-b243725a/xyq5perq6SLByPBn/forge/images/console/observe/alerts-light.png?fit=max\&auto=format\&n=xyq5perq6SLByPBn\&q=85\&s=2015a8da8e5b5e9aa010f09c421ff7a8)

Alert rules — Forge Console at `/observe/alerts`

## What you can do

* Read every rule in your org unit: your own and your team's.
* Create a rule with **New alert**, or from a saved view's **Alert** button in the **Views** menu on [Events](https://docs.gloo.com/forge/console/observe/events).
* Enable or disable your own rules, and delete them.

## The rules table

| Column | What it shows |
| - | - |
| **Name** | The rule name. A **Team** tag marks a rule someone else owns |
| **Predicate** | The condition, such as `≥ 3 in 15min`, `= 5 in 15min`, or `No matches in 15min (deadman)` |
| **Sink** | `Bell (info)`, `Bell (warn)`, `Bell (critical)`, or `Slack` |
| **Last fired** | When the rule last fired, or `never` |
| **24h fires** | How many times the rule fired in the last 24 hours |
| **Status** | **Enabled** or **Disabled**. On your own rule it is a button that switches the state |

Your own rules also have a delete button (**Delete this rule**), which asks you to confirm. Team rules are read-only. With no rules, the page shows **No alert rules yet** and a **New alert** button.

## Creating a rule

**New alert** opens **Create alert**. The dialog says whether the rule is bound to a saved view or defaults to all events.

| Field | What it sets |
| - | - |
| **Name** | For example `Production failures ≥ 3 in 15min`. From a saved view it defaults to `Alert: <view name>` |
| **Mode** | **At least** (fire when the count reaches the threshold) or **Exactly (deadman)** |
| **Count** and **In min** | The threshold count and the window, in minutes. **Exactly** with a count of 0 is a deadman rule: it fires when no events match in the window |
| **Sink** | **Bell notification**, with a **Severity** of **Info**, **Warn** or **Critical**, or **Slack channel**, with a **Slack channel ID** such as `C0123ABCD` |
| **Refire suppression (min)** | How long the rule waits before it can fire again. Default 15 |

Choose **Create alert** to save the rule.

## Key state to watch

* **24h fires** — a rule that fires all day pages people for nothing; raise its threshold or its suppression.
* **Last fired: never** — not proof that a rule is healthy. A rule that is not being evaluated never fires, whichever mode it uses. Only for an evaluated **Exactly (deadman)** rule with a count of 0 does "never" mean that matching events keep arriving.
* **Disabled** rules — they are not evaluated and page nobody.
* **Enabled-rule limit** — the workspace can have at most 50 enabled rules; creating or re-enabling a rule past that is refused, so disable rules you no longer need. Separately, each one-minute evaluation reads at most 500 enabled rules, oldest first, which the 50-rule limit keeps out of reach.
* **Dormant** rules — an enabled rule stops being evaluated when:

  * its owner no longer holds `audit:read`, `grants:read` and `policies:read`;
  * its saved view is deleted;
  * its saved view is neither the owner's own nor shared into the rule's org unit.

  The alerts table does not show this. The Events stream records one `observability_alert_dormant` event when a rule goes dormant.
* **The saved view behind a rule** — if the view's filter stops matching recent events, an **At least** rule never trips. A deadman rule fires instead, and again each time its refire suppression runs out.

## Related surfaces

* [Saved views](https://docs.gloo.com/forge/console/observe/saved-views.md) — the filters an alert rule can be bound to.
* [Events](https://docs.gloo.com/forge/console/observe/events) — where a saved view's **Alert** button creates a bound rule.
* [Analytics alerts](https://docs.gloo.com/forge/console/analytics/alerts.md) — metric-threshold rules.


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