diff options
author | Netdata bot <43409846+netdatabot@users.noreply.github.com> | 2024-04-19 09:35:45 +0300 |
---|---|---|
committer | GitHub <noreply@github.com> | 2024-04-19 09:35:45 +0300 |
commit | 19b73085fdf7705497d0001647b09e6a7afdaa96 (patch) | |
tree | db6ce14ba0e21bb49725cee807127cae57427d5b | |
parent | 7c93166cb3cd8b91bcbf7a94c4ed97ffcb061958 (diff) |
Regenerate integrations.js (#17446)
Co-authored-by: ilyam8 <22274335+ilyam8@users.noreply.github.com>
-rw-r--r-- | integrations/cloud-notifications/integrations/splunk_victorops.md | 46 | ||||
-rw-r--r-- | integrations/integrations.js | 21 | ||||
-rw-r--r-- | integrations/integrations.json | 21 |
3 files changed, 88 insertions, 0 deletions
diff --git a/integrations/cloud-notifications/integrations/splunk_victorops.md b/integrations/cloud-notifications/integrations/splunk_victorops.md new file mode 100644 index 0000000000..f44924f7c4 --- /dev/null +++ b/integrations/cloud-notifications/integrations/splunk_victorops.md @@ -0,0 +1,46 @@ +<!--startmeta +custom_edit_url: "https://github.com/netdata/netdata/edit/master/integrations/cloud-notifications/integrations/splunk_victorops.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/integrations/cloud-notifications/metadata.yaml" +sidebar_label: "Splunk VictorOps" +learn_status: "Published" +learn_rel_path: "Alerts & Notifications/Notifications/Centralized Cloud Notifications" +message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NOTIFICATION'S metadata.yaml FILE" +endmeta--> + +# Splunk VictorOps + + +<img src="https://netdata.cloud/img/victorops.svg" width="150"/> + + +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. + + +<img src="https://img.shields.io/badge/maintained%20by-Netdata-%2300ab44" /> + +## Setup + +### Prerequisites + +To add Splunk VictorOps notification (also known as Splunk On-Call) you need: + +- A Netdata Cloud account +- Access to the space as an **administrator** +- Space needs to be on **Business** plan or higher +- 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. + +### Steps + +1. Click on the **Space settings** cog (located above your profile icon) +2. Click on the **Notification** tab +3. Click on the **+ Add configuration** button (near the top-right corner of your screen) +4. On the **Splunk VictorOps** card click on **+ Add** +5. A modal will be presented to you to enter the required details to enable the configuration: + - **Notification settings** are Netdata specific settings + - Configuration name - provide a descriptive name for your configuration to easily identify it. + - Rooms - select the nodes or areas of your infrastructure you want to receive notifications about. + - Notification - choose the type of notifications you want to receive: All Alerts and unreachable, All Alerts, Critical only. + - **Integration configuration** are the specific notification integration required settings, which vary by notification method. For Splunk VictorOps: + - Destination URL - The URL provided by VictorOps of your REST endpoint. + + diff --git a/integrations/integrations.js b/integrations/integrations.js index f2d0628499..cddcabd59c 100644 --- a/integrations/integrations.js +++ b/integrations/integrations.js @@ -21742,6 +21742,27 @@ export const integrations = [ "troubleshooting": "" }, { + "id": "notify-cloud-victorops", + "meta": { + "name": "Splunk VictorOps", + "link": "https://www.splunk.com/en_us/about-splunk/acquisitions/splunk-on-call.html", + "categories": [ + "notify.cloud" + ], + "icon_filename": "victorops.svg" + }, + "keywords": [ + "VictorOps", + "Splunk", + "On-Call" + ], + "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", + "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", + "integration_type": "notification", + "edit_link": "https://github.com/netdata/netdata/blob/master/integrations/cloud-notifications/metadata.yaml", + "troubleshooting": "" + }, + { "id": "notify-cloud-webhook", "meta": { "name": "Webhook", diff --git a/integrations/integrations.json b/integrations/integrations.json index 5b602d6f71..36987d3f62 100644 --- a/integrations/integrations.json +++ b/integrations/integrations.json @@ -21740,6 +21740,27 @@ "troubleshooting": "" }, { + "id": "notify-cloud-victorops", + "meta": { + "name": "Splunk VictorOps", + "link": "https://www.splunk.com/en_us/about-splunk/acquisitions/splunk-on-call.html", + "categories": [ + "notify.cloud" + ], + "icon_filename": "victorops.svg" + }, + "keywords": [ + "VictorOps", + "Splunk", + "On-Call" + ], + "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", + "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", + "integration_type": "notification", + "edit_link": "https://github.com/netdata/netdata/blob/master/integrations/cloud-notifications/metadata.yaml", + "troubleshooting": "" + }, + { "id": "notify-cloud-webhook", "meta": { "name": "Webhook", |