qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "jiraposter@reviews.apache.org (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-3579) Tool to aid in analyzing trace messages in c++ broker log files
Date Wed, 02 Nov 2011 20:09:34 GMT

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

jiraposter@reviews.apache.org commented on QPID-3579:
-----------------------------------------------------


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/2675/
-----------------------------------------------------------

Review request for qpid, Alan Conway, Gordon Sim, and Ted Ross.


Summary
-------

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.


This addresses bug QPID-3579.
    https://issues.apache.org/jira/browse/QPID-3579


Diffs
-----

  trunk/qpid/tools/src/py/qpid-analyze-trace PRE-CREATION 

Diff: https://reviews.apache.org/r/2675/diff


Testing
-------

Testing on basic logs produced using simple qpid-perftest runs.


Thanks,

Kim


                
> 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:dev-subscribe@qpid.apache.org


Mime
View raw message