We use it on our site, which handles around 100M requests per month, works really nice. In fact, we have a screen in the office that continuously displays the stats, quite nifty!
I 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…
I think many developers overlook this aspect. If you're not in marketing, it's not just about tallying human visitors on our sites. It's essential to be vigilant against possible daily attacks and avoid excessive…
JS analytics are increasingly susceptible to inaccuracies as data manipulation methods multiply, leading to the production of unreliable events from JavaScript endpoints. Staying abreast of industry developments…
While JS analytics may suit the needs of marketing professionals concerned with product sales and article visibility, those focused on precise traffic patterns, like daily devops, find GoAccess to be a more effective…
I 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…
If accuracy refers solely to human-vs-bot detection, there might be a point, but for comprehensive traffic analysis, access logs are unparalleled in accuracy. JavaScript analytics are increasingly prone to inaccuracies…
Same here. We’ve been using goaccess for years on a 300M hits a month. Self-host is the way to go for us.
100% + Google $$$
Only canceled.
For sure lots of issues for peloton after those accidents with kids.
We’re using our own logs with https://goaccess.io processing over 300M requests a month with no issues. No privacy issues to worry about using trackers.
I think it depends a lot in what you are after. Accurate results through the logs, including bots. Or inaccurate results via JS. Bunch of services folks are using out there that blocks them.
Still, there's a lot more data outputting from goaccess with support for custom logs.
Tracking visitors at the client level deflates the actual number of visitors. On the other hand, server-side tracking provides a more accurate number with the tradeoff of not knowing for sure if the client is a human…
I'm waiting as well for the ability to use filters directly from goaccess. Hope they get to it soon! https://github.com/allinurl/goaccess/issues/117
We use goaccess against a pretty busy centralized log server and has worked really well for years. We don't have to worry about JS and that's always a plus. I personally like how it follows the unix philosophy.
I think server logs are more accurate, it will tell you exactly what's going on, but like you said, bots will show up as well. On the other hand, a bunch of folks (+600M) block JS analytics/trackers so it will deflate…
I agree, works really well for us. Above all, no javascript!
For us it was literately an `apt install goaccess`, picked the COMBINED log format and it's been running for over a month in prod without issues (rotating weekly). You should post the issue on their…
Doubt very much that ~2M will be a memory issue (unless you got less than ~130MB). https://goaccess.io/faq#performance We're running v1.4 in production and it has been working pretty nice for us.
It is 100% real-time. https://rt.goaccess.io/
You can always create an issue on their github page, lots of help in there: https://github.com/allinurl/goaccess/issues
I think a big problem with Google Analytics is accuracy, especially with the now so popular adblockers. Log analysis such as GoAccess should be able to track these down fine since it works at the server level. I believe…
Google Analytics keeps track of visitors using cookies, so if a browser has cookies or JavaScript disabled, then it won't keep track of it. This includes the now so popular adblockers and bots as well. Log analysis such…
We use it on our site, which handles around 100M requests per month, works really nice. In fact, we have a screen in the office that continuously displays the stats, quite nifty!
I 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…
I think many developers overlook this aspect. If you're not in marketing, it's not just about tallying human visitors on our sites. It's essential to be vigilant against possible daily attacks and avoid excessive…
JS analytics are increasingly susceptible to inaccuracies as data manipulation methods multiply, leading to the production of unreliable events from JavaScript endpoints. Staying abreast of industry developments…
While JS analytics may suit the needs of marketing professionals concerned with product sales and article visibility, those focused on precise traffic patterns, like daily devops, find GoAccess to be a more effective…
I 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…
If accuracy refers solely to human-vs-bot detection, there might be a point, but for comprehensive traffic analysis, access logs are unparalleled in accuracy. JavaScript analytics are increasingly prone to inaccuracies…
Same here. We’ve been using goaccess for years on a 300M hits a month. Self-host is the way to go for us.
100% + Google $$$
Only canceled.
For sure lots of issues for peloton after those accidents with kids.
We’re using our own logs with https://goaccess.io processing over 300M requests a month with no issues. No privacy issues to worry about using trackers.
I think it depends a lot in what you are after. Accurate results through the logs, including bots. Or inaccurate results via JS. Bunch of services folks are using out there that blocks them.
Still, there's a lot more data outputting from goaccess with support for custom logs.
Tracking visitors at the client level deflates the actual number of visitors. On the other hand, server-side tracking provides a more accurate number with the tradeoff of not knowing for sure if the client is a human…
I'm waiting as well for the ability to use filters directly from goaccess. Hope they get to it soon! https://github.com/allinurl/goaccess/issues/117
We use goaccess against a pretty busy centralized log server and has worked really well for years. We don't have to worry about JS and that's always a plus. I personally like how it follows the unix philosophy.
I think server logs are more accurate, it will tell you exactly what's going on, but like you said, bots will show up as well. On the other hand, a bunch of folks (+600M) block JS analytics/trackers so it will deflate…
I agree, works really well for us. Above all, no javascript!
For us it was literately an `apt install goaccess`, picked the COMBINED log format and it's been running for over a month in prod without issues (rotating weekly). You should post the issue on their…
Doubt very much that ~2M will be a memory issue (unless you got less than ~130MB). https://goaccess.io/faq#performance We're running v1.4 in production and it has been working pretty nice for us.
It is 100% real-time. https://rt.goaccess.io/
You can always create an issue on their github page, lots of help in there: https://github.com/allinurl/goaccess/issues
I think a big problem with Google Analytics is accuracy, especially with the now so popular adblockers. Log analysis such as GoAccess should be able to track these down fine since it works at the server level. I believe…
Google Analytics keeps track of visitors using cookies, so if a browser has cookies or JavaScript disabled, then it won't keep track of it. This includes the now so popular adblockers and bots as well. Log analysis such…