Server Monitor Pro
Know your Odoo is healthy.
Before your users tell you.
Servers, workers, PostgreSQL, services, backups and certificates — in one dashboard, inside Odoo. One server or five hundred.
| Community & Enterprise | No SaaS · No phone-home | Unlimited servers |
Your Odoo runs your business.
So why does its health live in four terminals, a cron log, and someone’s calendar reminder about an SSL certificate?
Nothing is watching Disk does not fill suddenly. It fills predictably over weeks, then crosses 100% at 03:00 on a Sunday. Certificates announce their expiry ninety days in advance. These are not surprises — they are unwatched counters. | The evidence is gone top is instantaneous. By the time a human looks, the spike has passed. Without retained history, “is 70% CPU normal?” is unanswerable and every diagnosis restarts from zero. | Nobody correlates A worker crash at 14:02 and a memory spike at 14:01 are the same event — observed in two terminals, by two people, an hour apart. |
It knows Odoo, not just Linux.
This is the difference between a generic monitor and one that has read Odoo’s source.
⚠ The insight no generic tool can produce
Your 8 workers can open 704 database connections. PostgreSQL allows 100.
Odoo’s connection pool is per-process, so every
worker opens its own pool of up to
db_maxconn.
The ceiling is (workers + max_cron_threads + 1) × db_maxconn.
It is silent until load arrives, extremely common, and invisible to any monitor
that does not know this about Odoo. We compute it from two numbers we already collect.
Slow query → Odoo method We show the model and method that issued the slow query, not just the SQL. Datadog can show you the statement; it structurally cannot tell you that account.move._post is what ran it. | Memory, measured correctly Odoo enforces limit_memory_soft against virtual memory on Linux, not RSS. Chart the intuitive number and your dashboard shows workers at 30% of limit while they recycle constantly. We chart what Odoo actually enforces. | Workers, seen honestly An Odoo worker cannot see its siblings — the registry that looks like it can is a fork-time snapshot that excludes the reader. We enumerate the real process tree instead. |
It catches what silence hides.
Your backup tool emails you when a backup succeeds. What emails you when one quietly stops?
Nothing does. You cannot fire an event for something that did not happen.
A backup that silently stops — cron disabled, credentials expired, profile
deactivated — produces no signal at all. Everything looks fine. The last job
still says success. It just happens to be from six weeks ago.
Only an external watcher with an expectation of cadence catches that. Server Monitor Pro watches for the backup that did not arrive — and it works whether or not you use any backup module, because a
Only an external watcher with an expectation of cadence catches that. Server Monitor Pro watches for the backup that did not arrive — and it works whether or not you use any backup module, because a
pg_dump in a
shell cron deserves the same protection.
Alerts you will still believe in six months.
Alert fatigue is how a working monitoring tool dies. Every alert can be technically correct and the product still ends up in a folder nobody reads.
Every rule needs a duration “CPU > 90%” fires on every garbage collection. “CPU > 90% for 5 minutes” fires on a problem. The duration is a required field, not an option. | Seasonality, on by default Odoo load is strongly diurnal and weekly. Anomaly detection compares Monday 09:00 to previous Monday 09:00s — a flat baseline would alert every weekday morning. | Silence is never green A server that stopped reporting is not healthy. It renders distinctly and takes a full penalty in the health score. Rendering it green is the most dangerous thing a monitoring dashboard can do. |
It refuses to guess Capacity forecasts come with a fit quality. When the trend is not clear enough to trust, it says “insufficient trend” and shows no date — because a confidently wrong date gets budgeted against. | Alerts become work An incident carries an owner, an activity and a chatter trail. A Grafana panel cannot assign the DBA and track it to closure. | Unavailable is not zero A metric we could not read is recorded as unavailable, never as 0. A zero drags averages down and can suppress the very alert that should have fired. |
What you get
|
✓Executive dashboard, health score & trends ✓CPU, per-core, load, RAM, swap ✓Disk usage, inodes, I/O, network ✓Uptime, reboot detection, top processes ✓Odoo workers, memory vs limits, recycles ✓HTTP response time & logged-in users ✓Database size & growth trend ✓Connections, idle-in-transaction, locks
|
✓Slow queries with the Odoo code path ✓Cache hit, deadlocks, autovacuum ✓Services, SSL & domain expiry ✓Backup staleness watchdog ✓Slack, Teams, Telegram, Discord, webhook, email ✓Capacity forecasting & anomaly detection ✓Maintenance console with an audit trail ✓PDF & Excel reports, multi-company
|
Honest about the edges
Above ~500 servers, or sub-15-second resolution? Use Prometheus.
At that scale a purpose-built time-series database wins on physics, and we would
rather tell you than sell you the wrong thing. This is built for the 99% of Odoo
estates that are smaller than that — and that today have no monitoring at all.
Everything else here we have measured: 500 agents at one report a minute, p95 ingest 84ms, zero data loss.
Everything else here we have measured: 500 agents at one report a minute, p95 ingest 84ms, zero data loss.
Community and Enterprise. Your data never leaves your server.
Requires the free Ops Cockpit alert engine
(do_ops_alert_base), included.
Do Incredible · doincredible.com · info@doincredible.com
Do Incredible · doincredible.com · info@doincredible.com
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Community Apps Dependencies | Show |
| Lines of code | 8147 |
| Technical Name |
do_server_monitor_pro |
| License | OPL-1 |
| Website | http://doincredible.com |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module