Cloud docs
Notifications
What the platform will tell you about, where it tells you, and who gets it.
The platform watches a handful of things and says something when they change. Configured per project, under Notifications on the project's configuration page, by an Admin or Owner.
#What it will tell you about
| Subject | When |
|---|---|
| Deployments | A deploy failed — once per environment until the next deploy succeeds, which says it works again — or a release went live |
| Backups | A backup failed, or has not run when it should have |
| Availability | Production stopped answering its health check, and when it starts again |
| Storage | A disk passed 80% |
| Machines | A machine was built, resized or destroyed |
| Load | A machine has been busy long enough that it is the size rather than a spike |
Each is chosen separately, because they are not equally interesting to the same person. A deploy failing matters to whoever pushed; a disk filling matters to whoever pays.
Some of these are said while there is still room to act rather than when they become a problem — storage at 80% and sustained load are both warnings about where something is heading. Availability is the opposite: by the time it is sent, the site is already not answering.
#Where it goes
Each subject gets one channel from those your team has connected under Integrations — Slack, Telegram, Discord, PagerDuty, or a webhook for anything else — and, separately, email on or off.
Email needs no setting up. Your account is an email address, so it is offered without anything being connected first. Availability, storage, machines and load start with email switched on, because all four can fire while nobody is reading a chat channel; deployments and backups start with it off, because a mail per deploy is how people learn to filter the sender.
A situation is said once. While a disk is still over 80% or production is still down, nothing is repeated on the same channel; the all-clear follows when it recovers, and only if the problem was announced in the first place.
#Who gets it
Everyone on the project from Developer upwards, except where the subject is the owner's business rather than the team's — an overdue invoice goes to the owner alone and does not appear in a deploy channel.
A person narrowed to particular projects is emailed about those and no others, and not about anything that concerns the team as a whole rather than one project. See Teams.
#Not a status page
These tell you about your own projects. If the platform itself is having a problem, that is a different thing and is not something a notification about your project would tell you.
#Next
- Integrations — connecting the channels
- Logs — the detail behind what a notification only summarises
- Monitoring — the metrics and checks an alert comes from