github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-07 03:18:23 -05:00
Code Issues 1.3k Packages Projects Releases 126 Wiki Activity

[GH-ISSUE #23248] issue: #35459

New Issue
Closed
opened 2026-04-25 09:40:11 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-25 09:40:11 -05:00
Owner
Copy Link

Originally created by @kamabokowen on GitHub (Mar 31, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/23248

Check Existing Issues

  • I have searched for any existing and/or related issues.
  • I have searched for any existing and/or related discussions.
  • I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!).
  • I am using the latest version of Open WebUI.

Installation Method

Docker

Open WebUI Version

v0.8.12

Ollama Version (if applicable)

No response

Operating System

ubuntu 24.04

Browser (if applicable)

No response

Confirmation

  • I have read and followed all instructions in README.md.
  • I am using the latest version of both Open WebUI and Ollama.
  • I have included the browser console logs.
  • I have included the Docker container logs.
  • I have provided every relevant configuration, setting, and environment variable used in my setup.
  • I have clearly listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
  • I have documented step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation. My steps:
  • Start with the initial platform/version/OS and dependencies used,
  • Specify exact install/launch/configure commands,
  • List URLs visited, user input (incl. example values/emails/passwords if needed),
  • Describe all options and toggles enabled or changed,
  • Include any files or environmental changes,
  • Identify the expected and actual result at each stage,
  • Ensure any reasonably skilled user can follow and hit the same issue.

Expected Behavior

Analytics should permanently record and retain all usage data (e.g., request counts, token usage, model usage statistics), regardless of whether the corresponding conversations are later deleted by users.

Specifically:
Deleting a conversation should only remove it from the user interface.
Historical usage metrics (request count, token consumption, model usage) should remain unchanged.
Administrative Analytics should reflect total historical usage, not only currently stored conversations.
Usage metrics should be immutable once recorded.

Actual Behavior

When a user deletes one or more conversations:
The associated usage data is removed from the Analytics dashboard.
Model usage counts decrease.
Token consumption metrics decrease accordingly.
The Analytics dashboard reflects only the usage from currently existing (non-deleted) conversations.
This results in inaccurate usage reporting and prevents administrators from reliably auditing historical consumption.

Steps to Reproduce

Using the normal user account:
Select a model (e.g., gpt or any available model).
Create conversations.
Log out from the normal user.
Log back in as Admin.
Record the following values: Total requests, Total tokens, Model usage counts, Any per-user usage statistics
At this point, you should see non-zero usage corresponding to the 10 conversations.
Log out as Admin.
Log back in as the normal user.
Go to the conversation list.
Delete all conversations manually:
Ensure that no conversations remain in the sidebar.
After deletion: Total request count has decreased (or returned to zero). Model usage statistics have decreased.
The Analytics dashboard now reflects only existing conversations (which are none).

Logs & Screenshots

Before delete:
Image

After delete:

Image

Additional Information

No response

Originally created by @kamabokowen on GitHub (Mar 31, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/23248 ### Check Existing Issues - [x] I have searched for any existing and/or related issues. - [x] I have searched for any existing and/or related discussions. - [x] I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!). - [x] I am using the latest version of Open WebUI. ### Installation Method Docker ### Open WebUI Version v0.8.12 ### Ollama Version (if applicable) _No response_ ### Operating System ubuntu 24.04 ### Browser (if applicable) _No response_ ### Confirmation - [x] I have read and followed all instructions in `README.md`. - [x] I am using the latest version of **both** Open WebUI and Ollama. - [x] I have included the browser console logs. - [x] I have included the Docker container logs. - [x] I have **provided every relevant configuration, setting, and environment variable used in my setup.** - [x] I have clearly **listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup** (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc). - [x] I have documented **step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation**. My steps: - Start with the initial platform/version/OS and dependencies used, - Specify exact install/launch/configure commands, - List URLs visited, user input (incl. example values/emails/passwords if needed), - Describe all options and toggles enabled or changed, - Include any files or environmental changes, - Identify the expected and actual result at each stage, - Ensure any reasonably skilled user can follow and hit the same issue. ### Expected Behavior Analytics should permanently record and retain all usage data (e.g., request counts, token usage, model usage statistics), regardless of whether the corresponding conversations are later deleted by users. Specifically: Deleting a conversation should only remove it from the user interface. Historical usage metrics (request count, token consumption, model usage) should remain unchanged. Administrative Analytics should reflect total historical usage, not only currently stored conversations. Usage metrics should be immutable once recorded. ### Actual Behavior When a user deletes one or more conversations: The associated usage data is removed from the Analytics dashboard. Model usage counts decrease. Token consumption metrics decrease accordingly. The Analytics dashboard reflects only the usage from currently existing (non-deleted) conversations. This results in inaccurate usage reporting and prevents administrators from reliably auditing historical consumption. ### Steps to Reproduce Using the normal user account: Select a model (e.g., gpt or any available model). Create conversations. Log out from the normal user. Log back in as Admin. Record the following values: Total requests, Total tokens, Model usage counts, Any per-user usage statistics At this point, you should see non-zero usage corresponding to the 10 conversations. Log out as Admin. Log back in as the normal user. Go to the conversation list. Delete all conversations manually: Ensure that no conversations remain in the sidebar. After deletion: Total request count has decreased (or returned to zero). Model usage statistics have decreased. The Analytics dashboard now reflects only existing conversations (which are none). ### Logs & Screenshots Before delete: <img width="1680" height="806" alt="Image" src="https://github.com/user-attachments/assets/fa24f3bf-9e71-4193-a6db-80b6b539744d" /> After delete: <img width="1668" height="653" alt="Image" src="https://github.com/user-attachments/assets/24563ea2-7260-4e63-9074-53b15a21afc2" /> ### Additional Information _No response_
GiteaMirror added the bug label 2026-04-25 09:40:11 -05:00
GiteaMirror commented 2026-04-25 09:40:13 -05:00
Author
Owner
Copy Link

@pr-validator-bot commented on GitHub (Mar 31, 2026):

⚠️ Invalid Issue Title

Hey @kamabokowen, please provide a descriptive title for your issue. Titles that are empty, very short (under 10 characters), or generic (like "issue:" or "feat:") make it difficult for volunteer contributors to understand and triage issues.

Please update the title to reflect the content of your issue.

⚠️ Missing Issue Title Prefix

@kamabokowen, your issue title is missing a prefix (e.g., bug:, feat:, docs:).

Please update your issue title to include one of the following prefixes:

  • bug: Bug report or error you've encountered
  • feat: Feature request or enhancement suggestion
  • docs: Documentation issue or improvement request
  • question: Question about usage or functionality
  • help: Request for help or support

Example: bug: Login fails when using special characters in password

<!-- gh-comment-id:4160554538 --> @pr-validator-bot commented on GitHub (Mar 31, 2026): # ⚠️ Invalid Issue Title Hey @kamabokowen, please provide a descriptive title for your issue. Titles that are empty, very short (under 10 characters), or generic (like "issue:" or "feat:") make it difficult for volunteer contributors to understand and triage issues. Please update the title to reflect the content of your issue. --- # ⚠️ Missing Issue Title Prefix @kamabokowen, your issue title is missing a prefix (e.g., `bug:`, `feat:`, `docs:`). Please update your issue title to include one of the following prefixes: - **bug**: Bug report or error you've encountered - **feat**: Feature request or enhancement suggestion - **docs**: Documentation issue or improvement request - **question**: Question about usage or functionality - **help**: Request for help or support Example: `bug: Login fails when using special characters in password`
GiteaMirror commented 2026-04-25 09:40:14 -05:00
Author
Owner
Copy Link

@Classic298 commented on GitHub (Mar 31, 2026):

not an issue, this is intended behaviour - open to discussion

<!-- gh-comment-id:4160554970 --> @Classic298 commented on GitHub (Mar 31, 2026): not an issue, this is intended behaviour - open to discussion
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#35459
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?