Set the default minLevel
and maxLevel
of LevelRangeFilter
#1503
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.
The default
minLevel
andmaxLevel
ofLevelRangeFilter
are both set toERROR
. As hinted in #1495, this is unintuitive and excludesFATAL
by default, unlessminLevel
is explicitly overridden. This PR replaces these defaults withOFF
andALL
, respectively, and adds documentation.Warning! This change breaks the backward compatibility. Though the expected impact is low, since
maxLevel
. This will still work, yet, after this PR, the filter will also allow events with levels higher than ERROR.