Adding upstream version 1.46.3.

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

1 files changed, 0 insertions, 73 deletions

diff --git a/health/notifications/pagerduty/metadata.yaml b/health/notifications/pagerduty/metadata.yaml
deleted file mode 100644
index 6fc1d640..00000000
--- a/health/notifications/pagerduty/metadata.yaml
+++ /dev/null
@@ -1,73 +0,0 @@
-# yamllint disable rule:line-length
----
-- id: 'notify-pagerduty'
-  meta:
-    name: 'PagerDuty'
-    link: 'https://www.pagerduty.com/'
-    categories:
-      - notify.agent
-    icon_filename: 'pagerduty.png'
-  keywords:
-    - PagerDuty
-  overview:
-    notification_description: |
-      PagerDuty is an enterprise incident resolution service that integrates with ITOps and DevOps monitoring stacks to improve operational reliability and agility. From enriching and aggregating events to correlating them into incidents, PagerDuty streamlines the incident management process by reducing alert noise and resolution times.
-      You can send notifications to PagerDuty using Netdata's Agent alert notification feature, which supports dozens of endpoints, user roles, and more.
-    notification_limitations: ''
-  setup:
-    prerequisites:
-      list:
-        - title: ''
-          description: |
-            - An installation of the [PagerDuty](https://www.pagerduty.com/docs/guides/agent-install-guide/) agent on the node running the Netdata Agent
-            - A PagerDuty Generic API service using either the `Events API v2` or `Events API v1`
-            - [Add a new service](https://support.pagerduty.com/docs/services-and-integrations#section-configuring-services-and-integrations) to PagerDuty. Click Use our API directly and select either `Events API v2` or `Events API v1`. Once you finish creating the service, click on the Integrations tab to find your Integration Key.
-            - Access to the terminal where Netdata Agent is running
-    configuration:
-      file:
-        name: 'health_alarm_notify.conf'
-      options:
-        description: 'The following options can be defined for this notification'
-        folding:
-          title: 'Config Options'
-          enabled: true
-        list:
-          - name: 'SEND_PD'
-            default_value: 'YES'
-            description: "Set `SEND_PD` to YES"
-            required: true
-          - name: 'DEFAULT_RECIPIENT_PD'
-            default_value: ''
-            description: "Set `DEFAULT_RECIPIENT_PD` to the PagerDuty service key you want the alert notifications to be sent to. You can define multiple service keys like this: `pd_service_key_1` `pd_service_key_2`."
-            required: true
-            detailed_description: |
-              All roles will default to this variable if left unconfigured.
-
-              The `DEFAULT_RECIPIENT_PD` can be edited in the following entries at the bottom of the same file:
-              ```conf
-              role_recipients_pd[sysadmin]="xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxa"
-              role_recipients_pd[domainadmin]="xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxb"
-              role_recipients_pd[dba]="xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxc"
-              role_recipients_pd[webmaster]="xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxd"
-              role_recipients_pd[proxyadmin]="xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxe"
-              role_recipients_pd[sitemgr]="xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxf"
-              ```
-      examples:
-        folding:
-          enabled: true
-          title: ''
-        list:
-          - name: 'Basic Configuration'
-            folding:
-              enabled: false
-            description: ''
-            config: |
-              #------------------------------------------------------------------------------
-              # pagerduty.com notification options
-
-              SEND_PD="YES"
-              DEFAULT_RECIPIENT_PD="xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
-              USE_PD_VERSION="2"
-  troubleshooting:
-    problems:
-      list: []