Changing Alert Rule’s Condition from Threshold Based to State Based

The action of changing an alert rule from threshold based to state based can’t be undone: once changed to state based the alert rule cannot be changed back to threshold based.

See below described the changes that you will observe once you change a threshold based alert rule to monitor state based.

RULES SET FROM MONITOR

Before you have changed the rule from threshold to state based:

When the monitor was migrated to Alerts 2.0, the updated alert rule was linked to a certain threshold, with the number of consecutive failures taken from the existing alert rule, forming a legacy rule.image29

The contact Demo Email 3 on the above screen would receive alerts whenever total free memory or free swap memory on your machine drops down below 100 MB for 1 consecutive check.

You can change this legacy rule to state based at any time as shown on the screen.

Important: a legacy alert rule is linked to a specific threshold that was created upon the migration. Unless you delete or change to monitor 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 the migration will keep working for as long as you need them.

 

After you have changed the rule from threshold to state based:

The rule is now set on your selected state of the monitor (e.g. CRITICAL selected on the screen below).
image30

The contact Demo Email 3 will now receive alerts whenever any CRITICAL level threshold is violated in the monitor.

 

RULES SET FROM CONTACT

Before you have changed the rule from threshold to state based:

As per the case 4 above, after migration the rule in your monitor that was added from contact was linked to a specific threshold, with the number of consecutive failures taken from the corresponding alert rule set to notify on failure of any monitor of the selected Agent or any Server-Device monitor.

1

This is a legacy alert rule, and you can change it to state based by selecting the Monitor’s condition changed to: radio button, as shown on the above screen.

As this rule was set from contact, it is part of the rule created to alert the contact on failure of any of monitors of the selected agent, or any Server-Device monitor.

You can see this rule among the alert rules set for the contact if you go to Alerts -> Contacts.
image31

This rule is linked to newly created thresholds to match the existing rule.
image32

After you have changed the rule to state based:

Once you change a legacy rule in your monitor to state based, it will be linked to your selected state of the monitor. In the below screen CRITICAL state is selected, so the alert rule will be triggered and you will receive an alert as soon as any CRITICAL level threshold in your monitor is violated (see Thresholds).
image33

If you now go to Alerts -> Contacts and open the “Alert upon the failure of any Server-Device monitor” alert rule of this contact, you will notice that:

1. The monitor for which you have changed the rule to state based is now excluded from the list of monitors in the rule set from contact (the box next to it is unchecked).
image34Notice also that the threshold the old alert rule was linked to is now removed from the list of thresholds contained in the general “Alert upon the failure of any Server-Device monitor” rule set for the contact. You will not see it there in the list of thresholds anymore.image35

  1. Instead, a new state based alert rule is added in the list of alert rules for this contact.
    image36Important: not only changing the alerting condition from threshold to state based, but also any other editing in monitor of the rule set from contact will exclude the monitor from the group alert rule, and separate alert rule for this monitor will be created.

The action of changing a legacy rule to state based is irreversible and cannot be undone. You will not be able to add back the monitor in the list in the alert rule set for the contact by checking the box next to it: the action of adding/removing manually monitors in the rule set for contact is disabled once your account is migrated to Alerts 2.0.
To be able to add/remove monitors in a rule set from contact you will need to change this rule to state based, as opposed to changing to state based separate rules in the monitors that are parts of this common rule.
image37

Select the Monitor’s condition changed to: radio button, and choose the state (CRITICAL or WARNING) from the combo box. Click Save.

You will see the alert rule for the contact is now set to alert on monitor entering the selected state (CRITICAL on the below screen).
image38

You can see also that the separate alert rules in the monitors that are parts of the rule set for the contact are changed now to state based as well.
image39