[DOCS]: where can see those logs for plug in? #273

New Issue

2026-02-16T05:19:41-05:00

yindo commented

2026-02-16 05:19:41 -05:00

Originally created by @shaojun on GitHub (Nov 19, 2025).

Type of Documentation Change

Other

Documentation Page URL or Path

No response

Current Content

No response

Suggested Changes

where can we see those logs??

Reason for Change

No response

Code of Conduct

I agree to follow Dify's documentation contribution guidelines
I have searched for existing issues search for existing issues, including closed ones.
I confirm that I am using English to submit this report, otherwise it will be closed.
【中文用户 & Non English User】请使用英语提交，否则会被关闭：）
Please do not modify this template :) and fill in all the required fields.

Originally created by @shaojun on GitHub (Nov 19, 2025). ### Type of Documentation Change Other ### Documentation Page URL or Path [_No response_](https://docs.dify.ai/plugin-dev-en/0222-debugging-logs) ### Current Content _No response_ ### Suggested Changes where can we see those logs?? ### Reason for Change _No response_ ### Code of Conduct - [x] I agree to follow Dify's documentation [contribution guidelines](https://github.com/langgenius/dify/blob/0277a37fcad5ad86aeb239485c27fffd5cd90043/CONTRIBUTING.md) - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report, otherwise it will be closed. - [x] 【中文用户 & Non English User】请使用英语提交，否则会被关闭：） - [x] Please do not modify this template :) and fill in all the required fields.

yindo added the documentation question labels 2026-02-16 05:19:41 -05:00

yindo closed this issue

2026-02-16 05:19:41 -05:00

yindo commented

2026-02-16 05:19:42 -05:00

@dosubot[bot] commented on GitHub (Nov 19, 2025):

You can view Dify logs in several ways, depending on your deployment:

For Docker deployments, logs are written by default to /app/logs/server.log inside the container. You can access them with commands like docker-compose logs api, docker logs <CONTAINER_ID>, or by running docker exec -it <container_name> tail -f /app/logs/server.log for real-time monitoring. To access logs from your host, mount a Docker volume to /app/logs details.
The log file location, log level, and other settings can be customized in your .env file using variables like LOG_FILE, LOG_LEVEL, LOG_FILE_MAX_SIZE, and LOG_FILE_BACKUP_COUNT reference.
To enable more detailed logs (including request/response info), set ENABLE_REQUEST_LOGGING=True and LOG_LEVEL=DEBUG in your .env file, then restart your containers. SQL statement logging can be enabled with SQLALCHEMY_ECHO=True how-to.
For plugin or workflow logs, check the plugin_daemon, api, and worker service logs with docker-compose logs plugin_daemon, docker-compose logs api, and docker-compose logs worker plugin logs.
Workflow run logs are stored in the workflow_app_logs database table, not in the file or Docker logs db logs.
In the Dify web app, there is a "Logs" section in the left navigation for monitoring user interactions and AI outputs, but backend/system logs are not shown there UI logs.

If you're using the Dify cloud version, log access may be limited or available via the dashboard's plugin section if provided.

To reply, just mention @dosu.

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

@dosubot[bot] commented on GitHub (Nov 19, 2025):  You can view Dify logs in several ways, depending on your deployment: - For Docker deployments, logs are written by default to `/app/logs/server.log` inside the container. You can access them with commands like `docker-compose logs api`, `docker logs <CONTAINER_ID>`, or by running `docker exec -it <container_name> tail -f /app/logs/server.log` for real-time monitoring. To access logs from your host, mount a Docker volume to `/app/logs` [details](https://github.com/langgenius/dify/issues/21773). - The log file location, log level, and other settings can be customized in your `.env` file using variables like `LOG_FILE`, `LOG_LEVEL`, `LOG_FILE_MAX_SIZE`, and `LOG_FILE_BACKUP_COUNT` [reference](https://github.com/langgenius/dify/issues/21078). - To enable more detailed logs (including request/response info), set `ENABLE_REQUEST_LOGGING=True` and `LOG_LEVEL=DEBUG` in your `.env` file, then restart your containers. SQL statement logging can be enabled with `SQLALCHEMY_ECHO=True` [how-to](https://github.com/langgenius/dify/discussions/20955). - For plugin or workflow logs, check the `plugin_daemon`, `api`, and `worker` service logs with `docker-compose logs plugin_daemon`, `docker-compose logs api`, and `docker-compose logs worker` [plugin logs](https://github.com/langgenius/dify/issues/25491). - Workflow run logs are stored in the `workflow_app_logs` database table, not in the file or Docker logs [db logs](https://github.com/langgenius/dify/issues/21773). - In the Dify web app, there is a "Logs" section in the left navigation for monitoring user interactions and AI outputs, but backend/system logs are not shown there [UI logs](https://github.com/langgenius/dify/issues/15016). If you're using the Dify cloud version, log access may be limited or available via the dashboard's plugin section if provided.  *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/64973b8f-719b-4423-a6fa-d17cb91eb9e6?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/64973b8f-719b-4423-a6fa-d17cb91eb9e6?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/64973b8f-719b-4423-a6fa-d17cb91eb9e6?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/64973b8f-719b-4423-a6fa-d17cb91eb9e6?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/64973b8f-719b-4423-a6fa-d17cb91eb9e6?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/64973b8f-719b-4423-a6fa-d17cb91eb9e6?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/64973b8f-719b-4423-a6fa-d17cb91eb9e6?feedback_type=other)</sup>  [![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot) [![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify-docs/issues/529)

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: langgenius/dify-docs#273