Where to find it: [Tools > Alarm] | Applies to: v1.3.2 | Control mode: KMA (GMA supports battery alerts only) | Last updated: 2026-07-24
Note: Alerts is a premium feature. Availability depends on your subscription plan. If the page shows an upgrade prompt, contact KiwiCloud to upgrade.
1. Features & Applicable Objectives
Alerts lets you set monitoring rules for your devices. The system checks device battery, storage, memory, or connectivity at the interval you define, and the moment a device meets your condition (e.g., battery below 20%), it notifies you by email or on-device message and keeps a record. Rules can target specific device groups or all devices, and a silence period prevents repeated notifications.
Who it's for: enterprise IT administrators who want to be notified proactively when devices run low on battery, storage, or memory — or go offline — instead of waiting for frontline staff to report problems.
Control mode support:
Control mode | Supported scope |
KMA | All alert types (Battery / Storage / Memory / Network) |
GMA | Battery alerts only |
IMA | Not applicable |
Typical workflow:
Create an alert rule → choose a type, set the threshold, pick notification channels;
Associate devices → define which devices the rule applies to;
Trigger → a device meets the condition; the system generates an alert and notifies you;
Review & act → check alert records and offline devices in the details page, and tune the rule as needed.
2. Primary Operations
Create an alert
Go to [Tools > Alarm] and click [Create Alert] in the top-right corner.
Step 1: Alert configuration
➊ Enter an alert name (required, ≤256 characters). Use a self-explanatory name such as "Low battery alert".
➋ Select the alert type: Battery / Storage / Memory / Network (each type has its own trigger condition — see 4. Configuration Item Descriptions).
➌ Set the detection interval and trigger condition.
➍ Select at least one notification channel and set a silence period if needed.
Click [Next Step].
Step 2: Select devices
➊ Choose the distribution scope: selected devices (pick below) or all devices.
➋ Select targets by Device Group or Device.
Click [Submit] to finish.
Tip: if you choose "all devices", newly enrolled devices are automatically covered by this rule.
3. Secondary Operations
The alert list at a glance
The list supports search by name and shows each rule's type, detection interval, associated device count, status, and total alert count. Offline devices is the number of devices currently disconnected; total alerts is the cumulative trigger count of the rule.
View details
Click [Details] in a list row to open the alert details page.
The top of the page shows an overview — alert type, detection interval, alert condition, associated groups, associated devices, and total alerts — with the following tabs:
Alert settings: the rule's notification channels, silence period, and other configuration;
Associated devices: devices the rule currently applies to;
Offline devices: devices currently disconnected;
Alert records: the history of triggered alerts;
Operation logs: create/edit operations performed on this rule.
Edit
Open [Action > Edit] in a list row. You can change the name, detection interval, trigger condition, notification channels, silence period, and associated devices.
Note: the alert type cannot be changed after creation (the field is grayed out when editing). To switch types, create a new rule.
Enable / disable
Toggle the switch in the Status column directly in the list — no need to open the editor. A disabled rule stops checking and notifying.
Delete
Open [Action > Delete] in a list row and confirm in the dialog.
Warning: deleted alerts cannot be recovered. Proceed with caution.
4. Configuration Item Descriptions
Alert types and trigger conditions
Type | What it monitors | Trigger condition | Unit | Typical scenario |
Battery | Device battery level | Level below threshold (e.g., | % | Keep handheld/mobile devices from dying |
Storage | Device storage space | Free storage below threshold (e.g., | % | Prevent full storage from breaking apps |
Memory | Available device memory | Free memory below threshold | MB | Spot performance/lag risks |
Network | Communication with the server | No communication beyond a set duration | days/hours/minutes | Detect offline/disconnected devices early |
Note: only Battery alerts take effect on GMA devices. Storage/Memory/Network rules do not generate alerts for GMA devices.
Suggested thresholds (for reference, not enforced): battery < 20%, storage < 10%, memory depends on device specs, network per your business tolerance (e.g., 1 day).
Detection interval
What it does: how often the system checks whether devices meet the condition (applies to Battery/Storage/Memory types);
Effect: shorter intervals detect issues sooner but add checking overhead;
Suggestion: the default 15 minutes works for most cases; shorten it for time-critical scenarios.
Notification channels
Send alert via email: sends alert emails to the addresses you specify (separate multiple addresses with commas/semicolons/spaces/line breaks). Emails follow a template including the alert name, alert type, trigger time, and device name;
Send alert to device: pops up a message on the device; requires a custom device alert message (≤120 characters);
Suggestion: use email for administrators and on-device messages for frontline users; both can be enabled together;
Note: Network (offline) alerts support email only — an offline device cannot receive on-device notifications.
Silence period
What it does: after a rule triggers, no repeat notification is sent within this period;
Effect: prevents the same issue from spamming you;
Suggestion: the default 60 minutes works for most cases; increase it if alerts get noisy.
5. FAQ
Q: The page says I don't have permission and asks me to upgrade. What should I do?
A: Alerts is a premium feature tied to your subscription. Contact KiwiCloud to upgrade.
Q: Why don't my GMA devices receive storage/memory/network alerts?
A: GMA mode supports battery alerts only; the other types apply to KMA devices.
Q: What's the difference between the detection interval and the silence period?
A: The detection interval controls how often the system checks for the condition; the silence period controls how long to wait before notifying again after a trigger.
Q: Why can't I change the alert type of an existing rule?
A: The alert type is fixed at creation and cannot be modified. Create a new rule to use a different type.
Q: Why is memory measured in MB while battery/storage use %?
A: Memory alerts are based on the device's available memory in MB; battery and storage are percentage-based.
Related articles