Hi, I think you might want to rethink your process so that it matches the paradigm of the tool you are using. It already can do what you want if you just work with the way it was designed, rather than forcing a process that breaks the paradigm.
On Wed, Aug 2, 2006, [EMAIL PROTECTED] wrote: >Service goes critical This is not a scheduled event. It is unscheduled. >SMS gets dispatched All the admins are made aware of the problem including CTO >Problem gets acknowledged >SMS gets dispatched Other admins know it is being handled as does the CTO Host DOES NOT get scheduled for downtime Since the unscheduled event has already been acknowledged and everyone who might want to jump in to help already knows it is being handled, there is no need to schedule a downtime for an unscheduled event. Just acknowledge it. >Reboot >Host/Service OK Recovery Note goes out to everyone, including CTO. Problem Solved. Everyone knows what is happening. Your performance evaluation gets a boost for being the one to solve the problem. Just a thought. ____________________________________________ Robert Snyder Outreach Technology Services The Pennsylvania State University 151A Outreach Building University Park PA 16802 Phone: 814-865-0912 Fax: 814-865-4406 E-mail: [EMAIL PROTECTED] ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ 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
