NodeFilesystemFillingUp

# NodeFilesystemFillingUp

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: `warning`
- Team: `platform`
- Pending duration (`for`): 30m

```promql
instance:node_filesystem_avail:ratio < 0.2
and
predict_linear(node_filesystem_avail_bytes{fstype!~"tmpfs|overlay"}[6h], 4 * 3600) < 0
```

## What the condition means

Available space is under 20 percent and predict_linear over 6 hours reaches zero within 4 hours. tmpfs and overlay are excluded.

## 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/NodeFilesystemFillingUp`. 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`.

返回告警目录