my-investigate

Investigate production issues by correlating logs, metrics, traces, and dashboards.

4|1|Updated May 31, 2015

Search Tags:#logs #metrics #observability #investigate #traces #incident

Ready to run

npx skills add https://github.com/samcdavid/dotfiles --skill my-investigate

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: my-investigate
Source: https://github.com/samcdavid/dotfiles/tree/main/claude/skills/my-investigate
Command: npx skills add https://github.com/samcdavid/dotfiles --skill my-investigate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Investigate production or runtime issues by exploring logs, metrics, traces, and dashboards. Product-agnostic — works with any observability stack. Follows the evidence to root cause.

Core Features & Use Cases

Evidence-driven investigation: Build timeline, gather data from logs, metrics, traces, and dashboards across services.
Platform-agnostic: Works with any observability stack and data source.
Root-cause guidance: Provides a structured process for hypotheses, testing, and RCA.

Quick Start

Describe the issue symptoms and gather available logs, metrics, and traces from the observed time window to start the investigation.

Frequently Asked Questions about my-investigate

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

FAQPage Schema

How do I investigate production incidents using logs, metrics, and traces?▼

To investigate production incidents, you collect time-aligned logs, metrics, and traces across affected services. This process builds an evidence-based timeline to systematically test hypotheses and pinpoint the root cause of the runtime issue.

What is the best way to find the root cause of a production issue across different services?▼

Finding a root cause across services requires a platform-agnostic approach to correlate observability data. By applying a structured hypothesis-testing workflow to logs and traces, you can follow the evidence end-to-end from event to resolution.

Does this incident investigation workflow work with any observability stack?▼

Yes, this incident investigation workflow is platform-agnostic and works with any observability stack. It requires no specific dependencies, allowing you to gather data from any available logs, metrics, traces, and dashboards.

How do I start an evidence-driven investigation for a runtime issue?▼

To start an evidence-driven investigation, describe the issue symptoms and gather available logs, metrics, and traces from the observed time window. This initial data collection forms the baseline for your root-cause analysis.

When do I need a structured hypothesis-testing workflow for observability data?▼

You need a structured hypothesis-testing workflow when a runtime issue requires end-to-end evidence-based analysis across logs, metrics, and traces. It guides the correlation of time-aligned data to methodically identify root causes rather than guessing.