[
https://issues.apache.org/jira/browse/QPID-5136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13765524#comment-13765524
]
Gordon Sim commented on QPID-5136:
----------------------------------
The issue here is that proton does its own logging. The broker can only turn
that on or off, it can't control the format or anything like that. So above,
the first two lines are the brokers own logging, the last four are protons
logging.
> C++ Broker issuing multiline log messages
> -----------------------------------------
>
> Key: QPID-5136
> URL: https://issues.apache.org/jira/browse/QPID-5136
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
> Affects Versions: 0.24
> Environment: --log-enable trace+
> Reporter: Chuck Rolke
>
> Running AMQP 1.0 sessions (on windows) leads to trace log files with
> multi-line entries:
> {noformat}
> 2013-09-12 10:48:20 [Broker] trace encode(65536)
> 2013-09-12 10:48:20 [Broker] trace qpid.[::1]:5672-[::1]:55834 decode(80)
> [006FE580:0] <- @disposition [role=true, first=0, last=0, settled=true,
> state=@accepted []]
> [006FE580:0] <- @end []
> [006FE580:0] <- @close []
> [006FE580:0] <- EOS
> {noformat}
> Each log statement needs enough context to stand on it's own, especially when
> being scraped by some SIEM system. In this example the entries could be
> concatenated into one line or the three [006FE580:0] lines could be separate
> entries each with the connection identifier.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
