On 15-02-06 05:22 PM, Mathieu Desnoyers wrote: > ----- Original Message ----- >> From: "Matthew Khouzam" <[email protected]> >> To: "tracecompass developer discussions" <[email protected]>, >> [email protected], >> [email protected] >> Sent: Friday, February 6, 2015 5:13:42 PM >> Subject: [diamon-discuss] Parsing external datasources in trace compass for >> regions of interest in a trace >> >> Hello, >> >> I am right now looking getting external datasources to supply >> information for a trace, like a region of interest. >> >> Background: we can run an analysis on a trace manually, in python, excel >> or what have you and come up with something interesting, like: around >> 12:30pm something happened to a trace. Let's dig deeper with tracecompass. >> >> To make this work: we need to find a way to import the data, so we >> should agree on a standard data standard. I personally like the LTTng >> analysis outputs so I am picking that for now. :) >> >> Here are some formats that could be acceptable as regions of interest >> * [2015-01-15 12:18:37.216484041, 2015-01-15 12:18:53.821580313] name >> * [2015-01-15 12:18:37.216484041, 2015-01-15 12:18:53.821580313] name >> boookmark >> * [ 2015-01-15 12:18:37.216484041] name boookmark >> * [12:18:37.216484041] name boookmark >> * [ 12:18:37.216484041, 12:18:53.821580313] name boookmark >> * [ 2014-12-12 17:29:43.802588035] name with space >> * [ 2014-12-12 17:29:43] irrational title >> * [17:29:43.802588035] rational title >> * [ 17:29:43] test test test >> * [17:29:43,17:29:44] thing >> * [12:18:37.216484041 ] (no text) >> >> When there is one timestamp, we will create one bookmark. >> When there is a range, we would create two bookmarks in a given trace, >> the first one being appended with " start" the second with " end" >> >> This should allow tracecompass to marginally benefit from the lttng >> analyses that are looking pretty nice, and later perhaps from tcp >> analyses from tshark and syslog stuff. >> >> Does anyone have an objection to this way of working? > > Do you intend on supporting timestamps that appear elsewhere than > the beginning of lines ? Do you consider all text at the right of > the timestamp or timestamp range to be part of the naming of the > region of interest linked to the timestamp/timestamp range ? > > Julien, did we want to reserve [] for only timestamp range or > we also want them for single timestamps ?
Right now the [] are only valid with time ranges (they are not accepted with --begin and --end). I don't mind allowing the brackets for all timestamps (like in dmesg), we still have the "," to identify if it's a range or not. But for convenience, they will remain optional for --begin and --end. We just have to keep in mind, that [32,64] could be a range of values/frequency and not necessarily timestamps. Julien _______________________________________________ lttng-dev mailing list [email protected] http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
