Fix for Backoff/Retry logging to Cloudwatch #285
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.
ποΈ Summary
This branch fixes several issues which prevented log messages pertaining to backoff/retry attempts from inclusion with those sent to CloudWatch logs. With these fixes, the log contents sent to CloudWatch should now properly mirror the log contents written to file on the local machine.
This branch also updates the Sphinx documentation for the client to document usage of the backoff/retry feature, and provide some examples of backoff/retry log messages a user might encounter within a log file.
βοΈ Test Data and/or Report
No changes to existing test suite by this branch. All regression tests are still passing.
β»οΈ Related Issues
Resolves #282