Where alerts go, what each device is told, and whether any of it arrives.
iAbout this page›
A device hears about a category rather than about everything above a severity. One floor per device was the only lever anybody had, and it is the wrong shape: turning warnings off to stop hearing about container updates also turns off the disk warnings.
Quiet hours are per device and in that device's own local time. Anything critical ignores them — a window that swallows a failing drive at three in the morning is a window that gets switched off the next morning.
Your own devices are yours, the way your own sign-ins are. Seeing everybody's, and managing webhooks, needs alerts.manage.
A device token and a webhook URL are credentials: anyone holding one can send notifications that look like they came from here. Neither is ever shown on this page.
Not loaded{{ devicesWhy }}
{{ apnsLabel }}{{ apnsNote }}
{{ devicesTitle }}
{{ devicesCount }}
No phone or watch has registered. That happens on the first launch of the app after signing in, once notifications are allowed.
{{ d.label }}{{ d.meta }}{{ d.state }}
{{ d.quiet }}
{{ c.label }}{{ c.detail }}{{ c.state }}
Webhooks and Discord
{{ hookCount }}
A Discord webhook URL is recognised and posted to as Discord; anything else gets the plain JSON. The address is never shown back — it is the credential.
Nothing is configured, so alerts reach Discord only if a target was added before this page existed.