You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Smithy based design changes to the SDK and the corresponding middleware design has highlighted the need to review our current approach to logging and log levels. Ideally each middleware should be able to produce sufficient logging at various levels of verbosity where necessary, and customers should be able to preferably target middleware by their identifiers to enable/disable and modify the verbosity of the logged statements. Most important is that we must not make assumptions about the underlying logging implementation provided, and allow users to plug into a minimal interface to satisfy with their own implementation or another community library.
The text was updated successfully, but these errors were encountered:
jasdel
changed the title
Improvements to SDK Logging Facilities for Smithy-based Clients
Improvements to SDK Logging and debug Facilities for Smithy-based Clients
Oct 21, 2020
jasdel
changed the title
Improvements to SDK Logging and debug Facilities for Smithy-based Clients
Improvements to SDK Logging and debug Facilities SDK middleware, API clients, and Config loading
Oct 21, 2020
Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.
The Smithy based design changes to the SDK and the corresponding middleware design has highlighted the need to review our current approach to logging and log levels. Ideally each middleware should be able to produce sufficient logging at various levels of verbosity where necessary, and customers should be able to preferably target middleware by their identifiers to enable/disable and modify the verbosity of the logged statements. Most important is that we must not make assumptions about the underlying logging implementation provided, and allow users to plug into a minimal interface to satisfy with their own implementation or another community library.
The text was updated successfully, but these errors were encountered: