Zabbix triggers and alerting actions¶

Triggers and actions are the core components of the Zabbix alerting logic, defining the conditions for an event and the system's response to it.

Triggers¶

A trigger is a logical expression that defines a problem state, evaluated based on data collected by [[Zabbix items|items]].^[600-developer-operation-maintenance-zabbix-zabbix-intro.md]

In the Zabbix backend, the triggers table stores all configuration information for every trigger instance^[600-developer-operation-maintenance-zabbix-zabbix-intro.md]. To define these states, triggers rely on calculation functions stored in the functions table, such as max(), last(), or nodata()^[600-developer-operation-maintenance-zabbix-zabbix-intro.md]. Triggers may also have dependencies defined in the trigger_depends table^[600-developer-operation-maintenance-zabbix-zabbix-intro.md].

Alerting Actions¶

When a trigger event occurs, Zabbix executes a predefined action.^[600-developer-operation-maintenance-zabbix-zabbix-intro.md]

The database table actions records the specific operations that must be performed when a trigger is fired^[600-developer-operation-maintenance-zabbix-zabbix-intro.md]. These operations can include sending notifications to users. The history of these executed alerts is archived in the alerts table^[600-developer-operation-maintenance-zabbix-zabbix-intro.md].

Notification Delivery¶

Actions typically deliver alerts through various media configured for users.

The media table stores the specific delivery configurations for a user (e.g., an email address or script parameters), while the media_type table defines the execution method (e.g., the specific script path) for that alert channel^[600-developer-operation-maintenance-zabbix-zabbix-intro.md].

Sources¶

^[600-developer-operation-maintenance-zabbix-zabbix-intro.md]