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

<!--startmeta customediturl: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/megacli/README.md" meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/megacli/metadata.yaml" sidebar_label: "MegaCLI MegaRAID" 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: megacli <img src="https://img.shields.io/badge/maintained%20by-Netdata-%2300ab44" /> Monitors the health of MegaCLI Hardware RAID by tracking the status of RAID adapters, physical drives, and backup batteries in your storage system. It relies on the `megacli` 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: `megacli -LDPDInfo -aAll -NoLog` `megacli -AdpBbuCmd -aAll -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 MegaCLI Adapter. Labels: | Label | Description | |:--|:-| | adapter_number | Adapter number | Metrics: | Metric | Dimensions | Unit | |:|:-|:-| | megacli.adapterhealthstate | optimal, degraded, partially_degraded, failed | state | These metrics refer to the MegaCLI Physical Drive. Labels: | Label | Description | |:--|:-| | adapter_number | Adapter number | | wwn | World Wide Name | | slot_number | Slot number | | drive_position | Position (e.g. DiskGroup: 0, Span: 0, Arm: 2) | | drive_type | Type (e.g. SATA) | Metrics: | Metric | Dimensions | Unit | |:|:-|:-| | megacli.physdrivemediaerrorsrate | media_errors | errors/s | | megacli.physdrivepredictivefailuresrate | predictive_failures | failures/s | These metrics refer to the MegaCLI Backup Battery

Labels: | Label | Description | |:--|:-| | adapter_number | Adapter number | | battery_type | Battery type (e.g. BBU) | Metrics: | Metric | Dimensions | Unit | |:|:-|:-| | megacli.bburelativecharge | charge | percentage | | megacli.bburechargecycles | recharge | cycles | | megacli.bbu_temperature | temperature | Celsius | The following alerts are available: | Alert name | On metric | Description | |:|:-|:| | | megacli.adapterhealthstate | MegaCLI adapter ${label:adapter_number} is in the degraded state | | | megacli.physdrivemediaerrors | MegaCLI physical drive adapter ${label:adapternumber} slot ${label:slot_number} media errors | | | megacli.physdrivepredictivefailures | MegaCLI physical drive (adapter ${label:adapternumber} slot ${label:slot_number}) predictive failures | | | megacli.bbucharge | MegaCLI Backup Battery Unit (adapter ${label:adapternumber}) average charge over the last minute | | | megacli.bburechargecycles | MegaCLI Backup Battery Unit (adapter ${label:adapter_number}) average charge over the last minute | No action required. The configuration file name for this integration is `go.d/megacli.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/megacli.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 | megacli binary execution timeout. | 2 | no | </details> Allows you to override the default data collection interval. <details><summary>Config</summary> ```yaml jobs: name: megacli update_every: 5 # Collect MegaCli Hardware RAID statistics every 5 seconds ``` </details> To troubleshoot issues with the `megacli` 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 megacli ```