obdiag V4.1.0

Version information

• Published: February 12, 2026
• Version number: V4.1.0

New version changes function points

Added new commands and scenarios

• [New] The obdiag display scene run command adds a new clog log volume/capacity statistics scene (observer.clog_volume_statistics), which supports displaying the clog log disk capacity and usage of each node/tenant. For scenario usage, please refer to clog log volume/capacity statistics.

• [New] Added obdiag display-trace <trace_id> command, which is used to view detailed logs of a single obdiag execution to facilitate troubleshooting command execution problems. After executing some commands, the terminal will prompt for available trace_id.

Function enhancement

• [New] obdiag gather perf command supports generating flame graph SVG to facilitate analysis of CPU hot spots. flamegraph.pl and stackcollapse-perf.pl need to be provided under dependencies/bin. For detailed introduction, please refer to Flame Diagram/Bianque Diagram Collection.

• [New] The --tenant_id option is added to the obdiag analyze log command, which supports filtering error statistics by tenant; the analysis logic is reconstructed and supports first collecting compressed packages and then decompressing and analyzing them locally to improve the efficiency of large log analysis. For detailed introduction, please refer to One-click Diagnosis Analysis Log.

• [New] obdiag analyze flt_trace supports filtering OBProxy nodes by client IP and obtains client IP from SQL audit view, which is compatible with multi-version OceanBase database. For detailed introduction, please refer to One-click full-link diagnostic log analysis.

• [New] Add statistical information histogram (table level/partition level) to the report generated by obdiag gather plan_monitor to facilitate analysis of execution plans and statistical information. For detailed introduction, please refer to SQL details collection.

• [Optimization] Card merging RCA scene (obdiag rca run --scene=major_hold) adds memory throttling check and dump/merge/freeze related information query to facilitate locating the cause of merging stuck. For detailed introduction, please refer to Root Cause Analysis Scenario: Card Merger.

• [Change] The inspection framework is refactored from checker to check, using TaskBase and Python inspection task system; a large number of inspection tasks are migrated from YAML to Python implementation, the behavior is consistent with V4.0.0, and supports flexible execution through --observer_tasks/--obproxy_tasks and other options of obdiag check run. For detailed introduction, please refer to One-click cluster inspection.

Installation and Build

• [Note] V4.1.0 continues to use pyproject.toml to manage dependencies and builds. For details, see obdiag installation.