Notifications
Alerts under the bell about deploys, failures and your services, and how to choose them.
Appentic tells you about important events with notifications under the bell icon in the dashboard. The bell shows how many are unread.
Read notifications
Click the bell icon to open Notifications, which lists your 20 most recent. Click a notification to mark it read, or click Mark all read.
Notifications go only to the workspace's owner. Members of the workspace don't get them.
Repeated deploy notifications for the same service are combined until you read them: if you push several times, you see one notification that moves to the top each time, instead of one for every deploy.
What you're notified about
| Setting | Notifies you when | On by default |
|---|---|---|
| Successful deployments | A deploy, rollback or restart goes live. | Yes |
| Failed deployments | A build or deploy fails. | Yes |
| Resources ready | A machine, database, key value store, worker, cron job, storage service, volume, firewall or load balancer is ready, a cron job run succeeds, or the tunnel between zones or the fixed outbound address comes up. | Yes |
| Resource failures | Something fails to set up or change, a web service keeps stopping, a worker crashes, a cron job run fails, a backup fails, a database fills up and becomes read-only, a database or store moves to its standby, or the firewall or the tunnel between zones goes down. | Yes |
| Service lifecycle | A service is created, suspended, resumed, paused, stopped or restarted, or a machine is stopped, started or resized. | No |
| Usage alerts | A database reaches 90% of its storage. | Yes |
| Product updates | Announcements about new features. None are sent yet. | No |
Choose what you get
- Open the user menu and choose User settings.
- Choose Notifications.
- Turn each setting on or off. Each change saves straight away.
These settings control what appears under the bell. Billing and account emails are always sent. You choose when a low-balance alert email is sent on the Billing page. See Running out of credits.