[HN Gopher] Toolong: Terminal application to view, tail, merge, ...
       ___________________________________________________________________
        
       Toolong: Terminal application to view, tail, merge, and search log
       files
        
       Author : ingve
       Score  : 90 points
       Date   : 2024-02-09 17:27 UTC (1 days ago)
        
 (HTM) web link (github.com)
 (TXT) w3m dump (github.com)
        
       | asmosoinio wrote:
       | Looks very interesting and should solve a pretty common use case
       | for me - am often trying to debug some issue over many log files.
       | I will for sure test this next week.
        
       | alserio wrote:
       | Nice! I've found this kind of tools really useful and love the
       | merge functionality. I've skimmed the README but maybe I've
       | missed the info: does toolong support multiline logs like
       | stacktraces? Or is it possible to customize the recognized
       | formats?
        
       | avtar wrote:
       | The code base seems like a good reference as a small Python
       | project.
       | 
       | My fav option in this class of apps: https://lnav.org/ It lets
       | you use journalctl with pipes as requested here:
       | https://github.com/Textualize/toolong/issues/4
        
         | maxyurk wrote:
         | lnav is great
        
       | hawski wrote:
       | What I often do when I analyze logs is removing timestamps and
       | changing unique identifiers to something more predictable and
       | diff them to see when things started diverting from the norm,
       | because it is often earlier than the usual error/crash. Is there
       | anything that does something like it?
        
       | jonnycoder wrote:
       | This would have been great when I used to work in embedded
       | development and had to grep log files to root cause bugs. I had
       | thought about writing something like this but was always too
       | busy. The biggest feature is combining log files and organizing
       | by timestamp.. well done
        
       | raldi wrote:
       | A handy utility I've written a few times is a tool that can
       | quickly extract a range of logs from a timestamped, ordered file
       | without reading every byte. This would be a good feature to add
       | to this.
        
       | piterrro wrote:
       | Congrats on the launch! I'm an author of https://logdy.dev seems
       | like we had a similar problem with logs and decided to solve it
       | but in a slightly different way. Logdy works with pipes very
       | well, I'm wrapping up another version to be released soon.
        
         | kinow wrote:
         | I maintain a workflow manager, and had both textualize and
         | logdy on my list of projects to try soon. Planning to add a TUI
         | written in textualize, and was thinking in something like logdy
         | (or use it directly). Not sure which way to go now, will play
         | with both now and see which version users like best. Thanks for
         | logdy, and thanks to the creators of toolong too!
        
       | mstudio wrote:
       | This looks great. I spend a good amount of time each week
       | grepping through Kubernetes log files. Looking forward to trying
       | this out next week. I particularly like the pretty-print and
       | merge options.
        
       | willm wrote:
       | Hello. Author of Toolong here. Happy to answer any questions!
        
       | nickjj wrote:
       | I'd love to see a tool that lets you modify large files
       | efficiently.
       | 
       | I had to replace line 4 of a 200 GB SQL dump, it took a
       | substantial amount of compute time to perform a find / replace
       | with sed and it also required having over double the disk space
       | since sed creates a temp file before it writes out the new file.
       | 
       | Using a hex editor could have worked but it seemed too risky
       | because data integrity was really important.
        
         | coolThingsFirst wrote:
         | What's the challenge in here? Loading the text efficiently in
         | RAM?
        
       ___________________________________________________________________
       (page generated 2024-02-10 23:00 UTC)