NVME-OCP-GET-TELE(1)

💖 NAME 💖

okay so this is nvme-ocp-get-telemetry-profile — a page from the NVMe Manual (section 1, for the girlies keeping track) — and its whole job is to define and print the get-telemetry-profile value. that's it. that's the vibe. ✨

---

🎀 SYNOPSIS 🎀

nvme [<global-options>] ocp get-telemetry-profile <device>
                        [--sel=<select> | -s <select>]
                        [--namespace-id <nsid> | -n <nsid>]
                        [--no-uuid | -u]

---

🌸 DESCRIPTION 🌸

so the <device> parameter is mandatory, no exceptions bestie — and it can be either the NVMe character device (like /dev/nvme0) or the block device (like /dev/nvme0n1). pick your fighter. 🦋

this will only work on OCP compliant devices that actually support this feature. results for any other device are undefined — like, genuinely undefined, we don't know what happens, so maybe don't. 😭

on success it returns 0. error code otherwise. periodt.

---

🔥 OPTIONS 🔥

• -n <nsid>, --namespace-id=<nsid> — NSID: assign the different kind of nsid value (like active, inactive and invalid nsids) and check the get feature command response. the broadcast value 0xffffffff can also be given as all or -1. yes, -1 is a valid way to say that, don't ask, it slays 💅
• -s <select>, --sel=<select> — Select (SEL): this field specifies which value of the attributes to return in the provided data:
  • 0 — current → Current
  • 1 — default → Default
  • 2 — saved → Saved
  • 3 — supported → Supported capabilities
• -u, --no-uuid — do not try to automatically detect UUID index for this command (required for old OCP 1.0 support). she's a legacy icon, respect her 👑

---

🌈 GLOBAL OPTIONS 🌈

these are defined at the top-level nvme command and are available to this subcommand too. iconique of them honestly:

• --dry-run — print the command that would be executed, but do not actually execute it. manifesting without committing 🫶
• --no-ioctl-probing — disable probing for 64-bit IOCTL support.
• --no-retries — disable retry logic on transient errors. one shot, one opportunity.
• -o <fmt>, --output-format=<fmt> — set the reporting format to normal, tabular, 'json (yes that stray apostrophe is literally in the original, iykyk 🙈) or binary. only one output format may be used at a time. pick one. choose your destiny.
• --output-format-version=<version> — select the output format version. version 1 uses the original field naming, while version 2 (the default) provides more consistent and script-friendly field names. any other versions are rejected — sorry to those versions specifically 💀
• --quiet — suppress informational messages. errors are still reported, and --quiet cancels any --verbose for the library log level. the way she shushes the whole room 😌
• --set-options=<key=value>[,<key=value>...] — set libnvme library options for this invocation. supported keys are force-4k, mi-probe-enabled, test-base-dir and test-sysfs-dir.
• --timeout=<ms> — set the timeout for the command in milliseconds. infinite or -1 waits without a time limit (0xffffffff). she will wait forever, literally.
• -v, --verbose — increase the level of detail in the output. may be specified multiple times to further increase verbosity. stack it like an iced matcha 🍵

these options can also be set as machine-wide defaults in nvme-cli.conf(5). a command-line flag always overrides the file — command line is the main character here, always ✨

---

🦋 EXAMPLES 🦋

• has the program issue a get-telemetry-profile to retrieve the 0xC8 get features:

# nvme ocp get-telemetry-profile /dev/nvme0

---

👑 NVME 👑

part of the nvme-user suite. fr fr, she runs with a whole crew 🌈

---

okay that's the whole page bestie, you're so ready for this command now 💜 and for the record — this one's from the NVMe manual, dated 10/30/2026, filed under NVME-OCP-GET-TELE(1). go forth and telemetry ✨🎀