feat: add debug logging for model converse requests #297
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.
Description
strands exposes
messages
,system_prompt
, andtool_configs
. Still, one cannot completely reconstruct the converse API request bodies since e.g., theconversation_manager
might truncate messages / tool outputs. The one-liner added in this PR will log the request bodies. This is helpful to exactly reconstruct what was sent to the model.We do this in
types.models.model.Model
abstract base class such that the logging is effective for all model providers.Related Issues
N/A
Documentation PR
N/A
Type of Change
Chore: Adding more debug logging
Testing
For testing, we added a unit test (which we think is not really required and we are happy to remove it before merging in a new revision).
hatch run prepare
Checklist
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.