Feature #106
openMissing context information in list command
0%
Description
After adding a context to an event there is no way to retrieve the context information, i.e. lttng list <session name> doesn't show the context information.
I think, a general rule should be, that things that can be configured should be able to be retrieved.
I used commit aeb968923d1245f4cb2be1eed2ab7b8b5eb45cf8
Here is an example sequence. As you can see "lttng list my"-comand doesn't show the context information:
lttng create my
Session my created.
Traces will be written in /home/eedbhu/lttng-traces/my-20120224-130527
lttng enable-event sched_switch -k
kernel event sched_switch created in channel channel0
lttng add-context -k -e sched_switch -t pid
kernel context pid added to event sched_switch
lttng list my
Tracing session my: [inactive]
Trace path: /home/eedbhu/lttng-traces/my-20120224-130527
=== Domain: Kernel ===
Channels:
-------------
- channel0: [enabled]
Attributes:
overwrite mode: 0
subbufers size: 262144
number of subbufers: 4
switch timer interval: 0
read timer interval: 200
output: splice()
Events:
sched_switch (loglevel: TRACE_EMERG (0)) (type: tracepoint) [enabled]
Updated by David Goulet over 12 years ago
- Status changed from New to Confirmed
- Assignee set to David Goulet
- Priority changed from Normal to Low
- Target version set to 2.0 stable
I will try to make it for 2.0-stable but it's really not sure. This is indeed a missing feature but not critical for 2.0.
Updated by Yannick Brosseau over 12 years ago
- Target version changed from 2.0 stable to 2.1 pre
postponed to next release
Updated by David Goulet over 12 years ago
- Target version changed from 2.1 pre to 2.2
Updated by David Goulet almost 12 years ago
- Tracker changed from Bug to Feature
- Priority changed from Low to Normal
Moving this issue from Bug to Feature.
Updated by Jérémie Galarneau about 9 years ago
- Assignee deleted (
David Goulet) - Target version set to Wishlist