Document new field on PagerDuty cloud integration (#17149)
Co-authored-by: Ilya Mashchenko <ilya@netdata.cloud>
Juan Cañete committed
Mar 12, 2024 at 10:56 UTC
70b49589947a97aeb954b2cb41068a04b6f0f16b
1 file changed
+2
-1
integrations/cloud-notifications/integrations/pagerduty.md
+2
-1
@@ -32,7 +32,7 @@ Steps to configure your PagerDuty to receive notifications from Netdata:
32
33
1. Create a service to receive events from your services directory page on PagerDuty
34
2. At step 3, select `Events API V2` Integration or **View Webhooks** if you already have some defined
35
-3. Once the service is created you will be redirected to its configuration page, where you can copy the **integration key**, that you will need need to add to your notification configuration on Netdata UI.
35
+3. Once the service is created, you will be redirected to its configuration page, where you can copy the **Integration Key** and **Integration URL (Alert Events)** fields to add them to your notification configuration in the Netdata UI.
36
37
### Netdata Configuration Steps
38
@@ -47,5 +47,6 @@ Steps to configure your PagerDuty to receive notifications from Netdata:
47
- Notification - you specify which notifications you want to be notified using this configuration: All Alerts and unreachable, All Alerts, Critical only
48
* **Integration configuration** are the specific notification integration required settings, which vary by notification method. For PagerDuty:
49
- Integration Key - is a 32 character key provided by PagerDuty to receive events on your service.
50
+ - Integration URL (Alert Events) - is the URL provided by PagerDuty where we will send notifications.
51
52