Hi I appreciate the assistance, but as I stated in my initial question the Host 
check period is 24x7, the Notification is now 24x7 but the service check itself 
is set to the Time period defined, but it still sends out email alerts on the 
service alert.  So it should not inherit the Notification period if it's set 
directly as a timed exception on that service.

At one point before that we had the notification set up for the time period and 
no timed exception on the service, so at that point it would have inherited it 
from there, but neither way work.

Any more ideas?

Thanks again all.

From: [email protected] 
[mailto:[email protected]] On Behalf Of MAGIN GEORGE
Sent: Wednesday, April 04, 2012 11:11 AM
To: Opsview Users
Subject: Re: [opsview-users] Opsview Time Periods not working

I assume you are getting service alerts. If yes, what is the Notification 
timeperiod for that servicecheck? Is it "blank" (Inherit from host notification 
period) or 24X7 ?

Thanks,

Magin
On Wed, Apr 4, 2012 at 9:49 PM, Mike Lee 
<[email protected]<mailto:[email protected]>> wrote:
It is a single master server.  Time zone is PST.  Yes the reload was successful 
and these are actual email alerts.

Thanks,
Mike Lee

From: 
[email protected]<mailto:[email protected]>
 
[mailto:[email protected]<mailto:[email protected]>]
 On Behalf Of Duncan Ferguson
Sent: Wednesday, April 04, 2012 10:14 AM
To: Opsview Users
Subject: Re: [opsview-users] Opsview Time Periods not working


On 4 Apr 2012, at 17:03, Mike Lee wrote:

Hello,
     Currently we are running Opsview version 20120308

We have a Time period set up for every day of the week that is to NOT monitor 
the server between 2am and 7am but monitor it during the rest of the time.  
Currently the format is this:
00:00-02:00,07:00-24:00

Here is how the host is set up for that Time period:
*         Host Check Period - is set to 24x7
*         Notification Period - was set to the Time Period defined.....yet it 
still alerted
*         We then put the Notification period back to 24x7 and changed the 
"Timed" exceptions for a specific service on that host to the Time period 
defined and still it alerted.

>From my understanding, I could have just put it on the "Notification Period" 
>section of that host and it should have not alerted at all.  Yet, the server 
>still alerts around 5am to 6am every day.  What are we doing wrong

Do you aheva distributed setup?  If so, are the slaves and master in the same 
time zone?

What time zone is your master on anyway?  Was the reload successful after you 
changed the time period?  Are these email alerts, or just what is seen in the 
GUI?

  Duncs

--
Duncan Ferguson
Support Team Leader




Global Headquarters: Unit 69 Suttons Business Park | Reading | Berkshire | RG6 
1AZ | UK

UK:               +44 (0) 845 057 7887<tel:%2B44%20%280%29%20845%20057%207887>
USA:     +1 866 879 9184<tel:%2B1%20866%20879%209184>
Fax:              +44 (0) 1189 074 071<tel:%2B44%20%280%29%201189%20074%20071>
email:   [email protected]<mailto:[email protected]>
Web:     www.opsview.com<http://www.opsview.com/>

This e-mail is confidential, intended only for the named recipient(s) above and 
may contain information that is privileged and confidential. If you receive 
this message in error, or are not the named recipient(s), please notify the 
sender at the phone number above, do not copy this message, do not disclose its 
contents to anyone, and delete this e-mail message from your computer. Although 
we routinely screen for viruses, addressees should scan this e-mail and any 
attachments for viruses. Opsview Limited is a company registered in the UK 
under Company Number 5396532. Our registered office is Gorse View, Horsell 
Rise, Woking, Surrey, GU21 4RB, UK


_______________________________________________
Opsview-users mailing list
[email protected]<mailto:[email protected]>
http://lists.opsview.org/lists/listinfo/opsview-users

_______________________________________________
Opsview-users mailing list
[email protected]
http://lists.opsview.org/lists/listinfo/opsview-users

Reply via email to