Default the netblock and AS number anomaly thresholds (closes #410)
check / check (push) Failing after 1m37s

The alert-only thresholds per netblock and per AS number now have
defaults that alert on obvious abuse alone: per netblock 1200 and
15000 requests a minute and an hour, 5G and 50G a minute and an hour;
per AS number five times those. The AS number ones default to off
while SWW_WAF_LOOKUP_SOURCE is off. The other scopes stay off. The
README says to tune them to the site's traffic.

Model: opus-5-5
This commit is contained in:
sneak committed 2026-11-20 05:05:29 +00:00
1 parent 8219664ad1
commit b8abb87738
7 files changed
+149 -32

No files matched your search

+8 -6
View File
@@ -2113,12 +2113,14 @@ host, sharing one address, would often fetch too close together.
### Anomaly thresholds
These only alert; nothing is blocked. None is set by default, and a threshold
left unset sends no alert. An alert needs a destination only the operator can
supply, and what counts as unusual depends on each service's normal traffic,
which the metrics show. They reveal a widely distributed scraper, thousands of
addresses at low rates each, which the per-client limits do not see. A low
percentage for its `asn=` tag in `SWW_WAF_TAG_LIMIT_PERCENT` is the response.
These only alert; nothing is blocked. The thresholds per netblock and per AS
number have defaults high enough to alert only on obvious abuse. The others are
off by default. What counts as unusual depends on each service's normal traffic,
which the metrics show, so the defaults are a starting point for the operator to
tune. An alert goes nowhere until the operator sets a destination. The
thresholds reveal a widely distributed scraper, thousands of addresses at low
rates each, which the per-client limits do not see. A low percentage for its
`asn=` tag in `SWW_WAF_TAG_LIMIT_PERCENT` is the response.
- Requests and body bytes, as `SWW_WAF_BYTES_COUNTED` counts them, are counted
per minute and per hour, for each of: