yarmo/yarmo.eu
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Update note
All checks were successful
continuous-integration/drone/push Build is passing
Details

Browse Source
This commit is contained in:
Yarmo Mackenbach 2020-06-11 17:24:53 +02:00
parent d2cb10bc5a
commit 605bc69a40
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
content/notes/2020-06-11--plausible-start.md
View File

@ -20,3 +20,9 @@ This is not my intention for the simple reason that this blog is not made to tar
In the near-future, I will also compare what can be learned from a "client-side" statistics solution like [Plausible](https://plausible.io) with what can be learned from a "server-side" statistics solution like [GoAccess](https://goaccess.io).
The reason I am not performing this comparative experiment right now is because both solutions above manage to not support a single common log format. It seems it was decided a month or so ago that [GoAccess should conform to Caddy's format](https://github.com/allinurl/goaccess/issues/1768#issuecomment-629652452) ([separate issue on Caddy's side](https://github.com/caddyserver/caddy/issues/3417#issuecomment-629836804)). Until that happens (or until I figure out a way to parse Caddy's log format in GoAccess), this comparative experiment will have to wait.
---
## Update
The comparative experiment is back on! Thanks to [@AlexMV12](https://fosstodon.org/@AlexMV12) and this [blog post](https://alexmv12.xyz/blog/goaccess_caddy/) he wrote, I now have a working bash script to analyze Caddy's log file. See you in thirty days!