We finally got fed up with having customers call us to alert us to their outage because we weren't constantly glued to the Zenoss dashboard watching for critical events.
And we, not being real programmers, came up with this admittedly UGLY hack. Our NOC has a Windoz box displaying Google Chrome with the Zenoss dashboard displayed on a projected screen. On the display computer, we used the windoz version of "netcat" and created a batch file that would listen on a tcp port, (i.e. 10200 or whatever) and execute a dos command (sndrec32) that would play an alert sound. When the sound is played, the batch script loops back and starts netcat again listening. ------------------------------------------------------ :top "C:\nc11nt\nc.exe" -l -p 10200 -e "sndrec32 /play /close c:\alert.wav" gogo top ------------------------------------------------------ Then we created a command in the event manager that telnets to the windoz box on tcp port 10200 whenever a NEW critical event occurs. So when netcat gets a connection it executes " sndrec32 /play /close c:/alert.wav ". We also created a second batch file for a clear event on a different port, but for some reason Zenoss keeps sending the " clear command " over and over every 60 seconds or so. Even though we set the repeat parameter to " 0 ". So for now until we figure out why Zenoss keeps sending the " clear command " its disabled. Any ideas to make this a little more elegant solution would be appreciated. Tom Intermountain Technology -------------------- m2f -------------------- Read this topic online here: http://forums.zenoss.com/viewtopic.php?p=33639#33639 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list zenoss-users@zenoss.org http://lists.zenoss.org/mailman/listinfo/zenoss-users
