analyze-logs

Parse NDJSON or JSON logs to extract errors, metrics, and request patterns.

8|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/daidr/irminsul --skill analyze-logs-daidr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analyze-logs
Source: https://github.com/daidr/irminsul/tree/main/.agents/skills/analyze-logs
Command: npx skills add https://github.com/daidr/irminsul --skill analyze-logs-daidr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers and operations teams quickly analyze structured application logs to identify errors, slow requests, and behavior patterns, facilitating efficient debugging.

Core Features & Use Cases

  • Error Investigation: Find and interpret errors from log files to determine root causes.
  • Performance Monitoring: Detect slow requests and analyze request durations to optimize system performance.
  • Usage Patterns: Review request patterns, error frequencies, and client versus server issues to improve system reliability.
  • Real-World Example: A developer receives user complaints about slow page loads; by analyzing logs with this Skill, they identify problematic endpoints and correlated errors.
  • Technical Scope: Reads structured NDJSON or pretty-printed JSON logs from evlog's .logs/ directory, parsing key fields like timestamps, levels, paths, statuses, and error details, enabling comprehensive log analysis.

Quick Start

Read the latest log files from .evlog/logs/ directory to locate errors, slow requests, and high-error endpoints, then interpret the insights for troubleshooting.

Frequently Asked Questions about analyze-logs

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

FAQPage Schema
How do I analyze structured application logs to find errors and slow requests?

You can analyze structured application logs by parsing NDJSON or pretty JSON files to extract timestamps, levels, paths, and error details to identify errors and slow requests for troubleshooting.

What is the best way to monitor application performance using structured logs?

Monitoring application performance with structured logs involves parsing request durations and status codes from JSON logs to detect slow requests, identify high-error endpoints, and optimize system reliability.

Does this log analysis approach work with NDJSON and pretty printed JSON formats?

Yes, this approach supports both NDJSON and pretty-printed JSON formats. It reads structured log files directly from the evlog `.logs/` directory to parse key fields like timestamps, levels, and paths.

How do I investigate root causes of errors from structured log files?

To investigate root causes of errors from structured log files, parse the JSON logs to find and interpret error details, review request patterns, and distinguish between client and server issues for debugging.

What are the limitations of analyzing logs for system optimization?

A limitation of analyzing logs for system optimization is that it strictly requires structured NDJSON or pretty JSON formats from the evlog `.logs/` directory to extract metrics, meaning unstructured logs cannot be parsed.