Log Aggregation
ELK Stack, structured logging, log query patterns, and centralized log management.
Install
/plugin marketplace add sethdford/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add sethdford/claude-skills --skill log-aggregationgit clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/engineer/devops-practices/skills/log-aggregation ~/.claude/skills/log-aggregationPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Log Aggregation Collecting, indexing, and querying logs for debugging and monitoring. ## Context You are setting up log aggregation. Use structured logs; make them queryable. ## Domain Context - **Structured**: JSON logs with fields; queryable not text - **Trace ID**: Correlate logs across services - **Centralized**: Logs from all services in one place - **Retention**: How long to keep logs? Cost/value tradeoff - **Searchability**: Fast queries for debugging ## Instructions 1. **Structured Logging**: JSON with fields not free text 2. **Trace ID**: Include on every log; correlate across services 3. **Log Levels**: DEBUG, INFO, WARN, ERROR; use appropriately 4. **Centralization**: ELK, Datadog, Splunk; pick one 5. **Filtering**: Useful queries to narrow down issues 6. **Retention**: Keep recent logs accessible; archive old 7. **Performance**: Don't log too much; expensive and slow ## Anti-Patterns - Text logs without structure; can't query programmatically - No trace IDs; can't correlate across services - Logging everything; too much data, hard to find signal - Keeping logs forever; expensive storage - No log pipeline; raw logs, no transformation/enrichment ## Further Reading - ELK Stack documentation - Structured logging guide - Log aggregation best practices (Google Cloud)
Details
- Skill name
log-aggregation- Repository
- sethdford/claude-skills
- Path
engineer/devops-practices/skills/log-aggregation/SKILL.md- License
- MIT
- Repo updated
- 11 March 2026
FAQ
What does the Log Aggregation skill do?
ELK Stack, structured logging, log query patterns, and centralized log management.
How do I install the Log Aggregation skill?
Claude Code plugin: /plugin marketplace add sethdford/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Log Aggregation popular?
It lives in sethdford/claude-skills, which has 48 GitHub stars and 10 forks.
Related skills
A B Test Design
48sethdford/claude-skills
Design rigorous A/B tests with hypotheses, variants, metrics, and sample size calculations.
A B Test Design Pm
48sethdford/claude-skills
Analytics and experimentation skill for product managers.
Abuse Case Design
48sethdford/claude-skills
Design abuse cases (negative use cases) showing how attackers misuse system features. Use when identifying attacks that exploit intended functionality or business logic flaws.
Log Analysis
48sethdford/claude-skills
Parsing logs, correlation analysis, reconstructing timeline of failures.
Lessons Learned
48sethdford/claude-skills
Conduct post-incident reviews to document lessons learned and implement process improvements preventing recurrence.
Market Sizing
48sethdford/claude-skills
Estimate total addressable market (TAM), serviceable market (SAM), and obtainable market (SOM).
Browse the most popular Claude skills, all other skills, or write your own with the skills generator.