qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DISPATCH-1082) Log messages can not be correlated to a specific connection
Date Thu, 19 Jul 2018 21:08:00 GMT

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

ASF subversion and git services commented on DISPATCH-1082:

Commit 8634429fa618a1f71bb3187101b697e5ca705839 in qpid-dispatch's branch refs/heads/master
from [~tross@redhat.com]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=8634429 ]

DISPATCH-1082 - Added missing include directive.

> Log messages can not be correlated to a specific connection
> -----------------------------------------------------------
>                 Key: DISPATCH-1082
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-1082
>             Project: Qpid Dispatch
>          Issue Type: Improvement
>    Affects Versions: 1.2.0
>            Reporter: Chuck Rolke
>            Priority: Major
> Several components use 'connection name' which is not unique.
>  * Policy logs indicating allow/deny at protocol level
>  * Connection setup
> A simple improvement is to include the connection_id integer at the beginning of the
messages. The format should be the same as the prefix added by the server to proton transport
tracer messages.
> Log files could be processed simply with
> {{    grep '\[4]' router.log}}
> to reveal connection setup, authenticated username associations, policy decisions, and
AMQP frame traffic.
> This addition would also make it easier to scrape the log file for low-level connection
life cycle details with no ambiguity.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org

View raw message