Alerts & Routing
Fewer alerts. Better routing. Engineers who actually look.
Set threshold rules with built-in noise suppression. Route different alert types to the right person at the right time — not to a shared inbox everyone ignores.
Active Alerts — Plant A
8 unacknowledged
Signal lost > 15 min
LA-007
2m ago
Battery below 15%
LB-041
8m ago
Firmware version drift
WH-012
14m ago
High packet loss rate
LA-019
21m ago
Signal restored
LB-008
33m ago
How it works
Signal that means something. Noise that stays quiet.
Alert fatigue is caused by misconfigured thresholds and bad routing — not by having too many sensors. Iotpathway fixes both.
Threshold rules with hysteresis
- Set trigger and clear thresholds independently — prevents flapping alerts on borderline conditions
- Per-metric rules: signal strength, battery, uptime, packet loss
- Group-level overrides for different environments
Noise suppression
- Suppress recurring non-critical alerts after N occurrences
- Maintenance mode: suspend alerts during planned downtime
- Cooldown periods prevent alert storm on batch failures
Role-based routing
- Critical alerts go to shift supervisor by name, not a group inbox
- Warning-level alerts go to maintenance lead on current shift
- Informational alerts go to a daily digest email only
Escalation chains
- If primary contact doesn't acknowledge within N minutes, escalate to next in chain
- Weekend and off-hours routing rules
- Webhook delivery for CMMS or PagerDuty integration
Cut your alert volume by 80%
Request access — we'll show you how to configure threshold rules for your specific fleet and routing structure.