Ngtop – Request analytics from the Nginx access logs

Goaccess (<a href="https:&#x2F;&#x2F;github.com&#x2F;allinurl&#x2F;goaccess">https:&#x2F;&#x2F;github.com&#x2F;allinurl&#x2F;goaccess</a>) does this in real time and has been very stable for well over a decade.

Found it much easier to just used structured logs and slice them with [angle grinder](<a href="https:&#x2F;&#x2F;github.com&#x2F;rcoh&#x2F;angle-grinder">https:&#x2F;&#x2F;github.com&#x2F;rcoh&#x2F;angle-grinder</a>)

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&#x27;s easier for me to manage for my personal sites. Thank you.

What is the simplest solution to access nginx log? Could it be setting an endpoint(behind simple user&#x2F;pass) that echos the content of the log?

Is there something like logwatch that could send me a digest of all 404s, 500s etc.?

ngxtop is also very useful for providing real-time metrics:<p><a href="https:&#x2F;&#x2F;github.com&#x2F;lebinh&#x2F;ngxtop">https:&#x2F;&#x2F;github.com&#x2F;lebinh&#x2F;ngxtop</a>

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.

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.<p>JS tracking leaves out most bots as well. They were a nuisance with this method.

It is not for production use because:<p>&quot;Whenever the program is run, it looks for the nginx access.logs, parses them and stores the data into an SQLite DB. &quot; ... &quot;The command line arguments express a filtering criteria, used to build the SQL query that counts the requests.&quot;