Repository navigation
Traffic analytics: exclude own and unwanted traffic at ingest (offer to implement) #12550
TobbyTravel
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Traffic analytics has been useful since v4.4. One thing I miss is a way to keep certain traffic out of the numbers.
The problem
On a small production server, I compared the dashboard with the proxy access log for four days:
/wp-admin,/.envand similar)For a low-traffic site the dashboard mostly shows me and the scanners. #12143 asks for something close to this for paths (static assets cluttering the view).
Proposal
Per-server exclusion rules, applied when Sentinel ingests a log line, before aggregation:
As far as I can tell the rollups are pre-aggregated per dimension, so this cannot be a filter at read time. It has to happen in Sentinel's
process_line, next to sampling. That makes it two changes:TRAFFIC_EXCLUDE_IPS,TRAFFIC_EXCLUDE_USER_AGENTS,TRAFFIC_EXCLUDE_PATHS), parsed in the config crate, checked per line, with a counter for excluded lines.TRAFFIC_IP_MODEis.Known limits: it applies from the moment it is set, existing rollups stay as they are, and excluded requests remain in the raw access log.
Questions
I am willing to implement both halves with tests if the direction is agreed here first.
All reactions