HPE Smart Arrays
HPE Smart Arrays
Plugin: go.d.plugin Module: hpssa
Overview
Monitors the health of HPE Smart Arrays by tracking the status of controllers, arrays, logical and physical drives in your storage system.
It relies on the ssacli 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:
ssacli ctrl all show config detail
This collector is supported on all platforms.
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.
Setup
You can configure the hpssa collector in two ways:
| Method | Best for | How to |
|---|---|---|
| UI | Fast setup without editing files | Go to Nodes → Configure this node → Collectors → Jobs, search for hpssa, then click + to add a job. |
| File | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit go.d/ssacli.conf and add a job. |
:::important
UI configuration requires paid Netdata Cloud plan.
:::
Prerequisites
Install ssacli
See official installation instructions.
Configuration
Options
The following options can be defined globally: update_every.
| Option | Description | Default | Required |
|---|---|---|---|
| update_every | Data collection frequency. | 10 | no |
| timeout | ssacli binary execution timeout. | 2 | no |
via UI
Configure the hpssa collector from the Netdata web interface:
- Go to Nodes.
- Select the node where you want the hpssa data-collection job to run and click the :gear: (Configure this node). That node will run the data collection.
- The Collectors → Jobs view opens by default.
- In the Search box, type hpssa (or scroll the list) to locate the hpssa collector.
- Click the + next to the hpssa collector to add a new job.
- Fill in the job fields, then click Test to verify the configuration and Submit to save.
- Test runs the job with the provided settings and shows whether data can be collected.
- If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
via File
The configuration file name for this integration is go.d/ssacli.conf.
The file format is YAML. Generally, the structure is:
update_every: 1
autodetection_retry: 0
jobs:
- name: some_name1
- name: some_name2
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/ssacli.conf
Examples
Custom update_every
Allows you to override the default data collection interval.
jobs:
- name: hpssa
update_every: 5 # Collect HPE Smart Array statistics every 5 seconds
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 |
|---|---|
| slot | Slot number |
| model | Controller model |
Metrics:
| Metric | Dimensions | Unit |
|---|---|---|
| hpssa.controller_status | ok, nok | status |
| hpssa.controller_temperature | temperature | Celsius |
| hpssa.controller_cache_module_presence_status | present, not_present | status |
| hpssa.controller_cache_module_status | ok, nok | status |
| hpssa.controller_cache_module_temperature | temperature | Celsius |
| hpssa.controller_cache_module_battery_status | ok, nok | status |
Per array
These metrics refer to the Array.
Labels:
| Label | Description |
|---|---|
| slot | Slot number |
| array_id | Array id |
| interface_type | Array interface type (e.g. SATA) |
| array_type | Array type (e.g. Data) |
Metrics:
| Metric | Dimensions | Unit |
|---|---|---|
| hpssa.array_status | ok, nok | status |
Per logical drive
These metrics refer to the Logical Drive.
Labels:
| Label | Description |
|---|---|
| slot | Slot number |
| array_id | Array id |
| logical_drive_id | Logical Drive id (number) |
| disk_name | Disk name (e.g. /dev/sda) |
| drive_type | Drive type (e.g. Data) |
Metrics:
| Metric | Dimensions | Unit |
|---|---|---|
| hpssa.logical_drive_status | ok, nok | status |
Per physical drive
These metrics refer to the Physical Drive.
Labels:
| Label | Description |
|---|---|
| slot | Slot number |
| array_id | Array id or “na” if unassigned |
| logical_drive_id | Logical Drive id or “na” if unassigned |
| location | Drive location in port:box:bay format (e.g. 1I:1:1) |
| interface_type | Drive interface type (e.g. SATA) |
| drive_type | Drive type (e.g. Data Drive, Unassigned Drive) |
| model | Drive model |
Metrics:
| Metric | Dimensions | Unit |
|---|---|---|
| hpssa.physical_drive_status | ok, nok | status |
| hpssa.physical_drive_temperature | temperature | status |
Alerts
There are no alerts configured by default for this integration.
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 hpssa 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.ddirectory, usually at/usr/libexec/netdata/plugins.d/. If that’s not the case on your system, opennetdata.confand look for thepluginssetting under[directories].cd /usr/libexec/netdata/plugins.d/ -
Switch to the
netdatauser.sudo -u netdata -s -
Run the
go.d.pluginto debug the collector:./go.d.plugin -d -m hpssaTo debug a specific job:
./go.d.plugin -d -m hpssa -j jobName
Getting Logs
If you’re encountering problems with the hpssa 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 hpssa
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 hpssa /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 hpssa