-
Notifications
You must be signed in to change notification settings - Fork 22
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
Set Default Log Levels for Containers to Warning or Error? #217
Comments
All logging levels should be override-able via the environment variables noted in the images README, or in the case of their parent images README for things that use some services like That being said choosing one level and using it everywhere sounds reasonable to me. I'd tend to go with @g7morris and @jefferya do you want to weigh in with a preference? |
I think the default level should be targeted to a specific use-case. I see |
My vote would be for production level expectations for logs, open ports, etc... Especially since ISLE is almost a "click to run" application, in which people could just stand this up and assume, yup everything is working, and put content in, and call it good. Having a way to easily override the log levels which it seems like it does, through the environment variables for development / troubleshooting purposes, and maybe that needs to be addressed in documentation |
Late to the party. The ability to change the levels via confd or variables is the key feature here. With respect to preferences, I'm with @nigelgbanks |
Okay the following services have been bumped up one level from
All other services were set to the following |
This has been rolled out in release 1.0.7 |
Can the default log levels be set to warning or error, with the option to override them via ENV variables?
cantaloupe
is outputting at least DEBUG logsfits
is outputting at least INFO logsactivemq
is outputting INFO as well...
The text was updated successfully, but these errors were encountered: