[lttng-dev] Proposal: Make lttng-analyses part of lttng-tools

[Philippe Proulx]

On Wed, Jul 18, 2018 at 11:37 AM Geneviève Bastien
<gbastien at versatic.net> wrote:
>
> > I'm eager to get some feedback from Mathieu and Jérémie on all this.
> So am I!

Adding mine even if you're not eager to get it ;-).

As someone who knows a few parts of the LTTng analyses project, it is
still considered experimental, prototypal, in other words not ready at
all to be integrated within any stable project. It is with good reason
that its version is still 0.x.

LTTng analyses helps us prove that such a tool can be useful (we
received good feedback in general), and it's a great project to quickly
develop a tracing analysis, but it's lacking thorough documentation
(outside its README file), tests, and by the nature of Python is very
slow and will probably remain like this forever. LTTng analyses also
does not handle exceptional scenarios very well.

Also, do not forget that this project has hard dependencies on Python
and Babeltrace. What would this mean, on the packaging level, when
making it part of LTTng-tools, which has a very limited set of
dependencies on purpose?

I believe our mid/long-term goal is to:

1. Release Babeltrace 2 ASAP.
2. Optimize Babeltrace 2 for the typical CTF input with stream muxing
   scenario.
3. Create/transfer LTTng analyses as Babeltrace 2 filter or sink
   components.
4. Encourage people to use Babeltrace 2 to analyse LTTng traces.

That's not to say I disagree with the highlighted problem: our efforts
should be directed towards offering a streamlined experience to the
user, from instrumenting to tracing to analyzing.

By the way, there are still a few professional, rigorous individuals who
read the documentation, thank God ;-).

Phil

>
> Cheers,
> Geneviève
> _______________________________________________
> lttng-dev mailing list
> lttng-dev at lists.lttng.org
> https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev