AWStats

There is a middle ground. Maybe one need not add third party privacy invading analytics but there are simple self hosted solutions that have been around for ages and probably covers most of what people are looking for such as AWStats [1]. Logs can be merged into a centralized tiny web server on ones private network and that node can be running AWStats. Demo [2]. Main site [3]. [1] - https://github.com/eldy/AWStats [2] - https://www.nltechno.com/awstats/awstats.pl?config=destaille... [3] - https://www.awstats.org/

Check out tirreno: https://play.tirreno.com (admin/tirreno) It's self-hosted, PHP/Postgresql, server-side. Plus, you can get a free tier with 1,000 API requests/month if you want to enrich data about your IP visitors. As a co-founder, I believe it's one of the most advanced solutions available. (-; If not joking, I use tirreno for some personal websites with partly masked IP as it shows very interesting insights about bots and their behavior. Under 90s thing you probably mean is awstats (https://github.com/eldy/awstats). CERN and many other organizations continue to use it even now.

This is really clever and fun. I'm curious how the results compare to something "old school" like AWStats? https://github.com/eldy/awstats

Based on your requirements it sounds like AWStats [1] may be a fit. It's rather old-school but it's simple and works great on access logs and can be run on any node that you consolidate your logs to. It's had a sketchy security history so run it on something only you can access and/or put decent authentication in front of it. Some Linux distributions include AWStats as a package in their repositories. [1] - https://github.com/eldy/AWStats

I don't know if many still use it but AWStats [1][2] is one of the oldest self hosted solutions. I used it ages ago. It uses access logs vs. other platforms depending on javascript being embedded in pages. It's had some vulnerabilities in the past so it should be protected by authentication. It depends on Perl and a web server that supports CGI scripts. Stats processing is done in cron against the access logs so there is no added load based on page visits. It could even be run on a separate machine/node that logs are aggregated to. Part of the installation is configuring which log format your servers use. If using a non standard format one can map the related fields. If configuring AWStats to perform reverse DNS lookups I would suggest also installing Unbound DNS specifically on that machine and setting the following in /etc/unboun

I’ve deployed this in the past. Analog[0], AWStat[1], W3Perl[2] are some that come to mind. [0] - https://www.c-amie.co.uk/software/analog/ [1] - https://github.com/eldy/awstats [2] - http://www.w3perl.com

Yes, I've also been using awstats for many years. It definitely works for a small site, has a lot of useful features and occasional releases still keep up with new user agents, etc. that pop up over time. Each time I want to switch I fail to find a suitable replacement. That said, behind the curtain, awstats has plenty of problems and shows its age. Most of it is a single ~20 kline script with hundreds of global variables, so it's very challenging to debug. There are no tests. Over time it also had plenty of security issues [1]. I wouldn't recommend running it in any other mode than for generating static HTML reports from an unprivileged cronjob. I've made my own test suite and I'm using a slightly patched version with ~20 commits on top of the latest release that fix problems I found and that upstream didn't merge (still from the times o