report-app-down

To diagnose a failing Dokploy app, you compile its status, deploy history, and runtime logs into a single report. This provides a comprehensive, read-only diagnostic snapshot to troubleshoot incidents or perform postmortems.

Compiling runtime logs and deploy history for an incident postmortem requires aggregating data from workflows and logs. The process preserves raw error messages, stack traces, and run URLs to output a structured summary suitable for escalation.

A diagnostic snapshot cannot fix app health issues directly because it is strictly read-only and takes no actions. You must use a separate fix-app skill to resolve issues after reviewing the compiled status, deploy history, and runtime logs.

The app health report includes raw error messages, stack traces, and run URLs. It aggregates data from workflows and logs to preserve the original context needed for escalation or writing a postmortem.

The best way to get a full picture of app health before escalating is to request a complete diagnostic snapshot. This aggregates status, deploy history, and runtime logs into one structured summary for the oncall engineer.

The diagnostic report does not start or stop your Dokploy app because it is designed purely for read-only troubleshooting. You must use dedicated start/stop skills to manage app lifecycle actions separately from the reporting process.