[ 
https://issues.apache.org/jira/browse/DISPATCH-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13996430#comment-13996430
 ] 

ASF subversion and git services commented on DISPATCH-16:
---------------------------------------------------------

Commit 1594235 from [~aconway] in branch 'dispatch/trunk'
[ https://svn.apache.org/r1594235 ]

QPID-DISPATCH-16: Improve logging for dispatch

Patches provided by Rajith Attapattu on 
https://issues.apache.org/jira/browse/DISPATCH-16
- separately configurable logging levels for each module.
- config stubs for syslog & file based logging (not yet implemented.)

Made some modifications:

Simplified schema:
- single configuration section "log", to set defaults use "log : { 
module:DEFAULT, ... }"
- shorter names for configuration items (print_to_stderr->stderr etc.)
- simplified config logic.

Changed correct but unintuitive bit mask logic: bits in mask were levels NOT 
selected.
- Flipped it around.

Only log ERROR and above before log system is configured. Avoid annoying INFO 
log
message leakage to stderr.

> Improve logging for dispatch
> ----------------------------
>
>                 Key: DISPATCH-16
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-16
>             Project: Qpid Dispatch
>          Issue Type: Improvement
>    Affects Versions: 0.1
>            Reporter: Rajith Attapattu
>            Assignee: Rajith Attapattu
>             Fix For: 0.3
>
>         Attachments: patch_1_schema_change.diff, 
> patch_2_registering_log_source.diff, patch_3_configure_logging.diff, 
> patch_4_use_log_source_to_filter.diff, patch_5_remove_set_mask_method.diff
>
>
> The following improvements are planned.
> 1. Add support for configuring logging on a per module basis.
> 2. File support including log rotation.
> 3. Syslog support.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to