This is cool. I just installed goaccess and was using that to look at the nginx logs but this is also neat. I like post-hoc analysis of these things rather than injecting JS just because it's easier for me to manage for my personal sites. Thank you.
Pick a slight variation on the name, look through the unmerged upstream PRs to find some "obviously good" ones (or to fix other deficiencies you noticed personally), merge them to your fork, and who knows ... your fork might become the next popular home of the project!
"Whenever the program is run, it looks for the nginx access.logs, parses them and stores the data into an SQLite DB. "
...
"The command line arguments express a filtering criteria, used to build the SQL query that counts the requests."
I used something similar in the past for website analytics but came to realize that javascript based tracking is more useful for my use case of understanding how people use my website.
JS tracking leaves out most bots as well. They were a nuisance with this method.
20 comments
[ 3.0 ms ] story [ 46.2 ms ] threadhttps://github.com/lebinh/ngxtop
"Whenever the program is run, it looks for the nginx access.logs, parses them and stores the data into an SQLite DB. " ... "The command line arguments express a filtering criteria, used to build the SQL query that counts the requests."
for exporting nginx logs elsewhere, vector.dev is nice. can send to dozens of places. can parse user agent string, and do ip geocoding too
JS tracking leaves out most bots as well. They were a nuisance with this method.
https://news.ycombinator.com/item?id=41115128 (11 comments)
https://news.ycombinator.com/item?id=40195557
Thank you for letting me know