Skills
Log Analysis
Error pattern recognition, log parsing techniques, and common error patterns. Use when analyzing log files, identifying root causes, or correlating errors across systems.
Log Analysis
Factory
Version: 1.0.0 | License: MIT
Tags: logs errors debugging monitoring operations
Log Analysis Skill
Knowledge base for analyzing log files, identifying error patterns, and performing root cause analysis.
When to Activate
Activate this skill when:
- Analyzing application or system logs
- Identifying error patterns and anomalies
- Performing root cause analysis
- Correlating events across log sources
- Investigating production issues
Core Capabilities
Error Pattern Recognition
- Common error signatures
- Stack trace analysis
- Timeout and connection patterns
- Memory and resource issues
Log Parsing
- JSON/structured log parsing
- Apache/Nginx combined format
- Syslog format
- Application-specific formats
Correlation Techniques
- Timestamp alignment
- Request ID tracing
- User session correlation
- Service dependency mapping
References
Quick Reference
Error Severity Mapping
| Pattern | Severity | Action |
|---|---|---|
| FATAL/CRITICAL | Critical | Immediate investigation |
| Exception/Error | High | Priority investigation |
| Timeout | High | Performance analysis |
| OOM/Memory | Critical | Resource scaling |
| Warning | Medium | Monitor for trends |
| Connection refused | High | Service health check |
Log Level Standards
| Level | Use Case | Production Setting |
|---|---|---|
| TRACE | Detailed debugging | Never |
| DEBUG | Development | Never |
| INFO | Normal operations | Yes |
| WARN | Potential issues | Yes |
| ERROR | Failures | Yes |
| FATAL | System crash | Yes |
Quick Grep Patterns
# All errors
grep -iE "(ERROR|EXCEPTION|FATAL|CRITICAL)" logfile.log
# Timeouts
grep -iE "(timeout|timed out|deadline)" logfile.log
# Memory issues
grep -iE "(OOM|out of memory|heap|allocation failed)" logfile.log
# HTTP errors
grep -E "HTTP/[0-9.]+ [45][0-9]{2}" logfile.logAnalysis Workflow
1. Format Detection
└── Identify log structure
2. Error Extraction
└── Filter by severity
3. Pattern Grouping
└── Count and categorize
4. Timeline Analysis
└── Identify spikes/trends
5. Correlation
└── Link related events
6. Root Cause Hypothesis
└── Evidence-based conclusionsIntegration
- Used by
ops-analystagent - Triggered by
/ops:logscommand - Feeds into
/ops:postmortemfor incident analysis
References
Log Parsing Techniques
Reference documentation
Error Pattern Recognition
Reference documentation
Common Error Patterns
Reference documentation