LTTNG-IOLOG-MI(1)

✨ LTTNG-IOLOG-MI(1) ✨

okay bestie, welcome to the User Commands section of the manual, this is lttng-iolog-mi and she is the I/O command for LTTng analyses — the machine interface that reads your IO logs for you 💅

🌸 NAME 🌸

lttng-iolog-mi — LTTng analyses IO log machine interface

🦋 DESCRIPTION 🦋

no literally, it's giving "usage:" energy, so here's the whole invocation in all her glory:

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

The I/O command. periodt. 🎀

💫 positional arguments 💫

• <path/to/trace> — the trace path, aka where your data lives bestie, point her at it 🫶

👑 optional arguments 👑

• -h, --help — show this help message and exit. classic. iconic. she ate.
• -r REFRESH, --refresh REFRESH — Refresh period, with optional units suffix (default units: s)
• --gmt — Manipulate timestamps based on GMT instead of local time
• --skip-validation — Skip the trace validation
• --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)
• --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
• --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
• --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)
• --no-color — Disable colored output
• --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
• --limit LIMIT — Limit to top X (default = 10)
• --top — Output the top I/O latencies by category
• --stats — Output the I/O latency statistics
• --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

and that's the whole page bestie, every single flag accounted for, no cap 💖

this little masterpiece comes to you from LTTng Analyses v0.6.0, dated January 2017, living under the name LTTNG-IOLOG-MI(1) 🎀 go forth and analyse those IO logs, you got this 👑✨