Skip to Content

NM Sentry Logger

by
Odoo

$ 57.41

v 19.0 Third Party
Availability
Odoo Online
Odoo.sh
On Premise
Lines of code 1672
Technical Name neuralmedic_sentry_logger
LicenseOPL-1
Websitehttps://neuralmedic.de
You bought this module and need support? Click here!
Availability
Odoo Online
Odoo.sh
On Premise
Lines of code 1672
Technical Name neuralmedic_sentry_logger
LicenseOPL-1
Websitehttps://neuralmedic.de
NeuralMedic GmbH

NM Sentry Logger

A professional Odoo 19 integration for centralized Sentry telemetry across backend requests, Python logs, Owl/web client errors and shared frontend pages. The module ships with a clean settings interface for operators inside Odoo. Frontend errors are proxied through Odoo so the browser never receives the private Sentry DSN and the addon does not download executable code from external CDNs.

Sentry DSN Backend logging Frontend bridge Settings UI Apps-compliant delivery
Operational focus
Backend observability Captures Python exceptions and configurable log levels via the Sentry Python SDK.
Frontend telemetry Uses a local browser bridge that forwards unhandled errors and rejected promises through Odoo.
Administration surface Provides a dedicated settings section in Odoo for DSN, sampling, privacy flags and frontend filters.
Feature set

What the addon delivers

  • Global switches for backend and frontend monitoring.
  • Configurable DSN, environment, release and server identity.
  • Sampling controls for events and backend request traces.
  • Privacy and payload flags such as send_default_pii and stack traces.
  • Allow/deny URL filters, ignore-message rules, page throttling and static JSON tags.
  • A clean settings page for administrators inside Odoo.
Odoo NeuralMedic Sentry settings screenshot
Runtime model

How events reach Sentry

  • The addon stores operational settings in ir.config_parameter.
  • An ir.http hook ensures the backend SDK is initialized before requests are processed.
  • A lightweight frontend bridge listens for browser errors locally and submits them to a secured Odoo route.
  • The DSN stays server-side, which keeps the module aligned with Odoo Apps restrictions on downloading executable code.
  • Captured exceptions and log events appear in Sentry with release, environment and logger context.
Sentry issue details screenshot
Administrator workflow

Configuration flow

  • Install the addon and open Settings.
  • Set the Sentry DSN, environment and release.
  • Choose whether backend logging, frontend capture, rejected promise handling and tracing should be active.
  • Save the configuration and verify incoming events in your Sentry project.
Privacy and support

Operational notes

The module only sends data after an administrator enables it and configures a Sentry DSN. Captured data can include exception messages, request URLs, technical context and optional user information when send_default_pii is enabled. Backend and proxied frontend capture both require the Python package sentry-sdk in the Odoo runtime environment. Review your Sentry project settings and your internal privacy documentation before enabling personal-data capture in production.

For Debian/Ubuntu-style Odoo servers, the recommended installation command is apt install -y python3-sentry-sdk. Use a pip-based installation only if your Odoo runtime is managed in a dedicated virtual environment.

Commercial support is available from support@neuralmedic.de.

Built for NeuralMedic GmbH. Professional Sentry operations for Odoo 19 with an Odoo Apps friendly delivery model.

NeuralMedic Sentry Logger

Overview

NeuralMedic Sentry Logger adds a production-oriented Sentry integration to Odoo 19. It captures:

  • backend Python exceptions
  • selected backend log records
  • proxied frontend browser errors
  • proxied unhandled Promise rejections

The frontend path is implemented through a local Odoo bridge. The browser does not receive the Sentry DSN and the module does not fetch executable code from external CDNs.

Configuration

  1. Install the addon.
  2. Open Settings and locate the NeuralMedic Sentry section.
  3. Set the Sentry DSN, environment and release.
  4. Enable backend and/or frontend monitoring.
  5. Optionally configure sampling, URL filters, ignored messages and static tags.
  6. Save the configuration and verify incoming events in your Sentry project.

Important settings

  • Event sample rate controls overall sampling between 0.0 and 1.0.
  • Trace sample rate enables backend request transactions created by the addon.
  • Frontend events per page limits browser-side noise on a single page load.
  • Frontend allow URLs and Frontend deny URLs scope where frontend events may be sent.
  • Ignored frontend messages suppresses noisy browser messages before they reach Sentry.
  • Send default PII allows user-identifying information to be attached where available.

Privacy note

The addon only sends data once an administrator enables it and configures a Sentry DSN. Depending on your configuration, Sentry events may contain technical metadata such as request URLs, traceback information, browser details and optional authenticated user information. Applicable privacy policy: https://neuralmedic.de/datenschutz

Support

Commercial support for installation, configuration and issue handling is provided by NeuralMedic GmbH.

Dependency

The addon requires the Python package sentry-sdk in the Odoo runtime environment.

Recommended installation on Debian/Ubuntu Odoo servers:

apt install -y python3-sentry-sdk

If your Odoo instance runs inside a dedicated virtual environment, install sentry-sdk into that exact environment instead of the system Python.

Odoo Proprietary License v1.0

This software and associated files (the "Software") may only be used (executed,
modified, executed after modifications) if you have purchased a valid license
from the authors, typically via Odoo Apps, or if you have received a written
agreement from the authors of the Software (see the COPYRIGHT file).

You may develop Odoo modules that use the Software as a library (typically
by depending on it, importing it and using its resources), but without copying
any source code or material from the Software. You may distribute those
modules under the license of your choice, provided that this license is
compatible with the terms of the Odoo Proprietary License (For example:
LGPL, MIT, or proprietary licenses similar to this one).

It is forbidden to publish, distribute, sublicense, or sell copies of the Software
or modified copies of the Software.

The above copyright notice and this permission notice must be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS IN THE SOFTWARE.

Please log in to comment on this module

  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author or have a question related to your purchase, please use the support page.