On a customer cluster the customer use Zabbix for OS monitor rancher-users #longhorn-storage

Title

sparse-fireman-14239

01/10/2023, 10:33 AM

On a customer cluster, the customer use Zabbix for OS monitoring and to keep an eye on disk usage/perf on /var/lib/longhorn. That works well, the issue is that they receive response time alarms on longhorn volumes, but seeing as Lognhorn is using the Linux SCSI subsystem and get dynamically assigned sdX devices, I struggle to find a good way to differentiate between what are OS and Longhorn disks. Anyone else struggle with this, and have found a solution?

quick-sandwich-76600

01/10/2023, 2:43 PM

Instead of telling Zabbix to use the /dev/sdX alias for disks use the real id:

/dev/disk/by-id/

For example:

/dev/disk/by-id/scsi-14f504e46494c45006779706e4d772d746d36582d6869556e

That way you can easily filter scsi disk from other disks

You can also use

/dev/disk/by-path/

And there iscsi disks will be something like this

/dev/disk/by-path/ip-192.168.20.149:3260-iscsi-iqn.2006-01.com.openfiler:tsn.0a16ba8cb6c9-lun-0

In Zabbix you can add filters so use them and pick only those whose name contains "scsi" or "iscsi"

sparse-fireman-14239

01/10/2023, 2:56 PM

Thanks @quick-sandwich-76600 🙂 Unfortunately the Zabbix supplied template doesn't discover /dev/disk/* otherwise that'd work. Our local OS disks have device-mapper (dm-*) devices and the Longhorn iSCSI disks don't, so I think that may be the solution.

quick-sandwich-76600

01/10/2023, 3:31 PM

Yes, that's a good option.

14 Views

#longhorn-storage Join Slack