@p almost done my live log parser complete with status code filtering, requests over a buffer limit highlighted in a different color, ip anonymity toggle (in this case it's the nitter log), the ability to search the entire log, pausing live to investigate, themes, ua agent filtering/sorting, live (shitty hemispheric map made with :: (going to redo this). might be ready to send a copy if you want to try it out since I know you like your mon2.sh. sorry it's written in python
Timeline
Post
Remote status
Context
2
@p it's got a memory leak for large logs (48GB ram usage for poast's 16GB access log minus instances for example) so I'm fixing it but maybe I should take the opportunity to rewrite it in Go so I can learn
Replies
2
@graf That is one reason it's convenient to use awk: stream in, stream out. It is not quite as slick as a single-button scoreboard but it's like, whatever question I'm interested in, I can ask the question in the form of a one-liner and get a sensible answer out of awk.
