🗒️ send a custom logger to the retryable HTTP client

[jadudm]

At a glance

In order to keep things quiet
as a developer
I want the ability to control the logging of my application

Acceptance Criteria

We use DRY behavior-driven development wherever possible.

then...

Beta Give feedback

1. [a thing happens]

Shepherd

• UX shepherd:
• Design shepherd:
• Engineering shepherd:

Background

On every fetch we are currently logging to STDOUT, because the http.Client in the retryable package is sending DEBUG-level messages.

We might want that... or we might want. That could mean ~25M log lines/month, which we do not necessarily want.

This should follow the app-wide logger, and only send info.

Security Considerations

Required per CM-4.

We need to log as part of our SSP/compliance work, but we also want to log what makes sense. Logging everything that we fetch is not necessary, because it shows up in the end product. (For debugging, we want it... not for production.) So, getting this disabled matters for production use.

---

Process checklist

• Has a clear story statement
• Can reasonably be done in a few days (otherwise, split this up!)
• Shepherds have been identified
• UX youexes all the things
• Design designs all the things
• Engineering engineers all the things
• Meets acceptance criteria
• Meets QASP conditions
• Presented in a review
• Includes screenshots or references to artifacts
• Tagged with the sprint where it was finished
• Archived

If there's UI...

• Screen reader - Listen to the experience with a screen reader extension, ensure the information presented in order
• Keyboard navigation - Run through acceptance criteria with keyboard tabs, ensure it works.
• Text scaling - Adjust viewport to 1280 pixels wide and zoom to 200%, ensure everything renders as expected. Document 400% zoom issues with USWDS if appropriate.