analyze-logs

Extract and interpret NDJSON log events from .evlog/logs/ to diagnose errors and evaluate performance.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/zhcndoc/evlog --skill analyze-logs-zhcndoc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analyze-logs
Source: https://github.com/zhcndoc/evlog/tree/main/apps/docs/skills/analyze-logs
Command: npx skills add https://github.com/zhcndoc/evlog --skill analyze-logs-zhcndoc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes structured log data to help developers debug errors, investigate slow requests, and understand application behavior from evlog NDJSON wide events.

Core Features & Use Cases

  • Reads logs from the local .evlog/logs/ directory and app-level logs.
  • Supports debugging errors, performance investigations, and pattern discovery across requests.
  • Use case: when facing an unhelpful error, pull the latest NDJSON events to identify root causes and trends.

Quick Start

Analyze the latest logs in .evlog/logs/ to identify recent errors and performance bottlenecks.

Frequently Asked Questions about analyze-logs

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

FAQPage Schema
How do I analyze NDJSON log events to debug application errors?

To analyze NDJSON log events, you can extract and interpret structured data from .evlog/logs/ to diagnose errors. This process reads evlog wide events to identify root causes and trends from unhelpful application errors.

What is the best way to investigate slow requests using structured logs?

Investigating slow requests with structured logs involves extracting performance metrics from NDJSON events. By analyzing evlog file system drain outputs, you can evaluate request performance and identify bottlenecks across your application.

Can I use log analysis to read events from both central and per-app locations?

Yes, log analysis can read events from both central and per-app locations. The workflow operates on NDJSON wide events written by evlog's file system drain, allowing you to pull logs from the local .evlog/logs/ directory and app-level sources.

How do I discover patterns across requests from evlog NDJSON events?

To discover patterns across requests, you analyze evlog NDJSON wide events to interpret application behavior. This workflow extracts structured log data from your file system drain to reveal trends and recurring issues.

Do I need specific log schema knowledge to analyze evlog file system drain outputs?

Yes, you need knowledge of the log schema to analyze evlog file system drain outputs effectively. Interpreting the NDJSON wide events requires understanding the structured log format to produce actionable insights.

What are the limitations when debugging errors with local NDJSON log files?

A limitation when debugging errors with local NDJSON log files is the requirement for physical access to the .evlog/logs/ directory. Without proper file access and schema knowledge, the log analysis cannot interpret the structured events.