diff options
| author | Ilya Mashchenko <ilya@netdata.cloud> | 2024-03-26 17:56:56 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-03-26 17:56:56 +0200 |
| commit | 55b5a9502927635d6ce4ec17bede7624dbf1aa82 (patch) | |
| tree | d26554417a2781148789fca58b6d010fef73ee12 /integrations | |
| parent | 4a8e31944c07d2cfce57baf0d157de2d894898d0 (diff) | |
docs: update pagerduty meta (#17264)
Diffstat (limited to 'integrations')
| -rw-r--r-- | integrations/cloud-notifications/metadata.yaml | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/integrations/cloud-notifications/metadata.yaml b/integrations/cloud-notifications/metadata.yaml index 4358b27473..f3d5a5dc95 100644 --- a/integrations/cloud-notifications/metadata.yaml +++ b/integrations/cloud-notifications/metadata.yaml @@ -101,7 +101,7 @@ 1. Create a service to receive events from your services directory page on PagerDuty 2. At step 3, select `Events API V2` Integration or **View Webhooks** if you already have some defined - 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. + 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. ### Netdata Configuration Steps @@ -116,6 +116,7 @@ - Notification - you specify which notifications you want to be notified using this configuration: All Alerts and unreachable, All Alerts, Critical only * **Integration configuration** are the specific notification integration required settings, which vary by notification method. For PagerDuty: - Integration Key - is a 32 character key provided by PagerDuty to receive events on your service. + - Integration URL (Alert Events) - is the URL provided by PagerDuty where we will send notifications. - id: 'notify-cloud-slack' meta: |