Say the anomaly thresholds only send an alert (closes #412)
check / check (push) Failing after 4m20s
check / check (push) Failing after 4m20s
Each SWW_WAF_ANOMALY_ threshold's description now says crossing it sends one alert to the alert destinations and bans, rate limits and blocks no client. The prefix and watched-netblock settings say their thresholds only alert. README's configuration notes and docs/settings.md explain "anomaly" once. Model: opus-5-5
This commit is contained in:
1 parent
dadd5768d5
commit
39f3387335
2 files changed
+32
-23
No files matched your search
@@ -364,6 +364,11 @@ tag that no request can get stops the start. A request can get only these:
|
||||
|
||||
## Anomaly thresholds
|
||||
|
||||
An anomaly is more requests or bytes than one of these thresholds allows.
|
||||
Crossing a threshold sends one `anomaly` alert to the destinations under
|
||||
"Alerting", and does nothing else: no client is banned, rate limited or blocked.
|
||||
`SWW_WAF_ALERT_COOLDOWN` holds back repeats of that alert.
|
||||
|
||||
Each scope has four thresholds: the most requests and the most body bytes
|
||||
counted in a minute and in an hour. The bytes are those `SWW_WAF_BYTES_COUNTED`
|
||||
names. Requests are counts, bytes are sizes. Each is `off` by default. The four
|
||||
|
||||
Reference in new issue
Block a user