'\" t
.\"     Title: nvme-solidigm-parse-telemetry-log
.\"    Author: [FIXME: author] [see http://www.docbook.org/tdg5/en/html/author]
.\" Generator: DocBook XSL Stylesheets vsnapshot <http://docbook.sf.net/>
.\"      Date: 09/18/2026
.\"    Manual: NVMe Manual
.\"    Source: NVMe
.\"  Language: English
.\"
.TH "NVME\-SOLIDIGM\-PARS" "1" "09/18/2026" "NVMe" "NVMe Manual"
.\" -----------------------------------------------------------------
.\" * Define some portability stuff
.\" -----------------------------------------------------------------
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.\" http://bugs.debian.org/507673
.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.ie \n(.g .ds Aq \(aq
.el       .ds Aq '
.\" -----------------------------------------------------------------
.\" * set default formatting
.\" -----------------------------------------------------------------
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.ad l
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
.SH "NAME"
nvme-solidigm-parse-telemetry-log \- Parse and display Solidigm Telemetry log
.SH "SYNOPSIS"
.sp
.nf
\fInvme\fR [<global\-options>] \fIsolidigm parse\-telemetry\-log\fR <device> [OPTIONS]
.fi
.SH "DESCRIPTION"
.sp
Retrieves, parses, and displays the Telemetry log for the given Solidigm NVMe device\&. This command provides detailed information about the device\(cqs telemetry data, which can be useful for diagnostics and performance analysis\&.
.sp
The <device> parameter is mandatory and may be either the NVMe character device (ex: /dev/nvme0), or a namespace block device (ex: /dev/nvme0n1)\&.
.SH "OPTIONS"
.PP
\-g <num>, \-\-host\-generate=<num>
.RS 4
Controls when to generate a new host\-initiated report\&. Default value
\fI1\fR
generates a new host\-initiated report, value
\fI0\fR
causes retrieval of an existing log\&. Valid values are 0 and 1\&.
.RE
.PP
\-c, \-\-controller\-init
.RS 4
Gather report generated by the controller\&.
.RE
.PP
\-d <num>, \-\-data\-area=<num>
.RS 4
Pick which telemetry data area to report\&. Default is 1, or 3 if a config file is specified\&. Valid options are 1, 2, 3, 4\&.
.RE
.PP
\-j <file>, \-\-config\-file=<file>
.RS 4
Specify a JSON configuration file for custom parsing of the telemetry log\&.
.RE
.PP
\-s <file>, \-\-source\-file=<file>
.RS 4
Specifies a binary file containing a telemetry log dump to parse instead of retrieving the log from a device\&. When this option is used, no device argument should be provided\&.
.RE
.SH "GLOBAL OPTIONS"
.sp
The following options are defined at the top\-level nvme command and are available to this subcommand:
.PP
\-\-dry\-run
.RS 4
Print the command that would be executed, but do not actually execute it\&.
.RE
.PP
\-\-no\-ioctl\-probing
.RS 4
Disable probing for 64\-bit IOCTL support\&.
.RE
.PP
\-\-no\-retries
.RS 4
Disable retry logic on transient errors\&.
.RE
.PP
\-o <fmt>, \-\-output\-format=<fmt>
.RS 4
Set the reporting format to
\fInormal\fR,
\fItabular, \*(Aqjson\fR, or
\fIbinary\fR\&. Only one output format may be used at a time\&.
.RE
.PP
\-\-output\-format\-version=<version>
.RS 4
Select the output format version\&. Version
\fI1\fR
uses the original field naming, while version
\fI2\fR
(default) provides more consistent and script\-friendly field names\&.
.RE
.PP
\-\-timeout=<ms>
.RS 4
Set the timeout for the command in milliseconds\&.
.RE
.PP
\-v, \-\-verbose
.RS 4
Increase the level of detail in the output\&. May be specified multiple times to further increase verbosity\&.
.RE
.sp
These options can also be set as machine\-wide defaults in nvme\-cli\&.conf(5)\&. A command\-line flag always overrides the file\&.
.SH "EXAMPLES"
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
Retrieve and parse the telemetry log with default options:
.sp
.if n \{\
.RS 4
.\}
.nf
# nvme solidigm parse\-telemetry\-log /dev/nvme0
.fi
.if n \{\
.RE
.\}
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
Retrieve an existing telemetry log without generating a new one:
.sp
.if n \{\
.RS 4
.\}
.nf
# nvme solidigm parse\-telemetry\-log /dev/nvme0 \-g 0
.fi
.if n \{\
.RE
.\}
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
Parse a specific data area of the telemetry log:
.sp
.if n \{\
.RS 4
.\}
.nf
# nvme solidigm parse\-telemetry\-log /dev/nvme0 \-d 2
.fi
.if n \{\
.RE
.\}
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
Use a custom configuration file for parsing:
.sp
.if n \{\
.RS 4
.\}
.nf
# nvme solidigm parse\-telemetry\-log /dev/nvme0 \-j config\&.json
.fi
.if n \{\
.RE
.\}
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
Parse a telemetry log from a binary file:
.sp
.if n \{\
.RS 4
.\}
.nf
# nvme solidigm parse\-telemetry\-log \-s telemetry_dump\&.bin
.fi
.if n \{\
.RE
.\}
.RE
.SH "OUTPUT"
.sp
The command outputs the parsed telemetry log in JSON format to stdout\&.
.SH "NVME"
.sp
Part of the nvme\-cli suite