-
Notifications
You must be signed in to change notification settings - Fork 4
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
NLogTargetListener is not using the LogListenerParser #19
Comments
Hi Robert, The This implies that, by the time Below is the execution workflow:
One possible solution would be to update the
|
One quick workaround was to inherit the NLogTargetListener and add my own logic to bypass the verbosity of the text log:
In the web interface everything works the same, as expected. |
If it works, keep it a while :) |
* updated LogListenerParser to fix issue #19
Published KissLog 3.5.1 which fixes this issue. Updated public class LogListenerParser
{
public virtual bool ShouldLog(BeginRequestArgs args, ILogListener logListener)
{
return true;
}
} This method gets executed at the begging of the request. If the result is
|
Registering the NLogTargetListener the following way
results in KissLog flushing every single message into NLog, ignoring the custom parser:
The text was updated successfully, but these errors were encountered: