LTTNG-CPUTOP-MI(1)

📦 version 0.6.1, in debian bookworm, ubuntu jammy

💅 LTTNG-CPUTOP-MI 💅

ok so bestie, welcome to lttng-cputop-mi from the LTTng girlies — it's the CPU top machine interface, and yes, it's as iconic as it sounds. This is the LTTng-CPUTOP-MI(1) page, User Commands energy, and we're gonna go through literally every single flag together. no skipping. periodt. 🎀

✨ NAME ✨

lttng-cputop-mi — LTTng analyses CPU top machine interface 🦋

🌸 DESCRIPTION 🌸

ok so here's the vibe, the whole usage, exactly as it comes:

usage: lttng-cputop-mi [-h] [-r REFRESH] [--gmt] [--skip-validation]
       [--begin BEGIN] [--end END] [--period PERIOD]
       [--period-captures PERIOD_CAPTURES] [--period-begin PERIOD_BEGIN]
       [--period-end PERIOD_END] [--period-begin-key PERIOD_BEGIN_KEY]
       [--period-end-key PERIOD_END_KEY] [--period-key-value
       PERIOD_KEY_VALUE] [--cpu CPU] [--timerange TIMERANGE]
       [--progress-use-size] [--no-intersection] [-V] [--debug]
       [--no-color] [--no-progress] [--procname PROCNAME] [--tid TID]
       [--limit LIMIT] [--top] <path/to/trace>

and like, that's it. that's the whole shape of it. The cputop command. 💖

🫶 positional arguments:

  • <path/to/trace> — the trace path. give it the path, it does the thing. that's the whole job bestie 🍓

🔥 optional arguments:

  • -h, --help — shows this help message and then dips out. exit, stage left 💅
  • -r REFRESH, --refresh REFRESH — the refresh period, and you can throw a units suffix on it if you're feeling fancy (default units: s). ⏱️
  • --gmt — manipulates timestamps based on GMT instead of local time. GMT girlie behavior, we respect it 🌍
  • --skip-validation — skips the trace validation. just… straight in, no questions asked. bold. 😭
  • --begin BEGIN — start time, formatted like hh:mm:ss[.nnnnnnnnn]. yes all those n's, count them, we don't make the rules ✨
  • --end END — end time, same deal: hh:mm:ss[.nnnnnnnnn] 🕰️
  • --period PERIOD — period definition 📅
  • --period-captures PERIOD_CAPTURES — period captures definition 📸
  • --period-begin PERIOD_BEGIN — analysis period start marker event name 🎬
  • --period-end PERIOD_END — analysis period end marker event name. and heads up bestie, this one requires --period-begin. you can't have the ending without the beginning, it's giving narrative arc 🎭
  • --period-begin-key PERIOD_BEGIN_KEY — optional, a list of event field names used to match period markers (default: cpu_id) 🔑
  • --period-end-key PERIOD_END_KEY — optional, a list of event field names used to match period marker. If none specified, use the same --period-begin-key. matching set, cute 🔐
  • --period-key-value PERIOD_KEY_VALUE — optional, define a fixed key value to which a period must correspond to be considered. very "you must be THIS specific to ride" of it 🎢
  • --cpu CPU — filter the results only for this list of CPU IDs. pick your faves 🖥️
  • --timerange TIMERANGE — time range: [begin,end]. brackets included, that's the format, don't @ me ⏳
  • --progress-use-size — use trace size to approximate progress. approximation era 📏
  • --no-intersection — disable stream intersection mode. intersection? declined 🚫
  • -V, --version — shows the program's version number and exits. knowing your version is self care 💜
  • --debug — enable debug mode (or set the LTTNG_ANALYSES_DEBUG environment variable). two ways to get the same tea 🐛
  • --no-color — disables colored output. sometimes you want the monochrome minimalism, we get it 🖤
  • --no-progress — don't display the progress bar. no bar, no waiting anxiety, just vibes 🙈
  • --procname PROCNAME — filter the results only for this list of process names. name-drop your processes 🏷️
  • --tid TID — filter the results only for this list of TIDs. thread IDs, but make it curated 🧵
  • --limit LIMIT — limit to top X (default = 10). ten is the number, that's the default, remember it ⭐
  • --top — output the top results. the crown goes to… 👑
fr fr, that's every single option. nothing left out, nothing invented, all facts intact. iykyk 🫶

🌈 a lil sign-off 🌈

this gorgeous page is from LTTng Analyses v0.6.0, dated January 2017, and it lives in the User Commands section of the manual as LTTNG-CPUTOP-MI(1). go forth and cputop, bestie. slay. 💖✨🎀

📦 where this page comes from