6 Media types

Overview

Media types are exported with all related objects and object relations.

Exporting

To export media types, do the following:

• Go to: Administration → Media types
• Mark the checkboxes of the media types to export
• Click on Export below the list

Depending on the selected format, media types are exported to a local file with a default name:

• zabbix_export_mediatypes.yaml - in YAML export (default option for export)
• zabbix_export_mediatypes.xml - in XML export
• zabbix_export_mediatypes.json - in JSON export

Importing

To import media types, do the following:

• Go to: Administration → Media types
• Click on Import to the right
• Select the import file
• Mark the required options in import rules
• Click on Import

A success or failure message of the import will be displayed in the frontend.

Import rules:

Update existing Existing elements will be updated with data taken from the import file. Otherwise they will not be updated.

Create new The import will add new elements using data from the import file. Otherwise it will not add them.

Delete missing The import will remove existing elements not present in the import file. Otherwise it will not remove them. |<| |<| |<| |<| type: WEBHOOK parameters: 7: name: eventid value: '{EVENT.ID}' 2: name: message value: '{ALERT.MESSAGE}' 6: name: priority value: "0" 3: name: title value: '{ALERT.SUBJECT}' 0: name: token value: <PUSHOVER TOKEN HERE> 8: name: triggerid value: '{TRIGGER.ID}' 4: name: url value: '{$ZABBIX.URL}' 5: name: url_title value: Zabbix 1: name: user value: '{ALERT.SENDTO}' max_sessions: "0" script: "try {//.Log(127, 'Pushover webhook script value='+value); = JSON.parse(value),= new CurlHttpRequest(),= {};.AddHeader('Content-Type: application/json');.token= params.token;.user = params.user;   /*If a device name is not specified for a user, or the specified device name is no longer enabled/valid,notifications will be sent to all active devices for that user to avoid losing messages.Messages may be addressed to multiple specific devices by joining them with a comma (such as device=iphone,nexus5).fields.device = params.device;/.title = params.title;.message = params.message;fields.url = params.url+"/tr_events.php?triggerid="+params.triggerid+"&eventid="+params.eventid;   fields.url_title = params.url_title;fields.priority = params.priority; resp = req.Post('https://api.pushover.net/1/messages.json',.stringify(fields); (req.Status() != 200) {JSON.parse(resp).errors[0];\t} = JSON.parse(resp);return "OK";} catch (error) {.Log(127, 'Pushover notification failed : '+error);throw 'Pushover notification failed : '+error;}" description: |- Please refer to setup guide here: https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/pushover

  Set token parameter with to your Pushover application key.
         When assigning Pushover media to the Zabbix user - add user key into send to field.

... ```

Element tags

Element tag values are explained in the table below.

Footnotes

¹ For string values, only the string will be exported (e.g. "EMAIL") without the numbering used in this table. The numbers for range values (corresponding to the API values) in this table is used for ordering only.