[logback-dev] [JIRA] Resolved: (LBCLASSIC-53) Add MDC Level Filtering

Ceki Gulcu (JIRA) noreply-jira at qos.ch
Mon Oct 27 19:23:21 CET 2008

     [ http://jira.qos.ch/browse/LBCLASSIC-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ceki Gulcu resolved LBCLASSIC-53.

    Fix Version/s: 0.9.10
       Resolution: Fixed

Patches reviewed and applied.

> Add MDC Level Filtering
> -----------------------
>                 Key: LBCLASSIC-53
>                 URL: http://jira.qos.ch/browse/LBCLASSIC-53
>             Project: logback-classic
>          Issue Type: New Feature
>         Environment: All
>            Reporter: Ralph Goers
>            Assignee: Logback dev list
>             Fix For: 0.9.10
>         Attachments: dynamic.patch, MDCLevelFilter.zip
> The company I work for is an Application Service Provider. Requests to the same software running in a single JVM might be on behalf of any one of these companies. In addition, our middle tier contains services that my be called from several different products and are run on behalf of a user of one of these companies. Operationally, we require the ability to be able to filter based on company, product, possibly the end user or several other criteria.
> The TurboFilter provided allows individual values for keys in the MDC to be associated with a logging level.  So if the MDC contains a key for the company the TurboFilter can be configured with the name of the company and the corresponding logging level. So if CompanyA's level is set to debug while the default level is error, only debug events for CompanyA will be passed on.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the logback-dev mailing list