Features/LTTng

From FedoraProject

< Features(Difference between revisions)
Jump to: navigation, search
(Page creation)
 
Line 1: Line 1:
{{admon/important | Comments and Explanations | The page source contains comments providing guidance to fill out each section.  They are invisible when viewing this page.  To read it, choose the "edit" link.<br/> '''Copy the source to a ''new page'' before making changes!  DO NOT EDIT THIS TEMPLATE FOR YOUR FEATURE.'''}}
 
 
{{admon/important | Set a Page Watch| Make sure you click ''watch'' on your new page so that you are notified of changes to it by others, including the Feature Wrangler}}
 
 
{{admon/note | All sections of this template are required for review by FESCo.  If any sections are empty it will not be reviewed }}
 
 
 
<!-- All fields on this form are required to be accepted by FESCo.
 
We also request that you maintain the same order of sections so that all of the feature pages are uniform.  -->
 
 
<!-- The actual name of your feature page should look something like: Features/Your_Feature_Name.  This keeps all features in the same namespace -->
 
 
 
= LTTng 2.0 =
 
= LTTng 2.0 =
  
Line 30: Line 18:
 
* Percentage of completion: 80%
 
* Percentage of completion: 80%
  
<!-- CHANGE THE "FedoraVersion" TEMPLATES ABOVE TO PLAIN NUMBERS WHEN YOU COMPLETE YOUR PAGE. -->
 
  
 
== Detailed Description ==
 
== Detailed Description ==
 
<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
 
<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
 +
 +
The LTTng project aims at providing highly efficient tracing tools for Linux. Its tracers help tracking down performance issues and debugging problems involving multiple concurrent processes and threads. Tracing across multiple systems is also possible.
 +
 +
The LTTng 2.0 Tracer Toolchain allows integrated kernel and user-space tracing from a single user interface: the "lttng" command. The 2.0 kernel tracer can be build against standard kernel. Other new features:
 +
 +
* Produces CTF (Common Trace Format) natively (http://www.efficios.com/ctf),
 +
* Support Tracepoints, detailed syscall tracing (fast strace replacement), Function tracer, CPU Performance Monitoring Unit (PMU) counters and kprobes support,
 +
* Integrated interface for both kernel and userspace tracing,
 +
* Have the ability to attach "context" information to events in the trace (e.g. any PMU counter, pid, ppid, tid, comm name, etc). All the extra information fields to be collected with events are optional, specified on a per-tracing-session basis (except for timestamp and event id, which are mandatory).
 +
  
 
== Benefit to Fedora ==
 
== Benefit to Fedora ==
 
<!-- What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new feature, what capabilities does it bring? Why will Fedora become a better distribution or project because of this feature?-->
 
<!-- What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new feature, what capabilities does it bring? Why will Fedora become a better distribution or project because of this feature?-->
 +
 +
Bringing the LTTng tracing capability to Fedora users.
 +
The lttng-ust library allows developper to instrument their application with static tracepoint. Other packages could be built with integrated ust tracepoint, allowing users to trace them without having to recompile them.
 +
  
 
== Scope ==
 
== Scope ==
 
<!-- What work do the developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
 
<!-- What work do the developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
  
 
+
UST tracer and control package are already in place.
 +
The last part to add are the basic viewers.
  
 
== How To Test ==
 
== How To Test ==
Line 62: Line 64:
  
 
New tool (lttng) will be available to manage the tracing.  
 
New tool (lttng) will be available to manage the tracing.  
The lttng-ust library allows developper to instrument their application with static tracepoint. Other packages could be built with integrated ust tracepoint, allowing users to trace them without having to recompile.
 
  
 
== Dependencies ==
 
== Dependencies ==

Revision as of 18:11, 20 July 2012

Contents

LTTng 2.0

Summary

Introduction of the new LTTng infrastructure for userspace and kernel tracing.

Owner

  • Email: yannick.brosseau at gmail.com

Current status

  • Targeted release: Fedora 18
  • Last updated: 2012-07-17
  • Percentage of completion: 80%


Detailed Description

The LTTng project aims at providing highly efficient tracing tools for Linux. Its tracers help tracking down performance issues and debugging problems involving multiple concurrent processes and threads. Tracing across multiple systems is also possible.

The LTTng 2.0 Tracer Toolchain allows integrated kernel and user-space tracing from a single user interface: the "lttng" command. The 2.0 kernel tracer can be build against standard kernel. Other new features:

* Produces CTF (Common Trace Format) natively (http://www.efficios.com/ctf),
* Support Tracepoints, detailed syscall tracing (fast strace replacement), Function tracer, CPU Performance Monitoring Unit (PMU) counters and kprobes support,
* Integrated interface for both kernel and userspace tracing,
* Have the ability to attach "context" information to events in the trace (e.g. any PMU counter, pid, ppid, tid, comm name, etc). All the extra information fields to be collected with events are optional, specified on a per-tracing-session basis (except for timestamp and event id, which are mandatory).


Benefit to Fedora

Bringing the LTTng tracing capability to Fedora users. The lttng-ust library allows developper to instrument their application with static tracepoint. Other packages could be built with integrated ust tracepoint, allowing users to trace them without having to recompile them.


Scope

UST tracer and control package are already in place. The last part to add are the basic viewers.

How To Test

User Experience

New tool (lttng) will be available to manage the tracing.

Dependencies

None (Having the lttng kernel module would be a nice add-on)

Contingency Plan

All the tracer component are integrated. The only missing part is one or more viewer. So even without the viewer, it would still be possible to create a trace with the lttng tool. You will need an external tool to view your trace.

Documentation

Release Notes

Comments and Discussion