Closed krrishdholakia closed 9 months ago
Checking with users if this is something they'd want
Seems like this should be opt-in.
Since this is for key-owners happiness, and we already gate key-owner specific permissions behind allow_user_auth
- https://docs.litellm.ai/docs/proxy/ui#step-2-enable-user-auth
We can gate this feature behind that too.
Live in v1.20.0
The Feature
Store the abbreviated string of sk-key in db like openai does (can do this in the token and spend logs table)
Motivation, pitch
easier for app owner viewing their spend logs to know which sk-key is causing a high spend
Twitter / LinkedIn details
No response