I know this is old, but it came up on a search I performed. Easiest way I can think of is to create an Event named 'critial-devices' with an eventClassKey set to 'defaultmapping'. Then create a rule to look at where the event originated by comparing the event IP address to a list of IPs of your critical devices:
Code: evt.ipAddress in ['192.168.1.1', '192.168.3.2'] Finally, set the zEventSeverity zProperty of the event to critical. Bingo, all events from those devices become critical. -------------------- m2f -------------------- Read this topic online here: http://forums.zenoss.com/viewtopic.php?p=35883#35883 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
