From a7c4872bcdfb11d62732bcdd663aece33f3eac1a Mon Sep 17 00:00:00 2001 From: Andre Miras Date: Mon, 30 Jan 2023 19:23:33 +0100 Subject: [PATCH] Alerting: Clarify PagerDuty integrationKey format (#62463) **What is this feature?** Simply a documentation update. **Why do we need this feature?** Clarify the doc, so people don't waste time integrating the wrong key, e.g. #8979, #9036, https://community.librenms.org/t/19013 **Who is this feature for?** Developers doing a PagerDuty integration. --- .../provision-alerting-resources/file-provisioning/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/sources/alerting/set-up/provision-alerting-resources/file-provisioning/index.md b/docs/sources/alerting/set-up/provision-alerting-resources/file-provisioning/index.md index 82b1c05ae20..71e7f73b46d 100644 --- a/docs/sources/alerting/set-up/provision-alerting-resources/file-provisioning/index.md +++ b/docs/sources/alerting/set-up/provision-alerting-resources/file-provisioning/index.md @@ -313,7 +313,7 @@ settings: ```yaml type: pagerduty settings: - # + # the 32-character Events API key https://support.pagerduty.com/docs/api-access-keys#events-api-keys integrationKey: XXX # options: critical, error, warning, info severity: critical