You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Marnie McCormack (JIRA)" <qp...@incubator.apache.org> on 2007/04/19 15:04:16 UTC

[jira] Updated: (QPID-19) Add protocol logging capability to client and broker

     [ https://issues.apache.org/jira/browse/QPID-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marnie McCormack updated QPID-19:
---------------------------------

        Fix Version/s:     (was: M2)
                       M3
    Affects Version/s: M2
                       M1

Moving unresolved JIRAs from M2 to M3, in preparation for M2 release

> Add protocol logging capability to client and broker
> ----------------------------------------------------
>
>                 Key: QPID-19
>                 URL: https://issues.apache.org/jira/browse/QPID-19
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Broker, Java Client
>    Affects Versions: M1, M2
>            Reporter: Robert Greig
>             Fix For: M3
>
>
> It is currently difficult to see the protocol traffic separately from the client and broker logs.
> It would be extremely useful to have the ability to switch on logging of protocol traffic with the following features:
> 1) log to separate file
> 2) easy to parse format such as XML
> 3) ability to "replay" these files, which will make analysing and diagnosing customer problems easy since we can just get the client to capture the protocol traffic, then play it back into a test broker for detailed analysis
> 4) ship an "anonymiser" tool that will allow customers to take the file and will anonymise the data - but will replace content bodies will random data of the same length and so on.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.