Logs Analysis

Analyze sosreport logs to identify root causes of system failures.

112|305|Updated Oct 10, 2025

Search Tags:#error detection #root cause analysis #log analysis #system logs #sosreport #journald #system troubleshooting

Ready to run

npx skills add https://github.com/openshift-eng/ai-helpers --skill logs-analysis

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Logs Analysis
Source: https://github.com/openshift-eng/ai-helpers/tree/main/plugins/sosreport/skills/logs-analysis
Command: npx skills add https://github.com/openshift-eng/ai-helpers --skill logs-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the time-consuming manual process of digging through complex system logs to identify the root causes of failures, crashes, and performance issues.

Core Features & Use Cases

Comprehensive Log Analysis: Automatically scan journald, system, and application logs for error patterns, kernel panics, OOM events, and service failures.
Structured Error Reporting: Generate detailed summaries with error statistics, timelines, and actionable recommendations.
Use Case: When a production server crashes unexpectedly, use this Skill to analyze the sosreport logs and quickly identify whether it was caused by memory exhaustion, kernel panic, or application failure.

Quick Start

Use the logs analysis skill to examine the extracted sosreport in the current directory and provide a summary of critical errors and their root causes.

Frequently Asked Questions about Logs Analysis

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

FAQPage Schema

How do I analyze sosreport logs to find root causes of system failures?▼

Sosreport log analysis scans journald, kernel messages, and application logs to identify error patterns, panics, OOM events, and service crashes. The Skill extracts error counts, timelines, top messages, affected components, and remediation guidance to pinpoint root causes quickly.

Can I detect kernel panics and out-of-memory events in system logs?▼

Yes. The Skill recognizes kernel panics, OOM events, segmentation faults, and service failures across journald and traditional log sources, extracting specific error patterns and timelines to identify what triggered the failure.

What's the best way to troubleshoot a production server crash using logs?▼

Extract the sosreport archive and use log analysis to examine journald, system, and application logs for error patterns. The Skill generates structured summaries identifying whether the crash was caused by memory exhaustion, kernel panic, or application failure.

Do I need to manually parse journald and system logs separately?▼

No. The Skill automatically scans and correlates journald, system, and application logs within the sosreport directory structure, surfacing critical errors and actionable recommendations without manual log parsing.

What output does log analysis provide for troubleshooting?▼

Log analysis generates error statistics, event timelines, top error messages, affected components, and remediation guidance—structured outputs that eliminate manual log digging and accelerate root cause identification.