-
Notifications
You must be signed in to change notification settings - Fork 106
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
Logging options #54
Comments
+1 to this the debug logging in console mode (which is the default) is very distracting. |
Are there any updates on this? console is not very usable with this configuration :( |
Logging is now switched off in console mode (v. 0.9.0.14), log-changing magic was merged into master |
As for now, you can configure logging in following ways:
<configuration>
<appender name="STDERR" class="ch.qos.logback.core.ConsoleAppender">
<!-- encoders are assigned the type
ch.qos.logback.classic.encoder.PatternLayoutEncoder by default -->
<target>System.err</target>
<encoder>
<pattern>%-4relative [%thread] %-5level %logger{35} - %msg %n</pattern>
</encoder>
</appender>
<appender name="file1" class="ch.qos.logback.core.FileAppender">
<file>/home/user/log.txt</file>
<encoder>
<pattern>%-4relative [%thread] %-5level %logger{35} - %msg %n</pattern>
</encoder>
</appender>
<root level="DEBUG">
<appender-ref ref="STDERR" />
<appender-ref ref="file1" />
</root>
</configuration> Read more about logback configuration here
See more info about magics here
If you need something else regarding logging, feel free to open new issue. |
Logging in Kernel is not configurable now. It would be great to do something (or all) of the folllowing:
The text was updated successfully, but these errors were encountered: