Notre avis
Consulte et agrège les logs provenant de plusieurs sources (systemd, Docker, fichiers d'application) pour faciliter le débogage et la surveillance.
Points forts
- Centralise la visualisation des logs de différents services
- Permet des filtres par niveau (error, warn) et des recherches par motif
- Support de multiples sources (systemd, Docker, fichiers) avec des commandes adaptées
Limites
- Nécessite une configuration préalable des sources de logs dans le SKILL
- Dépend de l'accès aux outils Bash, Read, Glob et Grep
- Pas de fonctionnalité de streaming en temps réel (simple tail)
Lorsque vous devez diagnostiquer un problème en analysant les logs d'un ou plusieurs services de votre projet.
Si vous avez besoin d'une solution de logging centralisée avancée avec indexation et recherche full-text, ou si les services ne sont pas accessibles via les sources listées.
Analyse de sécurité
SûrCommands are read-only log viewing (journalctl, docker logs, tail, grep). No destructive operations or exfiltration risks.
Aucun point d'attention détecté
Exemples
Show me the last 100 log entries for the erudition service, including any errors.Search the docker logs of agila-backend for any error or exception messages.Get the logs from all services (systemd and Docker) for the last hour and show a summary of errors and warnings.name: logs description: View and aggregate logs from various sources (systemd, docker, application files). Use when debugging, monitoring services, or investigating errors. argument-hint: [service] [options] allowed-tools: Bash, Read, Glob, Grep
Log Aggregator
View and search logs from multiple sources across your projects.
Arguments
$0: Service name or project (optional - shows all if not specified)$1: Options -error,warn,tail,search:pattern(optional)
Log Sources by Project
| Project | Source | Location/Command |
|---------|--------|------------------|
| eruditiontx-services-mvp | systemd | journalctl -u erudition-service |
| eruditiontx-services-mvp | app | ~/Projects/eruditiontx-services-mvp/logs/ |
| mathmatterstx-services | systemd | journalctl -u mathmatters-service |
| agila-tax-management | docker | docker logs agila-backend |
| notaryo.ph | Next.js | .next/ logs, terminal output |
| bocs-turbo | Vercel | vercel logs |
Commands
View Recent Logs
Systemd Services:
journalctl -u $SERVICE -n 100 --no-pager
# Follow mode
journalctl -u $SERVICE -f
Docker Containers:
docker logs $CONTAINER --tail 100
# Follow mode
docker logs $CONTAINER -f
Application Log Files:
tail -n 100 ~/Projects/$PROJECT/logs/app.log
# Follow mode
tail -f ~/Projects/$PROJECT/logs/app.log
Filter by Level
Errors Only:
# Systemd
journalctl -u $SERVICE -p err -n 100 --no-pager
# Docker/Files
docker logs $CONTAINER 2>&1 | grep -i "error\|exception\|traceback"
# Log files
grep -i "error\|exception\|traceback" ~/Projects/$PROJECT/logs/app.log
Warnings:
grep -i "warn\|warning" $LOG_SOURCE
Search Logs
# Search for pattern
journalctl -u $SERVICE | grep -i "$PATTERN"
docker logs $CONTAINER 2>&1 | grep -i "$PATTERN"
grep -i "$PATTERN" ~/Projects/$PROJECT/logs/*.log
Time-Based Filtering
# Last hour
journalctl -u $SERVICE --since "1 hour ago"
# Today
journalctl -u $SERVICE --since today
# Specific time range
journalctl -u $SERVICE --since "2024-01-01 00:00:00" --until "2024-01-01 23:59:59"
Log Aggregation Mode
View logs from multiple services at once:
# All Erudition services
journalctl -u erudition-service -u mathmatters-service -f
# All Docker containers
docker-compose logs -f
Log Analysis
Count Errors by Type
grep -i "error" $LOG_FILE | sort | uniq -c | sort -rn | head -20
Find Slow Requests
grep -E "took [0-9]+ms" $LOG_FILE | awk '{print $NF}' | sort -rn | head -10
Track Request IDs
grep "$REQUEST_ID" $LOG_FILE
Output Format
Logs: [service-name]
Source: [systemd/docker/file]
Filter: [all/error/warn]
Time: [range]
---
[Formatted log entries with timestamps]
---
Summary:
- Total entries: X
- Errors: Y
- Warnings: Z
- Time span: [start] to [end]
Common Log Patterns
FastAPI (Python)
INFO: 127.0.0.1:52847 - "GET /health HTTP/1.1" 200 OK
ERROR: Exception in route handler: [error message]
Next.js
ready - started server on 0.0.0.0:3000
error - Error: [error message]
warn - [warning message]
Docker
[timestamp] [level] [message]
Troubleshooting
If logs are empty:
- Check if service is running:
systemctl status $SERVICE - Check log rotation:
ls -la /var/log/ - Check Docker container status:
docker ps -a - Verify log file permissions
Expert Next.js App Router
Developpement
Un skill qui transforme Claude en expert Next.js App Router.
Générateur de README
Developpement
Crée des README.md professionnels et complets pour vos projets.
Rédacteur de Documentation API
Developpement
Génère de la documentation API complète au format OpenAPI/Swagger.