This shows you the differences between two versions of the page.
wiki:monitoring_alerting:alerting [2024/10/02 10:53] ehe created |
wiki:monitoring_alerting:alerting [2025/01/03 14:21] (current) ehe |
||
---|---|---|---|
Line 108: | Line 108: | ||
{{:images:alerts_gateway_overview.jpg?800|}} | {{:images:alerts_gateway_overview.jpg?800|}} | ||
+ | ===== Notification by Webhook ===== | ||
+ | You have the possibility to be notified of alerts on your gateways by configuring a Webhook as an alert destination to receive associated events. \\ | ||
+ | |||
+ | The notification applies to all the gateways in the alerting group. \\ | ||
+ | All the events (opening, updating, closing) related to each alert trigerred are published. | ||
+ | |||
+ | ==== Webhook configuration settings ==== | ||
+ | The following parameters are configurable: | ||
+ | * **Enable/disable** the notification | ||
+ | * **URL** where you want to receive the alert events (mandatory) | ||
+ | * **Security**: None (default), mTLS, Basic Authentication | ||
+ | |||
+ | You also have the possibility to add several **Custom Headers** in the list, with the following parameters for each one: | ||
+ | * **Key** (mandatory) | ||
+ | * **Value** (mandatory) | ||
+ | |||
+ | {{:images:alerting_webhook_custom_header.jpg?500|}} | ||
+ | |||
+ | When a Custom Header has already been configured, it is possible to update it or remove it from the list. | ||
+ | |||
+ | The following parameters are associated to the **mTLS** security option: | ||
+ | * **Certificate** (mandatory) | ||
+ | * **Key** (mandatory) | ||
+ | * **CA certiticate** | ||
+ | |||
+ | {{:images:alerting_webhook_mtls.jpg?500|}} | ||
+ | |||
+ | The following parameters are associated to the **Basic Authentication** security option: | ||
+ | * **Username** & **Password** (mandatory) | ||
+ | |||
+ | {{:images:alerting_webhook_basic_auth.jpg?500|}} | ||
+ | |||
+ | ==== Format of alert event ==== | ||
+ | Each alert event is sent as an HTTP POST command with a JSON-encoded payload. | ||
+ | |||
+ | //Examples for opening, updating and closing a **LoRaWAN uplink disruption** alert:// | ||
+ | |||
+ | {{:images:alert_opening.jpg?400|}} | ||
+ | |||
+ | {{:images:alert_updating.jpg?400|}} | ||
+ | |||
+ | {{:images:alert_closing.jpg?400|}} | ||