obdiag-check-rca

To run an RCA workflow, map user-described cluster symptoms like high CPU or slow queries to specific RCA scenes, then orchestrate check_cluster and rca_run workflows to identify root causes and recommended actions.

The standard SOP for cluster health checks guides users through check_cluster and check_list workflows, integrating with rca_run and rca_list entry points to perform comprehensive health assessments and start RCA workflows.

Yes, you can select a specific cluster for diagnostics in multi-cluster environments by configuring the optional cluster selection via the cluster_config_path parameter before executing check_cluster and RCA workflows.

Yes, RCA scene mapping integrates clearly with related log-analysis components including observer-log-analysis, observer-sql-analysis, and obproxy-log-analysis to coordinate end-to-end diagnostics and actionable outputs.

You need to perform an initial cluster health check using check_cluster before initiating an RCA run for an identified scenario, ensuring accurate scene mapping and actionable root cause analysis for observed symptoms.