[tor-bugs] #13887 [Chutney]: Pick a reporting format for Chutney

[Tor Bug Tracker & Wiki]

#13887: Pick a reporting format for Chutney
-------------------------+--------------------------------------
     Reporter:  nickm    |      Owner:  nickm
         Type:  defect   |     Status:  new
     Priority:  normal   |  Milestone:
    Component:  Chutney  |    Version:
   Resolution:           |   Keywords:  SponsorS design bikeshed
Actual Points:           |  Parent ID:
       Points:           |
-------------------------+--------------------------------------

Comment (by dgoulet):

 Replying to [ticket:13887 nickm]:
 > I'm especially interested in dgoulet's opinion on CTF in particular.

 So I'll detail a bit the CTF option here. First of all, here is a link to
 "what this is" :)

 http://www.efficios.com/ctf

 This is a "tracing" format but can actually be used for a multiple of
 things. The biggest project using it is LTTng (https://lttng.org), a
 kernel and user space tracer that produces traces in CTF format. I know
 that some hardware vendor are starting to adopt the format in order to
 have one single trace format across all their platforms.

 The main advantage is that it's a very very compact format with an
 available reader and reader/writer library
 (https://www.efficios.com/babeltrace). Python bindings also exists for
 *reading* the trace. A python tool exists also that generates C99 code to
 write CTF given a data description (metadata). It's also a very stable ABI
 based on a strict specification which is detached from the API producing
 it thus if the API changes well the underlaying ABI should not.

 Now does this makes sense for chutney question. I would say it depends on
 our use case here. If we expect a lot of data being produced by chutney at
 a fast paste where a JSON format would dump megabytes and megabytes of
 data, it could be very useful. However, you need an external tool to parse
 and read the data since it's not in a human readable form.

 Text base logging it great until you get way too much and you start to
 make scripts that parse long strings which I think is never ideal because
 well when you add a line or modify it, you need to update your regex.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/13887#comment:3>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online