This module allows painless Sentry integration with Odoo.
auto_awesome What this module does
AI-generated from the code · Odoo 19.0This module connects your Odoo server to Sentry so that technical errors and warnings are automatically reported to your Sentry account. It is configured through the Odoo configuration file, not through screens in Odoo.
This module is a technical integration: it does not add any menu, screen, button or report inside Odoo. Instead, once installed and configured, it sends information about errors happening on the server to an external Sentry monitoring service.
- It is enabled and configured through the Odoo configuration file, using settings such as the Sentry connection address, environment name, release version, sample rates, and which loggers to exclude.
- It automatically reports server errors and log messages at the chosen level, and can also send a startup message when the Odoo server begins.
- It ignores common user-facing Odoo exceptions (for example access errors, validation errors and user errors) so that only real technical problems are reported.
- It adds context to reported errors, such as the database, user login, user id and request details, and it hides sensitive values like passwords, API keys, tokens and the session cookie before sending.
- It can read the Odoo git commit to use as the release identifier, and it wraps the web application so that web request errors are captured too.
It depends only on the base module and requires the external Python library sentry_sdk to be installed. No Odoo models are added or modified.
Depends on
Text generated by AI (DeepSeek) from reading the Odoo 19.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 8 confirmed, 1 with no information of 9 versions.
Sources · Odoo 12.0
Confirmed on 2026-11-03 in branch 12.0 of OCA/server-tools.
terminal Installation and usage
OCA documentation · Odoo 19.0Installation
Source · Odoo 19.0The module can be installed just like any other Odoo module, by adding the module's directory to Odoo addons_path. In order for the module to correctly wrap the Odoo WSGI application, it also needs to be loaded as a server-wide module. This can be done with the server_wide_modules parameter in your Odoo config file or with the --load command-line parameter.
This module additionally requires the sentry-sdk Python package to be available on the system. It can be installed using pip:
pip install sentry-sdk
Configuration
Source · Odoo 19.0The following additional configuration options can be added to your Odoo configuration file:
[TABLE]
Other client arguments can be configured by prepending the argument name with sentry_ in your Odoo config file. Currently supported additional client arguments are: with_locals, max_breadcrumbs, release, environment, server_name, shutdown_timeout, in_app_include, in_app_exclude, default_integrations, dist, sample_rate, send_default_pii, http_proxy, https_proxy, request_bodies, debug, attach_stacktrace, ca_certs, propagate_traces, traces_sample_rate, auto_enabling_integrations.
Example Odoo configuration
Below is an example of Odoo configuration file with Odoo Sentry options:
[options] (...) server_wide_modules = web,sentry
[sentry] sentry_dsn = https://:@sentry.example.com/ sentry_enabled = true sentry_logging_level = warn sentry_exclude_loggers = werkzeug sentry_ignore_exceptions = odoo.exceptions.AccessDenied, odoo.exceptions.AccessError,odoo.exceptions.MissingError, odoo.exceptions.RedirectWarning,odoo.exceptions.UserError, odoo.exceptions.ValidationError,odoo.exceptions.Warning, odoo.exceptions.except_orm sentry_include_context = true sentry_environment = production sentry_release = 1.3.2 sentry_odoo_dir = /home/odoo/odoo/ sentry_startup_message = true
Usage
Source · Odoo 19.0Once configured and installed, the module will report any logging event at and above the configured Sentry logging level, no additional actions are necessary.
[](https://runbot.odoo-community.org/runbot/149/14.0)
Installation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.