Skip to main content
Use a PagerDuty notifier to use all the incident management features of PagerDuty with Axiom.

​
Benefits of using PagerDuty with Axiom

  • Increase the performance and availability of your apps and services.
  • Use specific insights in your backend, apps, and workloads by running PagerDuty in tandem with Axiom.
  • Detect critical issues before any disruption happens to your resources: Axiom automatically opens and closes PagerDuty incidents.
  • Obtain deep understanding of the issue root cause by visualising the data using Axiom.
Axiom creates PagerDuty events that arise from critical issues, disruptions, vulnerabilities, or workloads downtime on a service created in PagerDuty. The alert on Axiom side is linked to the PagerDuty Event allowing for Axiom to automatically close the Event incident if the Alert is resolved. This ensures no duplicate Events on PagerDuty side are created for the corresponding ones on Axiom side.

​
Prerequisites

​
Create PagerDuty notifier

To create a PagerDuty notifier, follow these steps:
  1. In PagerDuty’s Events V2 API, create a new service named Axiom with the default settings. Copy the integration key. For more information, see the PagerDuty documentation
  2. In Axiom, click the Monitors tab, and then click Manage notifiers on the right.
  3. Click New notifier on the top right.
  4. Name your notifier.
  5. Click Slack.
  6. Enter the integration key you have previously generated.
  7. Click Create.
You can now add your PagerDuty notifier to a specific monitor in Axiom. If any incident happens on your monitor, Axiom notifies you on the PagerDuty Service Activity dashboard.

​
Incident lifecycle

Axiom automatically opens and closes PagerDuty incidents based on your monitor state. This ensures that incidents in PagerDuty accurately reflect the current state of your system without manual intervention.
For automatic resolution, ensure the PagerDuty service accepts resolve events. Some PagerDuty services have settings that prevent automatic resolution. For more information, see the PagerDuty documentation.
When you configure a threshold monitor with a PagerDuty notifier in Axiom, the following happens:
  1. Incident creation: When your monitor enters the alarm state (the threshold condition is met), Axiom sends a trigger event to PagerDuty. This creates a new incident in PagerDuty with a unique deduplication key that links the incident to your specific monitor.
  2. Automatic resolution When your monitor returns to the OK state (the threshold condition is no longer met), Axiom automatically sends a resolve event to PagerDuty using the same deduplication key. This automatically resolves the open incident in PagerDuty.
The deduplication key ensures that if the same monitor triggers multiple times while already in an alarm state, PagerDuty doesn’t create duplicate incidents. All notifications for the same alarm are linked to the original incident.