- Please see the table in Threshold and Trigger Information for specific product limitations.
- For alerts with a traffic policy applied, traffic is NOT automatically unblocked at
the beginning of a new alert interval.
- For example, an alert is defined to block Packet traffic if usage exceeds 5 MB in one month. At some point during the current month, the device exceeds 5 MB and Packet traffic is blocked. At the beginning of the next month, packet data will remain blocked until the block is manually removed by either editing the device on the Devices tab or through the AerAdmin Traffic Policy API.
- Alerts are processed once every hour; therefore, it can take up to 60 minutes after
an event occurs before the user is notified.
- For example, an alert is defined to send an email notification if a device does not register within 15 minutes. The device de-registers at 6:05 and does not re-register by 6:20. Because alerts are analyzed at the beginning of the hour, the email alert notification for this device will be sent to the user at 7:00.
- MyAlerts based data blocking is evaluated upon receipt of continue records or stop
records from the underlying data network.
- Because these data feeds only occur periodically, it is possible that data usage will exceed the triggering threshold, but blocking will occur once MyAlerts detects the threshold has been exceeded. The period of time between data feeds varies between products, and depending on the device behavior it is possible for a significant amount of data to be consumed beyond the alert threshold. Some products may take as long as 75 minutes for usage threshold to be detected. For Fusion NA and Fusion Global products this period is 11 minutes. For Dual-Mode A-LH and Global SIM, this period is 75 minutes.
- For maximum threshold alerts, there may be an additional latency of up to 20
minutes before an event is detected in the system.
- For example, if a device reaches a maximum threshold at 11:50, the system may not detect this event until 12:10. A notification for this alert will be sent to the user at 1:00, when alerts are processed at the beginning of the following hour.
- For minimum threshold alerts, notifications are always sent at the end of the indicated time interval. The complete time duration must pass before determining whether usage was below the defined threshold. For hourly minimum threshold alerts, the user will receive the alert after each full hour has passed. For daily minimum threshold alerts, the user will receive the alert after each full day has passed (GMT). For month-to-date minimum threshold alerts, the user will receive an alert at the end of the month (after the last day of the month, GMT).
- There may be an additional latency of up to 15 minutes before an event is detected
in the system, resulting in the trigger of invalid minimum alerts.
- For example, an alert is configured to detect a minimum threshold of 5 SMS per hour. At 11:55, the device receives a 5th SMS. At 12:00, the system has not yet detected the final SMS occurrence, therefore an alert notification is sent to the user even though the device has met the minimum threshold. This latency affects hourly minimum alerts only; daily and monthly minimum alerts are not affected.
- For Aeris alerts, note that changes to the API Key will cause the publish operation to fail until the API Key cache is refreshed. API keys are refreshed every 24 hours at 00:05, GMT.
Have more questions? Submit a request