[jrumbut]

This is the tool I've wanted (and half written 3-4 times) my whole career. From reading the github it looks lightweight, not a big infrastructure addition, and that it helps you figure out wtf is going on with the web server.

Regarding the branding, for me top is a real-time tool rather than a logging tool. I was picturing something that may have been more useful for older style Apache httpd installs where you have several virtual hosts on a server and you'd want to know who is hogging the resources or causing the problems.

[jluxenberg]

Pro tip: you can make any command into a real-time one with `watch`:

  watch bash -c "topngx < /path/to/access.log"

Will run `topngx` against access.log every two seconds and display the output.

[gregoriol]

That's not "real time"! And definitely won't behave well if the processing takes more than 2 seconds (imagine log files of many millions rows)

[cyberpunk]

It'll just wait two seconds after the command returns, not spawn one every two seconds.....

[squiguy7]

Thanks for the feedback. I wanted to capture the same idea as the original tool I listed in the README. In the future I hope to add functionality to tail a log file in real time and do live updates of the stats. This is where the idea of top comes from.

[markstos]

Agreed. The defining feature of `top` is that it updates in real time.