From what I have seen, less is the most popular command used to analyse log files.
And what might be the reason for that? I mean, less (and more) allow(s) you to navigate back and forward within a log file, but it does not update automatically and filtering is really annoying with it.
I, personally, usually use tail -f LOGFILE | grep SEARCHTERM for filtering ongoing logs, ag for filtering existing logs.
Thanks for the info. I have updated the blog accordingly.
Same here, use tail for monitoring live logs. Haven’t heard of ag though.
Maybe due to the fact that less was the widely used command for debugging among devs in the companies I have worked.
It satisfied all my needs hence never needed to explore for something better.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
And what might be the reason for that? I mean,
less(andmore) allow(s) you to navigate back and forward within a log file, but it does not update automatically and filtering is really annoying with it.I, personally, usually use
tail -f LOGFILE | grep SEARCHTERMfor filtering ongoing logs, ag for filtering existing logs.Thanks for the info. I have updated the blog accordingly.
Same here, use tail for monitoring live logs. Haven’t heard of ag though.
Maybe due to the fact that less was the widely used command for debugging among devs in the companies I have worked.
It satisfied all my needs hence never needed to explore for something better.