All articles

Getting Started

What is CICDoo Getting started: the onboarding wizard The Dashboard and Infrastructure Map

Concepts

Production, staging and development stages Domains, subdomains and SSL Odoo versions and editions (Community vs Enterprise) Workspaces and team collaboration

Servers

Adding a server Server domains and DNS Using a load balancer Server actions: deploy, logs and charts Deleting a server

Projects & Git

Creating a project Connecting GitHub Project GitHub settings and webhook Connecting GitLab Branches and instances Tagging and filtering projects High availability with app nodes Project environments, extensions and deletion

Instances & Console

Creating an instance Restarting, stopping and removing an instance Merging branches between stages Web IDE and remote access SSH access to instances Instance settings explained Deployments and the job queue

Agent Tasks

What agent tasks are Setting up agent tasks Running a task and reviewing the result Agent time and top-ups Agent insights and task filters

Monitoring & Backups

Monitoring your instance Backups and restore S3 storage, uploads and bulk backup actions Alert notifications (email and SMS)

Workspaces & Permissions

Inviting workspace members Member permissions and resource access A member cannot see or use a resource Audit log and server activity

Account & Security

Two-factor authentication (2FA) Profile and integrations settings Passwords and account recovery

Billing & Plans

Plans and pricing Upgrading and managing your subscription If a project subscription goes unpaid The channel partner program Onboarding a client as a partner

Support & Tickets

Opening a support ticket Getting help from the CICDoo team

Troubleshooting

Troubleshooting: cannot connect a server Troubleshooting: a deployment failed Troubleshooting: git push fails with 403 after moving a repository Troubleshooting: my instance is down or slow Troubleshooting: domain or SSL problems

Monitoring & Backups

Alert notifications (email and SMS)

How to choose which monitoring alerts a project sends and deliver them by email, SMS or Telegram, in addition to the in-app notification bell.

How alerts work

Monitoring alerts are set per project and cover the project's production instance. Alerts always appear in the in-app notification bell at the top of the app. Email, SMS and Telegram are extra channels that you switch on by filling them in on the project's Notifications tab.

You need the Project settings permission in a workspace to change these settings.

Choosing which events alert you

  1. Open the project in the Console and click Project Settings at the bottom of the sidebar.
  2. Open the Notifications tab. The card is titled Monitoring Alerts.
  3. Under Alert Events, tick the events you want:
    • Instance down / back up: the production instance stops responding, and again when it recovers.
    • SSL certificate / domain expiry warnings: the certificate or domain is close to expiring.
    • Slow response time: the instance responds noticeably slower than normal.
  4. Untick an event to stop alerts for it.
  5. Click Save Changes at the top of the page.

Getting alerts by email

  1. On the Notifications tab, find Alert Emails.
  2. Enter one or more addresses separated by commas, for example [email protected], [email protected].
  3. Click Save Changes.

Every address in the list receives the alerts for the ticked events. Clear the field and save to turn email alerts off.

Getting alerts by SMS

  1. On the Notifications tab, find Alert Phone (SMS).
  2. Enter one phone number in international format with the country code, for example +31612345678.
  3. Click Save Changes.

Clear the field and save to turn SMS alerts off.

Note: SMS delivery depends on the platform having text messaging switched on. If you have saved a number and never receive texts while email alerts arrive, open a support ticket.

Getting alerts in Telegram

  1. On the Notifications tab, click Connect Telegram.
  2. Our Telegram bot opens. Press Start there to link the project to your chat. The settings page updates by itself once the link is made.
  3. If the link does not open, use Open in the Telegram app, or search for the bot name shown on the page and send it the message shown, using copy to copy it.
  4. When linked, the Telegram section shows Connected and the chat name.

To stop Telegram alerts, click Disconnect in the same section.

Note: If clicking Connect Telegram shows "Telegram notifications are not enabled on this platform", Telegram delivery is not available yet. Use email or SMS instead.

Where else to look

Related: Monitoring your instance, Troubleshooting: my instance is down or slow, Troubleshooting: domain or SSL problems.

If you get stuck, open a support ticket from the Tickets page or the chat widget.

Previous S3 storage, uploads and bulk backup actions Next Creating a project

Still stuck? Open a ticket from the app or talk to an engineer.