Bug 546123 - Add support of session rotated traces
Summary: Add support of session rotated traces
Status: NEW
Alias: None
Product: Tracecompass
Classification: Tools
Component: LTTng (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 enhancement
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Project Inbox CLA
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2019-04-04 14:16 EDT by Genevieve Bastien CLA
Modified: 2019-04-04 14:24 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Genevieve Bastien CLA 2019-04-04 14:16:22 EDT
LTTng 2.11 adds the feature or session rotation, where during a trace session, a new trace folder is created with all further events for this session being saved there instead.

The result is that in the trace session directory are many sub-directories named with begin and end timestamps, inside which are the traces from this session.

In the metadata is a trace UUID that can be used to identify those trace chunks.

In Trace Compass, opening many trace chunks should display analysis results as coming from the same trace (for eg. control flow view should be the sum of all traces), not X separate pieces for X chunks of trace.

Yet a user might wish to see only one chunk (because the whole can be quite big).

Implementation options:

1- Consider chunks as 1 trace: if the user imports many trace folders and the traces have the same trace uuid, consider those files as coming from one and the same trace.  Con: The user might wish to import a lot of folders and analyze them separately.

2- Do it at the analysis level: Require the traces to be imported in an experiment, and have a state system for the experiement. Con: an experiment might have traces from different hosts, that are completely independent, so the resulting state systems would be much larger _and_ each analysis would have to consider this, not very interesting...

3- Same as 1-  but add an option at import time to import traces with same trace uuid as one trace instead of multiple. Con: An additional global option for a specific use case

Thoughts