Log Analysis
Guide to structured log querying, correlation ID tracing, and error pattern analysis for crocbot debugging.Log Locations
| Deployment | Location |
|---|---|
| File logs | /tmp/crocbot/crocbot-YYYY-MM-DD.log |
| systemd | journalctl --user -u crocbot-gateway |
| Docker | docker logs crocbot |
| CLI | crocbot logs --follow |
Log Format
Crocbot uses structured JSON logging. Each line is a JSON object:Log Levels
| Level | Use |
|---|---|
trace | Extremely verbose, internal state |
debug | Debugging details, message bodies |
info | Normal operations |
warn | Potential issues, recoverable errors |
error | Failures requiring attention |
fatal | Critical failures, process exit |
Basic Querying
View Recent Logs
Filter by Level
Filter by Time
Filter by Subsystem
Correlation ID Tracing
Correlation IDs link related log entries across a request lifecycle. Use them to trace the full journey of a message or request.Find Correlation ID
Trace Full Request
Trace Script
Common Correlation Patterns
Error Pattern Analysis
Find Common Errors
Error Timeline
Find Related Errors
Error Context
Performance Analysis
Latency Distribution
Slow Requests
Message Volume
systemd / journalctl
Basic Queries
Filter by Priority
Search in Logs
Docker Log Analysis
Basic Queries
Parse JSON Logs
Common Debug Scenarios
Debug Message Flow
Debug Connection Issues
Debug Auth Issues
Find Memory Issues
Log Aggregation
Export for Analysis
Aggregate Metrics
Useful jq Recipes
Related Documentation
- Logging Configuration - Log levels and formats
- User Logging Guide - Overview for users
- Metrics - Prometheus metrics
- Alerting - Error alerting
- Incident Response - Troubleshooting procedures
