Skip to content

Conversation

collinss-jpl
Copy link
Contributor

πŸ—’οΈ 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

@collinss-jpl
Copy link
Contributor Author

@nutjob4life Champion-to-Champion: can I get a quick look here as well?

Copy link
Member

@nutjob4life nutjob4life left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Triple crown! πŸ‘‘πŸ‘‘πŸ‘‘

@collinss-jpl collinss-jpl merged commit 7bee7aa into main Sep 29, 2025
2 checks passed
@collinss-jpl collinss-jpl deleted the 282_backoff_logging_to_cloudwatch branch September 29, 2025 19:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

During DUM load, undocumented message about "Backing off"
2 participants