|
|
| Subject: | Maintenance windows not working |
| Author: | [Not Specified] |
| Posted: | 2014-11-26 10:04 |
I'm not sure what the deal is.
Running 4.2.5
Continue to get email alerts (daily) during maint. window for a server that reboots nightly (a Citrix box).
Saw this - http://community.zenoss.org/message/74306#74306
...but have no idea what they're talking about in the last post as a "solution."
Seems like the maintenance window never really "kicks in" as it should. I've confirmed time settings on the Zenoss box are synched and set to same as rest of our domain. The maint. window is set for an hour, and the server doesn't actually restart until about 30 min. past when that maint. window is set (it's set for 1hr.).
What can I do
I'm really trying to cut down on the "log spew" that this system generates.
| Subject: | Do your triggers have a |
| Author: | [Not Specified] |
| Posted: | 2014-11-26 11:11 |
Do your triggers have a "Device Production State" == "Production"
If not you'll still get nagged during maint windows
| Subject: | --edited--- |
| Author: | [Not Specified] |
| Posted: | 2014-11-26 11:14 |
--edited---
IMO the main way to reduce your spurious alerts is going to be adjusting the counts before a notification gets sent out. That will eliminate most of the network related issues (ping packets dropping, snmp timeouts)
| Subject: | Thanks, Jflindenjr - that's |
| Author: | [Not Specified] |
| Posted: | 2014-11-26 14:07 |
Thanks, Jflindenjr - that's certainly one approach I'll consider!
Dpirmann - I only have "error" - "critical" - "warning" as triggers that are defined for notifications. Nothing in there about production state.
Will test adding that. Thanks!
| Subject: | Still getting 12 emails |
| Author: | [Not Specified] |
| Posted: | 2014-12-01 10:24 |
Still getting 12 emails regarding a server that's rebooting around 3:30AM. Window is set for 1hr.
Outlook rules have cut down on some of the "junk" but there is still a ton of messages.
I think if I could just get this maint. window working, I'd feel a little better :(
Just overwhelmed by the amount of messages I wake up to on a daily basis using this relatively new 4.2.5 system (usually around 200 - several "cleared" messages as well, and some but that's for another thread). It's far more than I got from our older (3.x) system.
| Subject: | SUCCESS! One of the triggers |
| Author: | [Not Specified] |
| Posted: | 2014-12-01 20:39 |
SUCCESS! One of the triggers was set to "any" and not "all." Changed that, added another couple of triggers instead of one for three kinds of "severity" (critical, warning, and error types), then made sure all were set to match "all" sets of conditions.
My understanding of this has now improved.
Thank you, very, very much, Dpirmann.
Now, on to the notices about "Error collecting performance data: NT_STATUS_PIPE_NOT_AVAILABLE" which randomly appear and clear. For now, I can deal with Outlook rules helping there.
Finally feeling like I'm closer to decommissioning the old Zenoss instance, and moving more things to the new one!
| Subject: | Congrats, the new instance |
| Author: | Andrew Kirch |
| Posted: | 2014-12-02 08:41 |
Congrats, the new instance will serve you well, I'm sure!
Andrew Kirch
akirch@gvit.com
Need Zenoss support, consulting or custom development Look no further. Email or PM me!
Ready for Distributed Topology (collectors) for Zenoss 5 Coming May 1st from GoVanguard
| < |
Previous List Devices Using cUrl |
Next How to set criteria in one threshold for two datapoints |
> |