Odexalabs Vigil: The Odoo Operations Suite

Why Odoo needs a purpose-built operations dashboard

Generic infrastructure monitoring — Grafana, Datadog, New Relic — tells you your server has 87% RAM used and a load average of 4.2. It does not tell you that a specific Odoo cron job silently stopped running three days ago, that an unused index on account_move_line is consuming 4 GB, or that the hr_expense module is responsible for 30% of your slow queries. Vigil Suite closes that gap. Every metric on the dashboard maps back to something you can act on inside Odoo: a stuck scheduled action to re-run, a table to VACUUM, a module to roll back, a backup job to retry.

Cron reliability is the silent killer of production Odoo

Odoo's scheduled actions run recurring business logic — invoice reminders, mail queue flushing, inventory reordering, calendar sync. When a cron silently fails (raises an unhandled exception then gets auto-deactivated), the business logic simply stops. Users don't notice for days or weeks. Vigil's three-tier cron detection surfaces overdue, silently-failed, and auto-deactivated crons on the dashboard the moment it happens, with a one-click drill-down to the offending record and its most recent traceback.

PostgreSQL bloat compounds quietly

Odoo writes heavily. Every stock move, every mail message, every audit log entry adds rows to already large tables. Without VACUUM, dead tuples accumulate, indexes bloat, and query planner statistics drift. The result is a database that runs fine for six months, then degrades noticeably over the next six. Vigil's Storage & Bloat analyzer surfaces the top offenders by dead-tuple ratio, lets you run VACUUM ANALYZE with one click, and separately tracks index bloat where autovacuum can't help. The Over-Indexed Tables signal flags where your total index size exceeds heap size — a strong indicator of duplicated or unused indexes that are costing you both storage and write throughput.

Backup that survives worker limits

Odoo's built-in database backup is a foreground HTTP download — it holds a worker for the entire dump duration. For a 20 GB database on a modest server, that's 15-30 minutes of worker time; on Odoo.sh with a 300 second HTTP timeout, it simply fails. Vigil's Backup Manager streams the dump in chunks directly to your chosen destination — Amazon S3, Google Drive, OneDrive, Dropbox, SFTP, FTP, or local disk — with resume-on-failure semantics and multi-destination writes for redundancy. Retention policies prune old backups automatically so your storage bill doesn't grow unbounded.

Docker-aware from day one

Running Odoo in Docker changes what RAM you can trust. psutil.virtual_memory() reports the host's memory, not the container's — misleading you into thinking you have headroom you don't. Vigil detects cgroup limits and reports RAM against the container ceiling. Worker counting adapts to threaded vs multi-worker deployments; log tailing falls back to in-memory ERROR capture when STDOUT logging is in use. The dashboard works identically whether you run ./odoo-bin, systemd, docker-compose, or docker swarm.