multi-file-log-correlator

Merge heterogeneous log files into a unified timeline with correlation and gap detection.

5|4|Updated Nov 9, 2025
One-click install
npx skills add https://github.com/takusaotome/claude-skills-library --skill multi-file-log-correlator
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: multi-file-log-correlator
Source: https://github.com/takusaotome/claude-skills-library/tree/main/skills/multi-file-log-correlator
Command: npx skills add https://github.com/takusaotome/claude-skills-library --skill multi-file-log-correlator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python-dateutil, pandas, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Multi-system incidents are hard to debug when related events are scattered across multiple log files with different timestamp formats and timezones. This skill helps you merge those logs into a unified timeline and surface cross-system correlations, gaps, and timing anomalies.

Core Features & Use Cases

  • Unified timeline construction: Merge heterogeneous log sources into a single, time-ordered event stream with source attribution.
  • Timezone normalization & timestamp alignment: Parse and normalize timestamps (including format differences) to a chosen output timezone.
  • Cross-log correlation & trace reconstruction: Group events by extracted correlation IDs (e.g., request_id/trace_id) or by temporal proximity when IDs are absent.
  • Gap detection: Identify missing coverage windows per source using a configurable gap threshold.
  • Anomaly detection: Flag long correlation durations and error bursts to speed up incident triage.

Quick Start

Use the multi-file-log-correlator to correlate your app, nginx, and database logs into a single timeline and generate a full correlation report in Markdown.

Frequently Asked Questions about multi-file-log-correlator

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

FAQPage Schema
How do I correlate logs from multiple sources into a unified timeline for incident investigation?▼

To correlate logs from multiple sources into a unified timeline, you can merge heterogeneous log files by parsing different timestamp formats, normalizing them to a single output timezone, and sorting events into a time-ordered stream with source attribution.

What is the best way to normalize different timestamp formats and timezones when merging distributed logs?▼

The best way to normalize different timestamp formats when merging distributed logs is to parse heterogeneous date formats using python-dateutil, then convert and align all event times to a chosen output timezone before merging them into a sorted timeline.

How does cross-log correlation work when trace IDs or request IDs are missing from the log files?▼

Cross-log correlation without trace IDs works by using temporal proximity, grouping events within a configurable time window to reconstruct distributed traces when explicit correlation IDs are absent from the log files.

Can I use pandas to detect gaps and timing anomalies in a distributed system event timeline?▼

Yes, you can use pandas to detect gaps and timing anomalies in a distributed system event timeline by identifying missing coverage windows per log source and flagging long correlation durations or error bursts to speed up triage.

Do I need python-dateutil and pandas to reconstruct a unified timeline from multiple log files?▼

Yes, you need python-dateutil and pandas to reconstruct a unified timeline from multiple log files, as pandas handles merging and gap detection while dateutil parses the heterogeneous timestamp formats required for accurate timezone normalization.