Regenerate integrations.js (#17446)
Co-authored-by: ilyam8 <22274335+ilyam8@users.noreply.github.com>
Netdata bot committed
Apr 19, 2024 at 09:35 UTC
19b73085fdf7705497d0001647b09e6a7afdaa96
3 files changed
+88
integrations/cloud-notifications/integrations/splunk_victorops.md
new
+46
@@ -0,0 +1,46 @@
1
+<!--startmeta
2
+custom_edit_url: "https://github.com/netdata/netdata/edit/master/integrations/cloud-notifications/integrations/splunk_victorops.md"
3
+meta_yaml: "https://github.com/netdata/netdata/edit/master/integrations/cloud-notifications/metadata.yaml"
4
+sidebar_label: "Splunk VictorOps"
5
+learn_status: "Published"
6
+learn_rel_path: "Alerts & Notifications/Notifications/Centralized Cloud Notifications"
7
+message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NOTIFICATION'S metadata.yaml FILE"
8
+endmeta-->
9
+
10
+# Splunk VictorOps
11
+
12
+
13
+<img src="https://netdata.cloud/img/victorops.svg" width="150"/>
14
+
15
+
16
+From the Cloud interface, you can manage your space's notification settings and from there you can add a specific configuration to get notifications delivered on Splunk On-Call/VictorOps.
17
+
18
+
19
+<img src="https://img.shields.io/badge/maintained%20by-Netdata-%2300ab44" />
20
+
21
+## Setup
22
+
23
+### Prerequisites
24
+
25
+To add Splunk VictorOps notification (also known as Splunk On-Call) you need:
26
+
27
+- A Netdata Cloud account
28
+- Access to the space as an **administrator**
29
+- Space needs to be on **Business** plan or higher
30
+- Destination URL for your Splunk VictorOps REST Endpoint Integration. Refer to the [VictorOps documentation](https://help.victorops.com/knowledge-base/rest-endpoint-integration-guide) for detailed instructions.
31
+
32
+### Steps
33
+
34
+1. Click on the **Space settings** cog (located above your profile icon)
35
+2. Click on the **Notification** tab
36
+3. Click on the **+ Add configuration** button (near the top-right corner of your screen)
37
+4. On the **Splunk VictorOps** card click on **+ Add**
38
+5. A modal will be presented to you to enter the required details to enable the configuration:
39
+ - **Notification settings** are Netdata specific settings
40
+ - Configuration name - provide a descriptive name for your configuration to easily identify it.
41
+ - Rooms - select the nodes or areas of your infrastructure you want to receive notifications about.
42
+ - Notification - choose the type of notifications you want to receive: All Alerts and unreachable, All Alerts, Critical only.
43
+ - **Integration configuration** are the specific notification integration required settings, which vary by notification method. For Splunk VictorOps:
44
+ - Destination URL - The URL provided by VictorOps of your REST endpoint.
45
+
46
+
integrations/integrations.js
+21
@@ -21741,6 +21741,27 @@ export const integrations = [
21741
"edit_link": "https://github.com/netdata/netdata/blob/master/integrations/cloud-notifications/metadata.yaml",
21742
"troubleshooting": ""
21743
},
21744
+ {
21745
+ "id": "notify-cloud-victorops",
21746
+ "meta": {
21747
+ "name": "Splunk VictorOps",
21748
+ "link": "https://www.splunk.com/en_us/about-splunk/acquisitions/splunk-on-call.html",
21749
+ "categories": [
21750
+ "notify.cloud"
21751
+ ],
21752
+ "icon_filename": "victorops.svg"
21753
+ },
21754
+ "keywords": [
21755
+ "VictorOps",
21756
+ "Splunk",
21757
+ "On-Call"
21758
+ ],
21759
+ "overview": "# Splunk VictorOps\n\nFrom the Cloud interface, you can manage your space's notification settings and from there you can add a specific configuration to get notifications delivered on Splunk On-Call/VictorOps.\n",
21760
+ "setup": "## Setup\n\n### Prerequisites\n\nTo add Splunk VictorOps notification (also known as Splunk On-Call) you need:\n\n- A Netdata Cloud account\n- Access to the space as an **administrator**\n- Space needs to be on **Business** plan or higher\n- Destination URL for your Splunk VictorOps REST Endpoint Integration. Refer to the [VictorOps documentation](https://help.victorops.com/knowledge-base/rest-endpoint-integration-guide) for detailed instructions.\n\n### Steps\n\n1. Click on the **Space settings** cog (located above your profile icon)\n2. Click on the **Notification** tab\n3. Click on the **+ Add configuration** button (near the top-right corner of your screen)\n4. On the **Splunk VictorOps** card click on **+ Add**\n5. A modal will be presented to you to enter the required details to enable the configuration:\n - **Notification settings** are Netdata specific settings\n - Configuration name - provide a descriptive name for your configuration to easily identify it.\n - Rooms - select the nodes or areas of your infrastructure you want to receive notifications about.\n - Notification - choose the type of notifications you want to receive: All Alerts and unreachable, All Alerts, Critical only.\n - **Integration configuration** are the specific notification integration required settings, which vary by notification method. For Splunk VictorOps:\n - Destination URL - The URL provided by VictorOps of your REST endpoint.\n\n",
21761
+ "integration_type": "notification",
21762
+ "edit_link": "https://github.com/netdata/netdata/blob/master/integrations/cloud-notifications/metadata.yaml",
21763
+ "troubleshooting": ""
21764
+ },
21765
{
21766
"id": "notify-cloud-webhook",
21767
"meta": {
integrations/integrations.json
+21
@@ -21739,6 +21739,27 @@
21739
"edit_link": "https://github.com/netdata/netdata/blob/master/integrations/cloud-notifications/metadata.yaml",
21740
"troubleshooting": ""
21741
},
21742
+ {
21743
+ "id": "notify-cloud-victorops",
21744
+ "meta": {
21745
+ "name": "Splunk VictorOps",
21746
+ "link": "https://www.splunk.com/en_us/about-splunk/acquisitions/splunk-on-call.html",
21747
+ "categories": [
21748
+ "notify.cloud"
21749
+ ],
21750
+ "icon_filename": "victorops.svg"
21751
+ },
21752
+ "keywords": [
21753
+ "VictorOps",
21754
+ "Splunk",
21755
+ "On-Call"
21756
+ ],
21757
+ "overview": "# Splunk VictorOps\n\nFrom the Cloud interface, you can manage your space's notification settings and from there you can add a specific configuration to get notifications delivered on Splunk On-Call/VictorOps.\n",
21758
+ "setup": "## Setup\n\n### Prerequisites\n\nTo add Splunk VictorOps notification (also known as Splunk On-Call) you need:\n\n- A Netdata Cloud account\n- Access to the space as an **administrator**\n- Space needs to be on **Business** plan or higher\n- Destination URL for your Splunk VictorOps REST Endpoint Integration. Refer to the [VictorOps documentation](https://help.victorops.com/knowledge-base/rest-endpoint-integration-guide) for detailed instructions.\n\n### Steps\n\n1. Click on the **Space settings** cog (located above your profile icon)\n2. Click on the **Notification** tab\n3. Click on the **+ Add configuration** button (near the top-right corner of your screen)\n4. On the **Splunk VictorOps** card click on **+ Add**\n5. A modal will be presented to you to enter the required details to enable the configuration:\n - **Notification settings** are Netdata specific settings\n - Configuration name - provide a descriptive name for your configuration to easily identify it.\n - Rooms - select the nodes or areas of your infrastructure you want to receive notifications about.\n - Notification - choose the type of notifications you want to receive: All Alerts and unreachable, All Alerts, Critical only.\n - **Integration configuration** are the specific notification integration required settings, which vary by notification method. For Splunk VictorOps:\n - Destination URL - The URL provided by VictorOps of your REST endpoint.\n\n",
21759
+ "integration_type": "notification",
21760
+ "edit_link": "https://github.com/netdata/netdata/blob/master/integrations/cloud-notifications/metadata.yaml",
21761
+ "troubleshooting": ""
21762
+ },
21763
{
21764
"id": "notify-cloud-webhook",
21765
"meta": {