What is watched
One open alert per subject per type, so a disk that has been full for a week is
one row rather than two thousand notifications.
Resolving and dismissing
Most conditions clear themselves. A full disk resolves when space is freed; an unreachable server resolves when its agent reports in. A deployment that failed happened, and stays happened, so it is acknowledged rather than resolved. Dismissing something that is still true only hides it until the next check. A full disk stays full.The queue alert
Worth calling out because of what it means about everything else. Every button in Shipways queues work. With nothing running the queue, they all appear to do nothing, forever, and the only feedback is a spinner. This alert is reached by the scheduler rather than by the queue, so it still fires when the thing it is watching for has happened. If provisioning, deployments and certificate requests are all sitting at pending, this is why.Where alerts are sent
Owners and admins are always emailed and always see the bell. Beyond that, add destinations under Alerts:
The chat services are separate rather than one generic webhook because they do
not agree on what a message looks like — Slack reads
blocks, Discord reads
embeds, Mattermost reads attachments. Sending one shape to all three is how
Discord users end up appending /slack to their URL.
Each destination chooses which alert types it wants, so “tell me about
certificates but not disk space” is a thing you can actually say.