4 ms·

I prefer goaccess(1) over any other tool that uses client side Javascript. It's basically a real time website log analyser which gives you enough information t

I prefer goaccess(1) over any other tool that uses client side Javascript. It's basically a real time website log analyser which gives you enough information to know whats happening on your website but doesn't require any pesky Javascript etc to do it. Also since it is works by analysing your log files it can never be blocked. (1) https://rt.goaccess.io/?20210826211303 https://rt.goaccess.io/?20210826211303

kingcharles 5y ago
If you want total accuracy, then the only solution is to analyze your HTTP logs like this. You won't get much in the way of knowing your clients, except what comes through in the HTTP requests, e.g. URI, IP address, browser and platform, but you'll also know you're not missing any requests.
- jefftk 5y ago
  Most people running sites care less about exactly counting the number of requests than knowing details about their visitors and behavior. If I try to process my server logs directly I either need to manually filter out bots, which are the majority of traffic, or I need to use some sort of collaboratively maintained bot identification system. Alternatively, I can use any of the services people are mentioning here and they will do that for me.
  - joshyi 5y ago
    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.
Ciantic 5y ago
I use Goaccess too for simple things, but I've found that it's not really suitable if you want to compare stats of different months or years, or look into specific week. This is because goaccess aggregates reports to single HTML file. If you give it a year of logs, it compresses whole year in one graph. It didn't seem to have interactive way to explore whole year. Most people don't care and just generate monthly HTML report file, but that has same flaws as yearly file.

kingcharles 5y ago

If you want total accuracy, then the only solution is to analyze your HTTP logs like this. You won't get much in the way of knowing your clients, except what comes through in the HTTP requests, e.g. URI, IP address, browser and platform, but you'll also know you're not missing any requests.

jefftk 5y ago
Most people running sites care less about exactly counting the number of requests than knowing details about their visitors and behavior. If I try to process my server logs directly I either need to manually filter out bots, which are the majority of traffic, or I need to use some sort of collaboratively maintained bot identification system. Alternatively, I can use any of the services people are mentioning here and they will do that for me.
- joshyi 5y ago
  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.

Ciantic 5y ago

I use Goaccess too for simple things, but I've found that it's not really suitable if you want to compare stats of different months or years, or look into specific week. This is because goaccess aggregates reports to single HTML file. If you give it a year of logs, it compresses whole year in one graph. It didn't seem to have interactive way to explore whole year. Most people don't care and just generate monthly HTML report file, but that has same flaws as yearly file.