You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I like to route my application logs to their own file to aid debugging. All my logs are done using slf4j, so there's very little use of markers to be converted into tags. Would it be possible to support some kind of prefix such that I could say that either:
Only com.myapp logs go into this file
com.myapp is tagged as "APP", and then use that to do the routing
Right now, we achieve this with logback, but tinylog's benchmarks and simple configuration are alluring. Although I'm yet to test the benchmarks when used in conjunction with slf4j, I have no idea what kind of overheads would be present.
The text was updated successfully, but these errors were encountered:
You can archive this with the current tinylog version by creating your custom logging provider. Just extend TinylogLoggingProvider and override both log() methods. There, you can modify the tag and map com.myapp to the tag "APP".
I like to route my application logs to their own file to aid debugging. All my logs are done using slf4j, so there's very little use of markers to be converted into tags. Would it be possible to support some kind of prefix such that I could say that either:
Right now, we achieve this with logback, but tinylog's benchmarks and simple configuration are alluring. Although I'm yet to test the benchmarks when used in conjunction with slf4j, I have no idea what kind of overheads would be present.
The text was updated successfully, but these errors were encountered: