Zabbix not discovering /data volume

[Turil]

Hi there!

I'm new to Zabbix and set up a CentOS 7 VM with Zabbix 3.0 monitoring itself to test and learn.
Before installing Zabbix I created a LVM volume and mounted it to /data - This volume gets successfully mounted on boot and I can read/write to it, but it is not visible in Zabbix. What am I missing? The items for monitoring /boot, / and swap are there and have the red "mounted file system discovery" tag in front of them.
Even installing docker gets auto-discovered but not the /data drive.

Thank you for your help!

[kloczek]

So what on this host shows command

# sudo -u zabbix /usr/sbin/zabbix_agentd -t vfs.fs.discovery

?

[Turil]

The output is as follows:

vfs.fs.discovery                              [s|{"data":[{"{#FSNAME}":"/","{#FSTYPE}":"rootfs"},{"{#FSNAME}":"/sys","{#FSTYPE}":"sysfs"},{"{#FSNAME}":"/proc","{#FSTYPE}":"proc"},{"{#FSNAME}":"/dev","{#FSTYPE}":"devtmpfs"},{"{#FSNAME}":"/sys/kernel/security","{#FSTYPE}":"securityfs"},{"{#FSNAME}":"/dev/shm","{#FSTYPE}":"tmpfs"},{"{#FSNAME}":"/dev/pts","{#FSTYPE}":"devpts"},{"{#FSNAME}":"/run","{#FSTYPE}":"tmpfs"},{"{#FSNAME}":"/sys/fs/cgroup","{#FSTYPE}":"tmpfs"},{"{#FSNAME}":"/sys/fs/cgroup/systemd","{#FSTYPE}":"cgroup"},{"{#FSNAME}":"/sys/fs/pstore","{#FSTYPE}":"pstore"},{"{#FSNAME}":"/sys/fs/cgroup/net_cls,net_prio","{#FSTYPE}":"cgroup"},{"{#FSNAME}":"/sys/fs/cgroup/devices","{#FSTYPE}":"cgroup"},{"{#FSNAME}":"/sys/fs/cgroup/memory","{#FSTYPE}":"cgroup"},{"{#FSNAME}":"/sys/fs/cgroup/hugetlb","{#FSTYPE}":"cgroup"},{"{#FSNAME}":"/sys/fs/cgroup/perf_event","{#FSTYPE}":"cgroup"},{"{#FSNAME}":"/sys/fs/cgroup/cpu,cpuacct","{#FSTYPE}":"cgroup"},{"{#FSNAME}":"/sys/fs/cgroup/pids","{#FSTYPE}":"cgroup"},{"{#FSNAME}":"/sys/fs/cgroup/blkio","{#FSTYPE}":"cgroup"},{"{#FSNAME}":"/sys/fs/cgroup/cpuset","{#FSTYPE}":"cgroup"},{"{#FSNAME}":"/sys/fs/cgroup/freezer","{#FSTYPE}":"cgroup"},{"{#FSNAME}":"/sys/kernel/config","{#FSTYPE}":"configfs"},{"{#FSNAME}":"/","{#FSTYPE}":"xfs"},{"{#FSNAME}":"/proc/sys/fs/binfmt_misc","{#FSTYPE}":"autofs"},{"{#FSNAME}":"/dev/mqueue","{#FSTYPE}":"mqueue"},{"{#FSNAME}":"/dev/hugepages","{#FSTYPE}":"hugetlbfs"},{"{#FSNAME}":"/sys/kernel/debug","{#FSTYPE}":"debugfs"},{"{#FSNAME}":"/boot","{#FSTYPE}":"xfs"},{"{#FSNAME}":"/data","{#FSTYPE}":"xfs"},{"{#FSNAME}":"/var/lib/docker/overlay2/0c152ace75f15afdc0e35256b8f28e319898231c79e40f0b17f90ccd50879acc/merged","{#FSTYPE}":"overlay"},{"{#FSNAME}":"/var/lib/docker/overlay2/d55f7f84ab5952de7a69468a542ecd078cb1139d3ff6d4b39614cc3e99732a91/merged","{#FSTYPE}":"overlay"},{"{#FSNAME}":"/var/lib/docker/overlay2/aaf29b86a84f18cb0ec125cfb54f2bfff6dcc5bfbbb32bf01f00fd440ff75614/merged","{#FSTYPE}":"overlay"},{"{#FSNAME}":"/var/lib/docker/containers/ab7ea565791ae0ced9fad1db0d88d33c7dc84ba59ff674bd27f8cbe489010f65/mounts/shm","{#FSTYPE}":"tmpfs"},{"{#FSNAME}":"/var/lib/docker/containers/bdc6b89f658f8c457eceb21322f7c0d4ca89eb80bf233f9e5569c967659a2871/mounts/shm","{#FSTYPE}":"tmpfs"},{"{#FSNAME}":"/var/lib/docker/containers/2b9b3552365b662a283eb7d26e38c0fb528c6f8f9f1f3d51860dc4cd06023a62/mounts/shm","{#FSTYPE}":"tmpfs"},{"{#FSNAME}":"/run/docker/netns/2b4437669e4a","{#FSTYPE}":"proc"},{"{#FSNAME}":"/run/docker/netns/fc24ef0ddc34","{#FSTYPE}":"proc"},{"{#FSNAME}":"/run/docker/netns/a9dd79368e18","{#FSTYPE}":"proc"},{"{#FSNAME}":"/run/user/1000","{#FSTYPE}":"tmpfs"},{"{#FSNAME}":"/run/user/0","{#FSTYPE}":"tmpfs"}]}]

I don't know why / how, but after a restart and some waiting / not working with the VM the /data volume was discovered. Case closed I guess Although I would like to understand what was the issue.