[tracecompass-dev] Parsing external datasources in trace compass for reg

[Matthew Khouzam <matthew.khouzam@xxxxxxxxxxxx>]

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?