I realized that the #goAccess #web #analytics based on #nginx I use on #storySeedLibrary are pretty limited. Maybe too limited.

I'm considering to swapping to some JS-based ones, like Piwik or a similar #FLOSS solution.

Can you recommend anything?

Do you think that using JS-based analytics would compromise the privacy of the users?

14 days of #Luanti ContentDB stats, with ignore-crawlers (although some definitely remain)

From the Luanti client - 3.3M requests and 90K unique visitors last 14 days

From the web (likely including some bots): 2.3M requests and 112K unique users

The tool here is #GoAccess

I wrote a note about how to run a #Goaccess server on #NixOS: https://notes.abhinavsarkar.net/2025/goaccess-server-on-nixos

Question for the webmasters around here:

I'm parsing my web server logs with #goaccess. It tells me that this mornings blog post has around 2400 hits, 1600 visitors. The post includes an image, and I can see from the logs that the image has been accessed around 250 times.

I would expect the image to be downloaded roughly the same number of times as the website, however these numbers are vastly different. And I don't really understand why.

Any ideas?

And related, much of the traffic on the site is from crawlers with the user agent "http.rb/5.2.0". What could that be?

does anyone know why goaccess fills up my /tmp/ but doesn't delete it #goaccess #linux

I added a post aboout #guix + nginx + letsencrypt + #goaccess

https://mzan.dokmelody.org/posts/post-013/

Short blog article about leveraging goaccess to gather website analytics the easy way

#goaccess #linux #debian #ubuntu #webserver #selfhosted #nginx

https://jhx7.de/blog/website-analytics/

Roll your own static blog analytics!

Static blogs come with tons of advantages. They’re cheap to serve. You store all your changes in git. People with spotty internet connections can clone your blog and run it locally.

However, one of the challenges that I’ve run into over the years is around analytics.

https://major.io/p/static-blog-analytics/

I had forgotten what it was called earlier and therefore couldn't find their website. Now I have finally found #GoAccess again and will certainly use it on a #web offer now. Check how much the #server is loaded without revealing this to third part exploiters

https://goaccess.io

Petite question #sysadmin pour les personnes qui utilisent #Matomo : quelle est la consommation de CPU/RAM du logiciel en production, et avec quel volume de données ?

J’ai vu la doc de Matomo(1) à ce sujet, mais je n’arrive pas à croire qu’un programme qui lit 50 lignes de fichier journal par seconde aurait besoin de 4 serveurs dédiés avec 16 CPUs et 16 GB de RAM chacun.

Sinon, connaissez-vous un outil de génération de stats un peu plus poussé que #GoAccess qui reste utilisable sur une machine de taille raisonnable ?
Merci

1: https://matomo.org/faq/on-premise/matomo-requirements/

Für die #GoAccess Nutzer hier - aktuell sind die #Signaturen des #Debian / #Ubuntu #Repository kaputt.

For the #GoAccess users here - currently, the #signatures of the #Debian / #Ubuntu repository are broken.

Issue: https://github.com/allinurl/goaccess/issues/2321

A month ago, I promised a comparison between #plausible and #goaccess + server logs.

It's finally here [0] but much shorter than anticipated simply because @markosaric already made a great post [1] with nearly identical results and with excellent explanations.

Maybe just read his instead

Thanks again to @AlexMV12 for providing the bash script to use goaccess with caddy logs.

[0] https://yarmo.eu/post/plausible-versus-logs
[1] https://plausible.io/blog/server-log-analysis

Talking a bit about #goaccess and making my blog's stats publicly available. #100DaysToOffload

https://gabnotes.org/blog-statistics-part-2

Note on my #plausible experiment (and additional comment on #goaccess )

https://yarmo.eu/notes/plausible-start

#plausible vs #goaccess will have to wait. Goaccess and caddy found a way to NOT support a single common log format.

Apparently, a month or so ago it was decided goaccess should adapt to caddy.

https://github.com/allinurl/goaccess/issues/1768