[xenomachina]

Years ago, a friend and I talked about a similar idea. We called it a log file "audiolizer" (as opposed to visualizer). The idea is was you'd tail log files through it, and it would produce sound based on the log lines. The hope was that you'd learn what things should normally sound like, and if it started to sound "weird", you could investigate.

[the_third_wave]

Have a look at Peep (the Network Auralizer) [1] for an example of such a tool. I had this running about 24 years ago when traffic on the 'net was a bit more manageable but turned it off when I got fed up with the place sounding like a jungle.

[1] https://peep.sourceforge.net/intro.html

[forgotmypw17]

I do something like this with the text output of my scripts, when debug mode is enabled: https://imgz.org/i6DpehGZ-1280.png

Each character corresponds to one line in the debug log, and is determined (via hashing) by the subprocedure writing to the log.

It gives me a "general feel" of what's going on, and makes it easy to, at minimum, detect infinite loops.