Skip to main content

View Logs

Logs help you understand what a deployment is doing, whether it is a build that failed or a running instance throwing errors. Skysize shows logs per deployment.

Open the logs for a deployment​

  1. Open your project and go to the Deployments tab.
  2. Find the deployment you want to inspect and click View Logs (or open the deployment to reach its detail page).
  3. On the deployment detail page, open the Logs tab.

The build and install output streams here while a deployment is running, and the logs remain available afterwards.

Choose which log to read​

The Logs tab has a Log file selector. Use it to switch between the logs available for the deployment:

Log fileWhat it contains
odoo.logRuntime activity of the running instance: HTTP requests, errors, cron jobs, tracebacks
install.logOutput of the module installation that created the deployment
update.logOutput of the module update run on each new deployment of existing code
tests.logOutput of the test run, when tests are enabled for the branch
requirements.logOutput of the pip install of your repository's requirements.txt, if you have one

Filter and refresh​

  • Start date / End date: narrow the view to a specific time range. Click Clear dates to remove the filter and return to the full view.
  • Refresh logs: fetch the latest lines. The "Last updated at" indicator shows when the view was last refreshed.
  • Scroll up to load earlier lines; newer lines continue to load as the deployment produces them.
note

Build and deployment logs are stored durably, so they remain available after the deployment has finished, and even after it is later removed.

Tips for reading logs​

  • Look for tracebacks. Python errors appear as multi-line tracebacks ending with the exception type and message. Search for Traceback to jump to them.
  • Focus on the right severity. Odoo logs at DEBUG, INFO, WARNING, ERROR, and CRITICAL. Scan for ERROR and CRITICAL first.
  • Deployment failed? Open the failed deployment's Logs tab and select the build/install log. Module XML/parse errors, missing fields, and failed migrations surface there.
  • Runtime 500 error or broken view? Select the Odoo server log and check the entries around the time of the error.
  • Module fails on a missing Python library? Select requirements.log. It shows whether pip installed your dependencies and, if not, why. See Install Python Packages.
  • A cron / scheduled action misbehaving? Its errors are logged in the server log at ERROR level.