We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Store the abbreviated string of sk-key in db like openai does (can do this in the token and spend logs table)
easier for app owner viewing their spend logs to know which sk-key is causing a high spend
No response
The text was updated successfully, but these errors were encountered:
Checking with users if this is something they'd want
Sorry, something went wrong.
key
/key/info
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
allow_user_auth
We can gate this feature behind that too.
Live in v1.20.0
1.20.0
No branches or pull requests
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
The text was updated successfully, but these errors were encountered: