[
https://issues.apache.org/jira/browse/DISPATCH-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16547992#comment-16547992
]
ASF subversion and git services commented on DISPATCH-1082:
-----------------------------------------------------------
Commit f6a68fd14db5a47f2ef6ea3ae7057309b41dc83d in qpid-dispatch's branch
refs/heads/master from [~chug]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=f6a68fd ]
DISPATCH-1082: Add connection_id to log messages for disambiguation
Eleven log messages are prefixed with '[N]'.
Server on_accept log message deletes the from field as it is unknown
at this stage in the connection life cycle and always blank.
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
