Allow creating multiple channels in a tracing session #199
Description
Right now, a tracing session creates only one channel. This works fine for normal tracing, but it causes problems in snapshot mode. In snapshot mode, data is kept in sub-buffers (in memory) until the user decides to write it to disk. If tracing isn’t started soon after the application launches, high-frequency runtime events can overwrite the important initialization events (see #44 to know more about initialization and runtime events).
Allowing multiple channels in a tracing session would fix this. Users could enable recording initialization events in one channel and all runtime events in another. This way, critical initialization data is much less likely to be lost in snapshot sessions.
more about LTTng channels and sub-buffers: https://lttng.org/docs/v2.13/#doc-channel
more about snapshot mode: https://lttng.org/docs/v2.13/#doc-tracing-session-mode