TECHZEN Zenoss User Community ARCHIVE  

Setting device status to down

Subject: Setting device status to down
Author: [Not Specified]
Posted: 2014-10-06 12:33

New user of Resource Manager 4.2.5

We have several devices that are set to ignore PING.

When modeling fails, these devices show DEVICE STATUS of UP and green.

For the purposes of new installs, I would like an un-modeled, un-pingable device to show as down

For modeled servers, there will be other command failures I will want to show as down

- - - -

I wrote my first event transform which successfully changes the severity = "5" and the event class to "/Status/Ping"
This does not set the device status to RED / DOWN .

if evt.message.find("User timeout caused connection failure") >= 0:
evt.severity = 5
evt.eventClass = "/Status/Ping"
evt.eventClassKey = "SSH Modeling command timeout - on non-pingable device"

- - - -

Is there a better way to do this than event transform

Does my transform just need tweaking



Subject: If you would please provide a
Author: Andrew Kirch
Posted: 2014-10-27 15:38

If you would please provide a zenactiond.log of that transform being applied. You might also want to look into monitoring SSH in that device class by DEFAULT, so you'd get an SSH is down error before working too hard.

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



Subject: Emily Litella
Author: [Not Specified]
Posted: 2014-10-28 11:57

Seems remote SSH is deprecated at my work (on to SNMP.)

I probably won't be using Zenoss SSH definitions, so ...... nevermind!



Subject: I'm curious, are they under
Author: Andrew Kirch
Posted: 2014-10-28 13:43

I'm curious, are they under the impression that OpenSSH is more secure than net-snmp

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
Zenoss 5 Beta 2 bringup issues.
  Next
Choosing the partition for new zenoss install
>