skills.rest
andreasasprou
andreasasprouCOMMUNITY
Explore all skills by this author →
Website𝕏@andyasprouGitHub

analyze-logs

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

Updated Aug 23, 2026
Search Tags:#performance#log-analysis#ndjson#evlog#request-tracing#error-investigation
One-click install
npx skills add https://github.com/andreasasprou/polaris --skill analyze-logs-andreasasprou
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: analyze-logs
Source: https://github.com/andreasasprou/polaris/tree/main/.agents/skills/analyze-logs
Command: npx skills add https://github.com/andreasasprou/polaris --skill analyze-logs-andreasasprou

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers and operators quickly locate and explain errors, slow requests, and anomalous request patterns by analyzing structured wide-event logs produced by evlog, removing the need for manual line-by-line inspection.

Core Features & Use Cases

  • Parse and auto-detect NDJSON or pretty-printed JSON log formats from .evlog/logs/ and app-level log directories.
  • Filter and surface relevant events by error level, endpoint path, requestId, status, and duration, and summarize recurring failure patterns.
  • Extract actionable fields such as error.message, error.data.why, error.data.fix, timestamps, and durations to provide remediation guidance and performance insights.
  • Use case: investigate a recent 500 error, trace the requestId to a single wide-event, read the error.data.why and error.data.fix, and identify whether multiple requests show the same stack or root cause.

Quick Start

Analyze the most recent .evlog/logs/*.jsonl file for errors, slow requests, and provide a concise summary with suggested fixes.

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

To analyze NDJSON application logs, the Skill parses each line as an independent JSON event from .evlog/logs/ to identify errors, slow requests, and anomalous patterns. It filters by level, path, status, and duration to summarize recurring failures.

How does request tracing work with evlog wide-event JSON files?▼

Request tracing with evlog wide-event JSON files works by parsing structured log events to extract and trace specific requestId values. This allows you to isolate individual requests, read error.data.why, and determine if multiple requests share the same root cause.

Can I filter application logs by endpoint path, status, and duration?▼

Yes, you can filter application logs by endpoint path, status, and duration. The Skill detects the log format automatically and surfaces relevant events matching your criteria, extracting error.message and timestamps for remediation guidance.

Does this log analyzer work with both NDJSON and pretty-printed JSON formats?▼

Yes, this log analyzer works with both NDJSON and pretty-printed JSON formats. It automatically detects the format of files located under .evlog/logs/ or apps/*/.evlog/logs/ and parses each line independently to extract performance and error data.

What is the best way to investigate a 500 error in structured application logs?▼

The best way to investigate a 500 error in structured application logs is to filter by error level and status. The Skill extracts actionable fields like error.data.why and error.data.fix, providing direct remediation guidance without manual line-by-line inspection.

When do I need to parse NDJSON log files for request patterns instead of reading them manually?▼

You need to parse NDJSON log files for request patterns when manually inspecting wide-event logs becomes inefficient. The Skill automates extracting error messages, durations, and requestIds to measure endpoint error rates and pinpoint anomalous request behaviors.

Related Skills

Explore More Software Engineering Skills→
jmcmullenjmcmullen
1

analyze-logs

Analyze NDJSON event logs to identify errors, slow requests, and behavioral patterns.

Community
Advanced
JansenAnalyticsJansenAnalytics
5

error-monitor

Monitor application logs and stderr to detect errors, crashes, and exceptions.

Community
Intermediate
allthingslinuxallthingslinux
4

logging-best-practices

Enforce wide-event JSON logging with middleware and consistent schemas.

Official
Intermediate
Mekann2904Mekann2904

log-analyzer

Analyze log files to extract error patterns and detect anomalies.

Community
Intermediate