Allow configurable request logger in Store Gateway #7367
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
saswatamcode
previously approved these changes
May 17, 2024
fpetkovski
reviewed
May 17, 2024
fpetkovski
reviewed
May 17, 2024
Signed-off-by: Ben Ye <benye@amazon.com>
Signed-off-by: Ben Ye <benye@amazon.com>
fpetkovski
approved these changes
May 17, 2024
|
Thanks. Merging now |
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Follow up of #7356
Changes
Now Store Gateway internal logs don't contain any information about context information such as request ID because it is using either the instance level logger or block level logger.
This PR adds a hook
RequestLoggerFuncso that downstream projects can configure how to initialize the request time logger. For example, different projects have different ways to propagate request ID, like Cortex.Verification
Tested locally.