Adaptec RAID
Adaptec RAID
Plugin: go.d.plugin Module: adaptec_raid
Overview
Monitors the health of Adaptec Hardware RAID by tracking the status of logical and physical devices in your storage system.
It relies on the arcconf 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:
arcconf GETCONFIG 1 LDarcconf GETCONFIG 1 PD
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.
Setup
Prerequisites
No action required.
Configuration
File
The configuration file name for this integration is go.d/adaptec_raid.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/adaptec_raid.conf
Options
The following options can be defined globally: update_every.
| Name | Description | Default | Required |
|---|---|---|---|
| update_every | Data collection frequency. | 10 | no |
| timeout | arcconf binary execution timeout. | 2 | no |
Examples
Custom update_every
Allows you to override the default data collection interval.
jobs:
- name: adaptec_raid
update_every: 5 # Collect Adaptec Hardware RAID 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 logical device
These metrics refer to the Logical Device (LD).
Labels:
| Label | Description |
|---|---|
| ld_number | Logical device index number |
| ld_name | Logical device name |
| raid_level | RAID level |
Metrics:
| Metric | Dimensions | Unit |
|---|---|---|
| adaptecraid.logical_device_status | ok, critical | status |
Per physical device
These metrics refer to the Physical Device (PD).
Labels:
| Label | Description |
|---|---|
| pd_number | Physical device index number |
| location | Physical device location (e.g. Connector 0, Device 1) |
| vendor | Physical device vendor |
| model | Physical device model |
Metrics:
| Metric | Dimensions | Unit |
|---|---|---|
| adaptecraid.physical_device_state | ok, critical | status |
| adaptecraid.physical_device_smart_warnings | smart | warnings |
| adaptecraid.physical_device_temperature | temperature | Celsius |
Alerts
The following alerts are available:
| Alert name | On metric | Description |
|---|---|---|
| adaptec_raid_ld_health_status | adaptecraid.logical_device_status | Adaptec RAID logical device (number ${label:ld_number} name ${label:ld_name}) health status is critical |
| adaptec_raid_pd_health_state | adaptecraid.physical_device_state | Adaptec RAID physical device (number ${label:pd_number} location ${label:location}) health state is critical |
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 adaptec_raid 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 adaptec_raid
Getting Logs
If you’re encountering problems with the adaptec_raid 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 adaptec_raid
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 adaptec_raid /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 adaptec_raid