Monitoring
The MONITORING tab (Real-Time Monitoring) shows how much the branch's Odoo instance consumes: CPU, memory, network, database and backup sizes, plus HTTP traffic per URL. Use it to spot an overload or a slow page.
MONITORING tab of a production or staging branch. Available to every collaborator on the project.

Read the indicators
The cards at the top of the tab sum up the instance's state:
| Card | Content |
|---|---|
| Database Size | Size of the database. |
| Container Size | Size of the instance's container. |
| Backups Size | Total size of the branch's backups. |
| Network Traffic | Data sent (↑) and received (↓). |
| Memory Usage | Memory in use. |
| CPU Usage | CPU usage, as a percentage. |
Follow consumption in real time
The Network Traffic (Received / Sent), Memory Usage and CPU Usage charts update continuously.
- Update Interval: sets how often they refresh: 1s, 3s, 5s, 10s, 30s or 60s.
- Status: shows the state of the live metrics connection: Connecting..., Connected, Reconnecting..., Disconnected or Connection Failed.
Analyze HTTP traffic
-
In Http Lookback:, pick the period to analyze: from 30 seconds to 24 hours.
-
The Top Endpoints (Req/s) chart shows the busiest URLs.
-
The All Endpoints Metrics table details each URL:
Column Content Method HTTP method (GET, POST…). Endpoint The URL called. Req/Sec Requests per second. Avg Latency Average response time. Total Count Total number of calls over the period. Click a column header to sort, for example Avg Latency to find the slowest pages.
If no URL was called during the period, the table shows No active endpoints found.
If CPU or memory stay high for a long time, contact your Karizma representative to adjust the power allocated to the production instance. To analyze slow SQL queries, use SQL INSIGHTS.
See also
- LOGS to read the instance output.
- SQL INSIGHTS for database performance.