1. Are You Facing These Problems?

In many Odoo projects, issues are only noticed after complaints. During troubleshooting, teams often lack clear evidence.

• Users report “it is slow”, but the exact slow scope is unknown
• Errors happen intermittently and are hard to replay
• Teams cannot clearly explain when degradation started

Background: this module was built from these real production pains.

2. What Problem This Module Solves

Common Odoo production pain is: when slow/error events happen, teams cannot see clearly, cannot explain clearly, and cannot replay clearly. This module collects runtime data in a structured way and visualizes it, turning performance and incidents from “feelings” into “evidence”.

• See clearly: trends, heatmaps, and sampled evidence
• Explain clearly: metrics with time window and context
• Replay clearly: events and traces for post-incident review

3. Who It Serves

• Platform engineering and implementation teams
• Operations and on-call teams
• Project managers and business owners
• Developers doing self-test and debugging

4. How to Use

• Keep it enabled for daily monitoring and alerting
• Or enable it only when slow behavior appears, then monitor and analyze bottlenecks

1. 你是否遇见这些问题？

很多 Odoo 项目中，问题往往是用户先感知、技术后定位，排查时常常“有现象、缺证据”。

• 用户反馈“变慢了”，但慢在什么环节不清楚
• 错误偶发且不稳定，难以复现和回放
• 很难准确说明性能劣化从什么时候开始

背景：这个模块正是基于这些真实问题背景开发的。

2. 这个模块解决什么问题

Odoo 线上问题常见痛点是“出了慢/错，但看不见、说不清、回不去”。本模块把运行数据结构化采集并可视化，让性能与异常从“体感”变成“证据”。

• 看得见：趋势、热力图、样本明细
• 说得清：指标、窗口、上下文信息可解释
• 回得去：事件与轨迹可复盘

3. 为谁解决

• 平台研发与实施团队
• 运维与值班团队
• 项目管理与业务负责人
• 开发人员自测与排错

4. 如何使用

• 可以常开：用于持续监测系统状态并执行告警
• 也可以按需开启：当出现变慢迹象时再打开，快速监控并分析慢点