Adds docs for Splunk cloud notifications (#16586)
Co-authored-by: Ilya Mashchenko <ilya@netdata.cloud>
Juan Cañete committed
Dec 12, 2023 at 17:54 UTC
90aee26340df05282d5051376148b2a195a73c23
1 file changed
+38
integrations/cloud-notifications/metadata.yaml
+38
@@ -372,6 +372,44 @@
372
- 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.
373
- 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`
374
375
+- id: 'notify-cloud-splunk'
376
+ meta:
377
+ name: 'Splunk'
378
+ link: 'https://splunk.com/'
379
+ categories:
380
+ - notify.cloud
381
+ icon_filename: 'splunk.svg'
382
+ keywords:
383
+ - Splunk
384
+ overview:
385
+ 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."
386
+ notification_limitations: ''
387
+ setup:
388
+ description: |
389
+ ### Prerequisites
390
+
391
+ To add Splunk notification you need:
392
+
393
+ - A Netdata Cloud account
394
+ - Access to the space as an **administrator**
395
+ - Space needs to be on **Business** plan or higher
396
+ - 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.
397
+
398
+ ### Steps
399
+
400
+ 1. Click on the **Space settings** cog (located above your profile icon)
401
+ 2. Click on the **Notification** tab
402
+ 3. Click on the **+ Add configuration** button (near the top-right corner of your screen)
403
+ 4. On the **Splunk** card click on **+ Add**
404
+ 5. A modal will be presented to you to enter the required details to enable the configuration:
405
+ - **Notification settings** are Netdata specific settings
406
+ - Configuration name - provide a descriptive name for your configuration to easily identify it.
407
+ - Rooms - select the nodes or areas of your infrastructure you want to receive notifications about.
408
+ - Notification - choose the type of notifications you want to receive: All Alerts and unreachable, All Alerts, Critical only.
409
+ - **Integration configuration** are the specific notification integration required settings, which vary by notification method. For Splunk:
410
+ - HTTP Event Collector URI - The URI of your HTTP event collector in Splunk
411
+ - HTTP Event Collector Token - the token that Splunk provided to you when you created the HTTP Event Collector
412
+
413
- id: 'notify-cloud-webhook'
414
meta:
415
name: 'Webhook'