LTTNG-SYSCALLSTATS-MI(1)
π 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 setLTTNG_ANALYSES_DEBUGenvironment 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
- debian bookworm: python3-lttnganalyses 0.6.1-3 Β· MIT
- ubuntu jammy: python3-lttnganalyses 0.6.1-2 Β· MIT
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms