Read logs and errors after deploys
Use app_logs, app_errors, and deploy_log to triage failures.
Pick the right log tool
| Tool | Holds | When to read |
|---|---|---|
app_logs |
Fleet stdout/stderr, last 2000 lines. | Debug runtime behavior and server-side capture gaps. |
app_errors |
Fingerprint-grouped runtime errors. | Read after every deploy that touches server code. |
deploy_log |
Build output for one deploy. | Debug a failed build step. |
Triage in order
- Read
app_errorsafter every deploy that touches server code. - Triage
console.erroroutput over MCP when the page reports errors. - Open
app_logsfor the last 2000 lines of fleet stdout/stderr. - Open
deploy_logfor build output when the failure sits in the pipeline.
For the person-side walkthrough, see Read logs and errors.