Setting up Account Notifications
You can control when and how you would like to receive notifications from Cloud 66. There is a range of events that trigger notifications, which can be sent as emails or via Slack or Webhooks.
Editing account notifications
- Open your Dashboard
- Click on your account avatar (top-right) and select Account Settings
- Click on Notifications in the left panel
- Click on the tab for the notification type (either Account notification or Application notifications)
- Next to each notification type, click on the icon(s) of the channel through which you want to be notified. (Clicking the icons of already active channels deactivates them)
If you would prefer for your billing notifications to go straight to your finance team, you should create a Finance user using their email address, and then (optionally) deactivate finance notifications to your primary account.
Browser notifications use HTML5 to notify you of your selected events directly in supported browsers. Once enabled, your browser will ask your permission for these notifications to be shown.
Email notifications are enabled by default for all users. By default, you will get an email for a number of events, with the exception of account suspended notifications. You can easily turn email notifications on or off for each type by clicking on the email icon.
Slack is a real-time messaging, archiving and search application developed by Tiny Speck.
Visit the Slack Integrations page and select the Cloud 66 integration. Choose the channel you would like to receive notifications in (or create a new one), and click Add Cloud 66 Integration. You will then receive a URL, which you can provide in Cloud 66 integration modal.
The Webhooks standard uses HTTP POST to connect different systems, and is very simple to use but very powerful.
All notification types from Cloud 66 can trigger a webhook. To setup your webhook, click on the Webhook icon. There you can enter the URL for your webhook endpoint and test it to see how it behaves.
Each event type has its own payload that is sent to the endpoint via HTTP POST. The payload is the same as the one used with the API with two additional fields: timestamp and event_type:
|timestamp||Epoch timestamp of when the event was sent|
|event_type||Type of the event, see below|
The following event types are available:
|account.provision.ok||Account provisioned succesfully|
|account.provision.fail||Account provision failed|
|account.redeploy.ok||Account redeployed succesfully|
|account.redeploy.fail||Account redeploy failed|
|server.stopped||Server heartbeat stopped|
|server.backon||Sever heartbeat restored|
|job.fail||Job run failed|
|job.backon||Job run succeeded (after fail)|
|process.down||Process is down|
|app.auth||App authorized to access the account|
|app.deauth||App deauthorized from accessing the account|
|account.redeploy.hook.fail||Account redeployment hook failed|
|account.deploy.started||Account deployment started|