On Dec 3, 2009, at 5:49 PM, Gareth Beale wrote: > I'm looking at replacing a system that was used to monitor production > systems. > > It performed two basic functions:
> 2. Receive arbitrary text messages sent to it and display them, possibly > with an audio alert, on the console. > This was achieved by using remote copy to put a text file (with > several delimited fields) in a specific directory on the monitoring > system. A process checked the directory periodically and displayed any > messages found there, after interpreting the fields in the text file. > > Nagios is a no-brainer for the first function, and although it wouldn't > be hard to write a simple script to do part 2, I'd like to incorporate > it into nagios. You could treat these as a typical critical event. If you have a script that parses the file and determines that something is alertable, you're already mostly there. Create a new host/service definition; give it a generic name relevant to the type of alerts it will display; enable passive checks for it and set is_volatile. Have your script submit a passive CRITICAL or WARNING result to nagios based on it's alert logic. Each time this happens, it will show up as an event that must be acknowledged or reset to clear. -- Marc ------------------------------------------------------------------------------ Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev _______________________________________________ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
