Alert Rules watch a metric and notify you (or take action) the moment it crosses a threshold – a leak detector, not a clock. This is different from an , which fires at a set time regardless of conditions; see Setting Up Automation Schedules for that. Use an Alert Rule whenever the trigger is “when X happens,” and a Schedule whenever it’s “at this time, every day.”
Alert Rules and Metric Groups are available to integrator accounts. Client accounts see a read-only version – the rules that apply to them, without the ability to create or edit.
Creating a Rule
- Go to and click Create New Rule.
- Give it a Rule Name.
- Choose a Target Scope: Client (every device belonging to one client), Display Type / Display Model (every matching device, wherever it is), or Node ID (one specific device).
- Build the condition: pick a metric, an operator (
>,≥,<,≤,=), and a threshold value. Instead of a single metric you can pick a Metric Group (see below) to watch several related readings with one rule. - Set a Duration – how many minutes the condition has to stay true before it actually fires (0 = fire immediately). Useful for ignoring a brief spike.
- Set a Severity – Warning or Critical.
- Choose an Action: do nothing but notify, or automatically Power Off, Power On, or Reboot the affected device(s).
- Choose how you want to be told – see Notifications below.
- Save. The rule is active immediately.
Metric Groups
A Metric Group bundles several related numeric fields (e.g. five separate temperature sensors) so one rule can watch all of them at once and fire if any of them crosses the shared threshold – instead of building an identical rule five times. Create one from the section on the same page, then pick it from the “Metric Group” option when building a rule.
Notifications
Each rule has its own independent notification settings:
- Log & Notify Bell – records the alert in System Logs and shows it in the in-app notification bell.
- Send Email – sends an email when the rule fires. Choose which recipients get it: System Integrator and/or Client (the organization the affected device belongs to).
A rule with everything unchecked still evaluates and can still trigger its Action (e.g. auto-power-off) – it just won’t leave a visible trace or send anyone an email.
Maintenance Windows
Suppress alerts for a device, an entire organization, or globally during planned downtime – a firmware update or scheduled outage shouldn’t page anyone. Set a Scope, then either a one-time date/time range or a daily recurring window (e.g. every night 22:00–06:00, which correctly spans midnight). Give it a Reason so anyone looking at the list later knows why. A device inside an active window shows a Maint badge on the Hardware Fleet page instead of triggering alerts.
Managing Existing Rules
- Edit changes any part of a rule you created or have access to.
- Delete removes it permanently.
- A rule you can see but didn’t create (e.g. a fleet-wide rule set up by someone above you) may show as Read-only – you can view it, but not change or remove it.
Automation Scheduler
The same page also hosts the – time-triggered commands, independent of the condition-based rules above. See Setting Up Automation Schedules for the full guide to that section.