Reclassifying an event's significance

[Justin Shore]

> -----Original Message-----
> From: Andrew Cruse [mailto:andrew at profitability.net]
> Sent: Friday, August 19, 2005 4:28 PM
> To: Justin Shore; nagios-users at lists.sourceforge.net
> Subject: RE: [Nagios-users] Reclassifying an event's significance
> 
> nagios-users-admin at lists.sourceforge.net wrote:
> > I have 2.0b4 monitoring a number of hosts that go down
> > frequently, almost regularly.  Even though we monitor them we
> > do not care what their state is (unreachable, up, down,
> > flaming, etc).  These boxes are rebooted or are otherwise
> > inaccessible at various time during the day due to numerous
> > reasons.  Is it possible to reclassify an unreachable or down
> > state as nothing more than a simple warning at most or
> > ideally not show up at all on the tactical overview?  I do
> > not want to get paged, nor do I want the web interface to
> > send out any time of audible alert.  Like I said before we do
> > not care if these machines go offline.  I wouldn't mind them
> > showing up red in the status map.  Other than that I want
> > them to run silent.  Scheduling downtime as needed for these
> > hosts isn't an option.  I also don't want to simply disable
> > notifications for these hosts (what I'm currently doing).
> > Having 2 dozen hosts' notifications listed as disabled
> > prompts too many questions as to why they're disabled and
> > causes too many people to be concerned.  Is there a way to
> > achieve this desired result without not monitoring these
> > hosts at all and removing them from the config?
> 
> Why are you monitoring them if you don't want to know when they go down?
> But, to answer your question, why not change the host check to a dummy
> check that always returns ok, and then set each of the services for
> those hosts not to notify at any state.

These machines are controlled by numerous people who will reboot these machines as is necessary.  Few of these machines are shared between different people though.  I believe that the desired result will be for the helpdesk to know if a machine is currently offline if someone asks but to not be concerned about it in the least otherwise.  That's just for this very specific group of servers.  All the other "normal" servers are monitored like one would expect.  It's a rather unusual arrangement.  I'll give your suggestion a try.

Thanks
 Justin

 

-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.338 / Virus Database: 267.10.14/79 - Release Date: 8/22/2005
 


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Nagios-users mailing list
Nagios-users at 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