The lttng regenerate metadata action can be used to resample the offset
between the system’s monotonic clock and the wall-clock time.

This action is meant to be used to resample the wall-clock time following a
major NTP correction.
As such, a system booting with an incorrect wall time can be traced before its
wall time is NTP-corrected. Regenerating the tracing session’s metadata ensures
that trace viewers can accurately determine the events time relative to Unix
Epoch.

The lttng regenerate statedump action can be used to collect up-to-date state
dump information during the tracing session. This is particularly useful in
snapshot (see lttng-snapshot(1)) or trace file rotation (see
lttng-enable-channel(1)) modes where the state dump information may be
lost.

Note that the lttng-create(1) command can spawn an LTTng
session daemon automatically if none is running. See
lttng-sessiond(8) for the environment variables influencing
the execution of the session daemon.

This is where the per-user current tracing session is stored between
executions of lttng(1). The current tracing session can be set
with lttng-set-session(1). See lttng-create(1) for
more information about tracing sessions.

$LTTNG_HOME/lttng-traces

Default output directory of LTTng traces. This can be overridden
with the --output option of the lttng-create(1)
command.