-
Notifications
You must be signed in to change notification settings - Fork 674
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add debug log level to Mainflux logger #379
Comments
Along with adding the debug level, I was wondering if it would be beneficial to also be able to select the log level? That way someone can select if they want mainflux to write out all of the infos or not. Specifically something that would look like this:
For my team and I, everything that goes into stdout gets pulled into the ELK stack for us. So it would be beneficial for us to reduce the number of success messages printed out in each component. Let me know your thoughts on this. If it is something that sounds useful I can get a PR open asap, work has been done just have some hoops to jump through. |
This was the plan, just not written in issue description. I will update description. |
@mfinley3 looks like we are aligned, will you be sending PR? |
Yep! I will get a PR opened here ASAP. I am working on our teams path to contributing back now! I made a few small cleanup changes to the internal PR. Going to have someone look those over and should have an open PR here tomorrow morning! |
Resolved by #402. |
Currently, the Mainflux logger is missing the debug log level. There are many cases were this level can be used. Also, add
SetLevel
method to Mainflux logger. Every service should have this logging level parameter set as environment variableMF_<service_name>_LOG_LEVEL
.The text was updated successfully, but these errors were encountered: