| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Community Apps Dependencies | Show |
| Lines of code | 869 |
| Technical Name |
do_error_inbox |
| License | LGPL-3 |
| Website | http://doincredible.com |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Community Apps Dependencies | Show |
| Lines of code | 869 |
| Technical Name |
do_error_inbox |
| License | LGPL-3 |
| Website | http://doincredible.com |
Ops Cockpit — Error / Traceback Inbox
A Sentry-lite triage inbox inside Odoo: server tracebacks captured, grouped by fingerprint, and worked new → acknowledged → resolved.
Free & open-source · License LGPL-3
Fingerprint grouping
Storm-proof
Secrets stripped
Triage board
The problem
Production errors live in log files you have to SSH into and grep — if you even know to look. Error Inbox brings them into Odoo, deduplicated by fingerprint and ready to triage, so errors get seen and actually fixed instead of silently recurring.
What it does
Capture, group and triage every server traceback — safely.
▸ Storm-proof grouping
The same traceback ten thousand times becomes ONE group with a counter and a bounded sample of occurrences — not ten thousand rows.
▸ Safe by construction
The logging handler never touches the database; it buffers in memory and a drain cron writes later in a fresh cursor. No aborted-transaction risk.
▸ Secrets stripped
Only the formatted traceback is stored, and request params are sanitised — passwords, tokens, sessions and card/SSN-like fields are redacted.
▸ Request context
Web errors carry the request path, the user and the sanitised parameters, so you can reproduce what went wrong.
▸ A real triage board
A kanban grouped by status with one-click acknowledge, resolve and ignore. Ignore a fingerprint to suppress all future storage and alerts.
▸ Alerts & retention
A throttled alert the first time a brand-new error appears; auto-vacuum purges resolved and ignored groups.
See it in action
The triage board — errors grouped by fingerprint and sorted into New, Acknowledged, Resolved and Ignored.
Error detail — full traceback, occurrence count, sanitised request context and one-click triage.
How it works
1
A logging handler fingerprints each error and buffers it in memory — zero database work in the request path.
2
A drain cron upserts one group per fingerprint in a fresh cursor and caps the stored sample.
3
A brand-new fingerprint raises a throttled alert; a recurring resolved error reopens automatically.
4
You triage from the kanban — acknowledge, resolve, or ignore a fingerprint for good.
Tech & compatibility
✓ Odoo 19
✓ Community & Enterprise
✓ Depends on: base, mail, do_ops_alert_base (free)
✓ Admin-only (tracebacks are sensitive)
✓ Never modifies Odoo core
✓ License: LGPL-3 (free & open-source)
Part of the Ops Cockpit suite
Three small modules that watch your production Odoo.
Alert Base
do_ops_alert_base
The free, shared, throttled alert engine that powers the suite (required dependency).
Cron Health Monitor
do_cron_health
Record, score and alert on every scheduled-action run.
Error / Traceback Inbox THIS MODULE
do_error_inbox
Capture and triage production tracebacks inside Odoo.
Do Incredible
http://doincredible.com · info@doincredible.com
★★★★★
Odoo 19 · Community & Enterprise · five-star support
Please log in to comment on this module