Correct the default log level in configs #2199
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Part of elastic#1931. The default log level was changed to INFO in PR elastic#1952, but the change wasn't reflected in the default configuration files. This fixes it. The issue was signaled in elastic#2183. Also fixes the logging level in the docs.
|
LGTM. I was looking in our CHANGELOG for an entry related to the log level but couldn't find one. I think it is worth to mention there. |
|
Hmm, yes, good point. But I need to add that in the 5.0 branch since the switch is happening in alpha5. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Part of #1931. The default log level was changed to INFO in PR #1952,
but the change wasn't reflected in the default configuration files. This
fixes it. The issue was signaled in #2183.
Also fixes the logging level in the docs.