Say in each anomaly setting's description that it only sends an alert #412

Closed
opened 2026-11-19 08:39:19 +01:00 by clawbot · 1 comment
Collaborator

sneak on #410: "this suggests that setting this setting will mark a client as anomalous ... what it doesn't tell me is what 'anomaly' means. do they get banned? logged? rate limited?"

The descriptions of the SWW_WAF_ANOMALY_* settings (in the settings list in docs/ and wherever the code prints them) say "Alert when ..." but not what an alert does or does not do.

Definition of done: every SWW_WAF_ANOMALY_* description says plainly that crossing the threshold sends one alert to the configured alert destinations, and that the client is not banned, rate limited or blocked; the word "anomaly" is explained once where these settings are introduced; no setting is renamed; make check passes.

Model: opus-5-5

sneak on https://git.eeqj.de/sneak/smallwebwaf/issues/410: "this suggests that setting this setting will mark a client as anomalous ... what it doesn't tell me is what 'anomaly' means. do they get banned? logged? rate limited?" The descriptions of the `SWW_WAF_ANOMALY_*` settings (in the settings list in `docs/` and wherever the code prints them) say "Alert when ..." but not what an alert does or does not do. Definition of done: every `SWW_WAF_ANOMALY_*` description says plainly that crossing the threshold sends one alert to the configured alert destinations, and that the client is not banned, rate limited or blocked; the word "anomaly" is explained once where these settings are introduced; no setting is renamed; `make check` passes. Model: opus-5-5
Author
Collaborator

PR: #417 (branch issue-412-anomaly-alert-only, base next).

Every SWW_WAF_ANOMALY_* threshold in the README settings table now says crossing it sends one alert to the alert destinations and that no client is banned, rate limited or blocked. "Anomaly" is explained once in the README's configuration notes and once in docs/settings.md. Nothing is renamed.

Judgement call: the prefix settings and SWW_WAF_ANOMALY_WATCHED_NETS set no threshold, so their rows say instead that their thresholds only send alerts.

Load-sensitive internal/sww tests failed one make check and passed the rerun. Filed as #418.

Model: opus-5-5

PR: https://git.eeqj.de/sneak/smallwebwaf/pulls/417 (branch `issue-412-anomaly-alert-only`, base `next`). Every `SWW_WAF_ANOMALY_*` threshold in the README settings table now says crossing it sends one alert to the alert destinations and that no client is banned, rate limited or blocked. "Anomaly" is explained once in the README's configuration notes and once in `docs/settings.md`. Nothing is renamed. Judgement call: the prefix settings and `SWW_WAF_ANOMALY_WATCHED_NETS` set no threshold, so their rows say instead that their thresholds only send alerts. Load-sensitive `internal/sww` tests failed one `make check` and passed the rerun. Filed as https://git.eeqj.de/sneak/smallwebwaf/issues/418. Model: opus-5-5
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sneak/smallwebwaf#412