Inspect logs and running processes

Use bin/zotonic logtail for the configured console log, or select error or crash when those files are available. The command prints the last 500 lines and exits; it does not follow the log continuously.

For live process activity, use bin/zotonic etop if the Erlang installation includes the required tool. Identify the process and time period responsible for repeated activity before changing configuration.

Prefer structured logs containing the operation, result, reason on failure, and a useful resource or site identifier. Avoid logging request bodies or tokens as a shortcut to understanding a problem.

A busy process alone does not identify the slow request. Correlate request timing with template, function, and database traces. See Write logs that explain an operation and A page is slow.