Very basic notifications question

[Marc Powell]

> -----Original Message-----
> From: nagios-users-bounces at lists.sourceforge.net [mailto:nagios-users-
> bounces at lists.sourceforge.net] On Behalf Of Matthew Macdonald-Wallace
> Sent: Tuesday, March 18, 2008 10:31 AM
> To: Nagios-users at lists.sourceforge.net
> Subject: [Nagios-users] Very basic notifications question


> What we want:
> 
> - Monitoring of the following:
>    * Host Status (Up/Down)
>    * Disk Space on given partitions
>    * Swap Usage
>    * RAID Status
> - Alerts when the service/host fails and alerts when the service/host
> starts again.

Nothing unusual here... The documention should be sufficient...

> What we don't want:
> 
>  - Alerts for services that are not mission critical (we have a script
> that monitors the current Debian version for upgrade purposes)

http://nagios.sourceforge.net/docs/2_0/xodtemplate.html#service (and
#host)

notifications_enabled 0 (or)
notification_period none

>  - An inbox full of emails telling us that a system/service is down
> every five minutes.

http://nagios.sourceforge.net/docs/2_0/xodtemplate.html#service (and
#host)

notification_interval 0

> Is it possible to set alerts for individual services and have them
send
> an email when the service changes state but not every time it checks?

Nagios wouldn't do that unless you specified 'is volatile' so nothing
special needs to be done.
 
> I've had a read of the docs and I can't see how I'd achieve this,

There's nothing special about what you're looking for. Very typical
nagios config...

--
Marc

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
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