Migration Rules

The following rules apply to migration of your existing alert rules to Alerts 2.0, as per the below described cases:

  1. If all alert rules in the monitor have the same number of consecutive failures to alert upon:
    A CRITICAL level threshold is created in the monitor and all alert rules are mapped to the CRITICAL state of monitor.
  2. If alert rules in the monitor have 2 distinct numbers of consecutive failures:
    1 CRITICAL and 1 WARNING level thresholds are created in the monitor, alert rules with the smaller number of failures are mapped to the WARNING state, and alert rules with the greater number of failures are mapped to the CRITICAL state of monitor.
  3. If alert rules in the monitor have more than 2 distinct numbers of failures:
    All alert rules are mapped to certain thresholds created in the monitor, forming legacy alert rules: you can change them to state based at any time. Once changed to state based the rule can’t be rolled back to threshold based.
  4. If an alert rule is set from Contacts, to alert the contact on failure of any monitor associated with the selected Agent, or on failure of any Server-Device monitor:
    The alert rule is mapped to certain thresholds created for the monitors of the selected agent or for all Server-Device monitors to match the existing alert rule. This is legacy alert rule, and you can change it from threshold based to state based at any time. Once changed to state based the rule can’t be rolled back to threshold based.
  5. If there were no alert rules in the monitor:
    A threshold of CRITICAL level with the number of checks to fail equal to 1, and, depending on the monitor type, a metric condition based on the current threshold in the monitor settings, is created in the monitor upon the migration.