zlacker

>>Adriaa+(OP)
I've moved away from using any kind of script embedded in my webpages for tracking and instead just use Goaccess (https://goaccess.io/) to analyze my logs. Though there are obvious caveats with this, you need to install it, configure the server logging to match it and so on. But personally the benefits outweighs the cons, it all runs on the server, you are the sole owner off all the data and this tracking doesn't require any kind of JS on the webpage.

>>sondr3+L2
Isn't there a problem with GDPR compliance if you want to serve European pages? You are allowed to log IP addresses for security reasons. However, as far as I understand the situation, you need the agreement of the users if you use their personal data, which includes IP addresses, for anything else.

Has somebody figured out how to resolve this situation with log files?

>>southe+Jb
You can use goaccess to create a log every day to json, excluding IP while retaining stats for geolocation.

For this you can logrotate daily and run goaccess before rotation. I believe you can keep the server logs for a week for debugging while respecting GDPR.

For today's "realtime" data you can use goaccess on today's log on demand and use a cache.

You can write your custom stat viewers or use goaccess to view time range data from multiple json files.