troubleshooting-application-failures

Diagnose application failures by analyzing CloudWatch log groups for error patterns and root causes.

Updated Jul 1, 2026
One-click install
npx skills add https://github.com/sakicodes/BuildFestHackathon26 --skill troubleshooting-application-failures-sakicodes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: troubleshooting-application-failures
Source: https://github.com/sakicodes/BuildFestHackathon26/tree/main/.agents/skills/troubleshooting-application-failures
Command: npx skills add https://github.com/sakicodes/BuildFestHackathon26 --skill troubleshooting-application-failures-sakicodes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When an application starts failing, engineers often waste hours manually digging through scattered CloudWatch log groups trying to find error patterns and root causes. This Skill automates log group discovery, error pattern analysis, and root cause identification to produce a prioritized remediation plan. ## Core Features & Use Cases - Log Group Discovery: Automatically finds CloudWatch log groups related to an application name across Lambda, API Gateway, ECS, and custom log groups. - Error Pattern Analysis: Runs CloudWatch Logs Insights queries to detect exceptions, stack traces, timeouts, and authentication failures, then categorizes them by type and frequency. - Root Cause & Remediation Report: Generates a structured report with prioritized root causes, immediate/short-term/long-term fixes, and monitoring recommendations. - Use Case: Your payment-service in us-west-2 is returning errors. Provide the application name and region, and receive a report showing connection pool exhaustion as the primary cause with specific code fixes and CloudWatch alarm recommendations. ## Quick Start Troubleshoot my application payment-service in region us-west-2 by analyzing its CloudWatch logs from the last 4 hours.

Frequently Asked Questions about troubleshooting-application-failures

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

FAQPage Schema
How do I troubleshoot a failing application using CloudWatch logs?

Provide the application name, AWS region, and an optional time window in hours. The workflow discovers related log groups, runs CloudWatch Logs Insights queries for errors and exceptions, then generates a root cause analysis with prioritized fixes.

What AWS permissions are needed for CloudWatch log analysis?

The credentials need logs:DescribeLogGroups, logs:DescribeLogStreams, logs:StartQuery, and logs:GetQueryResults permissions. Without these, log group discovery and query execution will fail with access denied errors.

Which log groups does CloudWatch troubleshooting search?

It searches log groups containing the application name, including common patterns like /aws/lambda/, /aws/apigateway/, /aws/ecs/, /aws/applicationelb/, and custom application log groups. You confirm which discovered groups are relevant before analysis.

Why do CloudWatch Logs Insights queries time out?

Queries time out when scanning large log groups over long time windows. Reduce the time window to 1-2 hours, limit result counts, or split the analysis into multiple smaller queries to avoid timeouts.

Can I troubleshoot applications deployed across multiple AWS regions?

CloudWatch Logs are region-specific, so multi-region applications must be analyzed separately per region. Run the troubleshooting workflow once for each region where the application is deployed.