[HN Gopher] Ngtop - Request analytics from the Nginx access logs
       ___________________________________________________________________
        
       Ngtop - Request analytics from the Nginx access logs
        
       Author : facundo_olano
       Score  : 99 points
       Date   : 2024-07-30 23:31 UTC (23 hours ago)
        
 (HTM) web link (github.com)
 (TXT) w3m dump (github.com)
        
       | renewiltord wrote:
       | 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.
        
       | codazoda wrote:
       | This looks great. I wrote my own "counter" for my personal sites
       | but I haven't developed it a lot more. This probably makes more
       | sense.
        
       | vlasky wrote:
       | ngxtop is also very useful for providing real-time metrics:
       | 
       | https://github.com/lebinh/ngxtop
        
         | robohoe wrote:
         | Too bad the maintainer stopped responding to or accepting pull
         | requests...lot of PRs open for 10 years, including mine
        
           | ploxiln wrote:
           | 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!
        
           | antifarben wrote:
           | Did you consider maintaining a fork? Because it looks nice
           | indeed.
        
       | Cherian wrote:
       | Is there something like logwatch that could send me a digest of
       | all 404s, 500s etc.?
        
       | uldus wrote:
       | It is not for production use because:
       | 
       | "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."
        
         | anoother wrote:
         | Why does that exclude it from production use?
        
       | iamcreasy wrote:
       | What is the simplest solution to access nginx log? Could it be
       | setting an endpoint(behind simple user/pass) that echos the
       | content of the log?
        
         | rigid wrote:
         | a decent syslog daemon will stream it anywhere you like
        
         | elchief wrote:
         | ssh is the simplest
         | 
         | 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
        
       | ValtteriL wrote:
       | 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.
        
       | walth wrote:
       | Found it much easier to just used structured logs and slice them
       | with [angle grinder](https://github.com/rcoh/angle-grinder)
        
         | metadat wrote:
         | Recently discussed 3 months ago:
         | 
         | https://news.ycombinator.com/item?id=41115128 (11 comments)
        
           | skrause wrote:
           | Your link is to the current thread...
        
             | metadat wrote:
             | Oops, here is the correct link:
             | 
             | https://news.ycombinator.com/item?id=40195557
             | 
             | Thank you for letting me know
        
       | xorcist wrote:
       | Goaccess (https://github.com/allinurl/goaccess) does this in real
       | time and has been very stable for well over a decade.
        
       ___________________________________________________________________
       (page generated 2024-07-31 23:01 UTC)