Hi Patrick,
Thanks for your reply – I’ve found the “Manage Custom Parsers”, that’s indeed well hidden for import / export
J
I’ve also been able to fix my original trace import issue: All fields had been parsed OK, but the time stamp could not be parsed.
It’s not intuitive that there are TWO fields for the “time stamp” and both must be in sync.
See attached screenshot.
Now with the fixed parser, I can see my custom log rendered as a table, and an entry is shown in the Time Chart,
But I see no X-axis in the time chart and no events. Could it be that a CTF trace is required in addition to my custom traces ?
Or what else am I missing ?
I’m attaching my exported projects as ZIP for reference.
This is with the latest Linuxtools from Hudson BTW.
Not seeing my custom trace in the time chart or histogram is the biggest problem for me.
Some other things I’ve noticed –
-
When I import a text log, the “Linked Resource” is created with an absolute path. I think that a relative path should be used when possible such that
the project can be team-shared.
-
When I export a custom parser into an Eclipse project location, the resource gets out of sync (workspace update is missing). I think exporting into
an Eclipse project is important for team-sharing.
-
Importing multiple custom parsers in one step is missing. Maybe an approach like with Shared Launch Configurations would be better for custom parsers.
-
Some of my traces have integer timestamps (nnnnnnnn) with clocktick resolution. Would be interesting to get these converted + apply a time offset
for correlating with other traces (but I could also preprocess using perl or similar).
From: linuxtools-dev-bounces@xxxxxxxxxxx [mailto:linuxtools-dev-bounces@xxxxxxxxxxx]
On Behalf Of Patrick Tasse
Sent: Tuesday, November 20, 2012 5:46 PM
To: Linux Tools developer discussions
Subject: Re: [linuxtools-dev] lttng getting started : Sample "Custom Text Parser" config & files ?
Hi Martin,
If you're creating a text parser, you can paste your input text (or just a few sample lines) in the "Preview input" text box.
Then you will see if your lines are parsed properly (you want your important text to be green -- see the preview legend).
Make sure you create 'groups' under each regular _expression_ to capture the data and specify which field it corresponds to.
When you press "Next" you should see a preview table of how the trace would look like with this parser and this preview text.
And yes you can export, import and share the parsers, but you first have to find the well-hidden "Manage Custom Parsers" dialog:
http://wiki.eclipse.org/Linux_Tools_Project/LTTng2/User_Guide#Managing_custom_parsers
Patrick