[
https://issues.apache.org/jira/browse/LOG4NET-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797413#action_12797413
]
Manfred Braun commented on LOG4NET-205:
---------------------------------------
Hi All !
I'll vote for this too! I spent my last hours to find something like a
"MethodFilter", then I recognized that I would like have access to other event
properties as well.
This would be a great feature!
Thanks anyway.
> Allow filtering by Identity / UserName / ThreadName and Domain
> --------------------------------------------------------------
>
> Key: LOG4NET-205
> URL: https://issues.apache.org/jira/browse/LOG4NET-205
> Project: Log4net
> Issue Type: New Feature
> Components: Core
> Affects Versions: 1.2.10
> Reporter: Bruno Baia
>
> Background :
> See thread named PropertyFilter (
> http://mail-archives.apache.org/mod_mbox/logging-log4net-user/200903.mbox/browser
> )
> By default, there's no way to filter by those LoggingEvent properties.
> I want to avoid extra code to do that (by adding a property programmatically
> or implementing a custom IFilter)
> I see 2 solutions :
> - LoggingEvent.LookupProperty should be able to resolve internal keys like
> "log4net:Identity", "log4net:UserName", etc... (Note that It already works
> for "log4net:HostName" added by GlobalContext's static constructor). Then we
> can use the PropertyFilter.
> - Add a IFilter implementation for each property like it's done for the
> LoggerName and Level properties.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
