4 ms·
We had it implemented for quite sometime, but later on moved to a different platform as it had issues in correctly parsing historical logs. We did try to hack i
by rishabhd 7y ago
We had it implemented for quite sometime, but later on moved to a different platform as it had issues in correctly parsing historical logs. We did try to hack it and wrote some scripts to zcat, output/ merge but in vain.
Overall, it is fast, intuitive and customizable.
- dragonsh 7y agoWere you trying to parse nginx, apache or haproxy logs? I believe it depends on your logging strategy and then in go access you need to define the log format. It will parse according to the log format [1]. For example $sed -n '/'$(date '+%d\/%b\/%Y' -d '1 week ago')'/,$ p' access.log | goaccess -a - $awk '$8=$1$8' access.log | goaccess -a - $goaccess access.log --log-format='%^[ %^[ %^[%x.%^] %^ %^/%^/%^/%^/%L %^ %h:%^"%r" %s %v %^ "%u|%^" %^ %^ %^ %^=%b' --date-format=%s --time-format=%s These are just some example but I feel using sed or awk for text processing you can feed most of the common access logs with goaccess. [1] https://goaccess.io/man#custom-log https://goaccess.io/man#custom-log
- boundlessdreamz 7y agoWhich platform did you move to?