3 ms·
I've used both. GoAccess tends to be more useful to me when I have a set of log files and want to track down something specific to the web server config. That's
by trynewideas 10y ago
I've used both. GoAccess tends to be more useful to me when I have a set of log files and want to track down something specific to the web server config. That's particularly handy when working on a server I'm not already familiar with, or when I have logs but no access to the server, since I don't have to run GoAccess on the server itself. It's also the only IIS log analyzer I bother using.
netdata is more useful for tracking live stats across live servers that I'm actively maintaining (especially multiple servers), and pulls a broader set of information from more sources, which is handier for tracking down intermittent networking issues.
They can both do a little bit of each other's job, which is nice. I tend to use GoAccess more often but think they're both pretty good tools for visualizing server data.
- moreorless 10y agoI am having the hardest time getting goaccess to work with the IIS 8.0 W3C logs. It keeps on complaining about the date / time format. What is your secret sauce?
- joshyi 10y agoTry uncommenting the relevant date/time/log formats from your goaccess.conf. Then run goaccess -f access.log -p /path/goaccess.conf Or https://gist.github.com/soheilpro/a34957550b1bd7d42be2 https://gist.github.com/soheilpro/a34957550b1bd7d42be2