Alarm rules
Alarm rules define one or more conditions on template variables (e.g. "temperature > 8°C" and "humidity < 40%") that, when all are met on an asset, create an event in that asset's alarm history.
Rules live on the template: they apply to all assets of that type.
Where to create them
- From Settings → Asset Templates → [template] → Rules.
- Or from the Rules tab on an asset detail page — remembering the rule applies to every asset of the template (see Creating dashboards and rules from the asset detail page).
Who can create or edit
Admins and Support can add, edit and delete rules. Other roles can only view them.
Rule fields
| Field | Description |
|---|---|
| Name | Rule label (required) |
| Description | Optional text |
| Severity | Informational, Warning (default), Critical |
| Delay | Seconds all conditions must stay true before raising the alarm |
Conditions (AND)
You can add one or more conditions. The alarm fires only if all of them are true at the same time (AND logic).
If a telemetry update includes only some of the variables involved, the others are taken from the asset's last known values (datastore). If a variable has never been received, the rule is not evaluated.
For each condition:
| Field | Description |
|---|---|
| Variable (key) | Template field to monitor |
| Operator | < > <= >= == != |
| Threshold | Comparison value (numeric or string, depending on the data) |
Example: temperature > 8 AND door == open → the alarm fires only if both stay true for the configured delay.
Notifications
In the rule notification section you can add one or more notification rows. For each row:
| Field | Description |
|---|---|
| Send times | How many times to send this notification (minimum 1) |
| Resend delay | Seconds between sends (for this row) |
| Channel | Email or Telegram |
Timing (send count and resend delay) is independent per row: for example, one immediate email to the team and another with fewer sends and a different delay.
Recipients
- email addresses (more than one per row is allowed);
- special audience recipients, expanded at runtime to members who can see that asset:
- Everyone who can see the asset (
asset_viewers): all roles (admin, support, customer); - Everyone who can see the asset (customers) (
asset_viewers_customers): customer-role members only; - Everyone who can see the asset (support) (
asset_viewers_support): support-role members only.
- Everyone who can see the asset (
Each member's notification preferences email is used (or their membership email if unset). Members who disabled notifications in the Space are skipped.
Telegram
Recipients: one or more numeric chat IDs. You can enter a single ID, a comma-separated list, or multiple chips in the UI. With audience tokens (asset_viewers, asset_viewers_customers, asset_viewers_support), only chat IDs saved in members' notification preferences are used (if missing, that member is not notified on Telegram).
Recipients typed explicitly on the rule are not filtered by a member's on/off preference.
Personal notification preferences
Each member can configure them from Settings → Notifications (or Settings → Users for Admins):
- enable/disable receiving notifications in this Space;
- an alternate notification email;
- their Telegram chat ID.
These preferences apply when the rule uses an audience token (asset_viewers, asset_viewers_customers, asset_viewers_support). See also Managing members.
Telegram setup (end user)
- Open the notification bot with the direct link: https://t.me/trackle_iot_bot?start=1 and tap Start once so the bot is allowed to message you.
- Open @userinfobot, start it, and copy your chat ID.
- Paste it in the Space notification preferences (or as an explicit recipient on the rule).
Message and placeholders
Message placeholders (with double braces in the UI):
| Placeholder | Meaning |
|---|---|
{{key}}, {{value}}, {{operator}}, {{threshold}} | First condition (backward compatible) |
{{key.2}}, {{value.2}}, {{operator.2}}, {{threshold.2}} | N-th condition (1 = first, 2 = second, …) |
{{value.variableName}} | Live value of that variable (e.g. {{value.humidity}}) |
{{conditions}} | Summary of all AND conditions with values |
{{serialNumber}}, {{externalID}} | Asset metadata / external ID |
Example with two conditions: {{key.1}}={{value.1}} and {{key.2}}={{value.2}}.
Email appearance
Alarm emails use:
- the Space logo from Settings → General → Branding (if missing, a default Trackle logo);
- in the displayed sender, the Space name (from Settings → Labels), followed by the status (e.g.
MySpace ALARM). If no name is set,Notificationis used.