[lttng-dev] babeltrace
Jessica Foest
jessica.foest at gmail.com
Thu May 8 17:10:31 EDT 2014
Thanks for your detailed responses :)
Actually i will begin by taking my own trace that i will configure it in
advance ( same event type , and i will add the different event context that
i need ) .
It's my first time to develop with python and i don't really know the
architecture of babeltrace , So can you help me and tell me how to proceed
to filter my data from CTF to the output Format that i will choose ?
2014-05-08 11:53 GMT-04:00 Alexandre Montplaisir <alexmonthy at voxpopuli.im>:
>
> To avoid doing a complete first pass of the trace, you can just
>> iterate on the event types as described in the metadata, and take note
>> of all the possible field you can find in the trace. Then, during your
>> only pass, you already know all your "columns".
>>
>
> That's true. Although right now TMF doesn't have an API to ask a trace
> "give me all the event types you have", other than just reading the trace ;)
>
> wrt CTF, it's possible to have events in the metadata that don't actually
> show up in the trace. But that's not really a problem, at worst you'd end
> up with empty columns.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lttng.org/pipermail/lttng-dev/attachments/20140508/64525fd6/attachment.html>
More information about the lttng-dev
mailing list