The right people hear about real problems fast — and hear nothing about problems that aren't real. Alerting for mining fleets lives or dies on that second half.
Operational signals cover the failures that cost money: miners offline, thermal warnings and critical temperatures, hashrate loss, and site-level connectivity. Security signals cover the platform itself: failed-login bursts, sign-ins from a new device or location, and cross-organization access attempts. Alerts appear in the console with acknowledgment and resolution tracking, and are emailed to the recipients you route them to.
A mining host serves many parties who need different slices of the truth. Recipient routing is configured per organization and per client: the Site Owner picks who hears about which alert kinds for each client's machines, platform staff routing is separate, and per-organization copies are opt-in. If an organization configures nothing, alerts fall back to the owner's login email — silence by misconfiguration isn't an option.
