DEVPROD-13567: improve retry and traceability for GitHub app token creation errors #8693
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.
DEVPROD-13567
Description
This is some improvements in preparation to fix the issue where
github.generate_token
will time out requesting a token from Evergreen. This will help to verify that the actual fix for DEVPROD-13567 works and overall improve our ability to monitor for issues when creating tokens.I'm going to post a follow-up PR after this to address the ticket's issue.
Testing
Tested in staging that the spans went to Honeycomb and Splunk errors worked as expected with the retry function. Also verified that modifying the HTTP client's transport didn't cause token creation to fail.