Wanesy Management Cockpit (online) GMS API Web services documentation (online)

The alerting mechanism is based on the notion of group.

When creating/updating a group, it is possible to declare it as an alerting one.

Configuring the alerts is done at group level, i.e. the configuration applies to all the gateways in the alerting group.

To configure the alerts, you need to go to the group overview page and select ALERTING in the menu.

For each alert type, it is possible to:

• Activate/deactivate the alert
• Use default configuration (recommended), or custom it

The alert for Disconnection is triggered when the gateway has stopped receiving telemetry messages for more than 3h.

The alert is automatically closed when the gateway has successfully reconnected and is receiving telemetry messages again.

The alert for Backhaul consumption is triggered when the backhaul consumption forecasted for the current month exceeds the predefined limit (configurable from 50 to 5000 Mbytes, 400 Mb by default).

The global consumption is estimated until the reset day (configurable from 1 to 28), independently for each type of backhaul used (Ethernet, WiFi or Cellular).

The alert is automatically closed when the backhaul consumption forecasted for the month comes back within the limit.

The alert for LoRaWAN uplink disruption is triggered when the gateway has not receive any valid LoRaWAN messages for a certain period of time.

The monitoring window is configurable from 3 hours to 7 days (24h by default).

The alert is automatically closed when valid LoRaWAN messages have been received again during the last monitoring window.

The alert for LoRaWAN uplink trend change is triggered when a significant downward trend is detected on the number of valid LoRaWAN messages received, based on the last 30 days behavior.

Configuring the sensitivity mode (normal or low) allows to adjust the detection threshold.

The alert is automatically closed when the trend on the number of valid LoRaWAN messages received is stabilized.

The alert for LoRaWAN CRC error rate trend change is triggered when a significant upward trend is detected on CRC error rate for one or more frequencies, based on the last 30 days behavior.

Frequencies involved in trigerring this alert are listed in the reason field of the alert details.

Configuring the sensitivity mode (normal or low) allows to adjust the detection threshold.

The alert is automatically closed when the trend on CRC error rate on all detected frequencies is stabilized