[Feature]: turn_off_message_logging parameter per callback

[dominikkoller-hs]

The Feature

Currently, turn_off_message_logging is a global parameter that can be set in config.yaml:

litellm_settings:
  success_callback: ["langfuse"]
  turn_off_message_logging: True

We would like to be able to set this per callback instead, so that one callback logs messages, while another callback redacts messages. Something like:

litellm_settings:
  success_callback:
    - name: "langfuse"
      turn_off_message_logging: false
    - name: "s3_v2"
      turn_off_message_logging: true

Motivation, pitch

This would be helpful to separate callbacks with highly sensitive message content vs callbacks with lower data sensitivity.

LiteLLM is hiring a founding backend engineer, are you interested in joining us and shipping to all our users?

No

Twitter / LinkedIn details

No response

[dominikkoller-hs]

As a side note, having a negative in a config parameter is confusing. The parameter should be called something like message_logging instead. As a case in point, on your own docs page:
https://docs.litellm.ai/docs/proxy/logging

You have both turn_on_message_logging and turn_off_message_logging, one of which is probably a typo.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.