[
https://issues.apache.org/jira/browse/DISPATCH-578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15706340#comment-15706340
]
Andrew Stitcher commented on DISPATCH-578:
------------------------------------------
I tend to think that PN_TRACE_FRM is what you want instead of PN_TRACE_RAW
which is pretty much info overlaod and the same info anyway.
Not sure about PN_TRACE_DRV - that tends to be catch all stuff that probably
needs to be better categorised. We proabably really need more and useful proton
logging categories.
> Dispatch trace logging forces all proton tracing on
> ---------------------------------------------------
>
> Key: DISPATCH-578
> URL: https://issues.apache.org/jira/browse/DISPATCH-578
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Container
> Affects Versions: 0.7.0
> Reporter: Alan Conway
> Assignee: Ganesh Murthy
> Priority: Minor
> Fix For: 0.8.0
>
>
> Presently enabling TRACE logging for the SERVER module forces all proton
> PN_TRACE_* logging on and sends it to the router log. This makes trace logs
> hard to read, in particular the PN_TRACE_RAW output is verbose and rarely
> wanted.
> Make dispatch respect the PN_TRACE_* environment variables: it will still log
> proton traces as SERVER trace logs but only if the relevant env vars are
> turned on (and SERVER trace is enabled)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
