LTTNG-IOLATENCYSTATS(1)

💖 LTTNG-IOLATENCYSTATS 💖

okay bestie, so this is lttng-iolatencystats — the LTTng analyses girlie whose whole personality is IO latency statistics. it's a User Command, it lives in section 1 of the manual, and it is genuinely about to tell you everything about how your I/O is behaving. no cap. 🔥

✨ NAME ✨

lttng-iolatencystats — LTTng analyses IO latency statistics 💅

🌸 DESCRIPTION 🌸

here's the vibe, the usage, the whole synopsis moment:

lttng-iolatencystats [-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]
       [--min MIN] [--max MAX] [--log] [--limit LIMIT] [--top] [--stats]
       [--freq] [--freq-resolution FREQ_RESOLUTION] [--freq-uniform]
       [--freq-series] [--usage] [--minsize MINSIZE] [--maxsize MAXSIZE]
       <path/to/trace>

and it's the I/O command 🦋 that's literally its whole thing.

🎀 positional arguments 🎀

• <path/to/trace> — the trace path, queen. that's where your trace lives. 👑

💜 optional arguments 💜

• -h, --help — show this help message and exit. the classic. ask and ye shall receive. 🙈
• -r REFRESH, --refresh REFRESH — refresh period, with an optional units suffix (default units: s). so like, how often it refreshes its little display.
• --gmt — manipulate timestamps based on GMT instead of local time. timezone plot twist ✨
• --skip-validation — skip the trace validation. living dangerously, we respect it. 💀
• --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). ⚠️ yes it literally requires it, don't come for me.
• --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. teamwork fr fr 🫶
• --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. progress bar said "trust me, we're getting there" 📏
• --no-intersection — disable stream intersection mode.
• -V, --version — show program's version number and exit.
• --debug — enable debug mode (or set the LTTNG_ANALYSES_DEBUG environment variable). 👀 yes that's an environment variable, write it down.
• --no-color — disable colored output. (a tragedy, but valid.) 😭
• --no-progress — don't display the progress bar.
• --min MIN — filter out durations shorter than min usec.
• --max MAX — filter out durations longer than max usec.
• --log — output the I/O requests in chronological order. storyline in order, as it should be 📖
• --limit LIMIT — limit to top X (default = 10).
• --top — output the top I/O latencies by category.
• --stats — output the I/O latency statistics. the main character of the flags honestly 👑
• --freq — output the I/O latency frequency distribution.
• --freq-resolution FREQ_RESOLUTION — frequency distribution resolution (default 20).
• --freq-uniform — use a uniform resolution across distributions.
• --freq-series — consolidate frequency distribution histogram as a single one.
• --usage — output the I/O usage.
• --minsize MINSIZE — filter out, I/O operations working with less that minsize bytes.
• --maxsize MAXSIZE — filter out, I/O operations working with more that maxsize bytes.

bestie reminder: this whole thing is LTTng Analyses v0.6.0, dated January 2017. yes, that's the source and version and date, and it's giving vintage-but-iconic. 🎀

that's the page, ily, go analyze some I/O latency. periodt. 💅✨