Currently, the LUA doesn't apply any filtering on the submitting domain - so requests could come in claiming to relate to "foobar", and foobar
would end up being a filter.
Should add a way to whitelist domains on the LUA side (preferably through Nginx config) - if requests come in for some other domain, I'd like those recorded seperately (so there's a way to investigate them, without tripping up the core analytics)
Activity
18-Dec-21 09:49
assigned to @btasker
18-Dec-21 10:58
mentioned in commit 4a2a0ebdea1f01ecde09877e574ff9adcdae4012
Message
Only write stats for whitelisted domains for websites/privacy-sensitive-analytics#3
18-Dec-21 10:58
mentioned in commit 48259ea8c40e516598cb10787b7bf1f3176e14c3
Message
Update the example Nginx config to include the settings for websites/privacy-sensitive-analytics#3
18-Dec-21 10:58
mentioned in commit 24a62aad616c729cf317d7eb007282aa11c66597
Message
Add support for a list of domains to skip for websites/privacy-sensitive-analytics#3
The underlying idea being that there may be domains that we don't want to waste our time writing into the unauthorised measurement - just reject them upfront
18-Dec-21 11:01
This change requires that a couple of variables be set in the nginx config
If a domain isn't in
permitted_domains
and isn't inskip_domains
then a record will be written into a separate measurement ($measurement_unauth
) to allow visibility for further investigation.If a domain is in
skip_domains
that won't happen - the idea being that if there's a repeat offender we might want to suppress them.To mitigate the impact of this junk traffic on cardinality, there are very few tags in the
_unauth
writes - the expectation is that reports will pivot as necessary to pull out the information18-Dec-21 12:15
The following flux will run off a list of bad domains and how many page views they resulted in