The following examples show how to set up Device Health Alert Rules to monitor your deployed devices. Use them as guidelines to make sure alerts are triggered when it matters and to avoid alert fatigue from alerts that trigger too often. For the full settings of each rule type, see About Device Health Alert Rules.
| Use case | Deployed devices | Alert Rule setup |
|---|---|---|
| Portal Beam and Portal Light monitoring for Occupancy use cases | 100 Portal Beams, 20 Portal Lights per location, multiple locations | Portal Light Offline: alert when any Portal Light goes offline for 30 minutes. Battery Level: alert when at least 20 Portal Beams have a battery level below 20%. |
| Portal Beam and Portal Light monitoring for Asset tracking use cases, including Asset Tags | 100 Portal Beams, 20 Portal Lights, 500 Asset Tags per location, multiple locations | Portal Light Offline: alert when any Portal Light goes offline for 30 minutes. Battery Level: alert when at least 20 Portal Beams have a battery level below 20%, and when at least 100 Asset Tags have a battery level below 20%. |
| Portal Beam and Portal Light monitoring for Staff tracking use cases, including Smart Badges | 100 Portal Beams, 20 Portal Lights, 500 Smart Badges per location, multiple locations | Portal Light Offline: alert when any Portal Light goes offline for 15 minutes. Battery Level: alert when at least 20 Portal Beams have a battery level below 20%, and when at least 100 Smart Badges have a battery level below 20%. |
| Monitoring Anchor Beacon infrastructure for Indoor Wayfinding | 1000 Anchor Beacons and 100 Portal Lights per location, multiple locations | Portal Light Offline: alert when any Portal Light goes offline for 30 minutes. Battery Level: alert when at least 200 Anchor Beacons have a battery level below 20%. |