Connect Zabbix Monitoring with All Quiet
Integrate Zabbix with All Quiet in a matter of minutes. With webhooks, you can automatically send alerts from your Zabbix monitoring directly to All Quiet, streamlining your team’s incident management process.
Sign in to your All Quiet account.
Integrations > Inbound
tab.Create New Integration
.Zabbix
.Zabbix
as the integration’s type.Create Inbound Integration
.After creating the integration on All Quiet
Zabbix Media Type
file that you will need to upload in Zabbix in step 2. Download it.Once you’ve set up an integration of type “Zabbix” with All Quiet, the next crucial steps involve configuring a Zabbix user, connecting it with All Quiet via the Media Type and Webhook and adding it to the correct user group to be able to send alerts to All Quiet.
First, you need to sign in to your Zabbix Account.
We create a macro to always include the URL of the Zabbix alert in the related All Quiet incident.
Administration
Macros
Value
, enter your Zabbix frontend URL (https://…)Update
to save the macro.Now, we add the All Quiet Media Type.
Alerts
Media Types
Import
Import
You successfully added the media type.
Now, it’s time to create the All Quiet user.
Users
Users
Create User
Username
, e.g. “All Quiet” and create a password.Media
In Tab Media
, click add Media. This opens an overlay.
All Quiet
to use the Media Type we configured earlier.Add
.Afterwards, click Update
to create the user.
As said earlier, we need to ensure that the user has sufficient permissions in order to be able to forward incidents to All Quiet.
Permissions
tab.Read
permissions for the hosts that should be forwarded.If your user does not have these permissions, they can be changed on group level.
To update the permissions of your All Quiet user, edit the related user group(s).
Users > User groups
.Host Permissions
Read
and click Update
to save your changes.Now it’s time to create a trigger to connect Zabbix alerts with All Quiet, using the user we just created.
Alerts > Actions
Action
After giving your action a name,
Operations
and click Add
User Group
that you added the All Quiet user to earlierMedia Type
, select “All Quiet”.Add
.Repeat the steps from Operations
above for Recovery operations
(1) and Update operations
(2). Click Update
to save.
Looking to customize the fields of your incidents by adjusting the pre-built payload mapping? Simply head over to the “Payload” tab within your integration and make the necessary edits to the mapping. For detailed guidance, you may check out our payload mapping documentation.
allquiet_integration_mapping
resource for the Zabbix integration. Simply copy the syntax to your .tf file and tailor the resource to your team’s needs!Connect Zabbix Monitoring with All Quiet
Integrate Zabbix with All Quiet in a matter of minutes. With webhooks, you can automatically send alerts from your Zabbix monitoring directly to All Quiet, streamlining your team’s incident management process.
Sign in to your All Quiet account.
Integrations > Inbound
tab.Create New Integration
.Zabbix
.Zabbix
as the integration’s type.Create Inbound Integration
.After creating the integration on All Quiet
Zabbix Media Type
file that you will need to upload in Zabbix in step 2. Download it.Once you’ve set up an integration of type “Zabbix” with All Quiet, the next crucial steps involve configuring a Zabbix user, connecting it with All Quiet via the Media Type and Webhook and adding it to the correct user group to be able to send alerts to All Quiet.
First, you need to sign in to your Zabbix Account.
We create a macro to always include the URL of the Zabbix alert in the related All Quiet incident.
Administration
Macros
Value
, enter your Zabbix frontend URL (https://…)Update
to save the macro.Now, we add the All Quiet Media Type.
Alerts
Media Types
Import
Import
You successfully added the media type.
Now, it’s time to create the All Quiet user.
Users
Users
Create User
Username
, e.g. “All Quiet” and create a password.Media
In Tab Media
, click add Media. This opens an overlay.
All Quiet
to use the Media Type we configured earlier.Add
.Afterwards, click Update
to create the user.
As said earlier, we need to ensure that the user has sufficient permissions in order to be able to forward incidents to All Quiet.
Permissions
tab.Read
permissions for the hosts that should be forwarded.If your user does not have these permissions, they can be changed on group level.
To update the permissions of your All Quiet user, edit the related user group(s).
Users > User groups
.Host Permissions
Read
and click Update
to save your changes.Now it’s time to create a trigger to connect Zabbix alerts with All Quiet, using the user we just created.
Alerts > Actions
Action
After giving your action a name,
Operations
and click Add
User Group
that you added the All Quiet user to earlierMedia Type
, select “All Quiet”.Add
.Repeat the steps from Operations
above for Recovery operations
(1) and Update operations
(2). Click Update
to save.
Looking to customize the fields of your incidents by adjusting the pre-built payload mapping? Simply head over to the “Payload” tab within your integration and make the necessary edits to the mapping. For detailed guidance, you may check out our payload mapping documentation.
allquiet_integration_mapping
resource for the Zabbix integration. Simply copy the syntax to your .tf file and tailor the resource to your team’s needs!