cloudwatch-investigate

Diagnose CloudWatch logs by auto-routing queries to log groups and tracing errors to source code.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/fence-technology/claude-code-skills --skill cloudwatch-investigate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cloudwatch-investigate
Source: https://github.com/fence-technology/claude-code-skills/tree/main/engineering/cloudwatch-investigate
Command: npx skills add https://github.com/fence-technology/claude-code-skills --skill cloudwatch-investigate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps software teams quickly diagnose CloudWatch logs by auto-routing to the proper log group and surfacing traces back to the source code, reducing investigation time.

Core Features & Use Cases

  • Auto-routing: Determines the correct log group based on keywords (API, assets, metrics, webhooks, etc.) for fast investigations.
  • Source code tracing: Maps errors to local fence-backend files to aid root-cause analysis.
  • Structured output: Produces a readable investigation report with timeline, error details, root-cause analysis, and fix suggestions.
  • Use cases: Investigating API error bursts for a deal; checking asset declarations; debugging metric calculations or webhook failures.

Quick Start

  • Invoke the skill with a deal: /cloudwatch-investigate [deal_id] <description of what to investigate>.
  • Example: /cloudwatch-investigate asset_external_id 33112 declaration failures

Frequently Asked Questions about cloudwatch-investigate

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

FAQPage Schema
How do I find the correct CloudWatch log group when investigating an API error for a specific deal?

Auto-routing CloudWatch logs determines the correct log group based on keywords like API, assets, metrics, or webhooks. It uses identifiers such as deal_id or asset_external_id to quickly surface relevant log entries for investigation.

How do I trace a CloudWatch error back to the source code in my local repository?

Source code tracing maps deployed CloudWatch errors back to local fence-backend files. This mechanism aids root-cause analysis by linking the production logs directly to the relevant source tree in your local environment.

How do I generate a structured investigation report from AWS CloudWatch logs?

CloudWatch log analysis produces a structured investigation report containing a timeline, error details, root-cause analysis, and suggested fixes. This provides an actionable summary for debugging API bursts or webhook failures.

Do I need AWS CLI or Docker to investigate CloudWatch logs with deal identifiers?

Yes, investigating CloudWatch logs requires AWS CLI or Docker, and credentials management via Leapp. These tools provide the necessary environment to query log groups and map deployed paths to local source trees.

What is the best way to debug asset declaration failures using CloudWatch logs?

The best way to debug asset declaration failures is to invoke an investigation using the asset_external_id. CloudWatch auto-routing targets the assets log group, retrieves the relevant logs, and maps the errors to local source files.

Can I investigate webhook failures and metric calculation errors in CloudWatch?

Yes, CloudWatch log investigations support checking webhook failures and debugging metric calculations. The auto-routing mechanism directs queries to the appropriate log groups using keywords like webhooks or metrics.