Project

General

Profile

Actions

Feature #108

closed

Missing information in list command output

Added by Bernd Hufmann about 13 years ago. Updated over 9 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
02/24/2012
Due date:
% Done:

0%

Estimated time:

Description

The command "lttng enable-event" allows to enable events for one loglevel or for a range of loglevels. However, the "lttng list session"-command doens't show what is actually enabled. It should be clear if a single loglevel is enabled or a range.

Consider the two commands:

lttng enable-event a* -u --loglevel TRACE_DEBUG_LINE
lttng enable-event b* -u --loglevel-only TRACE_DEBUG_LINE

For both commands the output shows basically the same information. For the first one it doesn't show that the events are enabled for a range. This needs to be improved.

lttng list my

Tracing session my: [inactive]
Trace path: /home/user/lttng-traces/my-20120224-135914

=== Domain: UST global ===

Channels:
-------------
- channel0: [enabled]

Attributes:
overwrite mode: 0
subbufers size: 4096
number of subbufers: 4
switch timer interval: 0
read timer interval: 200
output: mmap()
Events:
a* (loglevel: TRACE_DEBUG_LINE (13)) (type: tracepoint) [enabled]
b* (loglevel: TRACE_DEBUG_LINE (13)) (type: tracepoint) [enabled]

I used the commit aeb968923d1245f4cb2be1eed2ab7b8b5eb45cf8

Actions #1

Updated by David Goulet about 13 years ago

  • Status changed from New to Confirmed

The wildcard activation is actually one single event for the lttng cli and session daemon point of view. The wildcard parsing is done on the tracer side.

At the moment, the session daemon is unable to know every event activated by a wildcard. It would require more communication between ust and the session daemon.

I will not target this feature for a know version since it implies important changes and is not on the roadmap for 2.1 at all.

Actions #2

Updated by Anonymous about 13 years ago

  • Target version set to 5
Actions #3

Updated by Anonymous almost 13 years ago

  • Target version deleted (5)

Ok we won't use the "Future" milestone anymore. Anything Confirmed but not assigned a milestone is implied to be "future".

Actions #4

Updated by David Goulet over 12 years ago

  • Tracker changed from Bug to Feature

Actually, listing events that wildcards enabled is a complete new feature that may come in the 2.x tool chain. I'm flagging this ticket as a feature request.

Actions #5

Updated by Jérémie Galarneau over 9 years ago

  • Status changed from Confirmed to Resolved
Actions

Also available in: Atom PDF