Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Trace Compass/Feature Roadmap"
(→Planned for 2.0) |
(→Planned for 2.0) |
||
| Line 20: | Line 20: | ||
* Dependency analysis framework ([http://multivax.blogspot.ca/2013/12/system-level-profiling-of-apt.html example]) | * Dependency analysis framework ([http://multivax.blogspot.ca/2013/12/system-level-profiling-of-apt.html example]) | ||
* Virtual Machine analysis (See screenshots at the end of [http://www.tracingsummit.org/w/images/c/cd/Tracingsummit2014-gbastien.pdf this presentation]) | * Virtual Machine analysis (See screenshots at the end of [http://www.tracingsummit.org/w/images/c/cd/Tracingsummit2014-gbastien.pdf this presentation]) | ||
| − | |||
* Support for new features of recent versions (2.5+) of LTTng Tools in LTTng Tracer Control view | * Support for new features of recent versions (2.5+) of LTTng Tools in LTTng Tracer Control view | ||
| − | |||
| − | |||
| − | |||
* Support for cropping of CTF traces (incl. state systems) | * Support for cropping of CTF traces (incl. state systems) | ||
* Automatic refresh of local traces | * Automatic refresh of local traces | ||
Revision as of 13:48, 22 February 2017
This page is meant to track all the higher-level planned features and feature requests. As features get implemented, we could move them to "Targeted for version x.y" and "Delivered in version x.y" sections. It would always track the "current" roadmap, but over time would also become a history of which feature was delivered in which version.
Released in 1.0
- Support for perf traces in CTF format
- Automatic vertical alignment of time-based views (Part 1 of this document)
For more details about released features see N&N 1.0
Ready for 1.1
- Moveable/hideable event table columns
- Copy-to-clipboard from Events Table
For more details about released features see N&N 1.1
Ready for 2.0
Planned for 2.0
- Dependency analysis framework (example)
- Virtual Machine analysis (See screenshots at the end of this presentation)
- Support for new features of recent versions (2.5+) of LTTng Tools in LTTng Tracer Control view
- Support for cropping of CTF traces (incl. state systems)
- Automatic refresh of local traces
- Auto-filtering of inactive elements in time graph views
- Support for arrows in data-driven time graph views
- Management of LTTng session profiles
- Management of data-driven analysis XML files
Wishlist
These features have been proposed and deemed interesting to have, but nobody has committed to work on them yet.
- Support for perf traces in standard perf.data
- Support for ftrace traces
- Documentation at https://www.kernel.org/doc/Documentation/trace/ftrace.txt
- Investigate if we could re-implement the KernelShark view using a generic time graph view
- Reduce the size of state system history files
- Timestamps (2x 64 bits) are repeated for every single interval. Low-hanging fruit (using protocol buffers?)
- Compress often-used values (including strings).
- Support for data-driven Sequence Diagrams
- Sequence Diagrams for PCAP traces
- Visually define data-driven state providers with state diagrams
- Aligned X axis (time) (Parts 2 and 3)