[lttng-dev] babeltrace

[Alexandre Montplaisir]

Hi,

Every event type has different fields though. So the "columns" would
vary from one event to another.

Although I can see that if you add let's say "context.pid" to ALL
events, then it would be nice in the CSV export to add this as a
separate column. However, the viewer cannot know for sure that all
events in the trace have that particular context enabled. Unless you do
a full pass of the trace first to look for common fields.

Or, you do a first pass to check for all possible existing fields in the
trace, and add all of those as separate columns. Then you write the
event information in the relevant columns only, and you end up with a
CSV with a lot of "holes".

It would be possible to hack ExportToTextRequest.java to have any
particular behavior. But I'm not sure how this option could be
implemented and exposed to the user generically.

Cheers,
Alexandre


On 14-05-07 07:53 PM, Jessica Foest wrote:
> Hi all
>
> i just want to have all the fields in my selected trace represented in a
> separated  column.
> Because when using TMF for example all fields of the context of the event
> are represented in one global field .
>
> i need to have every field in a separate column, that's the point , No
> mystery :)
>
> CSV or excel is just a format , but what i need is a way to parse the CTF
> trace and get every event and every field of the context with its value
> separately.
> Can you help me to do it ?
>
>
>
> 2014-04-17 14:35 GMT-04:00 Jérémie Galarneau <jeremie.galarneau at efficios.com
>> :
>> On Thu, Apr 17, 2014 at 10:51 AM, Matthew Khouzam
>> <matthew.khouzam at ericsson.com> wrote:
>>> Hi Jessica,
>>>
>>> <Shameless plug>How about opening it in TMF and right clicking export to
>>> text in the events table?</plug>
>>>
>> The plug may be over, but the shameless tag is still open! ;-)
>>
>>> I am just curious, why do you need to get out of CTF, if a log is ctf,
>>> chances are it's
>>> WAaaaaaaAAAAAAAaaaaaAAAAAAAaaaaaaaaaaaaaayYYYYYyyyyYYYyyyYYYyyyYYYyy to
>>> big for excel, or even calc.
>>>
>> Good point, I'd be curious to know the use case for converting a
>> complete trace to CSV.
>>
>> Jérémie
>>
>>> br,
>>> Matthew
>>> On 14-04-16 04:31 PM, Jessica Foest wrote:
>>>> Hi all
>>>>
>>>> i know that the default output format of babeltrace is text .
>>>> what are the others output format supported by babeltrace ?
>>>>
>>>> in my case , i need to convert the CTF log file of lttng to a CSV file
>>>> , did tou have any idea about how can i do it ?
>>>>
>>>> thanks
>>>>
>>>>
>>>> _______________________________________________
>>>> lttng-dev mailing list
>>>> lttng-dev at lists.lttng.org
>>>> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
>>>
>>> _______________________________________________
>>> lttng-dev mailing list
>>> lttng-dev at lists.lttng.org
>>> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
>>
>>
>> --
>> Jérémie Galarneau
>> EfficiOS Inc.
>> http://www.efficios.com
>>
>> _______________________________________________
>> lttng-dev mailing list
>> lttng-dev at lists.lttng.org
>> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
>>
>
>
> _______________________________________________
> lttng-dev mailing list
> lttng-dev at lists.lttng.org
> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev