Skip to content

Commit 1af35cb

Browse files
Describe required permissions for PagerDuty token (#91)
Co-authored-by: Mano Toth <[email protected]>
1 parent 67c36a1 commit 1af35cb

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

monitor-data/monitors.mdx

+5-3
Original file line numberDiff line numberDiff line change
@@ -116,9 +116,11 @@ For more information on creating an incoming webhook in Slack, see the [Slack do
116116

117117
Create a PagerDuty notifier to use all the incident management features of PagerDuty with Axiom.
118118

119-
To configure a new “Service” in PagerDuty using the Events V2 API, go to **Configuration** > **Services** > **Add New Service** and create a new Service named ‘Axiom’ with all the default settings. Take note of the Integration Key provided and enter this when creating a PagerDuty notifier in Axiom.
120-
121-
You will also need to provide an API Access Key with the right permissions which can be generated at **pagerduty.com/api_keys**.
119+
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](https://support.pagerduty.com/main/docs/services-and-integrations#create-a-service)
120+
1. In Axiom, go to the Monitors tab.
121+
1. Click **Manage notifiers**, and then click **New notifier**.
122+
1. Click **PagerDuty**, and then enter the integration key.
123+
1. Click **Create**.
122124

123125
### Custom webhook
124126

0 commit comments

Comments
 (0)