analyze-logs

Parse NDJSON logs to debug errors and investigate performance issues.

Updated Jul 28, 2026

Search Tags:#performance #debugging #logs #observability #error tracking #ndjson

Ready to run

npx skills add https://github.com/tuliof/dindin --skill analyze-logs-tuliof

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: analyze-logs
Source: https://github.com/tuliof/dindin/tree/main/.agents/skills/analyze-logs
Command: npx skills add https://github.com/tuliof/dindin --skill analyze-logs-tuliof

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the difficulty of manually parsing and correlating fragmented application logs, allowing you to quickly identify the root cause of errors and performance bottlenecks.

Core Features & Use Cases

Structured Log Analysis: Automatically parses NDJSON wide-event logs to extract meaningful insights from raw data.
Performance & Error Tracking: Identifies slow endpoints, recurring error patterns, and failed requests across your application.
Use Case: When a user reports a 500 error on the checkout page, use this Skill to filter logs by path and status code to pinpoint the exact error message and stack trace.

Quick Start

Use the analyze-logs skill to find all error events in the most recent log file and summarize the common failure patterns.

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 application logs to find the root cause of 500 errors?▼

Analyze NDJSON application logs by filtering structured log events by path and status code to pinpoint exact error messages and stack traces. This process correlates fragmented log data to identify the root cause of failed requests and performance bottlenecks.

What is the best way to identify slow endpoints and performance issues from structured logs?▼

Identifying slow endpoints and performance issues from structured logs requires parsing ISO 8601 timestamps and duration strings within wide-event NDJSON files. This extracts actionable insights regarding request patterns and recurring performance bottlenecks across your application.

Can I use this to investigate errors across log directories in a monorepo structure?▼

Yes, you can investigate errors across log directories within monorepo structures. The Skill operates directly on these nested directories to identify request patterns, status codes, and structured error metadata across your entire application architecture.

How do I parse ISO 8601 timestamps and duration strings in NDJSON logs for debugging?▼

Parse ISO 8601 timestamps and duration strings in NDJSON logs by processing wide-event log entries to extract timing metadata. This allows you to track request lifecycles, measure endpoint response times, and generate actionable remediation steps.

Does this log analysis approach work with wide-event NDJSON files without additional dependencies?▼

Yes, this log analysis approach works directly with wide-event NDJSON files without requiring additional dependencies. It automatically parses structured fields to extract meaningful insights regarding error tracking and application performance from raw data.