GoAccess VS lnav

If one wants server-side metrics with a little more info than the author's "hacky little script", there's always goaccess [1], which functions in broadly the same way. I even use it with Firebase Hosting-hosted sites via [2] (which I wrote).

[1] http://goaccess.io/

[2] https://github.com/Silicon-Ally/gcp-clf

> Just use GoAcces for fuck's sake.

GoAccess seems pretty cool and is probably a good task for the job, when you need something simple, thanks for recommending it: https://goaccess.io/

Even if you have analytics of some sort already in place, I think it'd probably still be a nice idea to run GoAccess on your server, behind some additional auth, so you can check up on how the web servers are performing.

That said, I'd still say that the analytics solutions out there, especially self-hostable ones like Matomo, are quite nice and can have both UIs that are very easy to interact with for the average person (e.g. filtering data by date range, or by page/view that was interacted with), as well as have a plethora of different datasets: https://matomo.org/features/

I think it can be useful to have a look at what sorts of devices are mostly being used to interact with your site, what operating systems and browsers are in use, how people navigate through the site, where do they enter the site from and how they find it, what the front end performance is like, or even how your e-commerce site is doing, at a glance, in addition to seeing how this changes over time.

People have also said good things about Plausible Analytics as well: https://plausible.io/

Maybe, if it's just local and need just information, maybe https://goaccess.io is an option.

I run goaccess on a cron job and have paired it with a MaxMind GeoIP database so that you can see where people are coming from etc.

https://goaccess.io/

file on GitHub.

There is small programm for linux https://goaccess.io/

I heard about https://goaccess.io/ (and even tested it) but first, nothing about tracing logs, and I think that the provided HTML dashboard isn't enough security-oriented for me but it's more about monitoring your customer volume... It does -partially- fit my case.

Loved AWStats! Still can be useful — but bots, client side caching, CDNs, and did I mention bots..? have made the data hard to rely on for much. A while ago I switched from AWStats to GoAccess (https://goaccess.io/) for this kind of thing. I prefer its interface, and it's way way faster to churn through big log files (C vs. Perl).

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.

GoAccess is a powerful web log analyzer that generates real-time web traffic statistics.

The code base seems like a good reference as a small Python project.

My fav option in this class of apps: https://lnav.org/ It lets you use journalctl with pipes as requested here: https://github.com/Textualize/toolong/issues/4

For local development, I cannot recommend lnav[1] enough. Discovering this tool was a game changer in my day to day life. Adding comments, filtering in/out, prettify and analyse distribution is hard to live without now.

I don't think a browser tool would fit in my workflow. I need to pipe the output to the tool.

[1] https://lnav.org/

It looks like they run an SSH server inside a Docker container defined by this Dockerfile [1]. This uses the ForceCommand directive in the sshd_config file to ensure that a specific command is run when a user connects (rather than the user connecting directly to a shell).

Depending on whether the user connects as the `playground` or `tutorial1` user they interact with a bash script that is either [2] or [3].

[1]: https://github.com/tstack/lnav/blob/master/demo/Dockerfile

[2]: https://github.com/tstack/lnav/blob/master/docs/tutorials/pl...

[3]: https://github.com/tstack/lnav/blob/master/docs/tutorials/tu...

This is really pretty - I do really wish for a good rust replacement for lnav[1] someday.

1: https://lnav.org/

> I also don't see something else I might want: a way to have a different "view" for certain log messages; maybe to switch between filtering/viewing particular ones, maybe to just have line-format be conditional based on the detected format.

Have a look at the following comment on an issue that might be similar to what you're thinking of:

https://github.com/tstack/lnav/issues/1065#issuecomment-1602...

> I guess I can sort of do this based on `module-field`? but I might want it lighter-weight/finer-grained than that.

Unfortunately, the "module-field" does not work for JSON logs at the moment. It's something I should really fix.

Ultimately, lnav has existed for almost two decades now and I use it every day. So, it's always seeing improvements. If you're having a problem with it, file an issue on github. I don't always get around quickly to fixing other folks feature requests / issues, but it tends to happen eventually.

Thanks.