[Reporting] Improve logging about re-creating requests #79209
Closed
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
Goal: This PR is a followup to #76998 to improve the tags in logs generated during report queuing and executing. By passing in a logger to the ReportingCore functions instead of using a class member of ReportingCore, the logger object is able to carry with it the tags that have accumulated through different modules that lead up the the logging call. This adds more context to the logs.
By doing this, this area of logging is brought up to the standard of logging in Reporting.
This PR also converts the log level to debug when the Space ID is
default
BEFORE:
AFTER:
Checklist
Delete any items that are not applicable to this PR.