[lttng-dev] [RELEASE] LTTng-Tools 2.4.0-rc1 - Époque Opaque

[lttng-dev] [RELEASE] LTTng-Tools 2.4.0-rc1 - Époque Opaque

[David Goulet]

Greetings everyone (including LTTng elves),

The lttng-tools project provides a session daemon (lttng-sessiond) that
acts as a tracing registry, the "lttng" command line for tracing
control, a lttng-ctl library for tracing control and a lttng-relayd for
network streaming.

Introducing the "?poque Opaque", the E version of the LTTng toolchain.
I invite everyone to read the small description of this version by doing
"lttng version" :).

This is the feature freeze and first 2.4.0 release candidate. This
version adds multiple fixes and some new *awesome* features.

1) Live support. It's now possible to stream traces (kernel and UST)
while they being extracted meaning a relayd can now receive traces live
and a viewer can attach to it to process the trace while running. The
"--live" has been added to lttng create command that sets up a live
tracing session.

See doc/live-reading-howto.txt and doc/live-reading-protocol.txt for
more detail on that feature.

2) Java Util Logging support. With a special LTTngAgent located in
lttng-ust project (liblttng-ust-jul) to trace JUL events and gather UST
traces with them.

The -j/--jul domain has been added to lttng command line so you can list
the possible JUL Logger object and enable/disable them. It is the same
as using the UST or Kernel domain.

As of now, filters and loglevel are ignored with the JUL domain.

3) Event exclusion. Thanks to JP Ikaheimonen for that contribution!, a
-x/--exclusion option has been added to lttng enable-event that allows
the user to exclude events from being enabled.

4) New health check API now integrated in lttng-sessiond, lttng-relayd
and the lttng-consumerd. Please see include/lttng/health.h for more
details on this new API.

Thanks to everyone that worked on this release! Too many people to thank
but just a special one to Julien Desfossez that worked like a *beast*
for the incredible live feature (and 4000 more lines of code to
maintain...  :P).

Please report ANY issues to bugs.lttng.org or through that mailing list.

Using it is testing it!

Project website: http://lttng.org/lttng2.0
Download link:
http://lttng.org/files/lttng-tools/lttng-tools-2.4.0-rc1.tar.bz2 (for
the PGP signature, same file with .asc appended)

Cheers!
David
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 620 bytes
Desc: Digital signature
URL: <http://lists.lttng.org/pipermail/lttng-dev/attachments/20131115/195f3f49/attachment-0001.pgp>

[lttng-dev] [RELEASE] LTTng-Tools 2.4.0-rc1 - Époque Opaque

[Thibault, Daniel]

-----Message d'origine-----
Date: Fri, 15 Nov 2013 12:27:01 -0500
From: David Goulet <dgoulet@efficios.com>

> 1) Live support. It's now possible to stream traces (kernel and UST)
> while they being extracted meaning a relayd can now receive traces live
> and a viewer can attach to it to process the trace while running. The
> "--live" has been added to lttng create command that sets up a live
> tracing session.
>
> See doc/live-reading-howto.txt and doc/live-reading-protocol.txt for
> more detail on that feature.

   Does this mean you can't do a "live" trace to local storage?

> 2) Java Util Logging support. With a special LTTngAgent located in
> lttng-ust project (liblttng-ust-jul) to trace JUL events and gather UST
> traces with them.
>
> The -j/--jul domain has been added to lttng command line so you can list
> the possible JUL Logger object and enable/disable them. It is the same
> as using the UST or Kernel domain.
>
> As of now, filters and loglevel are ignored with the JUL domain.

   Saying "It is the same as using the UST or Kernel domain" leaves a lot of questions unanswered, since the kernel and user-space behave *very* differently on a lot of points.

1) Does --jul require root privileges?
2) I suppose the various commands have --kernel pre-empting --userspace pre-empting --ul?
3) add-context: does --jul have the same possible context types as --userspace (i.e. ip, pthread_id, procname, vpid, vtid)?
4) enable-channel:
4.1) Are the --jul --subbuf-size, --num-subbuf and --read-timer defaults the same as with --userspace?
4.2) Presumably --output can only be mmap?
4.3) Are the --jul buffering schemes the same as with --userspace (i.e. --buffers-pid and --buffers-uid)?
4.4) If yes, won't they all degenerate to the virtual machine's user and process IDs?
5) enable-event:
5.1) Can you assign --jul events to multiple channels like you can in --userspace?
5.2) Is the --jul event type --tracepoint or something else entirely?
5.3) Can the trailing wild card (and exclusion option) be used in the event name when enabling/disabling --jul events?
6) list: Does bug #654 also apply to --jul?

Daniel U. Thibault
Protection des syst?mes et contremesures (PSC) | Systems Protection & Countermeasures (SPC)
Cyber s?curit? pour les missions essentielles (CME) | Mission Critical Cyber Security (MCCS)
R & D pour la d?fense Canada - Valcartier (RDDC Valcartier) | Defence R&D Canada - Valcartier (DRDC Valcartier)
2459 route de la Bravoure
Qu?bec QC  G3J 1X5
CANADA
Vox : (418) 844-4000 x4245
Fax : (418) 844-4538
NAC : 918V QSDJ <http://www.travelgis.com/map.asp?addr=918V%20QSDJ>
Gouvernement du Canada | Government of Canada
<http://www.valcartier.drdc-rddc.gc.ca/>