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:

Export format

Export to YAML:

---
zabbix_export:
  version: "5.2"
  date: "2020-08-06T08:19:30Z"
  media_types:
  - name: Pushover
    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 {\n//\tZabbix.Log(127, 'Pushover webhook script value='+value);\n\n\tparams
      = JSON.parse(value),\n\treq = new CurlHttpRequest(),\n\tfields = {};\n\n\treq.AddHeader('Content-Type:
      application/json');\n\n\tfields.token= params.token;\n\tfields.user = params.user;\n\n\n
      \      /*\n       If a device name is not specified for a user, or the specified
      device name is no longer enabled/valid,\n       notifications will be sent to
      all active devices for that user to avoid losing messages.\n       Messages
      may be addressed to multiple specific devices by joining them with a comma (such
      as device=iphone,nexus5).\n       fields.device = params.device;\n       */\n\tfields.title
      =  params.title;\n\tfields.message =  params.message;\n        fields.url =
      params.url+\"/tr_events.php?triggerid=\"+params.triggerid+\"&eventid=\"+params.eventid;\n
      \       fields.url_title = params.url_title;\n        fields.priority = params.priority;\n\tvar
      resp = req.Post('https://api.pushover.net/1/messages.json',\n\t\tJSON.stringify(fields)\n\t);\n\n\tif
      (req.Status() != 200) {\n\t\tthrow JSON.parse(resp).errors[0];\n\t}\n\n\tresp
      = JSON.parse(resp);\n        return \"OK\";\n\n} catch (error) {\n\tZabbix.Log(127,
      'Pushover notification failed : '+error);\n        throw 'Pushover notification
      failed : '+error;\n}"
    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

1 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.