skills.rest
selfmail
selfmailOFFICIAL
Explore all skills by this author →
WebsiteGitHub

analyze-logs

Parse NDJSON and JSONL logs to identify errors and slow requests.

21|Updated Aug 11, 2024
Search Tags:#performance#debugging#logs#analyze#jsonl#ndjson#evlog
One-click install
npx skills add https://github.com/selfmail/selfmail --skill analyze-logs-selfmail
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: analyze-logs
Source: https://github.com/selfmail/selfmail/tree/main/.agents/skills/analyze-logs
Command: npx skills add https://github.com/selfmail/selfmail --skill analyze-logs-selfmail

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Read and analyze structured wide-event logs from the local .evlog/logs/ directory to help developers debug errors, investigate performance issues, and understand application behavior.

Core Features & Use Cases

  • Read and parse NDJSON or pretty-printed JSONL log files from .evlog/logs across single projects or monorepos.
  • Automatically detect log format, locate logs using glob patterns, and provide guided analysis for common scenarios.
  • Identify errors, slow requests, and usage patterns by inspecting fields like path, status, duration, and timestamp.

Quick Start

Ask me to analyze the latest log file in .evlog/logs to identify errors and performance issues.

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 logs to find errors and slow requests?▼

To analyze NDJSON logs, the Skill parses per-line JSON events from the .evlog/logs directory to identify errors, slow requests, and usage patterns. It automatically detects the log format and inspects fields like path, status, duration, and timestamp.

Can I analyze pretty-printed JSONL log files in a monorepo?▼

Yes, you can analyze pretty-printed JSONL log files in a monorepo. The Skill locates logs using glob patterns across single projects or monorepos, detecting whether the format is NDJSON or pretty-printed JSONL before parsing.

How do I filter structured wide-event logs by path or duration?▼

Filtering structured wide-event logs by path, status, duration, and timestamp is handled by the Skill during parsing. It inspects these specific fields in your JSON events to guide you through the structured analysis.

Do I need a specific directory structure to parse local JSONL logs?▼

Yes, you need your local JSONL logs stored in a .evlog/logs/ directory. The Skill reads structured wide-event logs directly from this specific path to debug errors and investigate application behavior.

What is the best way to debug application performance issues from local logs?▼

The best way to debug application performance from local logs is to parse structured wide-event JSON files. The Skill identifies slow requests by inspecting duration fields and usage patterns within your stored log files.

Why is my log analysis not detecting the correct JSON format automatically?▼

Log format detection issues may occur if the structured wide-event logs are not valid NDJSON or pretty-printed JSONL. The Skill relies on parsing per-line JSON events from the .evlog/logs directory to automatically detect the format correctly.

Related Skills

Explore More Software Engineering Skills→
rongarederongarede
4

codex-parser

Parse Codex CLI NDJSON logs to extract execution summaries and failure details.

Community
Intermediate
89jobrien89jobrien
4

debugging

Parse logs and analyze stack traces to diagnose errors across languages.

Community
Advanced
JKc66JKc66
14

analyze-logs

Analyze NDJSON wide-event logs to diagnose application behavior.

Community
Intermediate
balkhaevbalkhaev

analyze-logs

Analyze NDJSON application logs to identify errors and performance issues.

Community
Intermediate