summaryrefslogtreecommitdiffstats
path: root/integrations
diff options
context:
space:
mode:
authorJuan CaƱete <2930882+juacker@users.noreply.github.com>2023-12-12 17:54:07 +0100
committerGitHub <noreply@github.com>2023-12-12 18:54:07 +0200
commit90aee26340df05282d5051376148b2a195a73c23 (patch)
tree9a4895b0bde2a540e9f31f382a172e85dc2988a7 /integrations
parentd36384f63c0db0b096292eb79dcfe2fa5f5cebd3 (diff)
Adds docs for Splunk cloud notifications (#16586)
Co-authored-by: Ilya Mashchenko <ilya@netdata.cloud>
Diffstat (limited to 'integrations')
-rw-r--r--integrations/cloud-notifications/metadata.yaml38
1 files changed, 38 insertions, 0 deletions
diff --git a/integrations/cloud-notifications/metadata.yaml b/integrations/cloud-notifications/metadata.yaml
index c033172427..ee4f9d7e28 100644
--- a/integrations/cloud-notifications/metadata.yaml
+++ b/integrations/cloud-notifications/metadata.yaml
@@ -372,6 +372,44 @@
- Contact the [@myidbot](https://t.me/myidbot) bot and send the `/getid` command to get your personal chat ID, or invite it into a group and use the `/getgroupid` command to get the group chat ID.
- Alternatively, you can get the chat ID directly from the bot API. Send your bot a command in the chat you want to use, then check `https://api.telegram.org/bot{YourBotToken}/getUpdates`, eg. `https://api.telegram.org/bot111122223:7OpFlFFRzRBbrUUmIjj5HF9Ox2pYJZy5/getUpdates`
+- id: 'notify-cloud-splunk'
+ meta:
+ name: 'Splunk'
+ link: 'https://splunk.com/'
+ categories:
+ - notify.cloud
+ icon_filename: 'splunk.svg'
+ keywords:
+ - Splunk
+ overview:
+ notification_description: "From the Cloud interface, you can manage your space's notification settings and from these you can add a specific configuration to get notifications delivered on Splunk."
+ notification_limitations: ''
+ setup:
+ description: |
+ ### Prerequisites
+
+ To add Splunk notification you need:
+
+ - A Netdata Cloud account
+ - Access to the space as an **administrator**
+ - Space needs to be on **Business** plan or higher
+ - URI and token for your Splunk HTTP Event Collector. Refer to the [Splunk documentation](https://docs.splunk.com/Documentation/Splunk/latest/Data/UsetheHTTPEventCollector) 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** 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:
+ - HTTP Event Collector URI - The URI of your HTTP event collector in Splunk
+ - HTTP Event Collector Token - the token that Splunk provided to you when you created the HTTP Event Collector
+
- id: 'notify-cloud-webhook'
meta:
name: 'Webhook'