LTTNG-PERIODSTATS-MI(1)

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

✨ NAME ✨

lttng-periodstats-mi β€” LTTng analyses period statistics machine interface πŸŽ€


🌸 DESCRIPTION 🌸

okay so bestie, this is the periods command, and it's giving machine interface energy. here's the whole vibe of how you call it:

usage: lttng-periodstats-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] [--freq] [--freq-resolution FREQ_RESOLUTION]
       [--freq-uniform] [--freq-series] [--limit LIMIT] [--top] [--log]
       [--stats] [--min-duration MIN_DURATION] [--max-duration MAX_DURATION]
       [--aggregate-by AGGREGATE_BY] [--select SELECT] [--group-by GROUP_BY]
       [--order-by ORDER_BY] <path/to/trace>

that's the whole shape of it, no cap. πŸ’–


🫢 POSITIONAL ARGUMENTS 🫢

  • <path/to/trace> β€” the trace path, literally just point it at your trace and let her cook πŸ¦‹

πŸ‘‘ OPTIONAL ARGUMENTS πŸ‘‘

  • -h, --help β€” shows this help message and dips. classic. πŸ’…
  • -r REFRESH, --refresh REFRESH β€” the refresh period, and you can tack a units suffix on it if you're feeling fancy (default units: s) ⏱️
  • --gmt β€” manipulate timestamps based on GMT instead of local time 🌍
  • --skip-validation β€” skip the trace validation. living dangerously, iconic 😭
  • --begin BEGIN β€” start time, formatted like hh:mm:ss[.nnnnnnnnn] ⭐
  • --end END β€” end time, same deal: 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 (and heads up bestie, this one requires --period-begin) πŸ™ˆ
  • --period-begin-key PERIOD_BEGIN_KEY β€” optional! a list of event field names used to match period markers (default: cpu_id)
  • --period-end-key PERIOD_END_KEY β€” optional, same thing but for the period end 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 the LTTNG_ANALYSES_DEBUG environment variable) πŸ›
  • --no-color β€” disable colored output (sad, but sometimes necessary) 🚫🌈
  • --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 πŸ“
  • --freq β€” output statistics about periods durations πŸ“Š
  • --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 🧚
  • --limit LIMIT β€” limit to top X (default = 10)
  • --top β€” output the top sched switch durations πŸ”
  • --log β€” output the sched switches in chronological order πŸ“œ
  • --stats β€” output sched switch statistics πŸ“ˆ
  • --min-duration MIN_DURATION β€” filter out, periods shorter that duration (usec)
  • --max-duration MAX_DURATION β€” filter out, periods longer than duration (usec)
  • --aggregate-by AGGREGATE_BY β€” FIXME πŸ’€ (yes bestie, that's literally what it says, i'm not making it up)
  • --select SELECT β€” FIXME πŸ’€ (same, we don't know either)
  • --group-by GROUP_BY β€” present the results grouped by a list of fields, written like period.captured_field[, period.captured_field2] πŸ—‚οΈ
  • --order-by ORDER_BY β€” hierarchy, time ⏳

ngl, --aggregate-by and --select are both marked FIXME in the source. that's not me being shady, that's literally the documentation. use with vibes and caution πŸ’…

and that's the whole page bestie!! 🌈 this was LTTng Analyses v0.6.0, dated January 2017, and the manual page is LTTNG-PERIODSTATS-MI(1). go forth and analyse those periods, you absolute main character πŸ‘‘πŸ’–βœ¨

πŸ“¦ where this page comes from