NOISSUE - Set VerneMQ default log level #1150
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
Signed-off-by: Nikola Marcetic <n.marcetic86@gmail.com>
dborovcanin
approved these changes
Apr 29, 2020
manuio
pushed a commit
that referenced
this pull request
Oct 12, 2020
Signed-off-by: Nikola Marcetic <n.marcetic86@gmail.com>
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.
Signed-off-by: Nikola Marcetic n.marcetic86@gmail.com
What does this do?
It sets VerneMQ to default log level
info. The current log leveldebug(which is really unusable, except for VerneMQ developers) causes huge log outputs to stdout and blocks other Mainflux logs. It's really hard to debug anything.Which issue(s) does this PR fix/relate to?
NA
List any changes that modify/break current functionality
NA
Have you included tests for your changes?
NA
Did you document any new/modified functionality?
NA
Notes
NA