Matching results

What's new in August 2016

Initializing Table Of Contents...

Alert engine evolution

Why introduce a new alert engine?

Alerting is a key functionality for a monitoring system, and the current alert mechanism has some limitations :

  • alerts needed to be acknowledged, for the next alert notification to be raised.
  • the user was only notified if the alert was raised, not when it was cleared, leading to unnecessary investigation on systems that had returned to normal behavior.
  • there was no way to easily identify which systems where in alert.

For these reasons, we decided to redesign the alert engine.

The new alert engine introduces the concept of an alert state on a system: a system can either be in alert or not in alert ‘-’.

A system in alert has at least one alert rule for which an alert is currently raised on the system. As soon as the previous alert criteria is no longer met, meaning that the system has gone back to expected behavior, its alert state will go back to ‘not in alert’.

If a system is in alert state due to several alerts being raised at the same time, it’s alert state will be cleared only once all rule violations have been fixed.

What will it change?

The alert rules that you have set-up previously will NOT be affected by this change. They will continue to work as before.

All the functionalities linked to acknowledging alerts have been removed.

The list of alerts available in Monitor>Alerts as well as the alerts displayed in the alerts shortcut (loudspeaker icon) on the top banner will now display all the alerts raised at the current time on your fleet, with one different entry per system and per alert rule. The same way, the alert widget in Monitor>System Details is displaying all alerts raised at the current time on the selected system, with one entry per alert rule.

The alert rule creation screen has also been improved. An alert rule is now simply composed of a set of up to 10 conditions. The alert will be raised if all conditions are satisfied. Some alert rules templates are proposed to you as examples with pre-filled conditions. You can create your own alert rule by changing values or adding more conditions or even choosing the custom template to start .

What functionalities does it add?

The new alert engine comes with new capabilities as described below. Additional new features will be brought in subsequent releases.

Efficient alerting - set and forget

You don’t have to come and acknowledge each alert, you set the alert rule once and you get notified when the alert is raised, and then when the alert is over and the system is working as expected again.

Easily identify systems in alert

Two new columns have been added to the grid of systems to give you a fleet view of which systems are in alert: “alert state” and “alert state change date”.

  • Alert state shows whether a system is currently in alert or not. A system in alert can be in alert due to one or more alert rules being fulfilled. This column is displayed by default.
  • Alert state change date informs you when the system became in alert, or reverted back to normal. This column is not displayed by default, but can be added.

You can use the filtering capabilities with the alert state criteria to display only systems that have at least one alert currently raised.


Change of offer

If you have contracted different connectivity offers for different bundles or zones, you can now switch a SIM from an offer to another. The change of offer can be done on one single SIM, on all SIMs or on a specific defined subset of SIMs that you can identify using manual selection or labels.

To change the offer, go to the Monitor> Systems screen:

  • first select the SIMs to which you want to apply the change,
  • click on the change offer button,
  • select the target offer,
  • click on Change Offer.

You can then check the evolution of the Change Offer operation in the operation widget.

Once launched, the change of offer will be effective within few minutes. As soon as the SIM is on the new offer, the usages consumed by the SIM will be associated to the new offer. The monthly subscription will be re-evaluated at the beginning of the next month based on the updated number of SIMs in each offer.


Connectivity Diagnose

In case you are suspecting something wrong with the connectivity or want more details about real time status of one device, the diagnose capability helps you to understand what is going on and to troubleshoot the service.

The diagnose is a 3 step operation that can be triggered from System>Details:

  • SIM state: checks whether the state of your SIM is currently in a correct state to perform traffic.
  • Voice state: checks the attachment status for voice services, including paging the device for real time voice service reachability
  • Data state: checks the attachment status for data services and real time session information such as visited network, allocated IP address, APN and data traffic since beginning of session.

Each step can result in one of the following statuses:

  • Success: Configuration and/or connectivity behavior are normal.
  • Warning: Connectivity has already been working as expected on this device but is currently temporary interrupted (device being off, or out of coverage, etc…)
  • Error: Device configuration and connectivity are not working and may have never been working before.

When an error is detected, the Diagnose tool will suggest possible causes and ways to troubleshoot the issue.

Note that Diagnose takes few minutes to complete and that it is currently limited to one request per SIM per 5 minutes.

TOP