StoreCLI RAID

Plugin: go.d.plugin Module: storcli

Overview

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 storcli 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 only supported on the following platforms:

• Linux
• BSD

This collector only supports collecting metrics from a single instance of this integration.

Default Behavior

Auto-Detection

This integration doesn't support auto-detection.

Limits

The default configuration for this integration does not impose any limits on data collection.

Performance Impact

The default configuration for this integration is not expected to impose a significant performance impact on the system.

Metrics

Metrics grouped by scope.

The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.

Per controller

These metrics refer to the Controller.

Labels:

Label	Description
controller_number	Controller number (index)
model	Controller model
driver_name	Controller driver (megaraid_sas or mpt3sas)

Metrics:

Metric	Dimensions	Unit
storcli.controller_health_status	healthy, unhealthy	status
storcli.controller_status	optimal, degraded, partially_degraded, failed	status
storcli.controller_bbu_status	healthy, unhealthy, na	status
storcli.controller_roc_temperature	temperature	Celsius

Per physical drive

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
storcli.phys_drive_errors	media, other	errors/s
storcli.phys_drive_predictive_failures	predictive_failures	failures/s
storcli.phys_drive_smart_alert_status	active, inactive	status
storcli.phys_drive_temperature	temperature	Celsius

Per bbu

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

Alerts

The following alerts are available:

Alert name	On metric	Description
storcli_controller_health_status	storcli.controller_health_status	RAID controller ${label:controller_number} is unhealthy
storcli_controller_bbu_status	storcli.controller_bbu_status	RAID controller ${label:controller_number} BBU is unhealthy
storcli_phys_drive_errors	storcli.phys_drive_errors	RAID physical drive c${label:controller_number}/e${label:enclosure_number}/s${label:slot_number} errors
storcli_phys_drive_predictive_failures	storcli.phys_drive_predictive_failures	RAID physical drive c${label:controller_number}/e${label:enclosure_number}/s${label:slot_number} predictive failures

Setup

Prerequisites

No action required.

Configuration

File

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 config directory.

cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
sudo ./edit-config go.d/storcli.conf

Options

The following options can be defined globally: update_every.

Config options

Name	Description	Default	Required
update_every	Data collection frequency.	10	no
timeout	storcli binary execution timeout.	2	no

Examples

Custom update_every

Allows you to override the default data collection interval.

Config

jobs:
  - name: storcli
    update_every: 5  # Collect StorCLI RAID statistics every 5 seconds

Troubleshooting

Debug Mode

Important: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature.

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

  cd /usr/libexec/netdata/plugins.d/

• Switch to the netdata user.

  sudo -u netdata -s

• Run the go.d.plugin to debug the collector:

  ./go.d.plugin -d -m storcli

Getting Logs

If you're encountering problems with the storcli collector, follow these steps to retrieve logs and identify potential issues:

• Run the command specific to your system (systemd, non-systemd, or Docker container).
• Examine the output for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem.

System with systemd

Use the following command to view logs generated since the last Netdata service restart:

journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep storcli

System without systemd

Locate the collector log file, typically at /var/log/netdata/collector.log, and use grep to filter for collector's name:

grep storcli /var/log/netdata/collector.log

Note: This method shows logs from all restarts. Focus on the latest entries for troubleshooting current issues.

Docker Container

If your Netdata runs in a Docker container named "netdata" (replace if different), use this command:

docker logs netdata 2>&1 | grep storcli