langgenius/dify-plugin-daemon
1
0
Fork 0
mirror of https://github.com/langgenius/dify-plugin-daemon.git synced 2026-07-21 17:25:23 -04:00
Code Issues 111 Packages Projects Releases 10 Wiki Activity

Implement structured logging and Trace ID propagation #224

New Issue
Closed
opened 2026-02-16 01:15:01 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 01:15:01 -05:00
Owner
Copy Link
Copy Source

Originally created by @41tair on GitHub (Dec 24, 2025).

Self Checks

To make sure we get to you in time, please check the following :)

  • 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."

Is your feature request related to a problem? Please describe.

  1. Logs are unstructured, making them difficult to be parsed by modern logging systems.
  2. Missing Trace ID and Span ID in the context.
  3. Requests returning 404 status codes are not logged.

Describe the solution you'd like

  1. Adopt a unified structured logging format
  2. Extract and propagate Trace ID and Span ID throughout the application context.
  3. Inject Trace ID into headers when making outbound HTTP requests.
  4. Ensure backward compatibility (e.g., via configuration flags) to avoid breaking existing log ingestion pipelines.

Describe alternatives you've considered

Additional context

Originally created by @41tair on GitHub (Dec 24, 2025). **Self Checks** To make sure we get to you in time, please check the following :) - [X] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify-plugin-daemon/issues), including closed ones. - [X] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [X] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:) - [X] "Please do not modify this template :) and fill in all the required fields." **Is your feature request related to a problem? Please describe.** 1. Logs are unstructured, making them difficult to be parsed by modern logging systems. 2. Missing Trace ID and Span ID in the context. 3. Requests returning 404 status codes are not logged. **Describe the solution you'd like** 1. Adopt a unified structured logging format 2. Extract and propagate Trace ID and Span ID throughout the application context. 3. Inject Trace ID into headers when making outbound HTTP requests. 4. Ensure backward compatibility (e.g., via configuration flags) to avoid breaking existing log ingestion pipelines. **Describe alternatives you've considered** **Additional context**
yindo added the enhancement label 2026-02-16 01:15:01 -05:00
yindo closed this issue 2026-02-16 01:15:01 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Windows
bug
cmd
documentation
enhancement
go
good first issue
plugin-daemon
pull-request
Mirrored from GitHub Pull Request
 question
No Label enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify-plugin-daemon#224
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?