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] (PROTON-2131) Improved logging API
Date Thu, 14 Nov 2019 06:31:00 GMT

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

ASF subversion and git services commented on PROTON-2131:
---------------------------------------------------------

Commit 2fca6618dc79aa937ffcf22d8bbdb325bded5206 in qpid-proton's branch refs/heads/master
from Andrew Stitcher
[ https://gitbox.apache.org/repos/asf?p=qpid-proton.git;h=2fca661 ]

PROTON-2131: Improve and rationalise logger settings from the environment
- Introduced a new environment variable PN_LOG which can be used to set
  multiple logger levels active.


> Improved logging API
> --------------------
>
>                 Key: PROTON-2131
>                 URL: https://issues.apache.org/jira/browse/PROTON-2131
>             Project: Qpid Proton
>          Issue Type: New Feature
>          Components: proton-c
>            Reporter: Andrew Stitcher
>            Assignee: Andrew Stitcher
>            Priority: Major
>             Fix For: proton-c-0.30.0
>
>
> Problems with current proton logging:
>  * There are multiple logging systems that are not connected
>  - {{pn_log_*}} is used for some things that are not connected to an AMQP
>  connection (but not all things)
>  - pn_transport_t has its own logging system that is the major logging
>  system in proton, with an {{pn_transport_logf()}} and friends API and an
>  ability to sink the log its output log messages using
> {{pn_transport_set_tracer()}}. However not everything that might need to
>  log messages is connected to a {{pn_transport_t}} so it makes a lot more
>  sense for logging to be its own system that the {{pn_transport_t}} is
>  connected to rather than the other way around.
>  * The logging only has a set of vague somewhat amorphous trace flags to
>  decide which messages get logged. Currently the only coherent use for
>  this subsystem is to set the environment variable {{PN_TRACE_FRM}} to get
>  AMQP frame traces. There are other environment variable which produce
>  output (and flags can be set programmatically by client programs) but
>  which flags produce what output is not very systematic. There is no way
>  to output only logging related to SSL/TLS for example.
>  * The callback function that an application can attach to receive the
>  log messages only gets the message and maybe the {{pn_transport_t}} that is
>  associated, but no indication of the severity or what pert of the
>  library it came from.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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


Mime
View raw message