LTTNG-SYSCALLSTATS(1)

✨ LTTNG-SYSCALLSTATS ✨

okay bestie, welcome to the lttng-syscallstats page from the LTTng manual (section 1, user commands, iykyk) 💅 this one's about analysing syscall statistics and it's lowkey iconic.

🎀 NAME 🎀

lttng-syscallstats — LTTng analyses syscall statistics

like. it literally does syscall statistics analysis. that's the whole vibe. no cap. 🦋

🌸 DESCRIPTION 🌸

here's how you call it, bestie, exactly as written:

usage: lttng-syscallstats [-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>

and like, that's the whole thing. The syscallstats command. 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 moment you're lost, she's there. 🌈
• -r REFRESH, --refresh REFRESH — Refresh period, with optional units suffix (default units: s). yes, seconds is the default, and yes you can slap a unit suffix on it if you're feeling fancy. ⭐
• --gmt — Manipulate timestamps based on GMT instead of local time. timezone girlies rise. 🌍
• --skip-validation — Skip the trace validation. skipping straight past the vibe check, bold of you, love that for you. 🙈
• --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, no begin, no end, that's the rule fr fr. 🔥
• --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 reuses, she's efficient, we love her. 💜
• --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
• --timerange TIMERANGE — time range: [begin,end]
• --progress-use-size — use trace size to approximate progress. approximation is still progress, bestie. ✨
• --no-intersection — disable stream intersection mode
• -V, --version — show program's version number and exit
• --debug — Enable debug mode (or set LTTNG_ANALYSES_DEBUG environment variable). yes bestie, there's an env var, go off. 🧚
• --no-color — Disable colored output. (not me gasping. no color?? but okay, do what you gotta do 💀)
• --no-progress — Don't display the progress bar
• --procname PROCNAME — Filter the results only for this list of process names
• --tid TID — Filter the results only for this list of TIDs

not me writing a whole manual page with all 20-something flags intact. every single one. no skipping. the details stay, the vibe just got cuter. that's the deal. 🫶

and that's the page, babes! this lil beauty comes to you from LTTng Analyses v0.6.0, dated January 2017. vintage. iconic. ate. 💅🎀💖