Alerts & Alert Rules
Create per-device alert rules, understand cooldowns, and review your in-app alert history, from device reading to notification.
Alerts & Alert Rules
Alert rules let you define thresholds for each device's telemetry readings and turn those thresholds into actionable alerts. When a reading crosses a rule condition, BrewWizz evaluates the rule, applies its cooldown, and records an alert event that you can review in the dashboard. Use this page to understand how rules work, why alerts fire or do not fire, and where to review your alert history.
Prerequisites
Your plan must include alert rules to create or edit alert rules, and in-app alerts to see alert history and the alert bell. See Understanding Your Plan.
Alert Rules
Each alert rule is tied to a specific device. You configure the rule on that device so the system knows which readings to watch and what condition should trigger an alert.
A rule compares incoming telemetry against a threshold condition, such as temperature above a value, temperature below a value, or pressure outside an expected range. When a new reading arrives, BrewWizz evaluates that reading against the device's active rules.
If your plan doesn't include alert rules, the rule settings are read-only and BrewWizz doesn't check new readings against your rules.
How an alert is created
- Your device sends a reading to BrewWizz.
- BrewWizz checks the reading and stores it.
- If your plan includes alert rules, BrewWizz compares the reading with that device's active rules.
- If the same rule fired recently and is still within its cooldown period, BrewWizz skips it.
- If the rule matches and the cooldown has passed, BrewWizz creates an alert.
- If your plan and notification preferences allow it, BrewWizz sends the alert by SMS, email, or both.
Cooldowns
Cooldowns prevent alert storms when the same problem continues across multiple readings. If a rule fires and later readings still match that same condition, BrewWizz waits until the rule's cooldown period has elapsed before creating another alert from the same rule.
Cooldown is set per rule, so different devices or conditions can use different repeat intervals. Short cooldowns make recurring issues more visible, while longer cooldowns reduce repeated notifications during extended fault conditions.
In-App Alert History
The Alerts page shows a chronological history of alert events for devices in your organization. Use it to confirm that a rule fired, review when it happened, and compare alert timing against device activity.
If your plan includes in-app alerts, the dashboard header also shows an alert bell with the count of unacknowledged alerts. That bell updates automatically as new alert events occur, so new in-app alerts appear without requiring a manual refresh.
Read-Only Rules
If your plan doesn't include alert rules, your existing rules are paused and shown as read-only, and BrewWizz stops checking readings against them. The rules aren't deleted, and they start working again if your plan includes alert rules later.
When Alerts Don't Fire
Check these conditions first:
- Your plan must include alert rules.
- A rule must exist for the device that sent the reading.
- The rule's cooldown window must have elapsed.
- The incoming reading must match the rule condition.
- Your subscription must be active or in trial.
For broader diagnosis steps, see Troubleshooting.