On Sun, 18 Jun 2006 [EMAIL PROTECTED] wrote:

> Gentlemen,
> I have two services that go down periodically on Sunday between 08:10am to
> 20:10pm .How do I
> disable notifications during this time period only but still need the 24/7
> notification enabled.I have
> included the service file entry. I am not sure what the syntax on line
> "notification period" should
> be for stopping emails going out all day Sunday while the Tokyo exchange
> feed is not trading during
> this time?.

Call me stupid by why do this the hardware? Give them a custome time
period so you do not notify during the given interval.

> # Service definition
> define service{
>         use                                     generic-service   ;
>
>         host_name
> r-tyomci-mcimpls,r-tyomci-clientdist,r-tyoanc-ancmpls,r-tyoanc-feed
>         service_description                Int F0/0 to Internal ComStock
> net0 LAN
>         is_volatile                       0
>         check_period                      24x7
Make this 'almost24x7' for the specific services.
>         max_check_attempts              2
>         normal_check_interval           5
>         retry_check_interval              2
>         contact_groups                    all-it-staff
>         notification_interval             30
>         notification_period               24x7
>         notification_options              w,u,c,r
>         check_command
> check_interface!FastEthernet0/0!no9tIeNo
>         }

I always prefer KIS (Keep It Simple) solutions because I am lazy.

Hugo.

-- 
        I hate duplicates. Just reply to the relevant mailinglist.
        [EMAIL PROTECTED]               http://hvdkooij.xs4all.nl/
                Don't meddle in the affairs of magicians,
                for they are subtle and quick to anger.


_______________________________________________
Nagios-users mailing list
[email protected]
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

Reply via email to