🚨 Supervision & alerts
Incidents detected, fixed — often before you even notice them.
Fuzz continuously monitors the health of your installation: equipment, controller, communication. And when something goes wrong, the platform acts.
Real-time monitoring
Equipment status
Each charge point and each asset exposes its live status:
| Charge point status | Meaning |
|---|---|
| Charging | Charging |
| Available | Available |
| Occupied | Vehicle connected without charging |
| Offline | Offline |
| Faulted | In error |
| Unavailable | Unavailable |
Modbus assets (meters, batteries, PV) are supervised in the same way: online, offline, not tracked.
Controller health
System resources, internal services, cloud communication: the controller monitors itself and reports everything to the cloud.
Intelligent alerts
- configurable rules: triggers on metrics, statuses or thresholds
- notification channels: Email, Telegram and Webhook
- full tracking: each alert carries a status (open, assigned, resolved…), an owner, comments and a history
- priorities to sort urgent from important
Telegram notifications
A Telegram channel can contain multiple destinations: private chats and groups. Each destination has its own status, attempt count, and retry information; a pending destination does not prevent the other destinations from receiving the alert.
Webhook notifications
A webhook channel delivers alerts into your own systems. Each target is an HTTP URL, with authentication where the system requires it (Basic, Token or OpenID Connect). As with Telegram, every target is delivered and retried independently, so an unreachable target does not prevent the others from receiving the alert.
Notifications on every status change
Unlike the Email and Telegram channels, which notify only when the alert is raised, a webhook channel is notified on every status change: resolved, assigned, closed, on hold, auto-resolved. This is useful when your own system has to close or escalate the incident it opened.
Email and Telegram channels remain limited to a single notification per alert: their history and the operator's inbox both assume one alert per issue.
Custom metadata
An alert definition accepts a list of key/value pairs, sent as-is in the body of every webhook notification it triggers. Fuzz does not interpret them: they are meant for your system, which can use them to route the notification to the right pipeline or tenant.
Auto-remediation: Fuzz Sentinel
This is where Fuzz stands out. Fuzz Sentinel, our proactive supervision service, does not just notify you:
- automatic detection of known faults: controller offline, smart charging blocked, repeated log errors
- automatic correction: remote controller restart, relaunch of failing services
- interventions traced in the alert history
- escalation to Fuzz support only if the problem persists
Result: the majority of incidents are resolved without human intervention, often before an end user notices any issue.
Remote diagnostics
When intervention is needed:
- logs accessible remotely (real-time and archives)
- built-in tools: OCPP tester, Modbus tester
- access to equipment web interfaces from the console
- controlled remote restart
👉 See also: Your data belongs to you