On May 12, 2008, at 6:01 PM, jpertschuk wrote:
Hi there. I found this link, which describes how create devise dependencies so that if devise A goes down, B will not alert because it is dependent upon A.
http://www.zenoss.com/Members/netdata/create-a-device-dependency/

Yet, I'm not able to get this to work. Here is what I wrote:
if device.id == 'fc6.localvm.com':
   db_server = device.findDevice('fc8.localvm.com')
   if db_server.pingStatus() > 0:
       evt.eventState = 2 # suppressed

I made the dependency part of the Event/Status class. So for example the url for that would look like something like this in your own environment: http://192.168.94.XXX:8080/zport/dmd/Events/Status/eventClassStatus. I then went to More__> Transform and added the above script. I thought this was the right place for this because "status" includes pinging a devise. Should I be making this "Transform" in the actual ping class?:
http://192.168.94.129:X/zport/dmd/Events/Status/Ping/eventClassStatus

So, I'm confused as to how far I have to drill down into an event class to make this work and also what other checks can I do other than just pingStatus. I'd like to be able create dependencies based on ports on application servers being down too. So lets say port 7070 is down on Server A, no events should be reported by server B,C and D. The documentation doesn't explain the syntax for other commands.

You do have to go all the way to the event class that the event is going to end up in. These transforms do not inherit down the hierarchy.

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

Reply via email to