LVM logical volumes

Plugin: go.d.plugin Module: lvm

Overview

This collector monitors the health of LVM logical volumes. It relies on the lvs 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.

This collector is only supported on the following platforms:

Linux
NetBSD

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/lvm.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/lvm.conf

Options

The following options can be defined globally: update_every.

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

Examples

Custom update_every

Allows you to override the default data collection interval.

jobs:
  - name: lvm
    update_every: 5  # Collect logical volume 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 volume

These metrics refer to the LVM logical volume.

Labels:

Label	Description
lv_name	Logical volume name
vg_name	Volume group name
volume_type	Type of the volume

Metrics:

Metric	Dimensions	Unit
lvm.lv_data_space_utilization	utilization	%
lvm.lv_metadata_space_utilization	utilization	%

Alerts

The following alerts are available:

Alert name	On metric	Description
lvm_lv_data_space_utilization	lvm.lv_data_space_utilization	LVM logical volume high data space usage (LV ${label:lv_name} VG ${label:vg_name} Type ${label:volume_type})
lvm_lv_metadata_space_utilization	lvm.lv_metadata_space_utilization	LVM logical volume high metadata space usage (LV ${label:lv_name} VG ${label:vg_name} Type ${label:volume_type})

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 lvm 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 lvm
```

Getting Logs

If you’re encountering problems with the lvm 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 lvm

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 lvm /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 lvm

Industry

Technology

Use cases