root-cause-localization

Correlate logs, trace spans, and dependency graphs to output structured JSON root cause reports.

3|2|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/openeuler-mirror/witty-diagnosis-agent --skill root-cause-localization-openeuler-mirror
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: root-cause-localization
Source: https://github.com/openeuler-mirror/witty-diagnosis-agent/tree/main/skills/root-cause-localization
Command: npx skills add https://github.com/openeuler-mirror/witty-diagnosis-agent --skill root-cause-localization-openeuler-mirror

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pandas, drain3, networkx, scikit-learn, pytz, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the complex process of identifying the root cause of system failures by correlating logs, trace data, and component dependencies, eliminating the need for manual, time-consuming investigation.

Core Features & Use Cases

  • Automated Root Cause Identification: Analyzes logs and traces to distinguish between root causes and secondary symptoms.
  • Temporal Correlation: Automatically aligns failure events across distributed components using time-window analysis.
  • Use Case: When a service experiences a latency spike, use this Skill to trace the request flow, identify the specific bottleneck component, and determine if the issue originated from a database lock or a network timeout.

Quick Start

Use the root-cause-localization skill to analyze the logs and traces for the disk fault scenario between 2024-05-20T10:00:00 and 2024-05-20T10:30:00.

Frequently Asked Questions about root-cause-localization

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

FAQPage Schema
How do I automate root cause analysis for distributed tracing and log data?

Automate root cause analysis by correlating log patterns, distributed trace spans, and service dependency graphs to pinpoint system failures. This process eliminates manual investigation by distinguishing actual root causes from secondary symptoms using temporal correlation.

How does temporal correlation work when debugging cascading errors across components?

Temporal correlation works by automatically aligning failure events across distributed components using time-window analysis. It matches telemetry data chronologically to identify the specific bottleneck component, such as a database lock or network timeout, causing cascading errors.

Do I need Python data processing tools to parse telemetry data for system diagnostics?

You need Python data processing tools to parse telemetry data for system diagnostics. The analysis relies on dependencies like pandas, drain3, networkx, and scikit-learn to process logs and traces, outputting structured JSON root cause reports.

What is the best way to identify performance bottlenecks from service failures without manual investigation?

The best way to identify performance bottlenecks is applying automated root cause analysis to trace request flows and service dependencies. This approach automatically parses telemetry data to locate the failing component and outputs a structured JSON report, bypassing manual investigation.

Why does root cause localization output a structured JSON report instead of raw logs?

Root cause localization outputs a structured JSON report to provide a parsed, machine-readable summary of system failures. This format separates the actual root cause from secondary symptoms clearly, making downstream automated alerting and remediation easier than raw logs.