1 Conditions

Overview

It is possible to define that an action is executed only if the event matches a defined set of conditions. Conditions are set when configuring the action.

Condition matching is case-sensitive.

Trigger actions

The following conditions can be used in trigger-based actions:

Service actions

The following conditions can be used in service actions:

Make sure to define message templates for Service actions in the Alerts → Media types menu. Otherwise, the notifications will not be sent.

Discovery actions

The following conditions can be used in discovery-based events:

Service checks in a discovery rule, which result in discovery events, do not take place simultaneously. Therefore, if multiple values are configured for Service type, Service port or Received value conditions in the action, they will be compared to one discovery event at a time, but not to several events simultaneously. As a result, actions with multiple values for the same check types may not be executed correctly.

Autoregistration actions

The following conditions can be used in actions based on active agent autoregistration:

Internal event actions

The following conditions can be set for actions based on internal events:

Type of calculation

The following options of calculating conditions are available:

• And - all conditions must be met

Note that using “And” calculation is disallowed between several triggers when they are selected as a Trigger= condition. Actions can only be executed based on the event of one trigger.

• Or - enough if one condition is met
• And/Or - combination of the two: AND with different condition types and OR with the same condition type, for example:

Host group equals Oracle servers
Host group equals MySQL servers
Trigger name contains ‘Database is down’
Trigger name contains ‘Database is unavailable’

is evaluated as

(Host group equals Oracle servers or Host group equals MySQL servers) and (Trigger name contains ‘Database is down’ or Trigger name contains ‘Database is unavailable’)

• Custom expression - a user-defined calculation formula for evaluating action conditions. It must include all conditions (represented as uppercase letters A, B, C, …) and may include spaces, tabs, brackets ( ), and (case sensitive), or (case sensitive), not (case sensitive).

While the previous example with And/Or would be represented as (A or B) and (C or D), in a custom expression you may as well have multiple other ways of calculation:

(A and B) and (C or D)
(A and B) or (C and D)
((A or B) and C) or D
(not (A or B) and C) or not D
etc.

Actions disabled due to deleted objects

If a certain object (host, template, trigger, etc.) used in an action condition/operation is deleted, the condition/operation is removed and the action is disabled to avoid incorrect execution of the action. The action can be re-enabled by the user.

This behavior takes place when deleting:

• host groups (“host group” condition, “remote command” operation on a specific host group);
• hosts (“host” condition, “remote command” operation on a specific host);
• templates (“template” condition, “link to template” and “unlink from template” operations);
• triggers (“trigger” condition);
• discovery rules (when using “discovery rule” and “discovery check” conditions).

If a remote command has many target hosts, and we delete one of them, only this host will be removed from the target list, the operation itself will remain. But, if it’s the only host, the operation will be removed, too. The same goes for “link to template” and “unlink from template” operations.

Actions are not disabled when deleting a user or user group used in a “send message” operation.