Pushover
Pushover for Teams is a monthly service offering for organizations sending messages to multiple users and includes a number of extra features such as user management and failover SMS message delivery.
Pushover for Teams is a monthly service offering for organizations sending messages to multiple users and includes a number of extra features such as user management and failover SMS message delivery.
Source: https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/pushover?at=release/7.4
With Pushover, a user can be notified the most convenient way — with push notification straight to a mobile device.
Zabbix version: 7.4 and higher.
After importing the webhook, you can configure it using webhook parameters.
The configurable parameters are intended to be changed according to the webhook setup as well as the user's preferences and environment.
| Name | Value | Description |
|---|---|---|
| endpoint | https://api.pushover.net/1/messages.json | Pushover API endpoint. |
| expire | 1200 | |
| priority_average | 0 | Average priority. |
| priority_default | 0 | Default priority. |
| priority_disaster | 0 | Disaster priority. |
| priority_high | 0 | High priority. |
| priority_information | 0 | Information priority. |
| priority_not_classified | 0 | Not classified priority. |
| priority_warning | 0 | Warning priority. |
| retry | 60 | |
| tls_verify | {$HTTP.TLS.VERIFY:"Pushover"} | TLS certificate verification for HTTP requests: "none" - disabled, "peer" - verify the certificate chain and expiration, "full" - full verification. Any other value enables full verification. To override the setting for this media type only, define the global macro with the context "Pushover", e.g. {$HTTP.TLS.VERIFY:"Pushover"}. |
| token | <PUSHOVER TOKEN HERE> | Pushover API token. |
| url | {$ZABBIX.URL} | Current Zabbix URL. |
| url_title | Zabbix | URL title. |
Internal parameters are reserved for predefined macros that are not meant to be changed.
| Name | Value | Description |
|---|---|---|
| eventid | {EVENT.ID} | Numeric ID of the event that triggered an action. |
| event_nseverity | {EVENT.NSEVERITY} | Numeric value of the event severity. Possible values: 0 - Not classified, 1 - Information, 2 - Warning, 3 - Average, 4 - High, 5 - Disaster. |
| event_source | {EVENT.SOURCE} | Numeric value of the event source. Possible values: 0 - Trigger, 1 - Discovery, 2 - Autoregistration, 3 - Internal, 4 - Service. |
| event_value | {EVENT.VALUE} | Numeric value of the event that triggered an action (1 for problem, 0 for recovering). |
| message | {ALERT.MESSAGE} | 'Default message' value from action configuration. |
| title | {ALERT.SUBJECT} | 'Default subject' value from action configuration. |
| triggerid | {TRIGGER.ID} | Numeric ID of the trigger of this action. |
| user | {ALERT.SENDTO} | 'Send to' value from user media configuration. |
Please be aware that each webhook supports an HTTP proxy. To use this feature, add a new media type parameter with the name
http_proxyand set its value to the proxy URL.
Register the account at https://pushover.net/ and then install Pushover app at your iOS or Android device.
Then click here to create new integration with Zabbix.
At this point, we have Application API Token (token) of the Zabbix application and Pushover User Key.
You would need both in Zabbix pushover webhook.
Go to Administration->General (Macro) and create new macro that points to your Zabbix frontend
{$ZABBIX.URL} = https://myzabbix.local
Proceed to Administration→ Media types at the Zabbix frontend and find Pushover. If you don't have it, import it from the official Zabbix repository here:
https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/pushover
Edit Pushover media type parameters and replace token with your Pushover application key.
Next, proceed to your User profile and create new Media of Pushover type, use your User key in Send to field.
Also, you can customize Pushover message priority for each Zabbix severity. Change value of priority_<severity_name> parameter. It must be between -2 and 2. By default, messages have normal priority (a priority of 0). For more information check Pushover documentation.
Make sure proper trigger actions are set at Configuration→Actions page. For starters, you can enable default "Report problems to Zabbix administrators" rule.
You are all set! Now break something to receive a notification :)
Please report any issues with the media type at https://support.zabbix.com.
You can also provide feedback, discuss the media type, or ask for help at ZABBIX forums.
4
