ops-investigator

Query CloudWatch logs to investigate incidents and generate reports.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/fractary/claude-plugins --skill ops-investigator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ops-investigator
Source: https://github.com/fractary/claude-plugins/tree/main/plugins/faber-cloud/.archive/phase4-clean-separation/ops-investigator
Command: npx skills add https://github.com/fractary/claude-plugins --skill ops-investigator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Bash, aws-cli, jq.

What problem does it solve?

Manual log analysis and incident investigation are time-consuming and complex, leading to slower resolution times and increased operational burden. This skill automates the process, providing quick insights and actionable reports.

Core Features & Use Cases

  • Log Querying: Query CloudWatch logs with advanced filters to pinpoint relevant events.
  • Event Correlation: Correlate events across multiple services to identify dependencies and impact.
  • Root Cause Analysis: Pinpoint the underlying causes of incidents and suggest remediations.
  • Use Case: An application is experiencing intermittent errors. Use this skill to query logs for the last hour, identify error patterns, and generate an incident report with a timeline and potential root causes.

Quick Start

Investigate an incident in the 'prod' environment for the 'auth-service' with the context "high latency detected".

Frequently Asked Questions about ops-investigator

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

FAQPage Schema
How do I automate CloudWatch log analysis for incident investigation?

Automate CloudWatch log analysis by querying logs with advanced filters to identify error patterns, correlate events across services, and generate incident reports with timelines and root cause recommendations—all without manual log review.

Can I use CloudWatch logs to perform root cause analysis across multiple services?

Yes. Query CloudWatch logs across services to correlate events, identify dependencies, pinpoint underlying causes of incidents, and generate actionable findings with evidence and log excerpts in a single report.

What's the fastest way to investigate production incidents and generate incident reports?

Query CloudWatch logs with filters to extract relevant events, correlate patterns across services, analyze root causes, and automatically generate incident reports with timelines—reducing investigation time from hours to minutes.

Does this work for investigating incidents in both test and production environments?

Yes. This approach handles incident investigation and root cause analysis in both test and prod environments, supporting operations across different service deployments with the same querying and analysis workflow.

What do I need to investigate incidents using CloudWatch logs?

You need Bash, aws-cli, and jq installed to query CloudWatch logs, parse responses, filter events, and correlate data for incident investigation and root cause analysis.

Why should I automate incident investigation instead of manual log analysis?

Automation reduces investigation time, eliminates manual log review errors, enables fast event correlation across services, and produces consistent incident reports with actionable root cause findings and remediation recommendations.