LTTNG-STATUS(1)

📦
version 2.15.1 · 12 versions
, in ubuntu stonking

💖 LTTNG-STATUS — bestie's guide to the status page 💖

okay so this is lttng-status, from the LTTng Manual (the LTTNG-STATUS(1) girlies know ✨), and it does exactly one iconic thing: shows you the status of the current recording session. no cap.

✨ NAME ✨

lttng-status — shows you the status of the current recording session 🎀

🌸 SYNOPSIS 🌸

lttng [GENERAL OPTIONS] status [--channel=CHANNEL]
      [--kernel] [--userspace] [--jul] [--log4j] [--log4j2] [--python]
      [--style=(compact | breathe)] [--no-truncate]
      [--mem-usage=(total | compact | full)]

💅 DESCRIPTION 💅

The lttng status command shows the status of the current recording session. (if you're like "girl what is a current recording session", go read lttng-concepts(7), it explains everything i promise 🫶)

This command is literally equivalent to:

lttng [GENERAL OPTIONS] list CURSESSION [--channel=CHANNEL]
      [--kernel] [--userspace]
      [--jul] [--log4j] [--log4j2] [--python]
      [--style=(compact | breathe)] [--no-truncate]
      [--mem-usage=(total | compact | full)]

where CURSESSION is the name of the current recording session. it's giving same energy, shorter name 💀

The way this works: this command effectively forwards all its options straight to the lttng-list(1) command. so anything list can do, status can do too. it's not doing extra work, it's just repping the current session for you. periodt. 👑

🦋 OPTIONS 🦋

lttng(1) has the GENERAL OPTIONS if you need them 💜

  • -c CHANNEL, --channel=CHANNEL — only list the properties and recording event rules of the channel(s) named CHANNEL. one channel only, bestie, we're being specific 🎯
  • -j, --jul — only list the java.util.logging recording event rules. java girlies rise 🌈
  • -k, --kernel — only list the Linux kernel channels and their recording event rules. kernel mode, main character energy 👑
  • -l, --log4j — only list the Apache log4j 1.x recording event rules. yes, 1.x. retro era 💅
  • --log4j2 — only list the Apache Log4j 2 recording event rules. the glow-up sequel ✨
  • --mem-usage=MODE — set the channel memory usage display mode to MODE. and MODE is one of these three icons:
    • total (default) — show the total memory usage of the channel. the big picture number 📊
    • compact — show the memory usage for each Unix user or process, depending on the buffer ownership model of the channel (peep the --buffer-ownership option of lttng-enable-channel(1)). iykyk 🔍
    • full — show the memory usage for each CPU (if available). every core gets its moment 🧚
  • --no-truncate — do NOT truncate long output lines. by default, the command truncates lines, adding an ellipsis, so it fits the current terminal width. so if you want the whole thing, no cuts, no edits, say it with me: --no-truncate 🫶
  • -p, --python — only list the Python recording event rules. snake girlies, this one's for you 🐍💚
  • --style=STYLE — set the command output style to STYLE. STYLE is one of:
    • breathe (default) — add empty lines so blocks of related information stand out. aesthetic spacing, we love a bit of breathing room 😌
    • compact — make the output compact. no space, all business, efficiency queen 💀
  • -u, --userspace — only list the user space channels and their recording event rules. user space represent 🏠

🎀 Program information 🎀

  • -h, --help — show help. this option attempts to launch /usr/bin/man to view this manual page. and you can override the manual pager path with the LTTNG_MAN_BIN_PATH environment variable if /usr/bin/man isn't your girl 💜
  • --list-options — list available command options and quit. a little menu of possibilities, then it dips 👋

⭐ EXIT STATUS ⭐

  • 0 — Success 🎉
  • 1 — Command error 😭
  • 2 — Undefined command 💀
  • 3 — Fatal error 🚨
  • 4 — Command warning (something went wrong during the command) 🙈

🌈 ENVIRONMENT 🌈

  • LTTNG_ABORT_ON_ERROR — set to 1 to abort the process after the first error is encountered. strictly no second chances 💅
  • LTTNG_HOME — path to the LTTng home directory. defaults to $HOME. super useful when the Unix user running the commands has a non-writable home directory. we love a workaround 🫶
  • LTTNG_LIST_LEGACY — set to 1 to use the legacy output format (LTTng 2.14 and earlier) for the lttng-list(1) command instead of the modern output format. heads up: the legacy output doesn't show anything related to features introduced after LTTng 2.14, so don't come crying when your new faves are missing 😭
  • LTTNG_MAN_BIN_PATH — absolute path to the manual pager to use to read the LTTng command-line help (with lttng-help(1) or with the --help option) instead of /usr/bin/man. custom pager, custom vibe ✨
  • LTTNG_NO_UTF_8 — set to 1 to NOT emit multi-byte UTF-8 sequences, even if the locale claims to support it. sometimes you just need plain bytes, no drama 💀
  • LTTNG_SESSION_CONFIG_XSD_PATH — path to the directory containing the session.xsd recording session configuration XML schema. schema location, that's it, that's the whole job 📁
  • LTTNG_SESSIOND_PATH — absolute path to the LTTng session daemon binary (see lttng-sessiond(8)) to spawn from the lttng-create(1) command. note: the --sessiond-path general option overrides this environment variable. option wins, always 👑
  • LTTNG_TERM_COLOR — controls when to emit terminal SGR codes in the output. the NO_COLOR environment variable overrides this. one of:
    • auto (default) — only emit SGR codes when the standard output is connected to a color-capable terminal. reading the room, respectfully 💅
    • always — always emit SGR codes. color everywhere, no restraint 🎨
    • never — never emit SGR codes. minimalism era 🤍
  • NO_COLOR — if set and not empty, then it's equivalent to setting LTTNG_TERM_COLOR to never. see NO_COLOR <https://no-color.org/> to learn more. it's a whole movement 🫶

💜 FILES 💜

  • $LTTNG_HOME/.lttngrc — the Unix user's LTTng runtime configuration. this is where LTTng stores the name of the Unix user's current recording session between executions of lttng(1). and psst: lttng-create(1) and lttng-set-session(1) are the ones that set the current recording session 📌
  • $LTTNG_HOME/lttng-traces — default output directory of LTTng traces in local and snapshot modes. you can override this path with the --output option of the lttng-create(1) command 🗂️
  • $LTTNG_HOME/.lttng — the Unix user's LTTng runtime and configuration directory. the whole home base 🏠
  • $LTTNG_HOME/.lttng/sessions — default directory containing the Unix user's saved recording session configurations (see lttng-save(1) and lttng-load(1)) 💾
  • /etc/lttng/sessions — directory containing the system-wide saved recording session configurations (see lttng-save(1) and lttng-load(1)) 🌍
Note 📝 $LTTNG_HOME defaults to the value of the HOME environment variable. so if you never touched it, it's just your regular home, bestie.

🧚 RESOURCES 🧚

This program is part of the LTTng-tools project.

LTTng-tools is distributed under the GNU General Public License version 2 — http://www.gnu.org/licenses/old-licenses/gpl-2.0.en.html. See the LICENSE file — https://github.com/lttng/lttng-tools/blob/master/LICENSE — for details. 📜✨

💖 THANKS 💖

Special thanks to Michel Dagenais and the DORSAL laboratory — http://www.dorsal.polymtl.ca/ — at École Polytechnique de Montréal for the LTTng journey. literal legends 🫶🎓

Also thanks to the Ericsson teams working on tracing, who helped greatly with detailed bug reports and unusual test cases. the way they found the weirdest edge cases… obsessed 😭💅

🔥 SEE ALSO 🔥

lttng(1), lttng-create(1), lttng-list(1), lttng-set-session(1), lttng-concepts(7)

and that's the whole page, bestie!! ✨ this was LTTng 2.15.1, dated 27 October 2025, signing off — go check your session status, you know you want to 💅🎀🦋

📦 where this page comes from