Crash diagnostics
Crash reports with the likely cause; your own AI assistant reads the details
When an app crashes, Percher records a crash report with the end of the log, explains the likely cause and emails you. The report is on the app's Health page.
Percher recognises common causes with fixed rules: running out of memory, a missing package or file, a syntax error, a port the app cannot listen on, a missing environment variable, an unreachable database, an uncaught async error, and outbound requests that bypass Percher's network proxy. Anything else is reported with its exit code and the log tail.
Percher does not send crash logs to an external AI provider. To have an AI explain a crash, ask your own assistant, for example: “Run percher doctor for my Percher app "my-app" in runtime mode and explain why it crashed.” With MCP, your assistant calls percher_doctor with mode="runtime" and gets the crash report and log tail. From a terminal, run percher doctor my-app.
The watchdog checks for stopped containers every five seconds by default. Reports older than 24 hours on apps that have recovered are left out of doctor's result.