Searching...

Matching results

    How to be alerted upon abnormal consumption in an unexpected country?

    For some deployments, you may have to enable a roaming zone that will not only enable the countries you are planning to deploy to, but also other countries, which may be much more expensive, and therefore induce a risk on your solution costs.

    To permit detection of a geographically abnormal usage consumption, you may want to set an alert in case a device starts a usage consumption in a list of countries you can define.

    The alert is raised as soon as we receive a consumption from a visited country listed as one target country in the rule, and will be cleared in the next usage consumption outside from the same list of countries.


    Create an alert rule with a suspension action in case of abnormal usage

    This how-to explains how, after having enabled the RZ - CARIBBEAN NORTH for deployments in Bahamas, you want to restrict usages to Bahamas only, by suspending a device doing traffic in any other countries enabled by the Roaming Zone. You will also want to be alerted by mail to react to the abnomaly.

    1. Click on Configure > Alert Rules.
    2. Click on Create. The New Alert Rule page opens.
    3. Select the Usage consumption from specified countries template.
    4. Set the alert:
      • Name
      • Description
    5. Change values of the pre-filled condition to modify the countries for which you want to avoid consumption by suspending the system. In our example, you shall list all countries from RZ - CARIBBEAN NORTH but Bahamas.
    6. Optionally add a condition on the system if you need to restrict the rule to a subset of systems only, or to the offer on which RZ - CARIBBEAN NORTH is authorized. You can use for example use: ‘System is’ or ‘System has label’ and then choose the label of choice to restrict the rule target.
    7. Add the action Suspend.
    8. You can also add other action such as sending an email if you want to be notified when the suspend occurs.
    9. Click on Save.

    Below shows the rule configured for our example:

    TOP