Analyze MikoPBX Docker logs to diagnose API, worker, and system issues.
npx skills add https://github.com/mikopbx/Core --skill log-analyzer-mikopbx
Please help me install this Agent Skill. Skill: log-analyzer Source: https://github.com/mikopbx/Core/tree/main/.claude/skills/log-analyzer Command: npx skills add https://github.com/mikopbx/Core --skill log-analyzer-mikopbx
Efficiently analyze Docker container logs for diagnosing problems, monitoring health, and understanding system behavior.
Quick access suggests using host-mounted logs for speed and docker exec for process checks. Examples cover API issues, worker status, and real-time monitoring.
High-intent search queries and answers about installing and using this skill.
Analyze Docker container logs by accessing system logs, PHP error logs, and nginx logs stored in /storage/usbdisk1/mikopbx/log/. Filter entries using grep to isolate relevant errors, then correlate across files to identify root causes for API failures, worker issues, or health problems.
Yes. Log analysis identifies API failures by examining nginx and system logs together, correlating timing and error patterns across multiple files to pinpoint whether issues originate in application code, worker processes, or infrastructure.
Use docker exec to access live container processes while cross-referencing system and PHP error logs. This dual approach tracks worker state changes and correlates process failures with error entries to diagnose performance or crash issues.
Apply grep tools to isolate actionable entries by searching for specific error keywords, timestamps, or process IDs across system/messages, php/error.log, and nginx logs, reducing clutter to focus on genuine issues.
Yes. Host-mounted log paths like /storage/usbdisk1/mikopbx/log/ enable fast direct access without entering the container, supporting quick diagnostics while docker exec provides process-level context when needed.
System behavior spans multiple services—nginx handles requests, PHP processes application logic, and system logs record infrastructure events. Correlating entries across files reveals causation chains that single-file inspection misses, enabling root-cause diagnosis.
jboothomasDiagnose NauggieClaw container failures by analyzing logs, mounts, and MCP errors.
0xRayAIAnalyzes log files for patterns, anomalies, and security threats via MCP server.
NVIDIA-BioNeMoMonitors detached KERMIT scientific workflows by parsing logs and querying Docker container statuses.
herdiansahDiagnose production outages using logs, traces, and Kubernetes debugging.
