log-analysis-patterns

What problem does it solve?

This Skill provides a structured, functionality-first approach to log analysis, preventing aimless searching and ensuring logs are used to diagnose broken features. It guides the user through understanding expected functionality, tracing flows, and identifying where functionality breaks, leading to faster and more accurate bug resolution.

Core Features & Use Cases

• Context-Dependent Functionality Analysis: Mandates understanding expected user, admin, and system flows before analyzing logs.
• Functionality Flow Tracing: Uses request IDs and log patterns to trace the step-by-step execution of a feature through logs.
• Expected vs. Observed Log Comparison: Systematically compares expected log patterns with observed patterns to pinpoint functionality divergence.
• Targeted Error & Performance Analysis: Provides strategies to analyze error logs for functionality issues and performance logs for functionality degradation.
• Use Case: When an API endpoint for file upload is failing, use this skill to first define the expected request flow, then analyze the server logs using the request ID to pinpoint exactly where the flow breaks (e.g., validation failure, CRM API timeout).

Quick Start

Analyze the logs for the recent user registration failures, tracing the request flow to identify where the functionality breaks.