> For the complete documentation index, see [llms.txt](https://docs.luganodes.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.luganodes.com/rpc/platform-guide/alerts.md).

# Alerts

Get notified when usage, latency or errors cross a threshold

Alerts watch your organization's metrics and email the selected recipients when a threshold is breached. Owners and Admins create and manage rules on the Alerts page, and every firing is logged in Alert history with its timestamp and value.

### Alert types

<table><thead><tr><th width="174.53515625">Type</th><th width="338.19921875">Fires when</th><th width="113.125">Scope</th><th>Plans</th></tr></thead><tbody><tr><td>CU usage threshold</td><td>Monthly compute units cross a percent of your plan limit</td><td>Organization</td><td>All plans</td></tr><tr><td>Overage</td><td>Usage goes past the plan limit by a chosen percent</td><td>Organization</td><td>Growth, Pro</td></tr><tr><td>High latency</td><td>Average latency for an app on a chain exceeds a value over a window</td><td>App and chain</td><td>Growth, Pro</td></tr><tr><td>Error rate spike</td><td>Error rate for an app on a chain exceeds a percent over a window</td><td>App and chain</td><td>Growth, Pro</td></tr><tr><td>Daily CU limit reached</td><td>An app uses its whole daily compute unit allowance</td><td>App</td><td>All plans</td></tr></tbody></table>

### How rules work

A rule has a threshold, notification recipients, and, for latency and error rate alerts, a measurement window and a cooldown between repeat notifications. CU usage and overage alerts have no cooldown: they fire once per billing cycle and reset at rollover.

Recipients are members of your organization. Each firing emails them the alert name, the current value against the threshold and a link to the relevant dashboard view. Alert emails never contain endpoint URLs or API keys.

The daily CU limit alert works differently. It is sent automatically to Owners and Admins when an app reaches the daily CU limit set in its usage limits, so there is no rule to create and it does not count toward your rule limit. Requests to that app are then refused with HTTP 429 and the code app\_daily\_cap\_exceeded until the limit resets at 00:00 UTC. The app stays active, your other apps are unaffected, and refused requests cost no compute units.

### Plan limits

| Plan           | Active rules | Types available |
| -------------- | ------------ | --------------- |
| Free           | 1            | CU usage only   |
| Growth and Pro | 100          | All four        |

Deactivating a rule frees a slot. On a downgrade to Free, rules are deactivated and preserved, and upgrading restores them.