Systemd-resolved.service Watchdog timeout

In the modern web, AWstats and Webalizer can’t tell you very much about your usage.

It can’t see traffic served by CDNs or from local caches. It can’t see SPA interactions. It doesn’t know all that much about your users (relatively speaking, it just sees User-Agent, Referer, and IP), and it’s impossible to track “visits” when a user might travel across a bunch of IP addresses. If someone is browsing your site on a train, they’ll look like a dozen visits.

In some regards, this is a good thing. I’d rather more sites knew less about me. But, complicated web apps can have bugs and without data about usage, they might go unnoticed for a long time. And, if you want to best serve your users, you have to know a few things about them and actions they take.

There’s a reason nobody is spending much effort on tools like that, anymore. I don’t love the alternatives (a JavaScript bug that can track your every interaction feels bad, and it feels much worse when it feeds back to Google and/or Meta and a few thousand other “data partners”).