From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Fri, 6 Feb 2015 22:22:53 +0000 (UTC) From: Mathieu Desnoyers Message-ID: <1226582540.88170.1423261373714.JavaMail.zimbra@efficios.com> In-Reply-To: <54D53C96.8030805@ericsson.com> References: <54D53C96.8030805@ericsson.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [diamon-discuss] Parsing external datasources in trace compass for regions of interest in a trace List-Id: DiaMon diagnostic and monitoring workgroup general discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Matthew Khouzam , Julien Desfossez Cc: diamon-discuss@lists.linuxfoundation.org, lttng-dev@lists.lttng.org, tracecompass developer discussions ----- Original Message ----- > From: "Matthew Khouzam" > To: "tracecompass developer discussions" , diamon-discuss@lists.linuxfoundation.org, > lttng-dev@lists.lttng.org > 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 ? Thanks, Mathieu > > _______________________________________________ > diamon-discuss mailing list > diamon-discuss@lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/diamon-discuss > -- Mathieu Desnoyers EfficiOS Inc. http://www.efficios.com