---
name: "nvme-ocp-telemetry-string-log-page"
section: "1"
platform: "linux"
package: "nvme-cli"
version: "2.13-2"
release: "Debian 13 (Trixie)"
platforms: ["linux"]
url: "https://new.carta.tech/nvme-ocp-telemetry-string-log-page"
---

# nvme-ocp-telemetry-string-log-page(1)

Retrieve OCP Telemetry String Log page

## NAME

nvme-ocp-telemetry-string-log-page - Retrieve OCP Telemetry String Log page

## SYNOPSIS

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

## DESCRIPTION

For the NVMe device given, Retrieve OCP Telemetry String Log page

The \<device\> parameter is mandatory and may be either the NVMe character device (ex: /dev/nvme0) or block device (ex: /dev/nvme0n1).

This will only work on OCP compliant devices supporting this feature. Results for any other device are undefined.

On success it returns 0, error code otherwise.

## OPTIONS

- \-o \<fmt\>, --output-format=\<fmt\>

  This option will set the reporting format to normal, json, or binary. Only one output format can be used at a time.

## 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.