When I was much younger, programming on my Amstrad CPC 6128, I found I was sometimes able to “debug” my programs by turning the volume up to maximum.

The sound circuitry wasn’t well isolated from the processor, and the resulting hiss and buzz was a way to monitor what was going on - it was pretty easy to discern a transition from normal processing into an infinite loop or another error state.

Fast forward a few years, and I heard about an effort to provide network monitoring in a similar way - generating an “audible landscape” of background noise, where each sound had a specific meaning. I didn’t keep any notes, however, and it became one of those oft repeated fantastic stories that I couldn’t substantiate.

Today, I stumbled across a ServerFault question White noise as a system monitoring aid? Real or myth?, and found the original report Peep (The Network Auralizer): Monitoring Your Network With Sound from the Lisa00 conference in December 2000.

Very cool reading - and a very powerful technique. Is is just office politics that have prevented this taking off, or is there a fundamental flaw I’m missing?

Comments

blog comments powered by Disqus
Next Post
A Drupal Views "Date Trap"  19 Jul 2009
Prior Post
Two dangerous little words  16 Jul 2009
Related Posts
Using Constructors  27 Feb 2023
An Inconvenient API  18 Feb 2023
Method Archetypes  11 Sep 2022
A bash puzzle, solved  02 Jul 2022
A bash puzzle  25 Jun 2022
Improve your troubleshooting by aggregating errors  11 Jun 2022
Improve your troubleshooting by wrapping errors  28 May 2022
Keep your promises  14 May 2022
When are you done?  18 Apr 2022
Fixing GitHub Authentication  28 Nov 2021
Archives
July 2009
2009