Brevis.one webhook

This guide describes how to integrate Zabbix 7.0 installation with Brevis.one SMS Gateway using HTTP API and Zabbix webhook feature. This guide provides instructions on setting up a media type, a user, and an action in Zabbix.

Setting up Brevis.one

1. Create a user for HTTP API or use an existing one.

2. Grant to the user Access to the HTTP API permission. See Brevis.one documentation for the information.

Setting up the webhook in Zabbix

1. Before setting up a media type, you need to set up a global macro "{$ZABBIX.URL}", which must contain the URL to Zabbix frontend.

2. In the Administration > Media types section, import media_brevis.one.xml.

3. Open the newly added Brevis.one media type and replace all <PLACEHOLDERS> with your values.
The following parameters should be filled out:
endpoint - the actual URL of your Brevis.one API instance. The API can be addressed with the following: https://<SMS Gateway IP>/api.php
username - Brevis.one API username.
password - user's password.

3. The following parameters can help you customize the alerts: *ring, flash, telauto
See Brevis.one documentation for details.

4. Create a service Zabbix user or use any existing user, then add Media with the Brevis.one. The "Send to" field should be filled as a phone number without a plus (+) sign or as "mode:option".
Allowed modes: number (Default), group, telgroup, telnumber, user, teluser.
Examples: 37167784742 (Send SMS to the individual telephone number)
group:11 (Send a text message to the specified user group. User groups are managed in the Configuration - Groups.)
telnumber:37167784742 (Send a message via Automatic to the individual telephone number. Automatic tries to deliver the notification via Telegram. If this fails the notification will be delivered by a text message.)
See Brevis.one documentation for additional information.
Note, that the "Send to" field cannot be empty. If the phone number or user/group ID is already specified in the send_to parameter, you can put any symbol in this field to comply with frontend requirements. Make sure this user has access to all hosts, for which you would like problem notifications to be sent via Brevis.one HTTP API.

For more information see Zabbix and Brevis.one documentations.

Supported versions

Zabbix 7.0 and higher

Brevis.one webhook

Overview

This guide describes how to integrate Zabbix installation with Brevis.one SMS Gateway using HTTP API and Zabbix webhook feature. This guide provides instructions on setting up a media type, a user, and an action in Zabbix.

Requirements

Zabbix version: 7.0 and higher.

Parameters

After importing the webhook, you can configure it using webhook parameters.

Configurable parameters

The configurable parameters are intended to be changed according to the webhook setup as well as the user's preferences and environment.

Internal parameters

Internal parameters are reserved for predefined macros that are not meant to be changed.

Please be aware that each webhook supports an HTTP proxy. To use this feature, add a new media type parameter with the name http_proxy and set its value to the proxy URL.

Service setup

1. Create a user for HTTP API or use an existing one.

2. Grant to the user Access to the HTTP API permission. See Brevis.one documentation for the information.

Zabbix configuration

1. Before setting up a media type, you need to set up a global macro "{$ZABBIX.URL}", which must contain the URL to Zabbix frontend.

2. In the Administration > Media types section, import media_brevis.one.xml.

3. Open the newly added Brevis.one media type and replace all <PLACEHOLDERS> with your values.
The following parameters should be filled out:
endpoint - the actual URL of your Brevis.one API instance. The API can be addressed with the following: https://<SMS Gateway IP>/api.php
username - Brevis.one API username.
password - user's password.

3. The following parameters can help you customize the alerts: *ring, flash, telauto
See Brevis.one documentation for details.

4. Create a service Zabbix user or use any existing user, then add Media with the Brevis.one. The "Send to" field should be filled as a phone number without a plus (+) sign or as "mode:option".
Allowed modes: number (Default), group, telgroup, telnumber, user, teluser.
Examples: 37167784742 (Send SMS to the individual telephone number)
group:11 (Send a text message to the specified user group. User groups are managed in the Configuration - Groups.)
telnumber:37167784742 (Send a message via Automatic to the individual telephone number. Automatic tries to deliver the notification via Telegram. If this fails the notification will be delivered by a text message.)
See Brevis.one documentation for additional information.
Note, that the "Send to" field cannot be empty. If the phone number or user/group ID is already specified in the send_to parameter, you can put any symbol in this field to comply with frontend requirements. Make sure this user has access to all hosts, for which you would like problem notifications to be sent via Brevis.one HTTP API.

Feedback

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.

Brevis.one webhook

This guide describes how to integrate Zabbix 6.2 installation with Brevis.one SMS Gateway using HTTP API and Zabbix webhook feature. This guide provides instructions on setting up a media type, a user, and an action in Zabbix.

Setting up Brevis.one

1. Create a user for HTTP API or use an existing one.

2. Grant to the user Access to the HTTP API permission. See Brevis.one documentation for the information.

Setting up the webhook in Zabbix

1. Before setting up a media type, you need to set up a global macro "{$ZABBIX.URL}", which must contain the URL to Zabbix frontend.

2. In the Administration > Media types section, import media_brevis.one.xml.

3. Open the newly added Brevis.one media type and replace all <PLACEHOLDERS> with your values.
The following parameters should be filled out:
endpoint - the actual URL of your Brevis.one API instance. The API can be addressed with the following: https://<SMS Gateway IP>/api.php
username - Brevis.one API username.
password - user's password.

3. The following parameters can help you customize the alerts: *ring, flash, telauto
See Brevis.one documentation for details.

4. Create a service Zabbix user or use any existing user, then add Media with the Brevis.one. The "Send to" field should be filled as a phone number without a plus (+) sign or as "mode:option".
Allowed modes: number (Default), group, telgroup, telnumber, user, teluser.
Examples: 37167784742 (Send SMS to the individual telephone number)
group:11 (Send a text message to the specified user group. User groups are managed in the Configuration - Groups.)
telnumber:37167784742 (Send a message via Automatic to the individual telephone number. Automatic tries to deliver the notification via Telegram. If this fails the notification will be delivered by a text message.)
See Brevis.one documentation for additional information.
Note, that the "Send to" field cannot be empty. If the phone number or user/group ID is already specified in the send_to parameter, you can put any symbol in this field to comply with frontend requirements. Make sure this user has access to all hosts, for which you would like problem notifications to be sent via Brevis.one HTTP API.

For more information see Zabbix and Brevis.one documentations.

Supported versions

Zabbix 6.2 and higher

Brevis.one webhook

This guide describes how to integrate Zabbix 6.2 installation with Brevis.one SMS Gateway using HTTP API and Zabbix webhook feature. This guide provides instructions on setting up a media type, a user, and an action in Zabbix.

Setting up Brevis.one

1. Create a user for HTTP API or use an existing one.

2. Grant to the user Access to the HTTP API permission. See Brevis.one documentation for the information.

Setting up the webhook in Zabbix

1. Before setting up a media type, you need to set up a global macro "{$ZABBIX.URL}", which must contain the URL to Zabbix frontend.

2. In the Administration > Media types section, import media_brevis.one.xml.

3. Open the newly added Brevis.one media type and replace all <PLACEHOLDERS> with your values.
The following parameters should be filled out:
endpoint - the actual URL of your Brevis.one API instance. The API can be addressed with the following: https://<SMS Gateway IP>/api.php
username - Brevis.one API username.
password - user's password.

3. The following parameters can help you customize the alerts: *ring, flash, telauto
See Brevis.one documentation for details.

4. Create a service Zabbix user or use any existing user, then add Media with the Brevis.one. The "Send to" field should be filled as a phone number without a plus (+) sign or as "mode:option".
Allowed modes: number (Default), group, telgroup, telnumber, user, teluser.
Examples: 37167784742 (Send SMS to the individual telephone number)
group:11 (Send a text message to the specified user group. User groups are managed in the Configuration - Groups.)
telnumber:37167784742 (Send a message via Automatic to the individual telephone number. Automatic tries to deliver the notification via Telegram. If this fails the notification will be delivered by a text message.)
See Brevis.one documentation for additional information.
Note, that the "Send to" field cannot be empty. If the phone number or user/group ID is already specified in the send_to parameter, you can put any symbol in this field to comply with frontend requirements. Make sure this user has access to all hosts, for which you would like problem notifications to be sent via Brevis.one HTTP API.

For more information see Zabbix and Brevis.one documentations.

Supported versions

Zabbix 6.2 and higher

Brevis.one webhook

This guide describes how to integrate Zabbix 6.0 installation with Brevis.one SMS Gateway using HTTP API and Zabbix webhook feature. This guide provides instructions on setting up a media type, a user, and an action in Zabbix.

Setting up Brevis.one

1. Create a user for HTTP API or use an existing one.

2. Grant to the user Access to the HTTP API permission. See Brevis.one documentation for the information.

Setting up the webhook in Zabbix

1. Before setting up a media type, you need to set up a global macro "{$ZABBIX.URL}", which must contain the URL to Zabbix frontend.

2. In the Administration > Media types section, import media_brevis.one.xml.

3. Open the newly added Brevis.one media type and replace all <PLACEHOLDERS> with your values.
The following parameters should be filled out:
endpoint - the actual URL of your Brevis.one API instance. The API can be addressed with the following: https://<SMS Gateway IP>/api.php
username - Brevis.one API username.
password - user's password.

3. The following parameters can help you customize the alerts: *ring, flash, telauto
See Brevis.one documentation for details.

4. Create a service Zabbix user or use any existing user, then add Media with the Brevis.one. The "Send to" field should be filled as a phone number without a plus (+) sign or as "mode:option".
Allowed modes: number (Default), group, telgroup, telnumber, user, teluser.
Examples: 37167784742 (Send SMS to the individual telephone number)
group:11 (Send a text message to the specified user group. User groups are managed in the Configuration - Groups.)
telnumber:37167784742 (Send a message via Automatic to the individual telephone number. Automatic tries to deliver the notification via Telegram. If this fails the notification will be delivered by a text message.)
See Brevis.one documentation for additional information.
Note, that the "Send to" field cannot be empty. If the phone number or user/group ID is already specified in the send_to parameter, you can put any symbol in this field to comply with frontend requirements. Make sure this user has access to all hosts, for which you would like problem notifications to be sent via Brevis.one HTTP API.

For more information see Zabbix and Brevis.one documentations.

Supported versions

Zabbix 6.0 and higher

Brevis.one webhook

This guide describes how to integrate Zabbix 5.4 installation with Brevis.one SMS Gateway using HTTP API and Zabbix webhook feature. This guide provides instructions on setting up a media type, a user, and an action in Zabbix.

Setting up Brevis.one

1. Create a user for HTTP API or use an existing one.

2. Grant to the user Access to the HTTP API permission. See Brevis.one documentation for the information.

Setting up the webhook in Zabbix

1. Before setting up a media type, you need to set up a global macro "{$ZABBIX.URL}", which must contain the URL to Zabbix frontend.

2. In the Administration > Media types section, import media_brevis.one.xml.

3. Open the newly added Brevis.one media type and replace all <PLACEHOLDERS> with your values.
The following parameters should be filled out:
endpoint - the actual URL of your Brevis.one API instance. The API can be addressed with the following: https://<SMS Gateway IP>/api.php
username - Brevis.one API username.
password - user's password.

3. The following parameters can help you customize the alerts: *ring, flash, telauto
See Brevis.one documentation for details.

4. Create a service Zabbix user or use any existing user, then add Media with the Brevis.one. The "Send to" field should be filled as a phone number without a plus (+) sign or as "mode:option".
Allowed modes: number (Default), group, telgroup, telnumber, user, teluser.
Examples: 37167784742 (Send SMS to the individual telephone number)
group:11 (Send a text message to the specified user group. User groups are managed in the Configuration - Groups.)
telnumber:37167784742 (Send a message via Automatic to the individual telephone number. Automatic tries to deliver the notification via Telegram. If this fails the notification will be delivered by a text message.)
See Brevis.one documentation for additional information.
Note, that the "Send to" field cannot be empty. If the phone number or user/group ID is already specified in the send_to parameter, you can put any symbol in this field to comply with frontend requirements. Make sure this user has access to all hosts, for which you would like problem notifications to be sent via Brevis.one HTTP API.

For more information see Zabbix and Brevis.one documentations.

Supported versions

Zabbix 5.4 and higher

Brevis.one webhook

This guide describes how to integrate Zabbix 5.0 installation with Brevis.one SMS Gateway using HTTP API and Zabbix webhook feature. This guide provides instructions on setting up a media type, a user, and an action in Zabbix.

Setting up Brevis.one

1. Create a user for HTTP API or use an existing one.

2. Grant to the user Access to the HTTP API permission. See Brevis.one documentation for the information.

Setting up the webhook in Zabbix

1. Before setting up a media type, you need to set up a global macro "{$ZABBIX.URL}", which must contain the URL to Zabbix frontend.

2. In the Administration > Media types section, import media_brevis.one.xml.

3. Open the newly added Brevis.one media type and replace all <PLACEHOLDERS> with your values.
The following parameters should be filled out:
endpoint - the actual URL of your Brevis.one API instance. The API can be addressed with the following: https://<SMS Gateway IP>/api.php
username - Brevis.one API username.
password - user's password.

3. The following parameters can help you customize the alerts: *ring, flash, telauto
See Brevis.one documentation for details.

4. Create a service Zabbix user or use any existing user, then add Media with the Brevis.one. The "Send to" field should be filled as a phone number without a plus (+) sign or as "mode:option".
Allowed modes: number (Default), group, telgroup, telnumber, user, teluser.
Examples: 37167784742 (Send SMS to the individual telephone number)
group:11 (Send a text message to the specified user group. User groups are managed in the Configuration - Groups.)
telnumber:37167784742 (Send a message via Automatic to the individual telephone number. Automatic tries to deliver the notification via Telegram. If this fails the notification will be delivered by a text message.)
See Brevis.one documentation for additional information.
Note, that the "Send to" field cannot be empty. If the phone number or user/group ID is already specified in the send_to parameter, you can put any symbol in this field to comply with frontend requirements. Make sure this user has access to all hosts, for which you would like problem notifications to be sent via Brevis.one HTTP API.

For more information see Zabbix and Brevis.one documentations.

Supported versions

Zabbix 5.0 and higher