langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-22 04:25:29 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Add end_user_id in the param of request to Moderation Extension API for convenient when doing user log audit #2489

New Issue
Closed
opened 2026-02-21 17:46:23 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 17:46:23 -05:00
Owner
Copy Link
Copy Source

Originally created by @DatumWorld on GitHub (Apr 23, 2024).

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).
  • Pleas do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing?

If we need to know which client( or end user) sent a piece of specified message , and whether sensitive words were found in this message, both user_id and the input or query are needed in the request. It is common when doing user log audit. While I found no client or end user info in request param.

2. Describe the feature you'd like to see

Add end_user_id or client id in the request params to Moderation Extension API,both inputs and outputs points.

3. How will this feature improve your workflow or experience?

It is convenient for us to finish user log audit with less time and more exactly，the log is too much

4. Additional context or comments

No response

5. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @DatumWorld on GitHub (Apr 23, 2024). ### Self Checks - [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 (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [X] Pleas do not modify this template :) and fill in all the required fields. ### 1. Is this request related to a challenge you're experiencing? If we need to know which client( or end user) sent a piece of specified message , and whether sensitive words were found in this message, both user_id and the input or query are needed in the request. It is common when doing user log audit. While I found no client or end user info in request param. ### 2. Describe the feature you'd like to see Add end_user_id or client id in the request params to Moderation Extension API,both inputs and outputs points. ### 3. How will this feature improve your workflow or experience? It is convenient for us to finish user log audit with less time and more exactly，the log is too much ### 4. Additional context or comments _No response_ ### 5. Can you help us with this feature? - [X] I am interested in contributing to this feature.
yindo added the 💪 enhancement label 2026-02-21 17:46:23 -05:00
yindo closed this issue 2026-02-21 17:46:23 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
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#2489
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?