Request (in order of importance): 1) Be able to move alerts from user to user 2) Be able to rename alerts 3) Be able to copy an alert to a new alert so that I don't have to modify all of the parameters of the new alert. 4) More flexible Boolean rules. I want to have rules equivalent to: "device class beginning with x" and NOT "device class beginning with y". I don't want inflexibility in the alerting rules dictate a complete rethink of my device class hierarchy. 5) How about an alerts organizer hierarchy (like Devices classes) with inheritance? Really, any place you have the organizer hierarchy concept (Device classes, templates, etc.), you should automatically put in copying, moving, renaming, inheritance.
Background: This 'per user' alerts management is good and not so good. We have a ticketing system that manages escalation and we have multiple Zenoss users (network/server admin types, management types). Our management systems (NNM and Zenoss) send emails to the ticketing system and we would like Zenoss to be more flexible and hierarchical. I don't want an alert that sends to the ticketing system tied to any active user's account. I want a Zenoss account that is only accessible by a few people and that account is the home of the 'standard' alerts that send to the ticketing system. But I don't want to have to develop all the alerts while logged into that user account. I want to be able to move alerts from my account to the 'ticketing' account that send alerts to the ticketing system. And I want any moves or any other alert changes to be logged and potentially put into an event. Matt -------------------- m2f -------------------- Read this topic online here: http://forums.zenoss.com/viewtopic.php?p=38652#38652 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
