Trace Compass

Screenshots

Call Stack

If you can define trace events representing function entries and exits, you can display the call stack of your application over time. You can also get profiling information from the Flame Graph or descriptive statistics.

Kernel Analysis

Displays the states of processes and resources over time, using information from Linux kernel traces.

UST Memory

Using LTTng-UST's C standard library wrapper, all calls to memory allocation and free are traced. You can display the memory utilization or find potential memory leaks.

Extend pes

The base framework can be extended to add support for new trace types. Support for libpcap traces (the format used by Wireshark) was added this way.

Key Features

Offline analysis of complex issues

Real-time deadline investigation
Latency analysis
Log correlation with operating system traces
Network packet correlation across layers
Identification of relevant information in large amounts of trace data
Critical path analysis
Causes of high processor usage and memory leaks
Correlation of hardware and software components execution traces
Time synchronization of traces from different nodes
Symbol name resolution using debug information
Additional analyses available with the Trace Compass Incubator
and more!

For more information, see the Trace Compass datasheet.

Multiple trace formats supported

Common Trace Format (CTF), including but not limited to:
- Linux LTTng kernel traces
- Linux LTTng-UST userspace traces
- Bare metal traces
- Integration with the LTTng-Analyses scripts
- Linux Perf traces converted to CTF*
- ROCm traces generated by the ROCm environment (ROC-tracer and/or ROC-profiler) converted to CTF*
- Robot Operating System (ROS and ROS2) traces*
- Open Trace Format Version 2 (OTF2) tracesconverted to CTF*
Linux FTrace raw binary and textual format*
Hardware traces (e.g. IEEE Nexus 5001 CTF conversion). See also this link
GDB traces for debugging
The Best Trace Format (BTF) for OSEK
The libpcap (Packet CAPture) format, for network traces
Open Tracing traces generated by Jaeger tracer*
Custom text or XML parsers that can be added right from the graphical interface by the user
Predefined Custom parser defintions*
Google's trace event json format*
Android traces*
UFtrace format*

Can be extended to support various log or trace files.

For user guides, see the Documentation section.

* Provided by the Trace Compass Incubator project.

Benefits

Reduce time to identify faults
Observe multi-core, heterogeneous, virtualized, and distributed systems
Use the same analysis tool for development, testing, and production
Extend the framework to fit the needs of your organization
Avoid vendor lock-in by using an open source solution

Downloads

Linux

Windows

OS X

To find out more about the release, see the New & Noteworthy page for this release.

Other downloads and source code...

Documentation

To get started with Trace Compass, you can follow this tutorial that describe a few use cases of how to use tracing and Trace Compass.

Here are the links to the Trace Compass user guides:

If you'd like to develop your custom extension using Trace Compass Framework API, then follow the project's Developer Guide.

More information is available on the project's official wiki.

Community

Here are the various ways to join the Trace Compass community:

Mailing list: tracecompass-dev@eclipse.org
IRC channel: #tracecompass on the OFTC network
Trace Compass
Trace Compass Incubator
- Project Page
- Report a Bug

Acknowledgments

YourKit supports open source projects with its full-featured Java Profiler. YourKit, LLC is the creator of YourKit Java Profiler and YourKit .NET Profiler, innovative and intelligent tools for profiling Java and .NET applications.