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 have implemented a custom logger to write all debug logs to a log file. Upon reviewing the log file, I noticed that it contains sensitive information such as LiteLLM API keys and LLM model API keys. After checking the code, it appears that all parameters (including kwargs and LiteLLM-specific parameters) are being logged in their raw form without any key masking.
Relevant log output
No response
Are you a ML Ops Team?
Yes
What LiteLLM version are you on ?
v1.53.1
Twitter / LinkedIn details
No response
The text was updated successfully, but these errors were encountered:
What happened?
I have implemented a custom logger to write all debug logs to a log file. Upon reviewing the log file, I noticed that it contains sensitive information such as LiteLLM API keys and LLM model API keys. After checking the code, it appears that all parameters (including kwargs and LiteLLM-specific parameters) are being logged in their raw form without any key masking.
Relevant log output
No response
Are you a ML Ops Team?
Yes
What LiteLLM version are you on ?
v1.53.1
Twitter / LinkedIn details
No response
The text was updated successfully, but these errors were encountered: