NVME-OCP-TELEMETRY(1)

📦
version 2.15 · 4 versions
, in fedora 43

👑 nvme-ocp-telemetry-string-log-page 💖

okay bestie, welcome to the NVMe Manual — this is the page for nvme-ocp-telemetry-string-log-page and honestly? it's giving "short but iconic." ✨

🌸 NAME 🌸

nvme-ocp-telemetry-string-log-page — go grab the OCP Telemetry String Log page, no cap 💅

🦋 SYNOPSIS 🦋

nvme ocp telemetry-str-log <device> [--output-format=<fmt> | -o <fmt>]

✨ DESCRIPTION ✨

So for the NVMe device you hand over, this retrieves the OCP Telemetry String Log page. that's the whole assignment. simple, clean, slay. 🎀

The <device> parameter is mandatory — like, you literally cannot skip it, bestie — and it can be either the NVMe character device (ex: /dev/nvme0) or the block device (ex: /dev/nvme0n1). either one works, pick your fighter. 🫶

okay real talk though: this will only work on OCP compliant devices that actually support this feature. results for any other device are undefined. undefined is not a vibe, it's a warning. 😭

On success it returns 0, error code otherwise. periodt. ✅

💅 OPTIONS 💅

  • -o <fmt>, --output-format=<fmt> — this sets the reporting format to normal, json, or binary. only one output format at a time, bestie — don't be greedy, it's not that kind of party. 🙈

🌈 EXAMPLES 🌈

  • has the program issue a telemetry-string-log command to get the log page data from bin file.
# nvme ocp telemetry-string-log /dev/nvme0n1

🧚 NVME 🧚

part of the nvme-user suite. iykyk 💜

and that's the whole page!! this one's from the NVMe crew, dated 08/15/2025, and it lives in the manual as NVME-OCP-TELEMETRY(1). go forth and read your logs, main character. ⭐🌸💖

📦 where this page comes from