obdiag icon indicating copy to clipboard operation
obdiag copied to clipboard

obdiag (OceanBase Diagnostic Tool) is designed to help OceanBase users quickly gather necessary information and analyze the root cause of the problem.

Results 111 obdiag issues
Sort by recently updated
recently updated
newest added

### Describe your use case 现有的obdiag gather perf 命令收集的数据是perf的原始数据,不方便用户直接查看 ### Describe the solution you'd like 希望obdiag gather perf 命令收集的数据再加工一下,方便用户查看火焰图 ### Describe alternatives you've considered _No response_ ### Additional context _No...

enhancement

### Describe your use case 现有的obdiag analyze log分析的时候是以节点、日志文件为维度进行分析,不足以更细致的定位具体租户问题。 ### Describe the solution you'd like 希望增加参数,支持展现租户维度的错误信息统计 ### Describe alternatives you've considered _No response_ ### Additional context _No response_

enhancement

### Describe your use case obproxy部署在了应用侧,可能有上千个obproxy节点,按照现有的逻辑需要全部扫描一遍obproxy ### Describe the solution you'd like 是否可以关联gv$ob_sql_audit中的client_ip去寻找对应节点的obproxy,然后动态再筛选一下obproxy节点,这样可以省去很多无关节点的扫描 ### Describe alternatives you've considered _No response_ ### Additional context _No response_

enhancement

### Describe your use case ob是分布式的集群,节点环境的影响需要关注,比如网络丢包: ![image](https://github.com/oceanbase/oceanbase-diagnostic-tool/assets/35712518/da5ee689-b71d-4154-b362-bad65c3a5d1d) ### Describe the solution you'd like obdiag巡检中增加网络丢包的检测 ### Describe alternatives you've considered _No response_ ### Additional context _No response_

enhancement

### Description 1、影响卡合并的要素有哪些,能否实现指标化?需要分析哪些指标? 2、这些指标分析后可能形成几种可能性(根据指标异常与正常的组合,这种组合有多少种?)

### Describe your use case ob的线程模型为固定的网络线程数量接收请求,由网络线程解出请求所属的租户,push给租户的工作队列,再由租户的工作线程从工作队列中pop请求处理,也就是一个典型的生产者消费者模型。当生产速度长期大于消费速度时,租户的工作队列就会打满,并返回-4019。即使没有打满,也会表现出请求排队耗时长。 ### Describe the solution you'd like OB租户队列积压的问题如何排查,期望obdiag能支持这个场景 ### Describe alternatives you've considered _No response_ ### Additional context _No response_

enhancement

### Description 很多情况下只是某个租户出现异常,这时再进行集群级别的分析和信息收集比较浪费时间,我们只会关系租户问题能否解决。

enhancement
help wanted

### Description 老师您好,我们这边通过连接业务租户定时(每分钟)select 1的方式验证OB数据库的sql响应时间,发现有租户select 1的响应时间很长,这个怎么去巡检下或分析下

enhancement
help wanted
question

### Description 3.x 4.x 我们这边环境都遇到过应用连接数据库慢的场景;业务通过proxy连接数据库慢,直连租户所在的2881端口连接还是慢,,希望通过obdiag实现ob数据库连接慢场景进行诊断和分析

help wanted
question

### Describe the bug obdiag gather stack的时候报错 /tmp/obstack_x86_64_7: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory ### Environment alma系统 ### Fast reproduce...

bug