Monitoring

import { Aside } from ‘@astrojs/starlight/components’;

Deploy Monkey provides built-in monitoring for your servers and Odoo instances — tracking server resources, instance health, and worker usage.

Server Metrics

Deploy Monkey collects server-level metrics every 5 minutes via SSH:

Metric	Description
CPU Usage	Percentage of CPU being used
Load Average	System load (1m, 5m, 15m)
Memory Usage	RAM consumption (used %, used MB, total MB)
Disk Usage	Storage used (used %, used GB, total GB)
Containers	Running and exited container counts

Metrics are available as raw samples (up to 14 days) and hourly rollups (up to 180 days).

Viewing Server Metrics

Navigate to your server’s Monitoring tab to see:

• Current metric values (CPU, RAM, Disk, Load)
• Timeseries charts with range selection (1h, 6h, 24h, 7d)
• Container status overview

Instance Health

Each instance is monitored with two signals:

1. Container status — checked via SSH during the server metrics pass (is the Docker container running?)
2. HTTP probe — checks https://domain/web/login every 5 minutes

These signals combine into an overall health state:

State	Meaning
Healthy	Container running AND HTTP responding
Degraded	One signal OK, one failing
Down	Both signals failing

Uptime Tracking

Instance health is rolled up hourly, giving you:

• Uptime percentage over time
• Average and max response times
• Health state distribution (healthy/degraded/down counts per hour)

Worker Usage

Deploy Monkey tracks Odoo worker process activity to help you make scaling decisions.

Metric	Description
Configured Workers	Worker count set in instance settings
Detected Processes	Total Odoo/Python processes in the container
Busy Workers	Processes that consumed CPU in the measurement window
Usage %	Busy workers ÷ configured workers × 100

Worker data is collected during the regular server metrics SSH pass — no additional connections needed.

If worker usage is consistently above 80%, consider increasing the worker count in your instance settings.

Alerts

Deploy Monkey evaluates alert rules against your metrics and health data:

Alert	Default Threshold
CPU > threshold	80% sustained
Memory > threshold	85% sustained
Disk > threshold	90%
High load	Load > 2× CPU cores
Instance down	Container + HTTP both failing
Instance degraded	One health signal failing
Slow responses	Response time > 5000ms

Alert Lifecycle

1. Open — threshold breached, notification sent
2. Acknowledged — operator has seen it
3. Resolved — condition recovered (auto or manual)

Alerts are visible in the Alerts section of the control panel and as notifications in the bell menu.

Alert thresholds are configured by the platform administrator in the Odoo backend under Deploy Monkey → Monitoring → Alert Rules.

Data Retention

Data Type	Retention
Raw metric samples	14 days
Hourly rollups	180 days
Resolved alerts	180 days