g/agent-pard0x
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

limit shell command output

Browse Source
This commit is contained in:
Gaetan Hurel 2025-06-27 13:53:57 +02:00
parent 985cda155b
commit bf2cc1a409
No known key found for this signature in database
1 changed files with 6 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
multi-agent-supervisor/agents/logs_analyzer.py
View File

@ -31,8 +31,9 @@ OS-Specific Log Analysis:
**macOS:** **macOS:**
- System logs: `log show` (unified logging) or Console.app - System logs: `log show` (unified logging) or Console.app
- Recent logs: `log show --last 1h --predicate 'eventType == logEvent'` - Recent logs: `log show --last 1h --predicate 'eventType == logEvent' | head -500`
- System events: `log show --predicate 'subsystem == "com.apple.kernel"'` - System events: `log show --predicate 'subsystem == "com.apple.kernel"' | head -200`
- Error-focused: `log show --last 1h --predicate 'messageType == error' | head -200`
- Application logs: `~/Library/Logs/`, `/Library/Logs/`, `/var/log/` - Application logs: `~/Library/Logs/`, `/Library/Logs/`, `/var/log/`
- Crash reports: `~/Library/Logs/DiagnosticReports/` - Crash reports: `~/Library/Logs/DiagnosticReports/`
@ -46,13 +47,15 @@ Analysis Techniques:
- Time-based filtering: Focus on relevant time periods - Time-based filtering: Focus on relevant time periods
- Pattern matching: Search for error, fail, critical, warning, denied - Pattern matching: Search for error, fail, critical, warning, denied
- Cross-reference multiple log sources for complete picture - Cross-reference multiple log sources for complete picture
- **CRITICAL: Always limit output with `| head -500` or `| tail -500` to prevent token overflow**
Best Practices: Best Practices:
1. **Detect OS first** using `uname -s` to choose appropriate log commands 1. **Detect OS first** using `uname -s` to choose appropriate log commands
2. **Start recent**: Use last 100-1000 lines or recent time periods 2. **Start recent**: Use last 500-1000 lines or recent time periods
3. **Search systematically**: Keywords → timestamps → context → correlation 3. **Search systematically**: Keywords → timestamps → context → correlation
4. **Multiple sources**: System, application, and service logs 4. **Multiple sources**: System, application, and service logs
5. **Summarize clearly**: Include timestamps, severity, and actionable insights 5. **Summarize clearly**: Include timestamps, severity, and actionable insights
6. **ALWAYS limit output**: Use `head -500`, `tail -500`, or `grep` to keep responses manageable
Log Location Hints: Log Location Hints:
- Linux: `/var/log/`, `journalctl`, `/proc/`, `/sys/kernel/debug/` - Linux: `/var/log/`, `journalctl`, `/proc/`, `/sys/kernel/debug/`