3 ms·
> 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
by KronisLV 3y ago
> 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/ 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 (in lieu of other options that aggregate your web server logs).
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/ 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.
As for performance, I guess it depends on whether you care about any of the above, whether they actually help you make your site better. If performance was the top goal, we probably wouldn't be using Angular, React or anything like that in the first place, but only very lightweight options. Or, you know, not putting ads or auto playing videos on the sites either.
People have also said good things about Plausible Analytics as well: https://plausible.io/ https://plausible.io/
- bluish29 3y agoActually you don't even need Goaccess running all the time. They parse nginx logs directly so you can only run it when you want to do it (although in practice it takes sometime to parse and create graphs).
- joshyi 3y agoI would contend the contrary. Our company consistently runs GoAccess because we are primarily concerned with unusual traffic patterns. This involves monitoring for potential attacks or abnormal bot traffic that might impact our servers, etc. While JS analytics tools might be of more interest to the marketing team, they are not as crucial for the devops team.
- joshyi 3y agoI believe JS analytics tools serve marketing well, providing estimates like who's purchasing my product or how many are reading my article. However, for devops, relying too much on these tools can be a trap, potentially causing security and server issues without immediate detection. Our team opts for goaccess for this reason. We prioritize accurate data from logs and scrutinize traffic patterns, focusing beyond just distinguishing between human and bot counts, a task we leave to the marketing/product department.