add pipeline id to thread context during init/start #17944
Merged
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.
Release notes
What does this PR do?
Executes pipeline-initialization and pipeline-startup code with the pipeline's id in the thread logging context
Why is it important/What is the impact to the user?
When logging is configured to show the pipeline id from the thread context (as it is by default), the messages related to pipeline startup include the pipeline's id.
Additionally, if per-pipeline logging is enabled, these messages will now be routed to the pipeline's isolated logs.
Checklist
[ ] I have commented my code, particularly in hard-to-understand areas[ ] I have made corresponding changes to the documentation[ ] I have made corresponding change to the default configuration files (and/or docker env variables)[ ] I have added tests that prove my fix is effective or that my feature worksHow to test this PR locally
Single logs:
Pipeline-separated logs:
Observe that logging includes the pipeline id.
Related issues
Use cases
Screenshots
Logs
Baseline
With this change: