OrdersApiErrorBudgetBurnFast

# OrdersApiErrorBudgetBurnFast

Larkspur Grocers is fictional. This note explains the alert. It is not an incident report. It does not record a page, a customer impact, or an MTTR.

## Signal

- Severity: `critical`
- Team: `orders`
- Pending duration (`for`): 2m

```promql
(
  slo:sli_error:ratio_rate1h{service="orders-api",slo="availability"} > (14.4 * 0.001)
  and
  slo:sli_error:ratio_rate5m{service="orders-api",slo="availability"} > (14.4 * 0.001)
)
or
(
  slo:sli_error:ratio_rate6h{service="orders-api",slo="availability"} > (6 * 0.001)
  and
  slo:sli_error:ratio_rate30m{service="orders-api",slo="availability"} > (6 * 0.001)
)
```

## What the condition means

Page when the orders-api availability SLI burns at 14.4x on both the 5m and 1h windows, or at 6x on both the 30m and 6h windows. The objective is 99.9 percent, so the budget is 0.001.

## What an on-call would check

1. Read the expression above and the recording rules it uses.
2. Compare it with the promtool unit tests in `tests/rules/`. Every alert except Watchdog has a firing case and a non-firing case.
3. The annotation `runbook_url` is `https://runbooks.larkspur.example/OrdersApiErrorBudgetBurnFast`. That host is a placeholder. This file is the copy in the repo.
4. This stack does not page anyone. Receivers use `*_file` credential paths and `example.invalid`.

返回告警目录