The platform watches a handful of things and tells you when they change. An Admin or Owner sets it per project, under Notifications on the project's configuration page.
What it will tell you about
| Subject | When |
|---|---|
| Deployments | A deploy failed, or a release went live. A failure is said once per environment until the next deploy succeeds, which says it works again |
| 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 | An environment or a disk passed 80% of its storage, and again at 95%. The disk is one bought for an environment, or the machine's own on a machine that is only your team's |
| Machines | A machine was built, resized or destroyed, or could not be built. A service on it (the application, a worker, the frontend, an extra) stopped or failed its health check for five minutes, and when it runs again |
| Load | A machine has been busy long enough that it is the size rather than a spike |
You choose each subject separately.
Storage at 80% and sustained load are early warnings. Availability is sent when the site is already not answering.
Where it goes
Each subject gets one channel and, separately, email on or off. The channels are those your team has connected under Integrations: Slack, Telegram, Discord, PagerDuty, or a webhook for anything else.
Email needs no setting up: it is offered without anything being connected first.
| Subject | Email starts |
|---|---|
| Availability, storage, machines, load | On |
| Deployments, backups | Off |
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.
Who gets it
Everyone on the project from Developer upwards. The exception is a subject that is the owner's business: 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. See Teams.
The monthly traffic report
Monthly traffic report in the team settings is separate from the notifications above. It is on for a new team until somebody turns it off.
On the first of each month, the team's owners and admins get one email with every project in it. Nobody else is sent it. It shows:
- what each environment served against the month before
- what the edge refused and why
- the SQL injection a project counts
- the pages most visited
- what scanners went looking for
- who asked
It is counted at the edge, so what your CDN answered from its cache is not in it, as on the Metrics tab.
Not a status page
These tell you about your own projects. A problem with the platform itself is not reported through them.
Next
- Integrations — connecting the channels
- Logs — the detail behind what a notification only summarises
- Monitoring — the metrics and checks an alert comes from
Thank you. Good to know it helped.
Thanks — tell us what was missing. Open a ticket from Support in the console, and we answer on the ticket. Open the console