[
https://issues.apache.org/jira/browse/QPID-3579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13146507#comment-13146507
]
[email protected] commented on QPID-3579:
-----------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/2675/#review3115
-----------------------------------------------------------
Ship it!
Works well, nice and simple. Don't offhand have a use for it but I can see how
it might be useful.
- Alan
On 2011-11-02 20:08:39, Kim van der Riet wrote:
bq.
bq. -----------------------------------------------------------
bq. This is an automatically generated e-mail. To reply, visit:
bq. https://reviews.apache.org/r/2675/
bq. -----------------------------------------------------------
bq.
bq. (Updated 2011-11-02 20:08:39)
bq.
bq.
bq. Review request for qpid, Alan Conway, Gordon Sim, and Ted Ross.
bq.
bq.
bq. Summary
bq. -------
bq.
bq. qpid-analyze-trace reads a c++ broker log file and analyzes and sorts the
trace-level entries into connections and sessions, then presents the log trace
activity in a structured format.
bq.
bq.
bq. This addresses bug QPID-3579.
bq. https://issues.apache.org/jira/browse/QPID-3579
bq.
bq.
bq. Diffs
bq. -----
bq.
bq. trunk/qpid/tools/src/py/qpid-analyze-trace PRE-CREATION
bq.
bq. Diff: https://reviews.apache.org/r/2675/diff
bq.
bq.
bq. Testing
bq. -------
bq.
bq. Testing on basic logs produced using simple qpid-perftest runs.
bq.
bq.
bq. Thanks,
bq.
bq. Kim
bq.
bq.
> Tool to aid in analyzing trace messages in c++ broker log files
> ---------------------------------------------------------------
>
> Key: QPID-3579
> URL: https://issues.apache.org/jira/browse/QPID-3579
> Project: Qpid
> Issue Type: New Feature
> Reporter: Kim van der Riet
> Assignee: Kim van der Riet
> Priority: Minor
>
> The c++ broker log files at trace level are complex to follow because the
> several connections, sessions and commands are interlaced. A simple tool
> which reads in a trace log file and presents a sorted chronological view of
> activity on each session and connection (linked to session) would make
> analysis simpler.
> There are many possibilities for creating such a tool, but I envisage that
> the first version would be written in Python and would have a text output. It
> would read the log file, looking only at trace-level entries. It would
> analyse and print out a list of connections in log order. For each
> connection, sessions would be shown in order. For each session, the commands
> would be shown in log order. Options may be construed to limit, control and
> format this output.
> A later version may use a graphical interface to filter and show activity on
> connections and sessions.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
