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

Some cases not tracked to Langfuse #4827

New Issue
Closed
opened 2026-02-21 18:08:11 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 18:08:11 -05:00
Owner
Copy Link
Copy Source

Originally created by @ymiyata910 on GitHub (Jul 30, 2024).

Originally assigned to: @takatost on GitHub.

Self Checks

  • 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 (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

0.6.15

Cloud or Self Hosted

Cloud, Self Hosted (Docker)

Steps to reproduce

Dify: 0.6.15
Langfuse: v2.66.0

We use Langfuse to track Chatflow.
Chat is now combined with Knowledge.

There are cases where the content of the chat is tracked and cases where it is not tracked.
Although such a case exists in the Cloud version,
In the local version of Dify x Langfuse, the tracking works properly.
Is this a bug?

Thank you.

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @ymiyata910 on GitHub (Jul 30, 2024). Originally assigned to: @takatost on GitHub. ### Self Checks - [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 (我已阅读并同意 [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. ### Dify version 0.6.15 ### Cloud or Self Hosted Cloud, Self Hosted (Docker) ### Steps to reproduce Dify: 0.6.15 Langfuse: v2.66.0 We use Langfuse to track Chatflow. Chat is now combined with Knowledge. There are cases where the content of the chat is tracked and cases where it is not tracked. Although such a case exists in the Cloud version, In the local version of Dify x Langfuse, the tracking works properly. Is this a bug? Thank you. ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 18:08:11 -05:00
yindo closed this issue 2026-02-21 18:08:11 -05:00
yindo commented 2026-02-21 18:08:12 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jul 30, 2024):

Hey @ymiyata910! 👋 I'm here to help you with any bugs, questions, or contributions you have for the project. Let's tackle this together!

There are a few potential reasons why Langfuse tracking might not be consistent in the cloud version of Dify compared to the self-hosted version:

  1. Network and Security Configurations: The cloud version of Dify has different network and security configurations compared to the self-hosted version. The cloud version is hosted on AWS in the U.S. region, which might have different network policies and restrictions that could affect Langfuse tracking [1][2].

  2. Error Logging: The cloud version of Dify generates logs for all interactions, including errors. Specific error codes or messages in the logs, such as error (level) and error (status_message), could indicate failures in Langfuse tracking. Reviewing these logs might help identify the issue [3][4].

  3. Chat and Knowledge Combination: The implementation of chat and knowledge combination in Dify involves configuring context settings, recall strategies, and enabling citation and attribution. This configuration could affect how user interactions are processed and logged, potentially impacting tracking [5][6].

  4. Version Differences: Ensure that both the cloud and self-hosted versions are running the same versions of Dify and Langfuse. Any discrepancies in versions could lead to differences in behavior.

Reviewing the logs for specific error messages and ensuring consistent configurations between the cloud and self-hosted versions might help resolve the issue.

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Jul 30, 2024): <!-- Greeting --> Hey @ymiyata910! 👋 I'm here to help you with any bugs, questions, or contributions you have for the project. Let's tackle this together! <!-- Answer --> There are a few potential reasons why Langfuse tracking might not be consistent in the cloud version of Dify compared to the self-hosted version: 1. **Network and Security Configurations**: The cloud version of Dify has different network and security configurations compared to the self-hosted version. The cloud version is hosted on AWS in the U.S. region, which might have different network policies and restrictions that could affect Langfuse tracking <sup>[[1]](https://github.com/langgenius/dify-docs/blob/main/en/policies/agreement/README.md)</sup><sup>[[2]](https://github.com/langgenius/dify-docs/blob/main/en/getting-started/install-self-hosted/environments.md)</sup>. 2. **Error Logging**: The cloud version of Dify generates logs for all interactions, including errors. Specific error codes or messages in the logs, such as `error` (level) and `error` (status_message), could indicate failures in Langfuse tracking. Reviewing these logs might help identify the issue <sup>[[3]](https://github.com/langgenius/dify-docs/blob/main/en/guides/biao-zhu/logs.md)</sup><sup>[[4]](https://github.com/langgenius/dify-docs/blob/main/zh_CN/guides/monitoring/integrate_external_ops_tools/integrate_langfuse.md)</sup>. 3. **Chat and Knowledge Combination**: The implementation of chat and knowledge combination in Dify involves configuring context settings, recall strategies, and enabling citation and attribution. This configuration could affect how user interactions are processed and logged, potentially impacting tracking <sup>[[5]](https://github.com/langgenius/dify-docs/blob/main/en/guides/knowledge-base/integrate-knowledge-within-application.md)</sup><sup>[[6]](https://github.com/langgenius/dify-docs/blob/main/en/learn-more/use-cases/create-an-ai-chatbot-with-business-data-in-minutes.md)</sup>. 4. **Version Differences**: Ensure that both the cloud and self-hosted versions are running the same versions of Dify and Langfuse. Any discrepancies in versions could lead to differences in behavior. Reviewing the logs for specific error messages and ensuring consistent configurations between the cloud and self-hosted versions might help resolve the issue. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
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 🐞 bug
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#4827
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?