How to oberseve execution logs of plugin in plugin daemon?

[razerzhang]

Self Checks

• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
• Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

Hi,
It looks like plugin-daemon isn’t printing the plugin’s execution logs. As a result, when a plugin throws an exception, it’s difficult to identify the root cause because we can’t find the corresponding runtime logs.

Could you please advise:

1. How to enable or increase logging for plugin execution in plugin-daemon?
2. Where the plugin execution logs are supposed to be written ?
3. Whether there is a way to capture full stack traces and context (plugin name, inputs/outputs, execution time) when exceptions occur?

2. Additional context or comments

No response

[dosubot[bot]]

Hi! Here's what I found about observing plugin execution logs in the plugin daemon:

1. How to enable/increase logging:

Set these environment variables on the Dify API service:

• LOG_LEVEL=DEBUG - for more verbose logs (default is "INFO")
• LOG_OUTPUT_FORMAT=json - for structured logs (helpful for parsing)
• DEBUG=true - enables debug mode

2. Where logs are written:

• Console (stdout): Always enabled by default
• File: Set LOG_FILE=/path/to/logfile to enable file logging
• File rotation is controlled by LOG_FILE_MAX_SIZE (default 20MB) and LOG_FILE_BACKUP_COUNT (default 5)

3. Exception/stack trace logging:

Plugin exceptions are logged with full stack traces using logger.exception() in the plugin client code. However, the current implementation does not automatically capture:

• Plugin inputs/outputs
• Execution time metrics

These would need custom implementation if required.

Important note: This logging is configured at the Dify application level (API service), not the plugin daemon itself. The plugin daemon operates as a separate remote HTTP service. If you're looking to see logs from within the plugin daemon process itself, you may need to check the plugin daemon's own configuration or repository.

See the LoggingConfig in feature/init.py for all available logging options.

To reply, just mention @dosu.

---

Docs are dead. Just use Dosu.