diff --git a/SPEC.md b/SPEC.md index 9d5d1e5..0a98378 100644 --- a/SPEC.md +++ b/SPEC.md @@ -2074,9 +2074,10 @@ host, sharing one address, would often fetch too close together. - Alerts go to a webhook as JSON, and to Slack and ntfy as formatted messages. `docs/alerts.md` lists the events, the JSON object and the messages. `SWW_WAF_ALERT_EVENTS` chooses which of the seven event types are sent; the - hourly `summary` is sent whatever it says. The bans an admin makes raise no - alert. In `observe` mode, a request that would have made a ban still raises - the ban's alert, with `mode` set to `observe` in its `detail`. + hourly `summary` is sent whatever it says. The bans an admin makes, and the + bans for AbuseIPDB's blacklist, raise no alert. In `observe` mode, a request + that would have made a ban still raises the ban's alert, with `mode` set to + `observe` in its `detail`. - A repeat is an alert with the same event, and the same netblock, source, file or anomaly scope, as one sent less than `SWW_WAF_ALERT_COOLDOWN` before. An anomaly scope is one of the things counted under "Anomaly thresholds". A diff --git a/docs/alerts.md b/docs/alerts.md index 0a11407..d692915 100644 --- a/docs/alerts.md +++ b/docs/alerts.md @@ -6,7 +6,7 @@ back or dropped. ## Events -- `ban`: a ban `waf` made. +- `ban`: a ban `waf` made for a broken limit or a clear sign of attack. - `permanent_ban`: a permanent ban it made, or an existing ban made permanent by a request. - `core_rule_set_match`: the Core Rule Set scored a request at or over the