Know when something goes wrong in your Odoo
The Health tab spots known Odoo problems in production and tells you what usually fixes them. Slow queries, uptime and logs are one click away.
The Health tab
Problems found for you
We read your production Odoo log and watch its container. When a known problem shows up, it becomes a signal: info, warning or issue. Each one tells you what happened, how often, and what usually fixes it.
Hard to miss
A coloured dot shows on the project card and on the Health tab. When there's an issue, a banner shows at the top of the project too.
Signals that grow when a problem repeats
If the same problem keeps coming back, the signal moves up from info to warning to issue. When it stops, the signal clears on its own.
Mark it seen, or mute it
Mark a signal as seen, and your name shows next to it. Or mute it for a day, a week or 30 days. If it gets worse, it asks for attention again.
What the Health tab watches
Every signal carries a level in the dashboard, and it moves up or down as a problem repeats or clears.
Only your live Odoo is watched. Errors are normal on test copies.
Docs ↗Speed and uptime
Slow queries
See the database queries that cost the most time, with how often they run and how long they take. Only slow ones are listed. Values are never shown, so no business data appears.
CPU, memory and response time
Charts for each environment, over any range up to 30 days. See if a problem is in the code or in the resources.
Uptime you can trust
We check your Odoo every 30 seconds. Time spent on your own builds, updates and restarts doesn't count as downtime, and we show how much was left out.
Every address, checked
Each web address gets two checks: one on the server, with its certificate, and one from outside, through DNS. If one fails, you see why.
Your servers at a glance
On your own servers, watch CPU, memory and disk live, so you add space before it runs out.
Logs
One log for each step
Pick the Odoo log, the install log, the update log, the test log or the pip log. You go straight to the part that failed.
Follow a build as it runs
Watch the output while a build runs. Filter by date to find the moment something broke.
Logs that stay after the build is gone
Build logs are kept even after an environment is removed. They're kept for 30 days by default, and you can change that for each project.
Ask your AI agent
Connect Claude, Cursor or Windsurf, and ask why a build failed. It reads the logs, slow queries and metrics, and can't change anything.
Where each feature works
Frequently asked
Are staging and development watched too?
Does the slow query list show my data?
Does a restart I start count as downtime?
How long are logs kept?
Do I need to install anything to use this?
Want to see what the Health tab would find?
Tell us what's gone wrong with your Odoo before. We'll show you where it would show up on Skysize.