# Inspect logs and running processes

Source: https://zotonic.com/docs/2935/inspect-logs-and-running-processes

URI: https://zotonic.com/id/2935

Language: en

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.

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](/id/1640) and [A page is slow](/id/3004).

License: 

Attribution: 

Related resources: https://zotonic.com/api/agent/related/2935?language=en


## API access

- [API help](<https://zotonic.com/api-help>)
- [OpenAPI specification](<https://zotonic.com/openapi.json>)
- [This resource as JSON](<https://zotonic.com/api/agent/resource/2935?language=en>)
