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
they switch on redaction like this but are seeing content redacted for s3. Even though they have excplicitly only redacted for otel
litellm_settings: callbacks: ["otel", "s3"] callback_settings: otel: message_logging: False
No
1.61.1
No response
The text was updated successfully, but these errors were encountered:
for this ticket, I'd like to re-architect/re-think our current approach to redaction. It has been especially bug prone
open to feedback from our community too
Sorry, something went wrong.
No branches or pull requests
What happened?
they switch on redaction like this but are seeing content redacted for s3. Even though they have excplicitly only redacted for otel
Relevant log output
Are you a ML Ops Team?
No
What LiteLLM version are you on ?
1.61.1
Twitter / LinkedIn details
No response
The text was updated successfully, but these errors were encountered: