Backport of Restore 'server' and 'agent' base loggers to use their original names into release/1.13.x #19308
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.
Backport
This PR is auto-generated from #19304 to be assessed for backporting due to the inclusion of the label backport/1.13.x.
The below text is copied from the body of the original PR.
When we added additional logging features to
server
andagent
in #18031, we introduced an unintended change to the base logger names in both commands (setting them tovault
andvault-agent
respectively).This PR restores the original names (in the case of
server
has no name) so that any log ingestion/parsing by downstream systems would not be impacted. Furthermore it also means that endpoints such assys/loggers
function as expected and don't require avault.
prefix forserver
loggers.Overview of commits