Rule. New condition -> existing rule

fabian.s

The "new" rule feature has some potential. A helpful addition would be that you can nest rules.

A simple example:

Rule 1

Name: MSSQL_TEST

Custom Properties: Environment = "TEST"

Database type: SQL Server

Rule 2

Name: MSSQL_PROD

Custom Properties: Environment = "PROD"

Database type: SQL Server

Rule 3

Name: MSSQL_ALL

Custom Properties: Rule = "MSSQL_TEST + MSSQL_PROD" 

With the ability to nest rules it is much easier to create useful rules for alerting

cpriddy

The syntax specified above for Rule 3 is a bit confusing as it might imply you are wanting rule 3's "Custom Properties: Rule = ..."  clause to pull out only the custom property clauses in the other two rules but ignore the database type. Ignoring the syntax, my interpretation of your intent is that you want Rule 3 to match on any instance that matches either of the complete rules of MSSQL_TEST  OR MSSQL_PROD - i.e. I take the "+"  in your syntax to mean OR instead of AND since it would be unlikely for a DB to be both in test and production environments. The goal being that if the definition of either MSSQL_TEST or MSSQL_PROD changes in the future, then rule 3 would automatically have a corresponding change. 

So Rule 3 to have your requested feature, might be done with syntax something like:

            rule.'MSSQL_TEST' = 'TRUE'  OR  rule.'MSSQL_PROD' = 'TRUE'  

which with those rules' current definition would be the equivalent of writing Rule 3 as:

            (database.'Database type' = 'SQL Server' AND property.'Environment' = 'TEST') OR (database.'Database type' = 'SQL Server' AND property.'Environment' = 'PROD') 

If you decided to change the MSSQL_TEST rule, then the latter rule 3 would have to be manually modified to match, whereas the first specification because of the "rule:" clauses would not require rule 3 to be updated. 

Is the above an accurate interpretation of your intent?