Project

General

Profile

Bug #738

create --live needs sane defaults.

Added by Mathieu Desnoyers over 6 years ago. Updated about 6 years ago.

Status:
Resolved
Priority:
High
Assignee:
Target version:
Start date:
02/25/2014
Due date:
% Done:

100%

Estimated time:

Description

Before 2.4 final, it would be good to provide a good UI for lttng create --live:

lttng create --live
-> defaults to flush interval of 1 second (1000000) if not specified
-> default to -U net://localhost if not specified

If a create -U net://localhost is performed but no relayd is listening on
localhost, lttng UI could spawn a relay daemon listening on localhost on
the default port.

In Babeltrace, we should also ensure that babeltrace -i lttng-live (without
net:// parameter) defaults to try to query relay daemon on localhost on the
default port.

We should also bind "lttng view" to "babeltrace -i lttng-live" when lttng view
is executed against a live session.

This would enable the following usage:

lttng create --live
lttng enable-event -u -a
lttng start
lttng view

#1

Updated by David Goulet over 6 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100
#2

Updated by Mathieu Desnoyers about 6 years ago

  • Status changed from Resolved to In Progress

Hi David,

Here is the sequence of commands I would like to work out of the box in terms of user experience:

lttng create --live
lttng enable-event -u -a
lttng start
lttng view

Without anything else. It means:
- lttng create --live (default) will start a lttng-relayd on localhost if there is not already one listening.
- lttng view will spawn babeltrace -i lttng-live to view the trace.

The fix you proposed only takes care of having defaults for --live, but does not take care of the rest of the user experience.

Thanks,

Mathieu

#3

Updated by David Goulet about 6 years ago

  • Status changed from In Progress to Resolved

Also available in: Atom PDF