If there are more than two distinct numbers of consecutive failures in the alert rules

If there are more than two distinct numbers of consecutive failures in the alert rules.

  • The existing threshold in the monitor and the number of consecutive failures in the alert rules are moved to new CRITICAL level thresholds created in the monitor. There will be as many CRITICAL level thresholds created in the monitor as there were distinct numbers of consecutive failures in the existing alert rules.
  • All alert rules are updated to be mapped to the newly created CRITICAL thresholds. Each alert rule is mapped to the threshold with the same number of consecutive failures as it was in the alert rule before migration.
    Alert rules will trigger and alerts will be sent whenever the threshold the rule is linked to is violated.
    These are legacy alert rules. You can change them from threshold based to state based by mapping them to the CRITICAL or WARNING state of the monitor instead of the specific thresholds that they are tied to.
    Once changed to state based the rule can’t be rolled back to threshold based.

Example: before migration to Alerts 2.0 the user had 5 alert rules in his Drive monitor, 2 of which were set to alert upon 1 failure, 2 were set to alert upon 2 failures, and 1 was set to alert upon 3 failures. There were thus three distinct numbers of failures in the monitor’s alert rules: 1, 2 and 3.
image16There was a threshold set in the monitor’s settings:
image17

Upon migration to Alerts 2.0:

  • As there are 3 distinct numbers of consecutive failures in the alert rules (1, 2 and 3), 3 CRITICAL level thresholds are created in the monitor.
  • image18Alert rules are updated to be mapped to the newly created CRITICAL thresholds. Each alert rule is mapped to the threshold with the same number of consecutive failures as it was in the alert rule before migration.

image19
Such rules are legacy alert rules. You can change them from threshold based to state based by mapping them to the CRITICAL or WARNING state of the monitor instead of the certain thresholds that they are linked to. Select the Monitor’s condition changed to: radio button, assign the state (CRITICAL or WARNING) and click Save. Once changed to state based the rule cannot be rolled back to threshold based.

Important: a legacy alert rule is linked to a specific threshold that was created when migrating the rule: such a rule uses this (and only this) threshold to trigger alerting. This threshold can be used also by new alert rules that you add in your monitor after Monitis has migrated your account to Alerts 2.0. Unless you delete or change to state based all the legacy alert rules that are using this threshold, you will not be able to delete it. This is to ensure that all the legacy alert rules you get in your monitors after Monitis migration to Alerts 2.0 will keep working for as long as you need them.