You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to propose a feature where, when a request is made to LiteLLM using a user API token issued by LiteLLM, the user ID associated with that token is automatically logged. Additionally, it would be beneficial if this information could be automatically logged in Langfuse to identify which user created the trace.
This integration will allow the automatic inclusion of user_id in the logging process when requests are sent to Langfuse using the issued tokens. This ensures that Langfuse can accurately track and differentiate request volumes on a per-user basis.
Motivation, pitch
I need accurately log and analyze user-specific spend and token usage in Langfuse. Currently, without the trace_user_id being included in metadata manually, it is challenging to distinguish between requests made by different users, which limits the ability to perform user-specific analytics and reporting (when user misses including metadata)
By enforcing the integration of user information from LiteLLM into Langfuse, we can ensure that each request is associated with the correct userID. This feature is crucial for projects that require detailed user activity tracking and analysis, such as those involving personalized services or usage-based billing.
This proposal addresses the problem of insufficient user-specific logging and enhances the overall functionality and utility of both LiteLLM and Langfuse systems.
Are you a ML Ops Team?
No
The text was updated successfully, but these errors were encountered:
The Feature
I would like to propose a feature where, when a request is made to LiteLLM using a user API token issued by LiteLLM, the user ID associated with that token is automatically logged. Additionally, it would be beneficial if this information could be automatically logged in Langfuse to identify which user created the trace.
This integration will allow the automatic inclusion of user_id in the logging process when requests are sent to Langfuse using the issued tokens. This ensures that Langfuse can accurately track and differentiate request volumes on a per-user basis.
Motivation, pitch
I need accurately log and analyze user-specific spend and token usage in Langfuse. Currently, without the
trace_user_id
being included in metadata manually, it is challenging to distinguish between requests made by different users, which limits the ability to perform user-specific analytics and reporting (when user misses including metadata)By enforcing the integration of user information from LiteLLM into Langfuse, we can ensure that each request is associated with the correct userID. This feature is crucial for projects that require detailed user activity tracking and analysis, such as those involving personalized services or usage-based billing.
This proposal addresses the problem of insufficient user-specific logging and enhances the overall functionality and utility of both LiteLLM and Langfuse systems.
Are you a ML Ops Team?
No
The text was updated successfully, but these errors were encountered: