If an alert rule is set from Contacts, to alert the contact on failure of any monitor associated with the selected Agent, or any Server-Device monitor

If an alert rule is set from Contacts, to alert the contact on failure of any monitor associated with the selected Agent, or any Server-Device monitor.

In Monitis an alert rule can be assigned by either of 2 ways:

– From monitor, to alert selected contacts upon the monitor’s failure.
– From contact, to alert the contact upon the failure of any of the selected monitors.

The following rules apply to migration of existing alert rules that were created from contact to alert on failure of any monitor associated with certain agent, or any Server-Device monitor.

  • Alert rules created from contact to alert on failure of any monitor associated with certain agent, or any Server-Device monitor are mapped to certain thresholds created for those monitors to match the existing alert rules. These are legacy alert rules. You can change the threshold based rules to monitor state based, by mapping them to the CRITICAL or WARNING state of the monitor instead of the threshold. Once changed, the rule can’t be changed back to threshold based.

Example: before migration the user had an alert rule set up for the Demo Email1 contact to alert on 2 consecutive failures of any Server-Device monitor.
image41After the migration, the existing alert rule set from contact 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.
image42
image43

This is a legacy alert rule. You can change the rule (see Changing Alert Rule’s Condition from Threshold-based to State-based) from threshold based to monitor state based. This action is irreversible and can’t be undone.
image44

When you add an alert rule from contact to alert upon failure of any monitor associated with the selected agent or any Server-Device monitor, this rule is also visible in all the monitors of the selected group.

Upon migration to Alerts 2.0, you will see that such rules in the monitor are tied to certain thresholds created to match the existing rule set from the contact.

Example: before migration to Alerts 2.0 the user had 4 alert rules in his PING monitor, 2 of which were set to alert upon 1 failure, and 2 were set to alert upon 5 failures. There were thus two distinct numbers of failures in the monitor’s alert rules: 1 and 5.
image20The alert rule “Alert Demo Email1 Upon 5th fail” (highlighted on the above screen) is part of the rule set by the user from the Contacts menu to alert the Demo Email1 contact on failure of any Server-Device monitors.image21

There was a threshold set in the monitor’s settings:
image22

Upon migration to Alerts 2.0:

  • As there are only 2 distinct numbers of failures in the existing alert rules in the monitor:
  • The existing threshold in the monitor’s setting is combined with the smaller number of consecutive failures and moved into a new WARNING level threshold created in the monitor.
  • image23The existing threshold in the monitor’s setting is combined with the greater number of consecutive failures and moved into a new CRITICAL level threshold created in the monitor.
  • image24All existing alert rule are updated.

– Alert rules with the smaller number of consecutive failures are mapped to the WARNING state of the monitor.
image25– The alert rule with the greater number of consecutive failures is mapped to the CRITICAL state of the monitor.
image26

The alert rule set from contact (“Alert Demo Email 1 upon 5 consecutive failures of any Server-Device monitor”) is mapped to a certain threshold created to match the existing rule set for the contact.image27

This is a legacy alert rule.

You can change this rule to monitor state based by mapping it to the CRITICAL or WARNING state of monitor instead of the threshold. Click the radio button next to Monitor’s condition changed to: and select the status (CRITICAL or WARNING).
Once changed, the rule cannot be rolled back to threshold based (see Changing Alert Rule’s Condition from Threshold based to State based).