Categorization of Alert Rules

FormerIdeaCreator

In , mentions grouping of alert rules.  In my situation I am using our one Orion install for Development, Demo and Production environments all in one.  For each of these environments I create a separate set of alert rules with different conditions and actions that fit the particular environment.  The combined list of alert rules has gotten very long.  To have a tree like categorization of these alert rules within Advanced Alert Manager would make management much easier.

tigger2

For categorization, I could see selecting some attribute or group and making that autobuild what part of the categorization tree it belonged to.  For example:

In each rule have a ....single drop down selector? of say "Grouping property" for the Node OR the class the rule is being written against (Volume, Network, etc.).  You choose a property, say, "Environment" and then select a value from all the values in the system, say "Development" (that has been added for all development nodes).  By selecting this property the alert rule implicitly adds this to the rule filter (as a "node/volume/network property = "<selected property>") so you don't have to add it again in the rule.  Then in the alert view there is a sub node in the tree that has the name of the class,property, and value you chose (e.g. the name would be "Environment is Development").

If you select no grouping property, you get the rule added to the root level alerts (not in a sub folder/group) OR it would auto-group based on the base class the alerts are tied to (Node/Volume/Network, etc) and would be in a sub folder called "Node" (or "Volume") so there would be no way to NOT group alerts. e.g. the tree would look like this if the examples above were used:

[Node] <- A folder icon

  + [Environment is Development] <- folder icon

     - *some rule where the grouping property is set to "Environment = Development"

  - *some rule where there is no grouping property set, so defaults to the main class of "Node"

  - *some rule where there is no grouping property set, so defaults to the main class of "Node"

  - ...

+[Volume]

+[Network]

...