-
Notifications
You must be signed in to change notification settings - Fork 152
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
Support custom log channels #37
Comments
+1 for custom log channels. I'd like to have the ability to change the log level for part of the program (for instance just the REST API). |
+1 for exact the same reason as esummers |
Thanks for your input, everyone. I'm happy to report that some form of a "custom log channel" feature is coming. Stay tuned... |
+1 |
This will be rolled into a bit of a refactoring that's warranted now that we're off the ASL dependency. However, this development on Issue #50 is a bit further along and will likely be made available first. |
@emaloney sounds like what we want is is not custom severity channels but orthogonal domain channels. To follow his example, I might want to log verbose/debug/warning/error messages in a custom REST domain and filter so that only error messages in that domain go through but have levels up to verbose in the SQL domain. Seem like an orthogonal system and not simply custom channels. |
I try to solve it using a simple adapter , sample in gist |
I had forked your project and added a User log channel and severity. Which proved pretty handy. For I could create a Log.user?.message() or use a corresponding traceUser() method to log user interactions.
For instance my methods such as "didTouchInsideButton" would log the user interaction. I can then easily filter the log file to see all the user actions that happened to get my app in the state it is.
A further enhancement could be to allow for the addition of custom log channels. Right now you have a fixed set of channels. Doing so would allow users to extend the library without forking it.
The text was updated successfully, but these errors were encountered: