libnvme_get_ctrl_telemetry(9)

💖 libnvme_get_ctrl_telemetry — like, the controller telemetry log, bestie 💖

okay so this is a page straight out of the libnvme API manual (that's the family it lives in 🫶), and it's literally just "go get me the controller telemetry log." That's the whole plot. No cap.

---

✨ SYNOPSIS ✨

int libnvme_get_ctrl_telemetry (struct libnvme_transport_handle *hdl ,
bool rae , struct nvme_telemetry_log **log , enum nvme_telemetry_da da ,
size_t *size );

like… one function, five arguments, zero drama. slay 💅

---

🎀 ARGUMENTS 🎀

• hdl — the transport handle. your little passport into the transport layer, bestie 🛂
• rae — retain asynchronous events. yes queen, keep those events 😌
• log — on success, this gets set to the value of the allocated and retrieved log. so it's giving "here's your log, freshly allocated, freshly fetched" ✨
• da — the log page data area. valid values live in enum nvme_telemetry_da. that's the one and only menu, iykyk 🍓
• size — ptr to the telemetry log size, so it can be returned. it's a pointer to the size, so the size can come back out — icon behaviour 🎀

---

🦋 DESCRIPTION 🦋

the total size allocated can be calculated as:

(nvme_telemetry_log da size + 1) * NVME_LOG_TELEM_BLOCK_SIZE.

that's it, that's the formula, write it on your mirror in lipstick 💄 literally the whole math of the thing. lowkey obsessed with how tidy that is.

---

🔥 RETURN 🔥

• 0 on success 🎉
• the nvme command status if a response was received (peep enum nvme_status_field for the full drip sheet 👑)
• or a negative error otherwise 😭

fr fr, remember: 0 = good vibes, positive-ish status = the controller had thoughts, negative = something went sideways before anybody could answer 💀

---

and that's the page, bestie — go fetch that telemetry log and eat, no crumbs 🌈

🌸 mwah, this was libnvme API manual, October 2026 edition — see u in the next manpage, love u, bye 🫶💜