This template is for Áú»¢¶Ä²© version: 7.2
Source:
Brevis.one webhook
This guide describes how to integrate Áú»¢¶Ä²© 7.0 installation with Brevis.one SMS Gateway using HTTP API and Áú»¢¶Ä²© webhook feature. This guide provides instructions on setting up a media type, a user, and an action in Áú»¢¶Ä²©.
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 for the information.
Setting up the webhook in Áú»¢¶Ä²©
1. Before setting up a media type, you need to set up a global macro "{$ZABBIX.URL}", which must contain the URL to Áú»¢¶Ä²© frontend.
2. In the Administration > Media types section, import .
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 for details.
4. Create a service Áú»¢¶Ä²© 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 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 Áú»¢¶Ä²© and documentations.
Supported versions
Áú»¢¶Ä²© 7.0 and higher
This template is for Áú»¢¶Ä²© version: 7.0
Source:
Brevis.one webhook
This guide describes how to integrate Áú»¢¶Ä²© 7.0 installation with Brevis.one SMS Gateway using HTTP API and Áú»¢¶Ä²© webhook feature. This guide provides instructions on setting up a media type, a user, and an action in Áú»¢¶Ä²©.
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 for the information.
Setting up the webhook in Áú»¢¶Ä²©
1. Before setting up a media type, you need to set up a global macro "{$ZABBIX.URL}", which must contain the URL to Áú»¢¶Ä²© frontend.
2. In the Administration > Media types section, import .
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 for details.
4. Create a service Áú»¢¶Ä²© 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 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 Áú»¢¶Ä²© and documentations.
Supported versions
Áú»¢¶Ä²© 7.0 and higher
This template is for Áú»¢¶Ä²© version: 6.4
Source:
Brevis.one webhook
This guide describes how to integrate Áú»¢¶Ä²© 6.2 installation with Brevis.one SMS Gateway using HTTP API and Áú»¢¶Ä²© webhook feature. This guide provides instructions on setting up a media type, a user, and an action in Áú»¢¶Ä²©.
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 for the information.
Setting up the webhook in Áú»¢¶Ä²©
1. Before setting up a media type, you need to set up a global macro "{$ZABBIX.URL}", which must contain the URL to Áú»¢¶Ä²© frontend.
2. In the Administration > Media types section, import .
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 for details.
4. Create a service Áú»¢¶Ä²© 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 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 Áú»¢¶Ä²© and documentations.
Supported versions
Áú»¢¶Ä²© 6.2 and higher
This template is for Áú»¢¶Ä²© version: 6.2
Source:
Brevis.one webhook
This guide describes how to integrate Áú»¢¶Ä²© 6.2 installation with Brevis.one SMS Gateway using HTTP API and Áú»¢¶Ä²© webhook feature. This guide provides instructions on setting up a media type, a user, and an action in Áú»¢¶Ä²©.
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 for the information.
Setting up the webhook in Áú»¢¶Ä²©
1. Before setting up a media type, you need to set up a global macro "{$ZABBIX.URL}", which must contain the URL to Áú»¢¶Ä²© frontend.
2. In the Administration > Media types section, import .
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 for details.
4. Create a service Áú»¢¶Ä²© 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 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 Áú»¢¶Ä²© and documentations.
Supported versions
Áú»¢¶Ä²© 6.2 and higher
This template is for Áú»¢¶Ä²© version: 6.0
Source:
Brevis.one webhook
This guide describes how to integrate Áú»¢¶Ä²© 6.0 installation with Brevis.one SMS Gateway using HTTP API and Áú»¢¶Ä²© webhook feature. This guide provides instructions on setting up a media type, a user, and an action in Áú»¢¶Ä²©.
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 for the information.
Setting up the webhook in Áú»¢¶Ä²©
1. Before setting up a media type, you need to set up a global macro "{$ZABBIX.URL}", which must contain the URL to Áú»¢¶Ä²© frontend.
2. In the Administration > Media types section, import .
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 for details.
4. Create a service Áú»¢¶Ä²© 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 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 Áú»¢¶Ä²© and documentations.
Supported versions
Áú»¢¶Ä²© 6.0 and higher
This template is for Áú»¢¶Ä²© version: 5.4
Source:
Brevis.one webhook
This guide describes how to integrate Áú»¢¶Ä²© 5.4 installation with Brevis.one SMS Gateway using HTTP API and Áú»¢¶Ä²© webhook feature. This guide provides instructions on setting up a media type, a user, and an action in Áú»¢¶Ä²©.
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 for the information.
Setting up the webhook in Áú»¢¶Ä²©
1. Before setting up a media type, you need to set up a global macro "{$ZABBIX.URL}", which must contain the URL to Áú»¢¶Ä²© frontend.
2. In the Administration > Media types section, import .
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 for details.
4. Create a service Áú»¢¶Ä²© 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 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 Áú»¢¶Ä²© and documentations.
Supported versions
Áú»¢¶Ä²© 5.4 and higher
This template is for Áú»¢¶Ä²© version: 5.0
Source:
Brevis.one webhook
This guide describes how to integrate Áú»¢¶Ä²© 5.0 installation with Brevis.one SMS Gateway using HTTP API and Áú»¢¶Ä²© webhook feature. This guide provides instructions on setting up a media type, a user, and an action in Áú»¢¶Ä²©.
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 for the information.
Setting up the webhook in Áú»¢¶Ä²©
1. Before setting up a media type, you need to set up a global macro "{$ZABBIX.URL}", which must contain the URL to Áú»¢¶Ä²© frontend.
2. In the Administration > Media types section, import .
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 for details.
4. Create a service Áú»¢¶Ä²© 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 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 Áú»¢¶Ä²© and documentations.
Supported versions
Áú»¢¶Ä²© 5.0 and higher
