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

I hope to see the original data obtained when the underlying layer requests LLM, rather than the data after dify packaging? #16354

New Issue
Closed
opened 2026-02-21 19:25:47 -05:00 by yindo · 2 comments
yindo commented 2026-02-21 19:25:47 -05:00
Owner
Copy Link
Copy Source

Originally created by @Vampxgg on GitHub (Aug 22, 2025).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • 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.

Dify version

1.7.2

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

I hope to see the original data obtained when the underlying layer requests LLM, rather than the data after dify packaging?

Image

✔️ Expected Behavior

1

❌ Actual Behavior

No response

Originally created by @Vampxgg on GitHub (Aug 22, 2025). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [x] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [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. ### Dify version 1.7.2 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce I hope to see the original data obtained when the underlying layer requests LLM, rather than the data after dify packaging? <img width="690" height="1434" alt="Image" src="https://github.com/user-attachments/assets/067c02fc-f2bc-41da-8a16-8771ede9ef7a" /> ### ✔️ Expected Behavior 1 ### ❌ Actual Behavior _No response_
yindo added the 💪 enhancement label 2026-02-21 19:25:47 -05:00
yindo closed this issue 2026-02-21 19:25:47 -05:00
yindo commented 2026-02-21 19:25:47 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Aug 22, 2025):

Dify does not currently provide a built-in way to view the raw LLM response before it is processed or packaged. However, since you are self-hosting, you can modify the code to log or expose the original data. The raw LLM response is accessible in the provider classes (under api/core/model_runtime/model_providers/) and in the LLMGenerator class (api/core/llm_generator/llm_generator.py) as response.message.content before any transformation or packaging occurs source.

To log the raw response, add a line like print(response.message.content) or use a logger right after the LLM call and before any parsing or cleaning. After making code changes, rebuild your Docker container to apply them.

Be mindful of privacy and log management—raw LLM responses may contain sensitive information. If you need help locating the exact provider file for your LLM, let me know which provider you use (e.g., OpenAI, Azure, etc.).

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Chat with Dosu Join Discord Share on X

@dosubot[bot] commented on GitHub (Aug 22, 2025): <!-- Answer --> Dify does not currently provide a built-in way to view the raw LLM response before it is processed or packaged. However, since you are self-hosting, you can modify the code to log or expose the original data. The raw LLM response is accessible in the provider classes (under `api/core/model_runtime/model_providers/`) and in the `LLMGenerator` class (`api/core/llm_generator/llm_generator.py`) as `response.message.content` before any transformation or packaging occurs [source](https://github.com/langgenius/dify/blob/2a43e634e83f98c59776f479c3c0e68e648e53b3/api/core/llm_generator/llm_generator.py). To log the raw response, add a line like `print(response.message.content)` or use a logger right after the LLM call and before any parsing or cleaning. After making code changes, rebuild your Docker container to apply them. Be mindful of privacy and log management—raw LLM responses may contain sensitive information. If you need help locating the exact provider file for your LLM, let me know which provider you use (e.g., OpenAI, Azure, etc.). <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/008b2926-6393-4edc-86ed-270bd82630a5?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/008b2926-6393-4edc-86ed-270bd82630a5?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/008b2926-6393-4edc-86ed-270bd82630a5?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/008b2926-6393-4edc-86ed-270bd82630a5?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/008b2926-6393-4edc-86ed-270bd82630a5?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/008b2926-6393-4edc-86ed-270bd82630a5?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/008b2926-6393-4edc-86ed-270bd82630a5?feedback_type=other)</sup>&nbsp;&nbsp;[![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![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/issues/24336)
yindo commented 2026-02-21 19:25:47 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Aug 22, 2025):

This is only for bug report, if you would like to ask a question, please head to Discussions.

@crazywoola commented on GitHub (Aug 22, 2025): This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general).
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#16354
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?