The trigger list for a host can be accessed from Data collection → Hosts by clicking on Triggers for the respective host.
|Severity||Severity of the trigger is displayed by both name and cell background color.|
|Value||Trigger value is displayed:
OK - the trigger is in the OK state
PROBLEM - the trigger is in the Problem state
|Host||Host of the trigger.
This column is displayed only if multiple hosts are selected in the filter.
|Name||Name of the trigger, displayed as a blue link to trigger details.
Clicking on the trigger name link opens the trigger configuration form.
If the host trigger belongs to a template, the template name is displayed before the trigger name, as a gray link. Clicking on the template link will open the trigger list on the template level.
If the trigger has been created from a trigger prototype, its name is preceded by the low-level discovery rule name, in orange. Clicking on the discovery rule name will open the trigger prototype list.
|Operational data||Operational data definition of the trigger, containing arbitrary strings and macros that will resolve dynamically in Monitoring → Problems.|
|Expression||Trigger expression is displayed. The host-item part of the expression is displayed as a link, leading to the item configuration form.|
|Status||Trigger status is displayed - Enabled, Disabled or Unknown. By clicking on the status you can change it - from Enabled to Disabled (and back); from Unknown to Disabled (and back).
Problems of a disabled trigger are no longer displayed in the frontend, but are not deleted.
|Info||If everything is working correctly, no icon is displayed in this column. In case of errors, a square icon with the letter "i" is displayed. Hover over the icon to see a tooltip with the error description.|
|Tags||If a trigger contains tags, tag name and value are displayed in this column.|
To configure a new trigger, click on the Create trigger button at the top right corner.
Os botões abaixo da lista oferecem algumas opções de edição em massa:
Para usar essas opções, marque as caixas de seleção antes do respectivo acionadores e, em seguida, clique no botão necessário.
You can use the filter to display only the triggers you are interested in. For better search performance, data is searched with macros unresolved.
The Filter icon is available at the top right corner. Clicking on it will open a filter where you can specify the desired filtering criteria.
|Host groups||Filter by one or more host groups.
Specifying a parent host group implicitly selects all nested host groups.
Host groups containing templates only cannot be selected.
|Hosts||Filter by one or more hosts.
If host groups are already selected above, host selection is limited to those groups.
|Name||Filter by trigger name.|
|Severity||Select to filter by one or several trigger severities.|
|State||Filter by trigger state.|
|Status||Filter by trigger status.|
|Value||Filter by trigger value.|
|Tags||Filter by trigger tag name and value. It is possible to include as well as exclude specific tags and tag values. Several conditions can be set. Tag name matching is always case-sensitive.
There are several operators available for each condition:
Exists - include the specified tag names
Equals - include the specified tag names and values (case-sensitive)
Contains - include the specified tag names where the tag values contain the entered string (substring match, case-insensitive)
Does not exist - exclude the specified tag names
Does not equal - exclude the specified tag names and values (case-sensitive)
Does not contain - exclude the specified tag names where the tag values contain the entered string (substring match, case-insensitive)
There are two calculation types for conditions:
And/Or - all conditions must be met, conditions having the same tag name will be grouped by the Or condition
Or - enough if one condition is met
Macros and macro functions are supported both in tag name and tag value fields.
|Inherited||Filter triggers inherited (or not inherited) from a template.|
|Discovered||Filter triggers discovered (or not discovered) by low-level discovery.|
|With dependencies||Filter triggers with (or without) dependencies.|