I have searched for all existing open AND closed issues and discussions for similar requests. I have found none that is comparable to my request.
Verify Feature Scope
I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions.
Problem Description
We have no way of knowing which models API users are using.
The audit log does not contain the model name for each log record.
The analytics dashboard do not count API calls.
Desired Solution you'd like
Add the model name to each audit log record.
Alternatives Considered
No response
Additional Context
No response
Originally created by @gaby on GitHub (Feb 20, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/21650
### Check Existing Issues
- [x] I have searched for all existing **open AND closed** issues and discussions for similar requests. I have found none that is comparable to my request.
### Verify Feature Scope
- [x] I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions.
### Problem Description
We have no way of knowing which models API users are using.
- The audit log does not contain the model name for each log record.
- The analytics dashboard do not count API calls.
### Desired Solution you'd like
- Add the model name to each audit log record.
### Alternatives Considered
_No response_
### Additional Context
_No response_
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @gaby on GitHub (Feb 20, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/21650
Check Existing Issues
Verify Feature Scope
Problem Description
We have no way of knowing which models API users are using.
Desired Solution you'd like
Alternatives Considered
No response
Additional Context
No response
@tjbck commented on GitHub (Feb 22, 2026):
Isn't this already being recorded with the request json?