ocp 的 SQL 诊断 没有数据

【 使用环境 】 测试环境
【 OCP 】
【 使用版本 】社区版4.2
【问题描述】ocp 的 SQL 诊断 没有数据
ocp 启动后 所有 agent都存活，ocp_monior db 中 很多 表没数据 列入ob_hist_sql_audit_sample;
日志中报错：caller=host/custom.go:670:doCollectCoredumpTime: get observer coredump time failed, err: open : no such file or directory

monagent.log 里 grep ERROR.*sql_audit

这里有一个排查方法。可以参考下。
提供下完整日志

monagent.err.log.txt (261.5 KB)

monagent.log 有好多 这样的错误：
2024-04-11T15:30:18.16982+08:00 ERROR [46082,98c0cf852d63ae76] caller=engine/pipeline_module_callback.go:40:addPipeline: add pipeline module config result status: failed, description: module monitor.ob config already exists fields:, module=monitor.ob, duration=“277.902µs”

monagent.log.411.zip (1.2 MB)

host.log.alarm
monitor.custom
monitor.mlog
monitor.node.host
monitor.ob
monitor.ob__version_compatibility_test
monitor.ob__version_compatibility_test_3.2.1
monitor.resource.trends
node.custom
ob.custom
ob.log.alarm
这些 模块都报错 config already exists field

ocp 页面 重新开关 sql检测功能后 提示
2024-04-11T16:32:07.76125+08:00 ERROR [29383,195e99702ac728b5] caller=engine/pipeline_manager.go:183:handleEvent: check exist failed fields: error=“handleUpdateEvent module monitor.ob.sql.audit does not exist”, pipelines=monitor.ob.sql.audit
2024-04-11T16:32:07.76133+08:00 ERROR [29383,195e99702ac728b5] caller=engine/pipeline_manager.go:136:func1: pipeline manager handle update event failed fields:, eventType=update, error=“handleUpdateEvent module monitor.ob.sql.audit does not exist”, module=monitor.ob.sql.audit, duration=“156.752µs”
2024-04-11T16:32:07.76145+08:00 ERROR [29383,195e99702ac728b5] caller=engine/pipeline_module_callback.go:149:func2: update pipeline module config failed fields: error=“update pipeline module config failed description update module monitor.ob.sql.audit failed, reason: handleUpdateEvent module monitor.ob.sql.audit does not exist”
2024-04-11T16:32:07.84865+08:00 ERROR [29383,fc0483b5a75ef3a9] caller=engine/pipeline_manager.go:183:handleEvent: check exist failed fields:, pipelines=monitor.ob.sql.plan, error=“handleUpdateEvent module monitor.ob.sql.plan does not exist”
2024-04-11T16:32:07.84873+08:00 ERROR [29383,fc0483b5a75ef3a9] caller=engine/pipeline_manager.go:136:func1: pipeline manager handle update event failed fields: error=“handleUpdateEvent module monitor.ob.sql.plan does not exist”, module=monitor.ob.sql.plan, eventType=update, duration=“118.085µs”
2024-04-11T16:32:07.84897+08:00 ERROR [29383,fc0483b5a75ef3a9] caller=engine/pipeline_module_callback.go:149:func2: update pipeline module config failed fields: error=“update pipeline module config failed description update module monitor.ob.sql.plan failed, reason: handleUpdateEvent module monitor.ob.sql.plan does not exist”
2024-04-11T16:32:07.92008+08:00 ERROR [29383,666b689288b8b803] caller=engine/pipeline_manager.go:183:handleEvent: check exist failed fields:, pipelines=monitor.ob.sql.transaction, error=“handleUpdateEvent module monitor.ob.sql.transaction does not exist”
2024-04-11T16:32:07.9202+08:00 ERROR [29383,666b689288b8b803] caller=engine/pipeline_manager.go:136:func1: pipeline manager handle update event failed fields:, eventType=update, module=monitor.ob.sql.transaction, error=“handleUpdateEvent module monitor.ob.sql.transaction does not exist”, duration=“194.047µs”
2024-04-11T16:32:07.92073+08:00 ERROR [29383,666b689288b8b803] caller=engine/pipeline_module_callback.go:149:func2: update pipeline module config failed fields: error=“update pipeline module config failed description update module monitor.ob.sql.transaction failed, reason: handleUpdateEvent module monitor.ob.sql.transaction does not exist”
2024-04-11T16:32:07.95593+08:00 ERROR [29383,4352deeca4f13a05] caller=engine/pipeline_manager.go:183:handleEvent: check exist failed fields: pipelines=monitor.ob.sql.plan.monitor, error=“handleUpdateEvent module monitor.ob.sql.plan.monitor does not exist”
2024-04-11T16:32:07.95602+08:00 ERROR [29383,4352deeca4f13a05] caller=engine/pipeline_manager.go:136:func1: pipeline manager handle update event failed fields: eventType=update, error=“handleUpdateEvent module monitor.ob.sql.plan.monitor does not exist”, duration=“175.398µs”, module=monitor.ob.sql.plan.monitor
2024-04-11T16:32:07.95633+08:00 ERROR [29383,4352deeca4f13a05] caller=engine/pipeline_module_callback.go:149:func2: update pipeline module config failed fields:, error=“update pipeline module config failed description update module monitor.ob.sql.plan.monitor failed, reason: handleUpdateEvent module monitor.ob.sql.plan.monitor does not exist”

这个环境是怎么部署的，ob集群是通过ocp部署的吗？

不是 是obd 部署的 observer obproxy obagent ，然后docker 部署的ocp

问题已经解决了，但是没找到原因，操作就是再ocp 集群页面 多次开关 sql 诊断功能开关， 过了ocp一会
自己就好了