As mídias são os canais de distribuição utilizados para enviar notificações e alertas no Zabbix. Podemos dizer que são através delas que o Zabbix se comunica com o mundo externo
As mídias podem ser de vários tipos:
Some parameters are common for all media types.
In the Media type tab the common general attributes are:
|Name||Name of the media type.|
|Type||Select the type of media.|
|Description||Enter a description.|
|Enabled||Mark the checkbox to enable the media type.|
See the individual pages of media types for media-specific parameters.
The Message templates tab allows to set default notification messages for all or some of the following event types:
To customize message templates:
Message template parameters:
|Message type||Type of event for which default message will be defined.
Only one default message can be defined for each event type.
|Subject||Subject of the default message. The subject may contain macros. It is limited to 255 characters.
Subject is not available for SMS media type.
|Message||The default message. The message may contain macros. It is limited to certain amount of characters depending on the type of database (see Sending messages for more information).|
To make changes to an existing message template: In the Actions column click on to edit the template or click on to delete the message template.
A notification message template can also be defined for each action individually (see action operations for details). Custom messages in actions can override message templates configured for a media type.
Message templates must be defined for all media types, including webhooks or custom alert scripts that are not using default messages for notifications. For example, an action "Send message to Pushover webhook" will fail to send problem notifications, if problem message has not been defined for the Pushover webhook.
The Options tab contains alert processing settings. The same set of options is configurable for each media type.
All media types are processed in parallel. While the maximum number of concurrent sessions is configurable per media type, the total number of alerter processes on server can only be limited by the StartAlerters parameter. Alerts generated by one trigger are processed sequentially. So multiple notifications may be processed simultaneously only if they are generated by multiple triggers.
|Concurrent sessions||Select the number of parallel alerter sessions for the media type:
One - one session
Unlimited - unlimited number of sessions
Custom - select a custom number of sessions
Unlimited/high values mean more parallel sessions and increased capacity for sending notifications. Unlimited/high values should be used in large environments where lots of notifications may need to be sent simultaneously.
If more notifications need to be sent than there are concurrent sessions, the remaining notifications will be queued; they will not be lost.
|Attempts||Number of attempts for trying to send a notification. Up to 100 attempts can be specified; default value is '3'. If '1' is specified Zabbix will send the notification only once and will not retry if the sending fails.|
|Attempt interval||Frequency of trying to resend a notification in case the sending failed, in seconds (0-3600). If '0' is specified, Zabbix will retry immediately.
Time suffixes are supported, e.g. 5s, 3m, 1h.
It is possible to test if a configured media type works.
For example, to test an e-mail media type:
Test success or failure message will be displayed in the same window:
To test a webhook media type:
By default, webhook tests are performed with parameters entered during configuration. However, it is possible to change attribute values for testing. Replacing or deleting values in the testing window affects the test procedure only, the actual webhook attribute values will remain unchanged.
To view media type test log entries without leaving the test window:
To receive notifications of a media type, a medium (e-mail address/phone number/webhook user ID etc) for this media type must be defined in the user profile. For example, an action sending messages to user "Admin" using webhook "X" will always fail to send anything if the webhook "X" medium is not defined in the user profile.
To define user media:
User media attributes:
|Type||The drop-down list contains names of all configured media types.|
|Send to||Provide required contact information where to send messages.
For an e-mail media type it is possible to add several addresses by clicking on below the address field. In this case, the notification will be sent to all e-mail addresses provided. It is also possible to specify recipient name in the Send to field of the e-mail recipient in a format 'Recipient name <[email protected]>'. Note, that if a recipient name is provided, an e-mail address should be wrapped in angle brackets (<>). UTF-8 characters in the name are supported, quoted pairs and comments are not. For example: John Abercroft <[email protected]> and [email protected] are both valid formats. Incorrect examples: John Doe [email protected], %%"Zabbix\@\<H(comment)Q\>" [email protected] %%.
|When active||You can limit the time when messages are sent, for example, set the working days only (1-5,09:00-18:00). Note that this limit is based on the user time zone. If the user time zone is changed and is different from the system time zone this limit may need to be adjusted accordingly so as not to miss important messages.
See the Time period specification page for description of the format.
|Use if severity||Mark the checkboxes of trigger severities that you want to receive notifications for.
Note that the default severity ('Not classified') must be checked if you want to receive notifications for non-trigger events.
After saving, the selected trigger severities will be displayed in the corresponding severity colors, while unselected ones will be grayed out.
|Status||Status of the user media.
Enabled - is in use.
Disabled - is not being used.