[PR #14803] [CLOSED] User level activity through time for app metrics #46648

New Issue

GiteaMirror · 2026-04-29T21:31:36-05:00

GiteaMirror commented

2026-04-29 21:31:36 -05:00

📋 Pull Request Information

Original PR: https://github.com/open-webui/open-webui/pull/14803
Author: @rragundez
Created: 6/9/2025
Status: ❌ Closed

Base: dev ← Head: user-historical-events

📝 Commits (4)

3572c7a Add table for registering the last user tampstamp per hour
2f81351 Add trigger listener from user action to user historical events
5143d6e Register new table and trigger
e5268a8 Add alembic migration logic

📊 Changes

4 files changed (+80 additions, -4 deletions)

View changed files

📝 backend/open_webui/main.py (+4 -0)
➕ backend/open_webui/migrations/versions/757136e86672_add_userhistoricalevents_table.py (+33 -0)
📝 backend/open_webui/models/users.py (+17 -4)
➕ backend/open_webui/utils/event_listener.py (+26 -0)

📄 Description

Currently there is no way of retrieving historical usage data from the application simply/natively. The only related information in the database is the last_active_at field in the user table, but that only acts as a sort of sliding window as the users use the application.
This is a major metric to assess the use, success and cost per user per month of the application. And the information is normally use to make decisions if to continue using the application or buy a SAAS.

This PR adds an extra table that keeps the historical activity time grouped by user and hour. WIth this change is easy to see users per hour or day or per month.

This implementation does not introduce any change in the application backend logic but it is based on setting a trigger on the existing database such that an entry is generated every time the user.last_active_at gets updated. The logic also makes sure there is a maximum a 1 entry per user-hour combination to avoid the table blowing up.

With this change it becomes very easy to retrieve user usage through time in external tools like Grafana for example. I did test the change and can see the entry being updated every hour if I make an action in the application.

I know there are some issues open asking for this but I did not have the time to go into them.

Note to first-time contributors: Please open a discussion post in Discussions and describe your changes before submitting a pull request.

Before submitting, make sure you've checked the following:

Target branch: Please verify that the pull request targets the dev branch.
Description: Provide a concise description of the changes made in this pull request.
Changelog: Ensure a changelog entry following the format of Keep a Changelog is added at the bottom of the PR description.
Documentation: Have you updated relevant documentation Open WebUI Docs, or other documentation sources?
Dependencies: Are there any new dependencies? Have you updated the dependency versions in the documentation?
Testing: Have you written and run sufficient tests to validate the changes?
Code review: Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards?
Prefix: To clearly categorize this pull request, prefix the pull request title using one of the following:
- BREAKING CHANGE: Significant changes that may affect compatibility
- build: Changes that affect the build system or external dependencies
- ci: Changes to our continuous integration processes or workflows
- chore: Refactor, cleanup, or other non-functional code changes
- docs: Documentation update or addition
- feat: Introduces a new feature or enhancement to the codebase
- fix: Bug fix or error correction
- i18n: Internationalization or localization changes
- perf: Performance improvement
- refactor: Code restructuring for better maintainability, readability, or scalability
- style: Changes that do not affect the meaning of the code (white space, formatting, missing semi-colons, etc.)
- test: Adding missing tests or correcting existing tests
- WIP: Work in progress, a temporary label for incomplete or ongoing work

Changelog Entry

Description

[Concisely describe the changes made in this pull request, including any relevant motivation and impact (e.g., fixing a bug, adding a feature, or improving performance)]

Added

[List any new features, functionalities, or additions]

Changed

[List any changes, updates, refactorings, or optimizations]

Deprecated

[List any deprecated functionality or features that have been removed]

Removed

[List any removed features, files, or functionalities]

Fixed

[List any fixes, corrections, or bug fixes]

Security

[List any new or updated security-related changes, including vulnerability fixes]

Breaking Changes

BREAKING CHANGE: [List any breaking changes affecting compatibility or functionality]

Additional Information

[Insert any additional context, notes, or explanations for the changes]
- [Reference any related issues, commits, or other relevant information]

Screenshots or Videos

[Attach any relevant screenshots or videos demonstrating the changes]

Contributor License Agreement

By submitting this pull request, I confirm that I have read and fully agree to the Contributor License Agreement (CLA), and I am providing my contributions under its terms.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/open-webui/open-webui/pull/14803 **Author:** [@rragundez](https://github.com/rragundez) **Created:** 6/9/2025 **Status:** ❌ Closed **Base:** `dev` ← **Head:** `user-historical-events` --- ### 📝 Commits (4) - [`3572c7a`](https://github.com/open-webui/open-webui/commit/3572c7aaa85b3f8bcf66bf476be047fccdd7bbe8) Add table for registering the last user tampstamp per hour - [`2f81351`](https://github.com/open-webui/open-webui/commit/2f81351ce63e93f8f1fdd835686aabc32fd87a10) Add trigger listener from user action to user historical events - [`5143d6e`](https://github.com/open-webui/open-webui/commit/5143d6e4793a6cc164c91060c55c944afb99c9bb) Register new table and trigger - [`e5268a8`](https://github.com/open-webui/open-webui/commit/e5268a8bd66d58c9bca298ec1b4ac20103aef10b) Add alembic migration logic ### 📊 Changes **4 files changed** (+80 additions, -4 deletions) <details> <summary>View changed files</summary> 📝 `backend/open_webui/main.py` (+4 -0) ➕ `backend/open_webui/migrations/versions/757136e86672_add_userhistoricalevents_table.py` (+33 -0) 📝 `backend/open_webui/models/users.py` (+17 -4) ➕ `backend/open_webui/utils/event_listener.py` (+26 -0) </details> ### 📄 Description Currently there is no way of retrieving historical usage data from the application simply/natively. The only related information in the database is the `last_active_at` field in the `user` table, but that only acts as a sort of sliding window as the users use the application. This is a major metric to assess the use, success and cost per user per month of the application. And the information is normally use to make decisions if to continue using the application or buy a SAAS. This PR adds an extra table that keeps the historical activity time grouped by user and hour. WIth this change is easy to see users per hour or day or per month. This implementation does not introduce any change in the application backend logic but it is based on setting a trigger on the existing database such that an entry is generated every time the `user.last_active_at` gets updated. The logic also makes sure there is a maximum a 1 entry per user-hour combination to avoid the table blowing up. With this change it becomes very easy to retrieve user usage through time in external tools like Grafana for example. I did test the change and can see the entry being updated every hour if I make an action in the application. I know there are some issues open asking for this but I did not have the time to go into them. ### Note to first-time contributors: Please open a discussion post in [Discussions](https://github.com/open-webui/open-webui/discussions) and describe your changes before submitting a pull request. **Before submitting, make sure you've checked the following:** - [ ] **Target branch:** Please verify that the pull request targets the `dev` branch. - [ ] **Description:** Provide a concise description of the changes made in this pull request. - [ ] **Changelog:** Ensure a changelog entry following the format of [Keep a Changelog](https://keepachangelog.com/) is added at the bottom of the PR description. - [ ] **Documentation:** Have you updated relevant documentation [Open WebUI Docs](https://github.com/open-webui/docs), or other documentation sources? - [ ] **Dependencies:** Are there any new dependencies? Have you updated the dependency versions in the documentation? - [ ] **Testing:** Have you written and run sufficient tests to validate the changes? - [ ] **Code review:** Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards? - [ ] **Prefix:** To clearly categorize this pull request, prefix the pull request title using one of the following: - **BREAKING CHANGE**: Significant changes that may affect compatibility - **build**: Changes that affect the build system or external dependencies - **ci**: Changes to our continuous integration processes or workflows - **chore**: Refactor, cleanup, or other non-functional code changes - **docs**: Documentation update or addition - **feat**: Introduces a new feature or enhancement to the codebase - **fix**: Bug fix or error correction - **i18n**: Internationalization or localization changes - **perf**: Performance improvement - **refactor**: Code restructuring for better maintainability, readability, or scalability - **style**: Changes that do not affect the meaning of the code (white space, formatting, missing semi-colons, etc.) - **test**: Adding missing tests or correcting existing tests - **WIP**: Work in progress, a temporary label for incomplete or ongoing work # Changelog Entry ### Description - [Concisely describe the changes made in this pull request, including any relevant motivation and impact (e.g., fixing a bug, adding a feature, or improving performance)] ### Added - [List any new features, functionalities, or additions] ### Changed - [List any changes, updates, refactorings, or optimizations] ### Deprecated - [List any deprecated functionality or features that have been removed] ### Removed - [List any removed features, files, or functionalities] ### Fixed - [List any fixes, corrections, or bug fixes] ### Security - [List any new or updated security-related changes, including vulnerability fixes] ### Breaking Changes - **BREAKING CHANGE**: [List any breaking changes affecting compatibility or functionality] --- ### Additional Information - [Insert any additional context, notes, or explanations for the changes] - [Reference any related issues, commits, or other relevant information] ### Screenshots or Videos - [Attach any relevant screenshots or videos demonstrating the changes] ### Contributor License Agreement By submitting this pull request, I confirm that I have read and fully agree to the [Contributor License Agreement (CLA)](/CONTRIBUTOR_LICENSE_AGREEMENT), and I am providing my contributions under its terms. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

GiteaMirror added the pull-request label 2026-04-29 21:31:36 -05:00

GiteaMirror closed this issue

2026-04-29 21:31:38 -05:00

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/open-webui#46648