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

[PR #29212] feat: add new WEAVIATE_DISABLE_TELEMETRY env to disable telemetry collection for weaviate #32336

New Issue
Closed
opened 2026-02-21 20:51:12 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 20:51:12 -05:00
Owner
Copy Link
Copy Source

Original Pull Request: https://github.com/langgenius/dify/pull/29212

State: closed
Merged: Yes

Summary

This PR allows users to disable Weaviate telemetry collection by using a new environment variable, WEAVIATE_DISABLE_TELEMETRY.
Changes have been made to both docker-compose.yaml and docker-compose.middleware.yaml.

The default value is false, which means telemetry collection is enabled (to maintain backward compatibility).

Closes #29210

Screenshots

Before After
image No telemetry started log.

Checklist

  • This change requires a documentation update, included: Dify Document
  • I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!)
  • I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change.
  • I've updated the documentation accordingly.
  • I ran dev/reformat(backend) and cd web && npx lint-staged(frontend) to appease the lint gods
**Original Pull Request:** https://github.com/langgenius/dify/pull/29212 **State:** closed **Merged:** Yes --- ## Summary This PR allows users to disable Weaviate telemetry collection by using a new environment variable, `WEAVIATE_DISABLE_TELEMETRY`. Changes have been made to both `docker-compose.yaml` and `docker-compose.middleware.yaml`. The default value is `false`, which means telemetry collection is _enabled_ (to maintain backward compatibility). Closes #29210 ## Screenshots | Before | After | |--------|-------| | <img width="2496" height="84" alt="image" src="https://github.com/user-attachments/assets/c500c8c6-d69a-4265-9dc5-635b3c1d071e" /> | No `telemetry started` log. | ## Checklist - [ ] This change requires a documentation update, included: [Dify Document](https://github.com/langgenius/dify-docs) - [x] I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!) - [ ] I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change. - [ ] I've updated the documentation accordingly. - [ ] I ran `dev/reformat`(backend) and `cd web && npx lint-staged`(frontend) to appease the lint gods
yindo added the pull-request label 2026-02-21 20:51:12 -05:00
yindo closed this issue 2026-02-21 20:51:12 -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 pull-request
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#32336
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?