Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: jdesfossez@efficios.com (Julien Desfossez)
Subject: [lttng-dev] Update in the babeltrace live CLI
Date: Mon, 10 Feb 2014 18:41:03 -0500	[thread overview]
Message-ID: <52F9638F.7070605@efficios.com> (raw)

Hi,

TL;DR:
the new URL format for Babeltrace live is :
$ babeltrace -i lttng-live net://host/<hostname>/<session-name>

Also the protocol has been slightly updated (main change : we require
the viewer to create a viewer_session before attaching to one or
multiple sessions), if you started to work on a live viewer, please make
sure you read doc/live-reading-protocol.txt in lttng-tools and update
your lttng-viewer-abi.h file.


More details :
For the adventurous ones who had already tried LTTng live with
Babeltrace, you were doing :
$ babeltrace -i lttng-live net://localhost/42

To connect to the session 42 on the relay running on localhost.
You might have noticed that if you had kernel and UST tracing running
inside the same session, you would see 2 sessions with the same name on
the relay and no way to attach to both of these.

As of now, this limitation is gone, the protocol allows to attach to
multiple "sessions" as seen by the relay. In Babeltrace, we now
automatically merge the sessions with the same hostname and
session-name, so if the user creates a session with kernel and UST
events, he will receive all the events when he attaches to the session
(as would be expected).
There might be clashes if two servers on the network have the same
hostname and create the same session name, but for now the relay cannot
distinguish these cases, so it is currently a known limitation. If you
implement your own client, you can choose which session you want to
attach to.
Finally, notifications are sent when new streams are created (especially
useful when using per-pid tracing), if you implement the protocol,
please make sure you check the return flags when necessary.

So the new URL format for Babeltrace live is :
$ babeltrace -i lttng-live net://host/<hostname>/<session-name>

If you have any questions, don't hesitate to ask here.

Have fun !

Julien



                 reply	other threads:[~2014-02-10 23:41 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=52F9638F.7070605@efficios.com \
    --to=jdesfossez@efficios.com \
    /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