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

# Severity

> How Stealth decides whether a drop is Light, Attention or Critical, with the exact thresholds.

Every incident has a severity: **Light**, **Attention** or **Critical**. Severity decides who is alerted and how fast, so it follows one simple principle: it measures money, and a break costs more attention than a slow drift. The same scale is used by incidents, by the list on the [Panel](https://docs.usestealth.dev/en/screens/panel.md), by emails and by webhooks.

## How it works

Severity depends on two things:

1. **The estimated loss per day** of the drop. For hourly kinds it is the average loss per hour of the drop times 24.
2. **The kind of drop**, which sets the highest level it can reach.

| Kind | Below R\$ 10/day | R$ 10 to R$ 29.99 | R$ 30 to R$ 49.99 | R$ 50 to R$ 199.99 | R\$ 200 or more |
| - | - | - | - | - | - |
| **Ad unit stopped**, **No ads served** | no incident | Light | Critical | Critical | Critical |
| **Client lost traffic**, **Client fill rate dropped** | no incident | Light | Light | Attention | Attention |
| **Revenue per request dropped**, **Revenue trending down** | no incident | Light | Light | Light | Light |

Why the caps:

* **A broken ad unit is Critical from R\$ 30 per day.** It is the most expensive problem to miss and the easiest to fix, so it never waits.
* **A client-wide drop is at most Attention.** It usually has an outside cause (traffic, a demand partner) that the team needs to investigate, not an emergency fix.
* **A gradual drop is always Light.** Revenue per request and trends move over days. They belong in the daily summary, not in an urgent email.

> [!NOTE]
>
> Thresholds are in reais. For a network in another currency, the loss is converted with a fixed factor of 0.2: in dollars or euros, Light starts at 2 per day, Attention at 10, Critical at 40, and an ad unit break is Critical from 6.

### Getting worse

While an incident is open, Stealth recalculates the loss each time it evaluates it. If the new loss reaches a higher level, the severity goes up and an **escalated** event (**Drop got worse**) is sent. Severity never goes down while the incident is open. It ends when the incident is resolved.

## What you see

* On the [Incidents](https://docs.usestealth.dev/en/screens/incidents.md) page and the client page, next to the type.
* In alert emails, in the in-app notification and in the `severity` field of webhooks (`light`, `attention`, `critical`).
* In the **Minimum severity** and **Mandatory** settings of the [Control Center](https://docs.usestealth.dev/en/screens/control-center.md), each person's preferences and each webhook.

## FAQ

> [accordion] Can I change the thresholds?
>
> Not the thresholds themselves. You decide what reaches people with the organization's **Minimum severity**, exceptions per network, client, format or ad unit, and each person's preferences.

> [accordion] Why is a large client drop only Attention?
>
> Because the kind is capped at Attention. The estimated loss in the incident still shows the full amount, so you can sort by money on the Incidents page.


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