observer-log-analysis

Analyze OceanBase observer, election, and rootservice logs to determine root causes.

161|40|Updated Nov 22, 2022
One-click install
npx skills add https://github.com/oceanbase/obdiag --skill observer-log-analysis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: observer-log-analysis
Source: https://github.com/oceanbase/obdiag/tree/main/plugins/agent/skills/observer-log-analysis
Command: npx skills add https://github.com/oceanbase/obdiag --skill observer-log-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This SOP provides a structured workflow to collect, filter, and interpret OceanBase cluster logs from observer/election/rootservice components for rapid RCA.

Core Features & Use Cases

  • Stage-based workflow: gather logs, analyze, and optionally inspect specific file segments.
  • Supports multi-cluster investigations and trace_id/keyword filtering to pinpoint issues.
  • Provides safe, stepwise guidance to avoid misconfigurations and OBProxy misuse.

Quick Start

Run the observer-log-analysis SOP on the target cluster to collect observer/election/rootservice logs for the last 30 minutes and filter by the given trace_id.

Frequently Asked Questions about observer-log-analysis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze OceanBase observer logs for root cause analysis?

To analyze OceanBase observer logs for root cause analysis, apply a structured workflow to collect, filter, and interpret observer, election, and rootservice outputs. This identifies cluster issues and determines recommended actions safely.

How do I filter OceanBase cluster logs by trace_id?

Filter OceanBase cluster logs by trace_id using keyword filtering within the analysis workflow. This pinpoints specific issues across multi-cluster environments by isolating relevant observer and election log entries.

What is the best way to troubleshoot OceanBase election issues from logs?

Troubleshooting OceanBase election issues from logs involves gathering recent election outputs and applying stepwise guidance to interpret root causes. This non-destructive process avoids misconfigurations and OBProxy misuse.

Can I inspect specific file segments of observer logs without modifying the cluster state?

You can inspect specific file segments of observer logs without modifying the cluster state. The analysis enforces safe, non-destructive methods by guiding users to gather, filter, and review outputs only.

Does observer log analysis support multi-cluster investigations?

Observer log analysis supports multi-cluster investigations by applying a standardized SOP across environments. It collects observer, election, and rootservice logs to rapidly determine root causes and recommended actions.

What limitations exist when diagnosing OceanBase rootservice issues?

Diagnosing OceanBase rootservice issues is limited to read-only log analysis and does not modify cluster state. The stepwise guidance focuses on safe interpretation to prevent misconfigurations and OBProxy misuse.