public inbox for diamon-discuss@lists.linux.dev
 help / color / mirror / Atom feed
From: Julien Desfossez <jdesfossez@efficios.com>
To: lttng-dev@lists.lttng.org, diamon-discuss@lists.linuxfoundation.org
Subject: [diamon-discuss] [RELEASE] LTTng-analyses v0.6
Date: Thu, 22 Dec 2016 14:57:39 -0500	[thread overview]
Message-ID: <20161222195739.GA5104@microsoft.com> (raw)

Hi,

We are glad to announce a new release of lttng-analyses !
https://github.com/lttng/lttng-analyses

This project is a collection of tools to extract metrics and high-level
informations from offline LTTng traces to investigate complex problems.

The main addition in this release is the new "period" mechanism which
allows users to define directly on the command line what events
constitute the beginning and the end of a period in their trace, and
which field(s) to use to match the two events. Periods can also be fully
nested within each other. A visual example of a period and how to define
it can be found in [1].

Once the period is defined on the command line, the new
lttng-period{top,log,freq,stats} scripts can be used to extract relevant
data from the trace put in the form of periods, so a lot of automated
statistics can be computed. The README on the github page has examples
of some possible outputs.

Since the user now defines the periods on the command line, all CTF
traces can be used as input, so this is the first release that supports
LTTng-UST traces in addition to LTTng kernel traces.

Defining a new period is not necessarily a trivial task at first, but it
is the same principle as reading a trace manually, you match events and
fields (and parent events/fields), once you understand the syntax, you
will start making very powerful analyses !

All these new analyses also output the LAMI format, and can be used
directly in TraceCompass (daily build or 2.3 release) to make
interactive graphs.

As always, we appreciate all kinds of feedback, use-cases and real-world
experiences, so please test it and let us know what you think about it.

Thanks,

Julien

[1] https://imgur.com/a/bZCgR

                 reply	other threads:[~2016-12-22 19:57 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20161222195739.GA5104@microsoft.com \
    --to=jdesfossez@efficios.com \
    --cc=diamon-discuss@lists.linuxfoundation.org \
    --cc=lttng-dev@lists.lttng.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox