Logs and debugging
Debugging starts with three questions. Is the Service failing now, what evidence explains it, and what is the next useful action? Tokay keeps those answers on the Service page so you do not have to reconstruct an incident from separate systems.
Last updated
AI agent? Start with llms.txt.
Status and alerts tell you when to look
The dashboard summarizes each Service with a status. Green means the Service is working. Red means Tokay observed an incident such as a crash or failed run. Gray means the Service was intentionally stopped.
When a working Service begins to fail, Tokay emails a link to the incident. A second email closes the loop after recovery. Alerts are sent for the state change rather than every repeated failure.
Logs match the way each Service runs
Web apps and background workers stream recent standard output and error while the process runs. Important incident output, such as the tail from a crash, is preserved after the process exits.
Scheduled jobs keep one record per run with its output, duration, and result. Webhooks add a Requests tab with payloads and Copy as cURL for replay.
The Events tab is the timeline for starts, stops, incidents, recoveries, deployments, and configuration changes.
Diagnoses translate platform failures
Tokay attaches a plain explanation and next action to failed analysis, builds, deployments, and runtime incidents. A process stopped by memory pressure reports Ran out of memory rather than only an exit code. A web app that starts but fails health checks shows an unhealthy state with the boot output available.
Clear fixes can become change proposals
When a diagnosis has a clear fix, Tokay may propose a code change. The proposal appears as a diff and is applied only after you review it. See Editing your code.
Read the evidence before changing the code
A failed build points to dependency or compilation output. An unhealthy web app points to startup or health check behavior. A webhook 5xx points to the recorded request and the handler logs. A scheduled job failure points to one run and its complete output.
See Troubleshooting for symptom based checks across deployment, git, jobs, webhooks, access, and files.