What problem does it solve?
It solves the problem of getting stuck during GEM-LLM operations when common runtime failures occur, such as GPU OOM, vLLM model/buffering issues, SSH/connectivity failures, database bottlenecks, and high-level “it’s broken” symptoms.
Core Features & Use Cases
- Rapid symptom-to-case matching: Quickly map observed symptoms (like 500s, OOM, disk I/O errors, QueuePool warnings, missing model keys, slow responses) to one of 13 known failure cases from GEM-LLM operations.
- Actionable, case-specific remedies: Provide concrete fixes per case, including environment dependency installs, prompt-routing adjustments, streaming option configuration, and database pool/recovery steps.
- Operational triage workflow: Establish a short diagnostic flow (supervisor status → logs → keyword mapping) to reduce time-to-resolution during live incidents.
Quick Start
Run install.sh with the gem-llm-troubleshooting skill to load the 13-case troubleshooting reference and follow the symptom-to-case matching workflow.