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

Monitoring your instance

How to read the Monitoring tab (uptime, response time, storage, CPU and memory charts, network and disk), drill from a chart into the logs, run an AI log analysis, and use the Logs tab.

Opening the Monitoring tab

  1. Open the instance in the Console.
  2. Click the Monitoring tab.

In a workspace, members need the Monitoring permission on the project to see this tab, and the Logs permission to open logs from a chart.

Reading uptime and response time

When external uptime monitoring is active for the instance (usually production), the top of the tab shows four cards:

  • Current status: Up, Down, Degraded, Paused or Pending, with how long it has been in that state.
  • Last check: when the instance was last checked, and how often it is checked.
  • Avg Response Time: in milliseconds.
  • Last 24 hours: the uptime percentage, with the number of incidents and total down time.

Below them, the Last 24 Hours strip shows availability across the day, and a second card shows Last 7 days, Last 30 days and Last 365 days with the same figures. A new monitor shows "Collecting data..." until it has history. The uptime percentage and response time also appear in the Console header.

If automatic restarts keep failing, a red banner at the top of the tab reads "This instance is down and is not restarting", with the reason. Our team is alerted in that case.

Checking storage use

The Storage card shows the size of the Filestore volume and the Database volume, and when they were last measured. Sizes are measured periodically, so they can lag a little. An external filestore shows "External, not measured".

Using the CPU and memory charts

Two charts show CPU and memory usage as percentages: Odoo Container - CPU & Memory Usage and Database Container - CPU & Memory Usage.

  1. Pick a time range: 6h, 24h, 48h, 7d or 30d.
  2. Click Refresh to reload, or tick Auto-refresh (30s) to keep the charts updating. "Last updated" shows when the data was fetched.
  3. Drag across a chart to zoom in. Both charts zoom together.
  4. Double-click a chart or click Reset zoom to zoom back out.

Sustained CPU near 100 percent, or memory climbing to a ceiling, usually explains slowness.

Viewing network, disk and processes

  1. Below the charts, click Network, Disk & Processes to expand it.
  2. Read the charts for the Odoo Container and the Database Container: network in and out, disk read and write, and process count.

Gaps mean the rate could not be measured, usually because the container restarted and its counters reset.

Opening the logs at a point in time

  1. Click any point on a CPU and memory chart.
  2. A log dialog opens, titled Odoo Container Logs or Database Container Logs depending on the chart, showing the logs around that moment.
  3. Use the copy icon (Copy logs) to copy the text, or the close icon to return.

Analyzing logs with AI

AI analysis uses your own AI provider account and key.

  1. In the log dialog, click the brain icon (Analyze with AI).
  2. The first time, the AI Provider Settings panel opens. Choose a Provider: Anthropic (Claude), OpenAI, Groq, Ollama (local) or Custom (OpenAI-compatible).
  3. Optionally enter a Model. Leave it empty to use the default.
  4. Enter an API Key, or a Base URL for Ollama and custom providers.
  5. Click Save & Analyze.
  6. Read the AI Analysis summary of errors and recommended actions, then type in Ask a follow-up question... to continue.

To change provider or key later, click the gear icon (Change AI settings) in the analysis panel.

Using the Logs tab

The Logs tab shows the raw Odoo container log. In a workspace it requires the Logs permission.

  1. Open the instance in the Console and click Logs.
  2. Click Refresh to load the latest lines.
  3. To follow the log live, set Interval (in seconds) and click Stream. Click Stop to end streaming.
  4. Click Clear to empty the view, or Download to save the log as a text file.

The footer shows the number of Lines and when the log was last updated.

Related: Alert notifications (email and SMS), Troubleshooting: my instance is down or slow, Member permissions and resource access.

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

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