log-analysis

Analyze Apache/Nginx and application logs for errors, performance issues, and security anomalies.

Updated Dec 20, 2023
One-click install
npx skills add https://github.com/Thiago-Cruz-eng/Hibrygame --skill log-analysis-thiago-cruz-eng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: log-analysis
Source: https://github.com/Thiago-Cruz-eng/Hibrygame/tree/main/.claude/skills/log-analysis
Command: npx skills add https://github.com/Thiago-Cruz-eng/Hibrygame --skill log-analysis-thiago-cruz-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Log analysis helps you quickly pinpoint why an application is failing, where performance degrades, and whether suspicious activity is occurring—without manually scanning huge log files.

Core Features & Use Cases

  • Error & Exception Detection: Find frequent errors by level (e.g., ERROR/exception/fail) and correlate by timestamp and HTTP status codes (4xx/5xx).
  • Performance Investigation: Identify slow requests and quantify traffic patterns by time window and endpoint.
  • Security Anomaly Scanning: Detect likely SQL injection, XSS attempts, directory traversal, and brute-force/login abuse patterns.
  • Use Case: When an outage happens after a deployment, analyze access and application logs to isolate a surge in 5xx responses, identify the failing endpoints, and check for concurrent malicious probing.

Quick Start

Use the log-analysis skill to analyze your access.log and application.log and produce an actionable incident-style summary of errors, performance hot spots, and potential security anomalies.

Frequently Asked Questions about log-analysis

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

FAQPage Schema
How do I analyze Nginx access logs to find 5xx errors after a deployment?

Analyze Nginx access logs to isolate surges in 5xx HTTP responses by correlating timestamps, failing endpoints, and error levels. This read-only process uses pattern matching to quickly pinpoint application failures without modifying log files.

What is the best way to detect security anomalies like SQL injection in web server logs?

Detect security anomalies in web server logs by scanning for likely SQL injection, XSS attempts, and directory traversal patterns. This identifies suspicious activity and brute-force login abuse through read-only inspection of access and application logs.

How do I identify performance bottlenecks and slow requests from application logs?

Identify performance bottlenecks by analyzing application logs to find slow requests and quantifying traffic patterns. This breaks down response times by endpoint and time window to highlight areas suffering from degraded performance.

Can I inspect JSON-like application logs without modifying the original files?

Yes, you can inspect JSON-like application logs using read-only grep and awk-style pattern matching. This enforces sensitive data masking while strictly avoiding any modification to the original log files during incident investigation.

Does log analysis work for incident response across both Apache and Nginx access logs?

Log analysis works for incident response across common Apache and Nginx access logs. It correlates HTTP status codes, timestamps, and IP addresses to produce actionable summaries of errors, performance hot spots, and security threats.