Skip to content

Zabbix media and alert notification

In Zabbix, the notification process relies on specific database tables to define how alerts are delivered and to maintain a record of alert history. The system distinguishes between the definition of a notification method (Media Type) and the specific assignment of that method to a user (Media).

Media Types

The media_type table stores the definitions for the various delivery methods available in the system^[600-developer-operation-maintenance-zabbix-zabbix-intro.md]. This table records the specific execution scripts or protocols associated with a notification method^[600-developer-operation-maintenance-zabbix-zabbix-intro.md]. It is linked to the user-specific configurations via the mediatypeid key^[600-developer-operation-maintenance-zabbix-zabbix-intro.md].

User Media Configuration

The media table is responsible for storing the configuration of notification methods for individual users^[600-developer-operation-maintenance-zabbix-zabbix-intro.md]. It acts as the link between a user account and a specific media_type, defining exactly how a particular user should receive an alert^[600-developer-operation-maintenance-zabbix-zabbix-intro.md].

Alert History

The alerts table serves as the log for all historical alarm events^[600-developer-operation-maintenance-zabbix-zabbix-intro.md]. Whenever a trigger condition is met and an action is performed, a record is stored here, providing an audit trail of all notifications sent^[600-developer-operation-maintenance-zabbix-zabbix-intro.md].

  • [[Zabbix Triggers]]
  • [[Zabbix Actions]]

Sources

  • 600-developer-operation-maintenance-zabbix-zabbix-intro.md