Reduce amount of logging from #[instrument] #2934
Merged
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.
Will be merged to
smithy-rs-release-0.56.x
branchAddresses awslabs/aws-sdk-rust#872
Motivation and Context
With the introduction of the orchestrator, the core functions that live in
aws-smithy-runtime/src/client/orchestrator.rs
were annotated by#instrument
. By default this emits logs at theINFO
level, which caused our customer to see the excessive amount of logging after switching to the latest SDK creates0.29
.Description
This PR reduces the log level to
DEBUG
wherever we use#instrument
throughout the file.Testing
No new tests have been added as part of this PR. An enhancement has been filed to check logging volume.
Here is a quick check that all instances in the file specify
trace
:Checklist
CHANGELOG.next.toml
if I made changes to the smithy-rs codegen or runtime cratesCHANGELOG.next.toml
if I made changes to the AWS SDK, generated SDK code, or SDK runtime cratesBy submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.