@cryptotaxi247 / netdata-1 / commits / b5ed454aa

include reachability alert fields (#17258)

Co-authored-by: Ilya Mashchenko <ilya@netdata.cloud>

Juan Cañete committed Mar 26, 2024 at 13:08 UTC b5ed454aa9e6efb636c61ee23f5c880efec36b51
1 file changed +9 -2
integrations/cloud-notifications/metadata.yaml
+9 -2
@@ -543,9 +543,9 @@
543
544 A webhook integration is a way for one service to notify another service about events that occur within it. This is done by sending an HTTP POST request to a specified URL (known as the "webhook URL") when an event occurs.
545
546 - Netdata webhook integration service will send alert notifications to the destination service as soon as they are detected.
546 + Netdata webhook integration service will send alert and reachability notifications to the destination service as soon as they are detected.
547
548 - The notification content sent to the destination service will be a JSON object having these properties:
548 + For alert notifications, the content sent to the destination service contains a JSON object with the following properties:
549
550 | field | type | description |
551 | :-- | :-- | :-- |
@@ -565,6 +565,13 @@
565 | additional_active_warning_alerts | integer | Number of additional warning alerts currently existing on the same node. |
566 | alarm_url | string | Netdata Cloud URL for this alarm. |
567
568 + For reachability notifications, the JSON object will contain the following properties:
569 +
570 + | field | type | description |
571 + | :-- | :-- | :-- |
572 + | message | string | A summary message of the reachability alert. |
573 + | url | string | Netdata Cloud URL for the host experiencing the reachability alert. |
574 +
575 #### Extra headers
576
577 When setting up a webhook integration, the user can specify a set of headers to be included in the HTTP requests sent to the webhook URL.