logger: force_stacktrace_level was not applied to PluginLogger #5038
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.
Which issue(s) this PR fixes:
What this PR does / why we need it:
In #5008, we have added a new feature
force_stacktrace_level
.However, it was not applied to
PluginLogger
.So, depending on the settings and error locations,
force_stacktrace_level
could not work.This PR fixes it.
Docs Changes:
Not needed because #5008 is not released yet.
Release Note:
Not needed because #5008 is not released yet.
How to reproduce the bug:
conf:
@id
to usePluginLogger
.buffer
to usePluginLogger
.buffer
,RootAgent
outputs the logs for flushing errors by using the global logger. (RootAgent#handle_emits_error
)log:
warn
, althoughforced_stacktrace_level
isinfo
.