Ignoring WMI monitoring errors when a server is down (not pingable) - Open Source Network Monitoring and Systems Management

Archived community.zenoss.org | full text search

Skip navigation

Up to Discussions in zenoss-windows

1819 Views 5 Replies Latest reply: May 21, 2013 2:02 PM by Shane Scott

bbbblaine

5 posts since
May 2, 2013

Currently Being Moderated

May 17, 2013 7:06 PM

Ignoring WMI monitoring errors when a server is down (not pingable)

From my initial searching, I'm unable to find info on how to go about accomplishing this...

The problem is: When a Windows server goes offline (pings dropping), I also get Zenoss alerts such as "Could not read Windows services" and "Error collecting performance data".

I want to know how I would configure Zenoss to NOT attempt WMI monitoring on a server that is currently not replying with ICMP.

Any pointers? Maybe some kind of event transform?

Software Component Versions

Zenoss	Zenoss 4.2.3
OS	Linux (x86_64) 2.6.32 (Linux pci-zen 2.6.32-358.el6.x86_64 #1 SMP Fri Feb 22 00:31:26 UTC 2013 x86_64)
Zope	Zope 2.13.13
Python	Python 2.7.2
Database	MySQL 5.5.28 (5.5.28)
RRD	RRDtool 1.4.7
Twisted	Twisted 11.0.0
RabbitMQ	RabbitMQ 2.8.7
Erlang	Erlang 5.8.5
NetSnmp	NetSnmp 5.5.0
PyNetSnmp	PyNetSnmp 0.30.6
WMI	Wmi 1.3.15

Like (0)

Tags: wmi, windows, zenoss_4.2.3

Shane Scott
1,373 posts since
Jul 6, 2009

Currently Being Moderated

1. May 20, 2013 5:09 PM (in response to bbbblaine)
Re: Ignoring WMI monitoring errors when a server is down (not pingable)

bbbbaine:

You'll want to add a transform to the '/' eventClass that checks the device pingStatus and when device.getPingStatus() > 0 (is down) then evt._action = 'drop' or evt.eventStatus = 2 (supressed)

Best,
--Shane Scott (hackman238)
http://shanewilliamscott.com
http://linkedin.com/in/shanewilliamscott

Report Abuse

Like (0)
bbbblaine
5 posts since
May 2, 2013

Currently Being Moderated

2. May 21, 2013 12:53 PM (in response to Shane Scott)
Re: Ignoring WMI monitoring errors when a server is down (not pingable)

Thanks, Shane! This sounds like the solution to me. I added this to the /Status/Wmi event class:
if device.getPingStatus() > 0:
evt._action = "drop"

I'll update again when some time has passed without these annoying WMI errors...

Report Abuse

Like (0)
Shane Scott
1,373 posts since
Jul 6, 2009

Currently Being Moderated

3. May 21, 2013 1:11 PM (in response to bbbblaine)
Re: Ignoring WMI monitoring errors when a server is down (not pingable)

bbbblaine:

Don't forget to add 4 spaces before the evt._action... That places the line under the if statement in python.

Best,
--Shane Scott (Hackman238)

Report Abuse

Like (0)
bbbblaine
5 posts since
May 2, 2013

Currently Being Moderated

4. May 21, 2013 1:19 PM (in response to Shane Scott)
Re: Ignoring WMI monitoring errors when a server is down (not pingable)

My transform has 6 spaces before the drop statement...

For testing, I changes it to 4 spaces, and changed it to supress the events so that I can see what events are affected.

if device.getPingStatus() > 0:
evt.eventStatus = 2

Report Abuse

Like (0)
Shane Scott
1,373 posts since
Jul 6, 2009

Currently Being Moderated

5. May 21, 2013 2:02 PM (in response to bbbblaine)
Re: Ignoring WMI monitoring errors when a server is down (not pingable)

bbbblaine:

Ah that'll work too. Jive ate the formatting.

Best,
--Shane Scott (Hackman238)

Report Abuse

Like (0)

Go to original post

Legend

Correct Answers - 4 points
Helpful Answers - 2 points