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, it is accessible from the ALERTING menu.

The configuration applies to all the gateways in the alerting group.

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.

You have the option to select:

• A pre-defined software update (previously declared by Kerlink) to apply a public software or configuration
• A Custom Magic Link to apply a specific software or configuration

After clicking on SEND button, you will be asked to confirm in a popup.

Once triggered, the udpate command will be sent to each gateway of the group when the next telemetry message is received (message expected every hour).

When an update command is in progress (waiting to be sent to all the gateways), an orange dot is displayed in the CONFIGURATION menu.

You can consult the software update history of your group in the Last updates table.

Depending on its progress, the update command goes through different possible statuses:

• Created: the update command has been created
• In progress: the update command is ready to be sent to the gateways
• Sent: the update command has been sent to all the gateways
• Partially sent: the update command has been sent to some of the gateways
• Cancel request: the cancellation of the update command has been requested
• Cancelled: the update command has been cancelled

To cancel the update command, you need to click on the CANCEL UPDATE button present in the table.

Clicking on the eye link in the Last updates table opens a dashboard allowing you to follow the progress of the group update.

Clicking on a status in the progress bar allows to only list the gateways with update specifically in this status.

You have the option to cancel the update individually at each gateway (by clicking on the CANCEL UPDATE button at the end of each line).

The dashboard is automatically refreshed and goes through the different statuses, until it is Sent, Partially sent or Cancelled.