Features/LTTng

From FedoraProject

< Features(Difference between revisions)
Jump to: navigation, search
(Page creation)
 
(update with status of babeltrace)
 
(13 intermediate revisions by 2 users not shown)
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 16: Line 4:
 
<!-- A sentence or two summarizing what this feature is and what it will do.  This information is used for the overall feature summary page for each release. -->
 
<!-- A sentence or two summarizing what this feature is and what it will do.  This information is used for the overall feature summary page for each release. -->
  
Introduction of the new LTTng infrastructure for userspace and kernel tracing.  
+
Introduction of the new LTTng infrastructure including its userspace tracer component and the control tool.  
  
 
== Owner ==
 
== Owner ==
Line 27: Line 15:
 
== Current status ==
 
== Current status ==
 
* Targeted release: [[Releases/18 | Fedora 18 ]]  
 
* Targeted release: [[Releases/18 | Fedora 18 ]]  
* Last updated: 2012-07-17
+
* Last updated: 2012-10-22
* Percentage of completion: 80%
+
* Percentage of completion: 100%
 
+
** The tracing component are all present. The babeltrace viewer would have been nice to have, but still in RC upstream.  
<!-- 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 manually built against a standard kernel. Other new features:
 +
 +
* Produces CTF (Common Trace Format) natively (http://www.efficios.com/ctf),
 +
* Emit SDT markers
 +
* See lttng.org/lttng2.0 for the complete feature list
 +
* Allow multiple users and multiple sessions to trace simultaniously
  
 
== 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 57: Line 58:
 
3. What are the expected results of those actions?
 
3. What are the expected results of those actions?
 
-->
 
-->
 +
# Install the packages (mainly lttng-tools)
 +
# For userspace tracing
 +
## Compile one of the example in /usr/share/doc/lttng-ust/examples/
 +
## Create, start a tracing session (http://lttng.org/quickstart)
 +
## Read the resulting trace
  
 
== User Experience ==
 
== User Experience ==
Line 62: Line 68:
  
 
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 ==
 
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this feature depends?  In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel feature)? -->
 
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this feature depends?  In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel feature)? -->
 
None
 
None
(Having the lttng kernel module would be a nice add-on)
 
  
 
== Contingency Plan ==
 
== Contingency Plan ==
  
 
All the tracer component are integrated. The only missing part is one or more viewer.  
 
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.  
+
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. (Work to package them are already underway)
  
 
== Documentation ==
 
== Documentation ==
Line 81: Line 85:
 
<!-- The Fedora Release Notes inform end-users about what is new in the release.  Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ -->
 
<!-- The Fedora Release Notes inform end-users about what is new in the release.  Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ -->
 
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns.  If there are any such changes involved in this feature, indicate them here.  You can also link to upstream documentation if it satisfies this need.  This information forms the basis of the release notes edited by the documentation team and shipped with the release. -->
 
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns.  If there are any such changes involved in this feature, indicate them here.  You can also link to upstream documentation if it satisfies this need.  This information forms the basis of the release notes edited by the documentation team and shipped with the release. -->
*
+
* Introduce LTTng 2.0 tracing tools
  
 
== Comments and Discussion ==
 
== Comments and Discussion ==
Line 87: Line 91:
  
  
[[Category:FeaturePageIncomplete]]
+
[[Category:FeatureAcceptedF18]]
 
<!-- When your feature page is completed and ready for review -->
 
<!-- When your feature page is completed and ready for review -->
 
<!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler -->
 
<!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler -->
 
<!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete-->
 
<!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete-->
 
<!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process -->
 
<!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process -->

Latest revision as of 19:09, 22 October 2012

Contents

[edit] LTTng 2.0

[edit] Summary

Introduction of the new LTTng infrastructure including its userspace tracer component and the control tool.

[edit] Owner

  • Email: yannick.brosseau at gmail.com

[edit] Current status

  • Targeted release: Fedora 18
  • Last updated: 2012-10-22
  • Percentage of completion: 100%
    • The tracing component are all present. The babeltrace viewer would have been nice to have, but still in RC upstream.

[edit] 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 manually built against a standard kernel. Other new features:

  • Produces CTF (Common Trace Format) natively (http://www.efficios.com/ctf),
  • Emit SDT markers
  • See lttng.org/lttng2.0 for the complete feature list
  • Allow multiple users and multiple sessions to trace simultaniously

[edit] 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.


[edit] Scope

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

[edit] How To Test

  1. Install the packages (mainly lttng-tools)
  2. For userspace tracing
    1. Compile one of the example in /usr/share/doc/lttng-ust/examples/
    2. Create, start a tracing session (http://lttng.org/quickstart)
    3. Read the resulting trace

[edit] User Experience

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

[edit] Dependencies

None

[edit] 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. (Work to package them are already underway)

[edit] Documentation

[edit] Release Notes

  • Introduce LTTng 2.0 tracing tools

[edit] Comments and Discussion