pgbadger VS AWStats

It might also help to use pgbadger or something similar to process your postgres logs and see whether some event is aligned with your outages.

Interestingly, when a place does get to the point where the single instance has capacity issues (after upgrading to EPYC and lots of flash drives) then other non-obvious stuff shows up too.

For example, at one place just over a year ago they were well into this territory. One of weird problems for them was with pgBadger's memory usage (https://github.com/darold/pgbadger). That's written in perl, which doesn't seem to go garbage collection well. So even on a reporting node with a few hundred GB's of ram, it could take more than 24 hours to do a "monthly" reporting run.

There wasn't a solution in place at the time I left, so they're probably still having the issue... ;)

First of all I used a profiler (pgbadger and netdata) to figure out where the lags were coming from. I then tried the usual stuff (increasing shared_buffers, max_wal_size, min_wal_size from their ultra low defaults), but the biggest performance gain came from moving the database from eMMC to a mechanical hard drive :-D

Look into PgBadger (a log parser/analyser): https://github.com/darold/pgbadger

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.

[1] - https://github.com/eldy/AWStats

Back in my day it was awstats. Still works great. I have 18 years of data.

https://www.awstats.org/

matomo and goatcounter are nice, but there are even solutions which don't need any extra CPU or any extra client request:

• https://goaccess.io/

• https://www.awstats.org/

Both of them are free/open-source.

I have decided to do something with my Apache server's log file beautifiers and analytics. When I moved from Fedora to Windows I added Google Analytics and more or less forgot about the older Analog, AWStats, and Webalizer that I was using.

AWStats does something similar: https://www.awstats.org/

You get a full picture of traffic without relying on inserting JS into the page

AWStats or Webaliser are two really good ones for parsing Apache logs, but I've always loved Matomo for projects where I need more than just webserver logs.

Analytics? Web server logs + AWstats

Your httpd will likely have an access log (e.g. apache, nginx). If enabled you can do something as simple as say grep /page/you/are/interested/in /var/log/$httpd/access_log | wc -l etc or look at tools such as https://www.awstats.org/