CheckMK does not show all LVM pools reported by the agent

Hi all,

I’m new in the CheckMK community as I’m changing the monitoring in my homelab from Zabbix (which I’ve used for the last 5 years) to CheckMK. After I’ve had an initial look at CheckMK I find it much more easy to use for me :wink:

After reading and learning a lot in the last days, I’m struggling with the LVM monitoring of my Proxmox hosts.

I’ve installed the LVM plugin to the agent of my Proxmox hosts and the plugin returns correct data:

root@pmx1:~# /usr/lib/check_mk_agent/plugins/lvm.txt
<<<lvm_vgs>>>
  local-lvm1    1       21      0       wz--n-  9000099774464   394264576
  local-lvm2    1       19      0       wz--n-  9000099774464   394264576
  local-lvm3    1       5       0       wz--n-  12000671301632  394264576
  pve   1       3       0       wz--n-  998575702016    17184063488
<<<lvm_lvs:sep(124)>>>
  local-lvm1|local-lvm1|twi-aotz--|8965605818368|||40.85|5.80||||
  vm-114-disk-0|local-lvm1|Vwi-aotz--|3298534883328|local-lvm1||2.22|||||
  vm-115-disk-0|local-lvm1|Vwi-aotz--|805306368000|local-lvm1||6.49|||||
  vm-116-disk-0|local-lvm1|Vwi-aotz--|268435456000|local-lvm1||5.51|||||
  vm-117-disk-0|local-lvm1|Vwi-aotz--|536870912000|local-lvm1||5.28|||||
  local-lvm2|local-lvm2|twi-aotz--|8965605818368|||22.75|3.49||||
  local-lvm3|local-lvm3|twi-aotz--|11966177345536|||30.00|8.16||||
  data|pve|twi-aotz--|852332904448|||0.00|0.24||||
  root|pve|-wi-ao----|103079215104||||||||
  swap|pve|-wi-ao----|8589934592||||||||

On this host the Proxmox lvm-thin storages which I want to monitor are:

  • data/pve (This is what Proxmox creates by default on /dev/sda, named “local-lvm” in Proxmox
  • local-lvm1 (Additional datastore)
  • local-lvm2 (Additional datastore)
  • local-lvm3 (Additional datastore)

But when I run the discovery in CheckMK, I’m getting only three LVM pools:

The output from the agent lists 10 pools, why do I only get 3 in CheckMK? Especially I absolutely need the “data/pve” pool as this is a used LVM pool which I need to monitor.

Any idea is highly appreciated.

After digging around I found the answer to my question: A LVM group is only discovered if there are any objects in there (in this case: virtual machine disks).

At the host in my example there are no VMs in /data/pve (this is a decicated boot drive), hence the LVM is not discovered.

That’s absolutely fine. :slightly_smiling_face:

2 Likes

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact an admin if you think this should be re-opened.