log-analysis

Diagnose errors and performance issues using CloudWatch Logs Insights, Kubernetes, and system log queries.

3|1|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/LiboMa/agenticops-chat --skill log-analysis-liboma
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: log-analysis
Source: https://github.com/LiboMa/agenticops-chat/tree/main/skills/log-analysis
Command: npx skills add https://github.com/LiboMa/agenticops-chat --skill log-analysis-liboma

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Troubleshooting production incidents requires digging through scattered logs across CloudWatch, Kubernetes pods, and system journals, and writing effective queries from scratch under pressure is slow and error-prone. ## Core Features & Use Cases - CloudWatch Logs Insights Query Library: Copy-paste ready queries for Lambda cold starts, ALB 5XX errors, VPC flow log rejections, CloudTrail unauthorized calls, API Gateway latency, and ECS container errors. - Kubernetes and System Log Workflows: Decision trees for pod log inspection with kubectl and stern, journald error filtering, and kernel-level diagnostics with dmesg. - Error Pattern Recognition: Language-specific guides for Java, Python, Node.js, and Go covering root causes and remediations for common failures like OutOfMemoryError, connection pool exhaustion, and nil pointer panics. - Use Case: When an alert fires for elevated 5XX errors, use the ALB query templates to identify failing targets, correlate the timestamp with CloudTrail deployment events, and match stack traces against the error pattern reference to find the root cause. ## Quick Start Analyze the recent errors in my Lambda function logs and help me find the root cause using CloudWatch Logs Insights.

Frequently Asked Questions about log-analysis

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

FAQPage Schema
How do I investigate a log volume spike in CloudWatch?▼

Check the IncomingBytes metric in the AWS/Logs namespace, then run an Insights query counting lines per log stream to find the chatty source. Common causes are debug logging left enabled, retry loops, and error cascades.