"use strict";(self.webpackChunkinfluxdb_ui=self.webpackChunkinfluxdb_ui||[]).push([[385],{86248:e=>{e.exports='# Read metrics from storage devices supporting S.M.A.R.T.\n[[inputs.smart]]\n    ## Optionally specify the path to the smartctl executable\n    # path_smartctl = "/usr/bin/smartctl"\n\n    ## Optionally specify the path to the nvme-cli executable\n    # path_nvme = "/usr/bin/nvme"\n\n    ## Optionally specify if vendor specific attributes should be propagated for NVMe disk case\n    ## ["auto-on"] - automatically find and enable additional vendor specific disk info\n    ## ["vendor1", "vendor2", ...] - e.g. "Intel" enable additional Intel specific disk info\n    # enable_extensions = ["auto-on"]\n\n    ## On most platforms used cli utilities requires root access.\n    ## Setting \'use_sudo\' to true will make use of sudo to run smartctl or nvme-cli.\n    ## Sudo must be configured to allow the telegraf user to run smartctl or nvme-cli\n    ## without a password.\n    # use_sudo = false\n\n    ## Skip checking disks in this power mode. Defaults to\n    ## "standby" to not wake up disks that have stopped rotating.\n    ## See --nocheck in the man pages for smartctl.\n    ## smartctl version 5.41 and 5.42 have faulty detection of\n    ## power mode and might require changing this value to\n    ## "never" depending on your disks.\n    # nocheck = "standby"\n\n    ## Gather all returned S.M.A.R.T. attribute metrics and the detailed\n    ## information from each drive into the \'smart_attribute\' measurement.\n    # attributes = false\n\n    ## Optionally specify devices to exclude from reporting if disks auto-discovery is performed.\n    # excludes = [ "/dev/pass6" ]\n\n    ## Optionally specify devices and device type, if unset\n    ## a scan (smartctl --scan and smartctl --scan -d nvme) for S.M.A.R.T. devices will be done\n    ## and all found will be included except for the excluded in excludes.\n    # devices = [ "/dev/ada0 -d atacam", "/dev/nvme0"]\n\n    ## Timeout for the cli command to complete.\n    # timeout = "30s"\n\n    ## Optionally call smartctl and nvme-cli with a specific concurrency policy.\n    ## By default, smartctl and nvme-cli are called in separate threads (goroutines) to gather disk attributes.\n    ## Some devices (e.g. disks in RAID arrays) may have access limitations that require sequential reading of\n    ## SMART data - one individual array drive at the time. In such case please set this configuration option\n    ## to "sequential" to get readings for all drives.\n    ## valid options: concurrent, sequential\n    # read_method = "concurrent"\n'}}]);