Project: Netdata (Observability and Analysis / Observability)
File: storecli_raid.md

<!--startmeta customediturl: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/storcli/README.md" meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/storcli/metadata.yaml" sidebar_label: "StoreCLI RAID" learn_status: "Published" learnrelpath: "Collecting Metrics/Storage, Mount Points and Filesystems" most_popular: False message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE COLLECTOR'S metadata.yaml FILE" endmeta--> <img src="https://netdata.cloud/img/hard-drive.svg" width="150"/> Plugin: go.d.plugin Module: storcli <img src="https://img.shields.io/badge/maintained%20by-Netdata-%2300ab44" /> Monitors the health of StoreCLI Hardware RAID by tracking the status of RAID adapters, physical drives, and backup batteries in your storage system. It relies on the CLI tool but avoids directly executing the binary. Instead, it utilizes `ndsudo`, a Netdata helper specifically designed to run privileged commands securely within the Netdata environment. This approach eliminates the need to use `sudo`, improving security and potentially simplifying permission management. Executed commands: `storcli /cALL show all J nolog` `storcli /cALL/eALL/sALL show all J nolog` This collector is supported on all platforms. This collector only supports collecting metrics from a single instance of this integration. This integration doesn't support auto-detection. The default configuration for this integration does not impose any limits on data collection. The default configuration for this integration is not expected to impose a significant performance impact on the system. Metrics grouped by scope. The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels. These metrics refer to the Controller. Labels: | Label | Description | |:--|:-| | controller_number | Controller number (index) | | model | Controller model | Metrics: | Metric | Dimensions | Unit | |:|:-|:-| | storcli.controllerstatus | optimal, degraded, partiallydegraded, failed | status | | storcli.controllerbbustatus | healthy, unhealthy, na | status | These metrics refer to the Physical Drive. Labels: | Label | Description | |:--|:-| | controller_number | Controller number (index) | | enclosure_number | Enclosure number (index) | | slot_number | Slot number (index) | | media type | Media type (e.g. HDD) | Metrics: | Metric | Dimensions | Unit | |:|:-|:-| |

| media, other | errors/s | | storcli.physdrivepredictivefailures | predictivefailures | failures/s | | storcli.physdrivesmartalertstatus | active, inactive | status | | storcli.physdrivetemperature | temperature | Celsius | These metrics refer to the Backup Battery Unit. Labels: | Label | Description | |:--|:-| | controller_number | Controller number (index) | | bbu_number | BBU number (index) | | model | BBU model | Metrics: | Metric | Dimensions | Unit | |:|:-|:-| | storcli.bbu_temperature | temperature | Celsius | The following alerts are available: | Alert name | On metric | Description | |:|:-|:| | | storcli.controllerstatus | RAID controller ${label:controllernumber} health status is not optimal | | | storcli.controllerbbustatus | RAID controller ${label:controller_number} BBU is unhealthy | | | storcli.physdriveerrors | RAID physical drive c${label:controllernumber}/e${label:enclosurenumber}/s${label:slot_number} errors | | | storcli.physdrivepredictivefailures | RAID physical drive c${label:controllernumber}/e${label:enclosurenumber}/s${label:slotnumber} predictive failures | No action required. The configuration file name for this integration is `go.d/storcli.conf`. You can edit the configuration file using the `edit-config` script from the Netdata . ```bash cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata sudo ./edit-config go.d/storcli.conf ``` The following options can be defined globally: update_every. <details><summary>Config options</summary> | Name | Description | Default | Required | |:-|:--|:-|:--:| | update_every | Data collection frequency. | 10 | no | | timeout | storcli binary execution timeout. | 2 | no | </details> Allows you to override the default data collection interval. <details><summary>Config</summary> ```yaml jobs: name: storcli update_every: 5 # Collect StorCLI RAID statistics every 5 seconds ``` </details> To troubleshoot issues with the `storcli` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. Navigate to the `plugins.d` directory, usually at `/usr/libexec/netdata/plugins.d/`. If that's not the case on your system, open `netdata.conf` and look for the `plugins` setting under `[directories]`. ```bash cd /usr/libexec/netdata/plugins.d/ ``` Switch to the `netdata` user. ```bash sudo -u netdata -s ``` Run the `go.d.plugin` to debug the collector: ```bash ./go.d.plugin -d -m storcli ```