Skip to main content

Check health and request an Odoo operation

Purpose: Interpret the monitoring screen and request a supported operation for the intended environment.

Prerequisites: Access to an entitled Corvus Cloud project. Use only operations enabled for your project-owner account and active project; visible buttons do not establish permission or service readiness.

Version: 1.1, Corvus Cloud customer console. Verified date: 28 October 2026. Authenticated controls and permission conditions are confirmed from source; live execution has not been verified for this guide.

Steps​

  1. Open the project and choose Monitoring. Check Observed health, Provider state, Service access, the observation time and whether the data is fresh.
  2. Use the available time filters to review resource pressure, load, network throughput and Odoo worker observations. Expand View latest values as a table, when offered, if you prefer values and timestamps to charts. Refresh the page when needed and check the measurement timestamp; a page refresh does not guarantee a fresh measurement.
  3. Review Environment routes and probes and Current alerts. Confirm the affected environment. Maintenance, restricted access and stale measurements have different meanings; a lack of current alerts is not a substitute for fresh health data.
  4. Open Operations and explicitly select the intended Environment; do not rely on a preselected value. For an investigation, select status, doctor or bounded logs. Status and doctor describe the managed node; the environment selection applies to logs, restart and backup. The reviewed project interface requests a bounded excerpt of Odoo logs for the selected environment; do not assume the public tour’s extra selectors are available in your project.
  5. If an Odoo restart is appropriate, select restart, read the confirmation and confirm the environment. Active requests may be interrupted. Cancel if the target or timing is wrong.
  6. Note the queued operation reference. Refresh the project page and review Builds & releases → Recent operations for its outcome. Expand Bounded output where available. A queued request is not a completed operation; check its status before submitting another request.
  7. For a backup request, follow Backups and recovery.

Expected result​

You can distinguish current service observations from release history and see whether the requested operation succeeded, failed or remains pending.

Troubleshooting​

  • Session expired: Reopen the console from the project in your Odoo account.
  • Stale, unknown or missing measurements: Check the observation time and allow a refresh. Contact support if the gap persists; do not treat missing measurements as healthy uptime.
  • Operation unavailable: Confirm owner access and that the project is active. Check recent operations before retrying, and give support the operation reference or displayed error.
  • Operation failed: Read its failure code and available output. Escalate with the project, environment, operation reference and time; keep passwords, tokens and private source out of support notes.
  • Service access is restricted: Review the notice in your Odoo account or contact Corvus. The monitoring screen says the VM and managed services remain present.

Limitations​

The current operation panel contains status, doctor, bounded logs, restart and local backup. Restart targets Odoo in one environment. This guide does not provide VM power-on, power-off, reboot, resize or deletion instructions because those customer controls were not established. General terminal and root access are not provided by this panel.

Guest network throughput and provider billing-period traffic are separate measurements. Node uptime is not a service-availability guarantee. Output may be truncated, and the project page shows a limited recent history.

The public monitoring and operations pages were checked live. Project controls and permission conditions were source-reviewed; no operation was submitted. For an incident, use Support handoff.