PagerDuty webhook

Overview

This guide describes how to integrate your Zabbix installation with PagerDuty using the Zabbix webhook feature, providing instructions on setting up a media type, user, and action in Zabbix.

Why PagerDuty + Zabbix

• Notify on-call responders based on alerts sent from Zabbix.
• Send enriched event data from Zabbix, including operational data triggered during the event.
• Create high- and low-urgency incidents based on the severity of the event from Zabbix.
• Problem updates are synchronized to PagerDuty from Zabbix.
• Incidents will automatically resolve in PagerDuty when the metric in Zabbix returns to normal.

How it works

• When a trigger fires, Zabbix sends an event to a service in PagerDuty. Events from Zabbix will trigger a new incident on the corresponding PagerDuty service or will be grouped as alerts into an existing incident.
• Once the trigger is resolved, a resolving event will be sent to the PagerDuty service to resolve the alert and the associated incident on that service.

Supported versions

PagerDuty integrations with Zabbix require an Events API v2 key. If you do not have permission to create an Event API v2 key, please reach out to an Admin or Account Owner within your organization to help you configure the integration.

Requirements

Zabbix version: 7.2 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

• From the PagerDuty Service menu, select Service Directory.

• On your Services page:

  • If you are creating a new service for your integration, click +New Service.

  

  • Set the name and description for the new service.

  

  • Assign an escalation policy (required).

  

  • Enable alert grouping.

  

  • In the Integrations section, select the Zabbix Webhook using the search field and click Create service.

  

• If you are adding your integration to an existing service, click the name of the service you want to add the integration to. Then click the Integrations tab and click the +Add an Integration button, select the Zabbix Webhook using the search field, and click Add.

  

• After successfully adding the integration, use its Integration Key in the token macros for the PagerDuty Zabbix media type.

  

Zabbix configuration

The configuration includes a media type in Zabbix that invokes a webhook to send alerts to PagerDuty through the PagerDuty Event API v2. To use this media type, we will create a Zabbix user to represent PagerDuty and set up an alert action to notify this user whenever a problem is detected.

Create global macro

1. In the Zabbix web interface, go to Administration > Macros.

2. Add the macro {$ZABBIX.URL} with Zabbix frontend URL (for example, http://192.168.7.123:8081).

3. Click the Update button to save.

Create the PagerDuty media type

1. In the Zabbix interface Alerts > Media types section, click the Import button.

2. Select the import file media_pagerduty.yaml and click the Import button at the bottom to import the PagerDuty media type.

Create the PagerDuty user for alerting

1. In the Zabbix interface, go to Users > Users and click the Create user button.

2. Assign the new user the username "PagerDuty User". The default settings should suffice as this user will not be logging into Zabbix.

3. Click the Select button next to Groups.

• Please note that in order to be able to notify on problems with host, this user must have at least read permissions for the respective host.

4. Click on the Media tab and, inside the Media box, click the Add button.

5. In the new window that appears, configure the media for the user as follows:

• For the Type, select PagerDuty (the new media type that was created).
• Specify the token as the user's Send to field.
• Make sure the Enabled box is checked.
• Click the Add button when done.

6. Click the Add button at the bottom of the user page to save the user.

7. Use the PagerDuty User in any actions of your choice.

For more information, please see the Zabbix and PagerDuty documentation.

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.

PagerDuty webhook

Overview

This guide describes how to integrate your Zabbix installation with PagerDuty using the Zabbix webhook feature, providing instructions on setting up a media type, user, and action in Zabbix.

Why PagerDuty + Zabbix

• Notify on-call responders based on alerts sent from Zabbix.
• Send enriched event data from Zabbix, including operational data triggered during the event.
• Create high- and low-urgency incidents based on the severity of the event from Zabbix.
• Problem updates are synchronized to PagerDuty from Zabbix.
• Incidents will automatically resolve in PagerDuty when the metric in Zabbix returns to normal.

How it works

• When a trigger fires, Zabbix sends an event to a service in PagerDuty. Events from Zabbix will trigger a new incident on the corresponding PagerDuty service or will be grouped as alerts into an existing incident.
• Once the trigger is resolved, a resolving event will be sent to the PagerDuty service to resolve the alert and the associated incident on that service.

Supported versions

PagerDuty integrations with Zabbix require an Events API v2 key. If you do not have permission to create an Event API v2 key, please reach out to an Admin or Account Owner within your organization to help you configure the integration.

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

• From the PagerDuty Service menu, select Service Directory.

• On your Services page:

  • If you are creating a new service for your integration, click +New Service.

  

  • Set the name and description for the new service.

  

  • Assign an escalation policy (required).

  

  • Enable alert grouping.

  

  • In the Integrations section, select the Zabbix Webhook using the search field and click Create service.

  

• If you are adding your integration to an existing service, click the name of the service you want to add the integration to. Then click the Integrations tab and click the +Add an Integration button, select the Zabbix Webhook using the search field, and click Add.

  

• After successfully adding the integration, use its Integration Key in the token macros for the PagerDuty Zabbix media type.

  

Zabbix configuration

The configuration includes a media type in Zabbix that invokes a webhook to send alerts to PagerDuty through the PagerDuty Event API v2. To use this media type, we will create a Zabbix user to represent PagerDuty and set up an alert action to notify this user whenever a problem is detected.

Create global macro

1. In the Zabbix web interface, go to Administration > Macros.

2. Add the macro {$ZABBIX.URL} with Zabbix frontend URL (for example, http://192.168.7.123:8081).

3. Click the Update button to save.

Create the PagerDuty media type

1. In the Zabbix interface Alerts > Media types section, click the Import button.

2. Select the import file media_pagerduty.yaml and click the Import button at the bottom to import the PagerDuty media type.

Create the PagerDuty user for alerting

1. In the Zabbix interface, go to Users > Users and click the Create user button.

2. Assign the new user the username "PagerDuty User". The default settings should suffice as this user will not be logging into Zabbix.

3. Click the Select button next to Groups.

• Please note that in order to be able to notify on problems with host, this user must have at least read permissions for the respective host.

4. Click on the Media tab and, inside the Media box, click the Add button.

5. In the new window that appears, configure the media for the user as follows:

• For the Type, select PagerDuty (the new media type that was created).
• Specify the token as the user's Send to field.
• Make sure the Enabled box is checked.
• Click the Add button when done.

6. Click the Add button at the bottom of the user page to save the user.

7. Use the PagerDuty User in any actions of your choice.

For more information, please see the Zabbix and PagerDuty documentation.

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.

PagerDuty + Zabbix Integration Benefits

• Notify on-call responders based on alerts sent from Zabbix.
• Send enriched event data from Zabbix including operational data that was triggered during event.
• Create high and low urgency incidents based on the severity of event from Zabbix.
• Problem updates are synchronised to PagerDuty from Zabbix.
• Incidents will automatically resolve in PagerDuty when the metric in Zabbix returns to normal.

How it Works

• If a trigger fires, Zabbix will send an event to a service in PagerDuty. Events from Zabbix will trigger a new incident on the corresponding PagerDuty service or group as alerts into an existing incident.
• Once the trigger is resolved, a resolving event will be sent to the PagerDuty service to resolve the alert and associated incident on that service.

Requirements

1. PagerDuty integrations with Zabbix require Events API v2 key. If you do not have permission to create Event API v2 key, please reach out to an Admin or Account Owner within your organization to help you configure the integration.
2. PagerDuty webhook integration works with Zabbix version 6.2 or higher.

Support

• If you need help use forum
• If you have encountered a bug, please report it using Zabbix Jira bug tracker.

Description

This guide describes how to integrate your Zabbix 6.2 installation with PagerDuty using the Zabbix webhook feature. This guide will provide instructions on setting up a media type, a user and an action in Zabbix.

In PagerDuty

• From the Service menu, select Service Directory.

• On your Services page:

  • If you are creating a new service for your integration, click +New Service.

  

  • Set name and description for new service.

  

  • Assign required an Escalation Policy.

  

  • Select Alert Grouping.

  

  • In integration section select Zabbix Webhook using search field and click Create service.

  

• If you are adding your integration to an existing service, click the name of the service you want to add the integration to. Then click the Integrations tab and click the +Add an Integration button, select Zabbix Webhook using search field and click Add.

  

• After successfully added integration use Integration Key from it in token macros for PagerDuty zabbix media type.

  

In Zabbix

The configuration consists of a media type in Zabbix, which will invoke webhook to send alerts to PagerDuty through the PagerDuty Event API v2. To utilize the media type, we will create a Zabbix user to represent PagerDuty. We will then create an alert action to notify the user via this media type whenever there is a problem detected.

Create Global Macro

1. Go to the Administration tab.

2. Under Administration, go to the General page and choose the Macros from drop-down list.

3. Add the macro {$ZABBIX.URL} with Zabbix frontend URL (for example http://192.168.7.123:8081).

4. Click the Update button to save the global macros.

Create the PagerDuty media type

1. Go to the Administration tab.

2. Under Administration, go to the Media types page and click the Import button.

3. Select Import file media_pagerduty.yaml and click the Import button at the bottom to import the PagerDuty media type.

4. Change the value of the variable token

Create the PagerDuty user for alerting

1. Go to the Administration tab.

2. Under Administration, go to the Users page and click the Create user button.

3. Fill in the details of this new user, and call it “PagerDuty User”. The default settings for PagerDuty User should suffice as this user will not be logging into Zabbix.

4. Click the Select button next to Groups.

• Please note, that in order to notify on problems with host this user must have at least read permissions for such host.

5. Click on the Media tab and, inside of the Media box, click the Add button.

6. In the new window that appears, configure the media for the user as follows:

• For the Type, select PagerDuty (the new media type that was created).
• For Send to: enter any text, as this value is not used, but is required.
• Make sure the Enabled box is checked.
• Click the Add button when done.

7. Click the Add button at the bottom of the user page to save the user.

8. Use the PagerDuty User in any Actions of your choice.

For more information, use the Zabbix and PagerDuty documentations.

Supported Versions

Zabbix 6.2, PagerDuty Events API v2.

PagerDuty + Zabbix Integration Benefits

• Notify on-call responders based on alerts sent from Zabbix.
• Send enriched event data from Zabbix including operational data that was triggered during event.
• Create high and low urgency incidents based on the severity of event from Zabbix.
• Problem updates are synchronised to PagerDuty from Zabbix.
• Incidents will automatically resolve in PagerDuty when the metric in Zabbix returns to normal.

How it Works

• If a trigger fires, Zabbix will send an event to a service in PagerDuty. Events from Zabbix will trigger a new incident on the corresponding PagerDuty service or group as alerts into an existing incident.
• Once the trigger is resolved, a resolving event will be sent to the PagerDuty service to resolve the alert and associated incident on that service.

Requirements

1. PagerDuty integrations with Zabbix require Events API v2 key. If you do not have permission to create Event API v2 key, please reach out to an Admin or Account Owner within your organization to help you configure the integration.
2. PagerDuty webhook integration works with Zabbix version 6.2 or higher.

Support

• If you need help use forum
• If you have encountered a bug, please report it using Zabbix Jira bug tracker.

Description

This guide describes how to integrate your Zabbix 6.2 installation with PagerDuty using the Zabbix webhook feature. This guide will provide instructions on setting up a media type, a user and an action in Zabbix.

In PagerDuty

• From the Service menu, select Service Directory.

• On your Services page:

  • If you are creating a new service for your integration, click +New Service.

  

  • Set name and description for new service.

  

  • Assign required an Escalation Policy.

  

  • Select Alert Grouping.

  

  • In integration section select Zabbix Webhook using search field and click Create service.

  

• If you are adding your integration to an existing service, click the name of the service you want to add the integration to. Then click the Integrations tab and click the +Add an Integration button, select Zabbix Webhook using search field and click Add.

  

• After successfully added integration use Integration Key from it in token macros for PagerDuty zabbix media type.

  

In Zabbix

The configuration consists of a media type in Zabbix, which will invoke webhook to send alerts to PagerDuty through the PagerDuty Event API v2. To utilize the media type, we will create a Zabbix user to represent PagerDuty. We will then create an alert action to notify the user via this media type whenever there is a problem detected.

Create Global Macro

1. Go to the Administration tab.

2. Under Administration, go to the General page and choose the Macros from drop-down list.

3. Add the macro {$ZABBIX.URL} with Zabbix frontend URL (for example http://192.168.7.123:8081).

4. Click the Update button to save the global macros.

Create the PagerDuty media type

1. Go to the Administration tab.

2. Under Administration, go to the Media types page and click the Import button.

3. Select Import file media_pagerduty.yaml and click the Import button at the bottom to import the PagerDuty media type.

4. Change the value of the variable token

Create the PagerDuty user for alerting

1. Go to the Administration tab.

2. Under Administration, go to the Users page and click the Create user button.

3. Fill in the details of this new user, and call it “PagerDuty User”. The default settings for PagerDuty User should suffice as this user will not be logging into Zabbix.

4. Click the Select button next to Groups.

• Please note, that in order to notify on problems with host this user must have at least read permissions for such host.

5. Click on the Media tab and, inside of the Media box, click the Add button.

6. In the new window that appears, configure the media for the user as follows:

• For the Type, select PagerDuty (the new media type that was created).
• For Send to: enter any text, as this value is not used, but is required.
• Make sure the Enabled box is checked.
• Click the Add button when done.

7. Click the Add button at the bottom of the user page to save the user.

8. Use the PagerDuty User in any Actions of your choice.

For more information, use the Zabbix and PagerDuty documentations.

Supported Versions

Zabbix 6.2, PagerDuty Events API v2.

PagerDuty + Zabbix Integration Benefits

• Notify on-call responders based on alerts sent from Zabbix.
• Send enriched event data from Zabbix including operational data that was triggered during event.
• Create high and low urgency incidents based on the severity of event from Zabbix.
• Problem updates are synchronised to PagerDuty from Zabbix.
• Incidents will automatically resolve in PagerDuty when the metric in Zabbix returns to normal.

How it Works

• If a trigger fires, Zabbix will send an event to a service in PagerDuty. Events from Zabbix will trigger a new incident on the corresponding PagerDuty service or group as alerts into an existing incident.
• Once the trigger is resolved, a resolving event will be sent to the PagerDuty service to resolve the alert and associated incident on that service.

Requirements

1. PagerDuty integrations with Zabbix require Events API v2 key. If you do not have permission to create Event API v2 key, please reach out to an Admin or Account Owner within your organization to help you configure the integration.
2. PagerDuty webhook integration works with Zabbix version 6.0 or higher.

Support

• If you need help use forum
• If you have encountered a bug, please report it using Zabbix Jira bug tracker.

Description

This guide describes how to integrate your Zabbix 6.0 installation with PagerDuty using the Zabbix webhook feature. This guide will provide instructions on setting up a media type, a user and an action in Zabbix.

In PagerDuty

• From the Service menu, select Service Directory.

• On your Services page:

  • If you are creating a new service for your integration, click +New Service.

  

  • Set name and description for new service.

  

  • Assign required an Escalation Policy.

  

  • Select Alert Grouping.

  

  • In integration section select Zabbix Webhook using search field and click Create service.

  

• If you are adding your integration to an existing service, click the name of the service you want to add the integration to. Then click the Integrations tab and click the +Add an Integration button, select Zabbix Webhook using search field and click Add.

  

• After successfully added integration use Integration Key from it in token macros for PagerDuty zabbix media type.

  

In Zabbix

The configuration consists of a media type in Zabbix, which will invoke webhook to send alerts to PagerDuty through the PagerDuty Event API v2. To utilize the media type, we will create a Zabbix user to represent PagerDuty. We will then create an alert action to notify the user via this media type whenever there is a problem detected.

Create Global Macro

1. Go to the Administration tab.

2. Under Administration, go to the General page and choose the Macros from drop-down list.

3. Add the macro {$ZABBIX.URL} with Zabbix frontend URL (for example http://192.168.7.123:8081).

4. Click the Update button to save the global macros.

Create the PagerDuty media type

1. Go to the Administration tab.

2. Under Administration, go to the Media types page and click the Import button.

3. Select Import file media_pagerduty.yaml and click the Import button at the bottom to import the PagerDuty media type.

4. Change the value of the variable token

Create the PagerDuty user for alerting

1. Go to the Administration tab.

2. Under Administration, go to the Users page and click the Create user button.

3. Fill in the details of this new user, and call it “PagerDuty User”. The default settings for PagerDuty User should suffice as this user will not be logging into Zabbix.

4. Click the Select button next to Groups.

• Please note, that in order to notify on problems with host this user must have at least read permissions for such host.

5. Click on the Media tab and, inside of the Media box, click the Add button.

6. In the new window that appears, configure the media for the user as follows:

• For the Type, select PagerDuty (the new media type that was created).
• For Send to: enter any text, as this value is not used, but is required.
• Make sure the Enabled box is checked.
• Click the Add button when done.

7. Click the Add button at the bottom of the user page to save the user.

8. Use the PagerDuty User in any Actions of your choice.

For more information, use the Zabbix and PagerDuty documentations.

Supported Versions

Zabbix 6.0, PagerDuty Events API v2.

PagerDuty + Zabbix Integration Benefits

• Notify on-call responders based on alerts sent from Zabbix.
• Send enriched event data from Zabbix including operational data that was triggered during event.
• Create high and low urgency incidents based on the severity of event from Zabbix.
• Problem updates are synchronised to PagerDuty from Zabbix.
• Incidents will automatically resolve in PagerDuty when the metric in Zabbix returns to normal.

How it Works

• If a trigger fires, Zabbix will send an event to a service in PagerDuty. Events from Zabbix will trigger a new incident on the corresponding PagerDuty service or group as alerts into an existing incident.
• Once the trigger is resolved, a resolving event will be sent to the PagerDuty service to resolve the alert and associated incident on that service.

Requirements

1. PagerDuty integrations with Zabbix require Events API v2 key. If you do not have permission to create Event API v2 key, please reach out to an Admin or Account Owner within your organization to help you configure the integration.
2. PagerDuty webhook integration works with Zabbix version 5.4 or higher.

Support

• If you need help use forum
• If you have encountered a bug, please report it using Zabbix Jira bug tracker.

Description

This guide describes how to integrate your Zabbix 5.4 installation with PagerDuty using the Zabbix webhook feature. This guide will provide instructions on setting up a media type, a user and an action in Zabbix.

In PagerDuty

• From the Service menu, select Service Directory.

• On your Services page:

  • If you are creating a new service for your integration, click +New Service.

  

  • Set name and description for new service.

  

  • Assign required an Escalation Policy.

  

  • Select Alert Grouping.

  

  • In integration section select Zabbix Webhook using search field and click Create service.

  

• If you are adding your integration to an existing service, click the name of the service you want to add the integration to. Then click the Integrations tab and click the +Add an Integration button, select Zabbix Webhook using search field and click Add.

  

• After successfully added integration use Integration Key from it in token macros for PagerDuty zabbix media type.

  

In Zabbix

The configuration consists of a media type in Zabbix, which will invoke webhook to send alerts to PagerDuty through the PagerDuty Event API v2. To utilize the media type, we will create a Zabbix user to represent PagerDuty. We will then create an alert action to notify the user via this media type whenever there is a problem detected.

Create Global Macro

1. Go to the Administration tab.

2. Under Administration, go to the General page and choose the Macros from drop-down list.

3. Add the macro {$ZABBIX.URL} with Zabbix frontend URL (for example http://192.168.7.123:8081).

4. Click the Update button to save the global macros.

Create the PagerDuty media type

1. Go to the Administration tab.

2. Under Administration, go to the Media types page and click the Import button.

3. Select Import file media_pagerduty.yaml and click the Import button at the bottom to import the PagerDuty media type.

4. Change the value of the variable token

Create the PagerDuty user for alerting

1. Go to the Administration tab.

2. Under Administration, go to the Users page and click the Create user button.

3. Fill in the details of this new user, and call it “PagerDuty User”. The default settings for PagerDuty User should suffice as this user will not be logging into Zabbix.

4. Click the Select button next to Groups.

• Please note, that in order to notify on problems with host this user must has at least read permissions for such host.

5. Click on the Media tab and, inside of the Media box, click the Add button.

6. In the new window that appears, configure the media for the user as follows:

• For the Type, select PagerDuty (the new media type that was created).
• For Send to: enter any text, as this value is not used, but is required.
• Make sure the Enabled box is checked.
• Click the Add button when done.

7. Click the Add button at the bottom of the user page to save the user.

8. Use the PagerDuty User in any Actions of your choice.

For more information, use the Zabbix and PagerDuty documentations.

Supported Versions

Zabbix 5.4, PagerDuty Events API v2.

PagerDuty + Zabbix Integration Benefits

• Notify on-call responders based on alerts sent from Zabbix.
• Send enriched event data from Zabbix including operational data that was triggered during event.
• Create high and low urgency incidents based on the severity of event from Zabbix.
• Problem updates are synchronised to PagerDuty from Zabbix.
• Incidents will automatically resolve in PagerDuty when the metric in Zabbix returns to normal.

How it Works

• If a trigger fires, Zabbix will send an event to a service in PagerDuty. Events from Zabbix will trigger a new incident on the corresponding PagerDuty service or group as alerts into an existing incident.
• Once the trigger is resolved, a resolving event will be sent to the PagerDuty service to resolve the alert and associated incident on that service.

Requirements

1. PagerDuty integrations with Zabbix require Events API v2 key. If you do not have permission to create Event API v2 key, please reach out to an Admin or Account Owner within your organization to help you configure the integration.
2. PagerDuty webhook integration works with Zabbix version 5.0 or higher.

Support

• If you need help use forum
• If you have encountered a bug, please report it using Zabbix Jira bug tracker.

Description

This guide describes how to integrate your Zabbix 5.0 installation with PagerDuty using the Zabbix webhook feature. This guide will provide instructions on setting up a media type, a user and an action in Zabbix.

In PagerDuty

• From the Service menu, select Service Directory.

• On your Services page:

  • If you are creating a new service for your integration, click +New Service.

  

  • Set name and description for new service.

  

  • Assign required an Escalation Policy.

  

  • Select Alert Grouping.

  

  • In integration section select Zabbix Webhook using search field and click Create service.

  

• If you are adding your integration to an existing service, click the name of the service you want to add the integration to. Then click the Integrations tab and click the +Add an Integration button, select Zabbix Webhook using search field and click Add.

  

• After successfully added integration use Integration Key from it in token macros for PagerDuty zabbix media type.

  

In Zabbix

The configuration consists of a media type in Zabbix, which will invoke webhook to send alerts to PagerDuty through the PagerDuty Event API v2. To utilize the media type, we will create a Zabbix user to represent PagerDuty. We will then create an alert action to notify the user via this media type whenever there is a problem detected.

Create Global Macro

1. Go to the Administration tab.

2. Under Administration, go to the General page and choose the Macros from drop-down list.

3. Add the macro {$ZABBIX.URL} with Zabbix frontend URL (for example http://192.168.7.123:8081).

4. Click the Update button to save the global macros.

Create the PagerDuty media type

1. Go to the Administration tab.

2. Under Administration, go to the Media types page and click the Import button.

3. Select Import file media_pagerduty.xml and click the Import button at the bottom to import the PagerDuty media type.

4. Change the value of the variable token

Create the PagerDuty user for alerting

1. Go to the Administration tab.

2. Under Administration, go to the Users page and click the Create user button.

3. Fill in the details of this new user, and call it “PagerDuty User”. The default settings for PagerDuty User should suffice as this user will not be logging into Zabbix.

4. Click the Select button next to Groups.

• Please note, that in order to notify on problems with host this user must have at least read permissions for such host.

5. Click on the Media tab and, inside of the Media box, click the Add button.

6. In the new window that appears, configure the media for the user as follows:

• For the Type, select PagerDuty (the new media type that was created).
• For Send to: enter any text, as this value is not used, but is required.
• Make sure the Enabled box is checked.
• Click the Add button when done.

7. Click the Add button at the bottom of the user page to save the user.

8. Use the PagerDuty User in any Actions of your choice.

For more information, use the Zabbix and PagerDuty documentations.

Supported Versions

Zabbix 5.0, PagerDuty Events API v2.