logging-log4net-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dominik Psenner (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (LOG4NET-205) Allow filtering by Identity / UserName / ThreadName and Domain
Date Wed, 07 Aug 2013 13:34:48 GMT

     [ https://issues.apache.org/jira/browse/LOG4NET-205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dominik Psenner resolved LOG4NET-205.
-------------------------------------

    Resolution: Fixed

Fixed as of revision: 1511303
                
> 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
>            Assignee: Dominik Psenner
>             Fix For: 1.2.11
>
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message