LTTNG-SYSCALLSTATS-MI(1)

πŸ“¦ version 0.6.1, in debian bookworm, ubuntu jammy

πŸ’– LTTNG-SYSCALLSTATS-MI πŸ’–

okay bestie, welcome to lttng-syscallstats-mi, a User Command in the LTTng Analyses family, and it is literally the machine interface that analyses your syscall statistics. no cap. πŸ¦‹


✨ NAME ✨

lttng-syscallstats-mi β€” LTTng analyses syscall statistics machine interface


🌸 DESCRIPTION 🌸

here's the whole vibe, the usage line, exactly as it is:

usage: lttng-syscallstats-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]
              <path/to/trace>

it's the syscallstats command. that's the whole thing. periodt. πŸ’…


πŸŽ€ positional arguments πŸŽ€

  • <path/to/trace> β€” the trace path, bestie. that's where your trace lives. point at it. 🫢

πŸ‘‘ optional arguments πŸ‘‘

  • -h, --help β€” show this help message and exit. the classic. the icon. ✨
  • -r REFRESH, --refresh REFRESH β€” Refresh period, with optional units suffix (default units: s). so if you don't say a unit, it's seconds, okay? 😌
  • --gmt β€” Manipulate timestamps based on GMT instead of local time. your timezone is not the main character here. 🌍
  • --skip-validation β€” Skip the trace validation. no vibe check for your trace, we're just going in. πŸ’€
  • --begin BEGIN β€” start time: hh:mm:ss[.nnnnnnnnn]
  • --end END β€” end time: 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 (requires --period-begin). so like, you literally cannot have the end without the begin. it's giving dependency. πŸŽ€
  • --period-begin-key PERIOD_BEGIN_KEY β€” Optional, list of event field names used to match period markers (default: cpu_id)
  • --period-end-key PERIOD_END_KEY β€” Optional, list of event field names used to match period marker. If none specified, use the same --period-begin-key. she's flexible like that. πŸ’…
  • --period-key-value PERIOD_KEY_VALUE β€” Optional, define a fixed key value to which a period must correspond to be considered.
  • --cpu CPU β€” Filter the results only for this list of CPU IDs. so specific. so selective. πŸ‘‘
  • --timerange TIMERANGE β€” time range: [begin,end]
  • --progress-use-size β€” use trace size to approximate progress. approximation? we love her. 🌈
  • --no-intersection β€” disable stream intersection mode
  • -V, --version β€” show program's version number and exit. say hi to the version bestie. ⭐
  • --debug β€” Enable debug mode (or set LTTNG_ANALYSES_DEBUG environment variable). yes, the env var is a whole thing, don't forget it. πŸ”₯
  • --no-color β€” Disable colored output. sad, but valid. 😭
  • --no-progress β€” Don't display the progress bar. if the bar is stressing you out, this is your out. πŸ™ˆ
  • --procname PROCNAME β€” Filter the results only for this list of process names. name your faves. πŸ“
  • --tid TID β€” Filter the results only for this list of TIDs. thread ids only, mwah. 🧚

ok literally that's every single flag, nothing skipped, nothing merged, nothing invented. i would never do you like that bestie πŸ’œ

and that's the whole page!! this was LTTng Analyses v0.6.0, dated January 2017, and it lives at the bottom of the page as LTTNG-SYSCALLSTATS-MI(1). slay, go read your traces, i'm obsessed with you, bye!! πŸ’–βœ¨πŸŽ€πŸ¦‹πŸŒΈπŸ’…πŸ«Ά

πŸ“¦ where this page comes from