Cannot enable channel for JUL (-j) or Log4j (-l) domains
lttng enable-event command allows
-l flags, to enable events for the JUL and Log4j domains respectively. However, the
lttng enable-channel command does not allow these flags. Interestingly, the "missing domain" error message mentions the
-j flag, but it does not actually work:
$ lttng enable-channel MyChannel
Error: Please specify a domain (-k/-u/-j).
Error: Command error
$ lttng enable-channel MyChannel -j
usage: lttng enable-channel NAME[,NAME2,...] (-u | -k) [OPTIONS]
Updated by Jérémie Galarneau almost 5 years ago
- Status changed from New to Confirmed
- Target version set to 2.6
The explicit creation of "agent" channels is unsupported. All agent events are assumed to be part of each agent-domain's default channel, which is created when an event in that domain is enabled for the first time. Therefore, enable-channel's documentation should not mention them.
Updated by Anonymous over 4 years ago
Something I forgot to mention in the original report, this means that we have to enable at least one event before we can start tracing in the "agent channels". Whereas with -u we can do:
lttng create lttng enable-channel -u mychannel lttng start
and enable events later on.