Disabled Notifications Are Enabled After A Server Reload

6 replies [Last post]
billcampbell
User offline. Last seen 37 weeks 2 hours ago. Offline
Opsview Sensei - 3rd DanOpsview Sensei - 2nd DanOpsview Sensei - 1st Dan
Joined: 04 Dec 2009
Posts:
Points: 153

Has anyone else had the problem of disabled notifications on a service being enabled after a server reload?

0
Your rating: None
Karsten Müller's picture
Karsten Müller
User offline. Last seen 1 week 5 days ago. Offline
Opsview Enterprise SubscriberOpsview Sensei - 3rd DanOpsview Sensei - 2nd DanOpsview Sensei - 1st Dan
Joined: 04 Jun 2010
Posts:
Points: 186

Maybe its related to http://www.opsview.com/forum/opsview-community-edition/latest-release/371-not-honouring-disabled-renotification?

Your rating: None
dferguson's picture
dferguson
User offline. Last seen 22 hours 2 min ago. Offline
Opsview Sensei - 1st Dan
Joined: 02 Jun 2010
Posts:
Points: 35

Best practise is to set downtime on the affected service rather than disable notifications for it.

Duncs

Your rating: None
billcampbell
User offline. Last seen 37 weeks 2 hours ago. Offline
Opsview Sensei - 3rd DanOpsview Sensei - 2nd DanOpsview Sensei - 1st Dan
Joined: 04 Dec 2009
Posts:
Points: 153

I can see that solution for some situations, but we have a service check that we want notifications about for some hosts, but we only want to be able to see the status of the check for other hosts and not get notifications about it. What is the purpose "Disable Notifications" now if it defaults back after a reload?

Your rating: None
tonvoon's picture
tonvoon
User offline. Last seen 5 days 7 hours ago. Offline
Opsview Sensei - 1st Dan
Joined: 26 May 2010
Posts:
Points: 65

For a specific service check you do not want notifications for some hosts, you could use the Notification Period inheritance of the service check. Set the host to a timeperiod of "Never", and then the service check would inherit from the host.

Note this may affect more service checks than just the one.

Alternatively, it maybe that you need to create a separate service check that doesn't alert.

What's the scenario?

Ton

Your rating: None
cvanderwpc's picture
cvanderwpc
User offline. Last seen 39 weeks 6 days ago. Offline
Joined: 23 Aug 2010
Posts:
Points: 20

I want to revisit this issue with you. We have the exact same problem, and it only appeared after upgrading to 3.7.2. Forever before that, whenever we had notifications for alerts that were unnecessary for certain machines, we would disable them using "Disable Notifications" and that would be that. Even after a Configuration Reload, the disabled notifications would stick. Now, however, every time we reload, all the previously disabled notifications start up again.

I'm not sure if you changed the handling of this purposely in 3.7.x, but this is definitely a change from earlier versions. it's been a few months since this thread was active. Have you attributed this now to a bug or an intentional change? If a bug, has it been fixed?

Thanks,
Chris

Your rating: None
cvanderwpc's picture
cvanderwpc
User offline. Last seen 39 weeks 6 days ago. Offline
Joined: 23 Aug 2010
Posts:
Points: 20

Hate to reply so quickly to my own comment, but I think I've figured out that this is a intentional design change in 3.7, and the Release Notes state this: "Notification state on host and services is reset to configuration value after a reload - use scheduled downtime if you have to disable notifications temporarily". I should RTFM more better 8^). Let me know if I'm off base here.

Your rating: None