Skip to main content

Adaptec RAID controller monitoring with Netdata

Collects logical and physical devices metrics using arcconf command-line utility.

Executed commands:

  • sudo -n arcconf GETCONFIG 1 LD
  • sudo -n arcconf GETCONFIG 1 PD

Requirements#

The module uses arcconf, which can only be executed by root. It uses sudo and assumes that it is configured such that the netdata user can execute arcconf as root without a password.

  • Add to your /etc/sudoers file:

which arcconf shows the full path to the binary.

netdata ALL=(root) NOPASSWD: /path/to/arcconf

The default CapabilityBoundingSet doesn't allow using sudo, and is quite strict in general. Resetting is not optimal, but a next-best solution given the inability to execute arcconf using sudo.

As the root user, do the following:

mkdir /etc/systemd/system/netdata.service.d
echo -e '[Service]\nCapabilityBoundingSet=~' | tee /etc/systemd/system/netdata.service.d/unset-capability-bounding-set.conf
systemctl daemon-reload
systemctl restart netdata.service

Charts#

  • Logical Device Status
  • Physical Device State
  • Physical Device S.M.A.R.T warnings
  • Physical Device Temperature

Enable the collector#

The adaptec_raid collector is disabled by default. To enable it, use edit-config from the Netdata config directory, which is typically at /etc/netdata, to edit the python.d.conf file.

cd /etc/netdata # Replace this path with your Netdata config directory, if different
sudo ./edit-config python.d.conf

Change the value of the adaptec_raid setting to yes. Save the file and restart the Netdata Agent with sudo systemctl restart netdata, or the appropriate method for your system.

Configuration#

Edit the python.d/adaptec_raid.conf configuration file using edit-config from the Netdata config directory, which is typically at /etc/netdata.

cd /etc/netdata # Replace this path with your Netdata config directory, if different
sudo ./edit-config python.d/adaptec_raid.conf

image


Reach out

If you need help after reading this doc, search our community forum for an answer. There's a good chance someone else has already found a solution to the same issue.

Documentation

Community

Last updated on