Page 100 of the 2.3 Admin Guide says the following (with apologies to lack of formatting):
Once an event has been mapped to its class, two things happen: (1) Its Event context is applied and (2) its Device context(s) are applied. EventClass context application is done by looking up the zProperty list zEventProperties. Any property names found in zEventProperties are set in the same way that other zProperties are, except that when looking up the property, the prefix 'zEvent_' is added to the property name. When the zEventProperties value is changed, Zenoss creates a placeholder for each of the properties in the list on the zProperties screen. A common event property to change is 'Severity' and, in fact, Severity is added by default to zEventProperties. To change the Severity of a classified event, change the value of zEvent_severity in the Event Class Path for the event. After the event context has been applied, then the device context is applied. During this process, the productionState, location, DeviceClass, DeviceGroups, and Systems, are all attached to the event in the event database. Once these properties have been associated with the event, Zenoss attempts to update the zEventProperties (as described above) but using the device class path instead of the event class path. This allows a particular device or class of devices to override the default values for any given event. My difficulties are with the "device context". The five fields documented above are, in fact, available during the event mapping process and certainly before the event context is applied. How can Zenoss "attempt to update the zEventProperties (as described above) but using the device class path instead of the event class path"??? If my scenario is that I want to set the action event zProperty to status if the device is a member of Location Centre but set action to history if the device is a member of the Location Remote, how do I do that with device context and event context?? I know I can do this with an event transform but the Admin manual seems to be implying that there is a trick here that I am missing. Thanks, Jane -------------------- m2f -------------------- Read this topic online here: http://forums.zenoss.com/viewtopic.php?p=29807#29807 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
