Add suppression for input and output data #5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds two config parameters:
suppress_response_data
, which when set toTrue
, will NOT log response data (like chat responses) to a spansuppress_input_content
, which when set toTrue
, will NOT log input data (like a corpus of text passed to a model with a large context window) to a spanThis lets people avoid reaching limits on spans. Imagine an app that passes in a large amount of data per request, or a long conversation in a chatbot where the entire conversation history is passed in as input each time -- this would likely exceed the total size a span can have.