Logs UI — end_user field not visible in logs table

[pierrelouisbess]

Hi,
I'm using LiteLLM v1.82.4 and tracking end users by passing the user field in request body (or via x-litellm-end-user-id header). The end_user field is correctly stored in LiteLLM_SpendLogs and visible in the Customer Usage tab, but it doesn't appear as a column in the Logs UI view.
Would it be possible to add end_user as a visible/filterable column in the Logs table? This would be very useful for audit purposes in enterprise deployments where multiple users share the same virtual key.
Thanks !

[jagmarques]

The end_user visibility gap is a real blocker for enterprise audit. We hit the same issue - you need to answer "which user triggered this LLM call" months later, and having to query LiteLLM_SpendLogs directly defeats the purpose of having a logs UI.

Until this lands natively, one pattern that works: set up a custom callback that writes end_user + request metadata to a separate audit table, then join it in your SIEM. Not ideal but it decouples your audit trail from the LiteLLM UI release cycle.

For the feature itself, making end_user both visible and filterable would also solve per-user cost attribution - the other common enterprise ask alongside audit.