[Egress Extensibility] Fix Logging Verbosity Propagation #4136
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
Currently, extensions aren't respecting dotnet-monitor's configured
LogLevel
verbosity. This could result in a user asking forDebug
level logs, receiving them from dotnet-monitor, but only receivingInformation
from an extension. This change propagates theLogLevel
from dotnet-monitor to the extension.Release Notes Entry