Forge-Log-Analysis

Extracts structured incident evidence from application and system logs through triage and cross-service correlation.

Updated Jul 18, 2026
One-click install
npx skills add https://github.com/Nealsch/ForgeOS --skill forge-log-analysis-nealsch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Forge-Log-Analysis
Source: https://github.com/Nealsch/ForgeOS/tree/main/Framework/05-Skills/09-Operations/Forge-Log-Analysis
Command: npx skills add https://github.com/Nealsch/ForgeOS --skill forge-log-analysis-nealsch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Raw log output is hard to turn into reliable incident evidence: entries may lack timestamps, versions, or correlation IDs, and investigations often rely on memory rather than reconstructed timelines. This Skill provides a structured method for assessing logging quality, triaging log data, correlating events across services, and producing evidence summaries for root-cause analysis. ## Core Features & Use Cases - Logging Quality Assessment: Checks whether log entries are timestamped, versioned, correlated, and free of secrets, turning gaps into corrective actions. - Triage and Correlation: Scopes time windows, filters by severity and component, and correlates events across services using shared identifiers and causality. - Evidence Production: Reconstructs event sequences and produces an evidence summary attached to the incident record. - Use Case: During an outage investigation, use this Skill to scope the incident time window, correlate events across microservices, and deliver a timeline-based evidence summary to the incident record. ## Quick Start Analyze the application logs from the last deployment window and produce a correlated event timeline and evidence summary for the open incident.

Frequently Asked Questions about Forge-Log-Analysis

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

FAQPage Schema
How do I analyze logs for root-cause analysis?▼

Log root-cause analysis starts by scoping the incident time window, filtering entries by severity and component, then correlating events across services using shared identifiers. The result is a reconstructed event timeline and an evidence summary attached to the incident record.

How do I correlate logs across multiple services?▼

Cross-service log correlation relies on shared identifiers such as request or trace IDs present in each service's log entries. Events are ordered by timestamp and causality to reconstruct the sequence leading to the observed behavior.

What makes application logs good enough for incident investigation?▼

Adequate logs are timestamped, versioned, correlated with shared identifiers, and free of secrets. Logging gaps discovered during analysis should be recorded as corrective actions so future investigations are not blocked.

When should I use log analysis instead of monitoring or incident management?▼

Use log analysis when you need to determine what happened from log evidence. Monitoring defines what to alert on, and incident management coordinates the response workflow; log analysis supplies the evidence those processes consume.

Why must logs not contain secrets during analysis?▼

Logs containing secrets create security risk because investigators and incident records would expose credentials or sensitive data. Security standards require log data access to be controlled and entries to exclude secrets before analysis.