Thank you for your reply.
I dont think thats correct.
Also I ran a stand alone so its all in one. The Kibana interface is showing 64Gigs is used up.?
My concern is which one the correct one. Ive already ran into an issue where everything went into read only because of space.
[root@waz01 ~]# df -P
Filesystem 1024-blocks Used Available Capacity Mounted on
/dev/mapper/vg_local-root 5109760 111068 4998692 3% /
devtmpfs 3992644 0 3992644 0% /dev
tmpfs 4004620 0 4004620 0% /dev/shm
tmpfs 4004620 385984 3618636 10% /run
tmpfs 4004620 0 4004620 0% /sys/fs/cgroup
/dev/mapper/vg_local-usr 10475520 2774028 7701492 27% /usr
/dev/sda1 1020588 190020 830568 19% /boot
/dev/mapper/vg_local-home 10229760 36144 10193616 1% /home
/dev/mapper/vg_local-var 104601600 59860240 44741360 58% /var
/dev/mapper/vg_local-var_log 10475520 3823568 6651952 37% /var/log
/dev/mapper/vg_local-tmp 2037760 33832 2003928 2% /tmp
/dev/mapper/wazuh-ossec 104806400 24652044 80154356 24% /var/ossec
tmpfs 800924 0 800924 0% /run/user/297800546
[root@waz01 ~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/vg_local-root 4.9G 109M 4.8G 3% /
devtmpfs 3.9G 0 3.9G 0% /dev
tmpfs 3.9G 0 3.9G 0% /dev/shm
tmpfs 3.9G 377M 3.5G 10% /run
tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup
/dev/mapper/vg_local-usr 10G 2.7G 7.4G 27% /usr
/dev/sda1 997M 186M 812M 19% /boot
/dev/mapper/vg_local-home 9.8G 36M 9.8G 1% /home
/dev/mapper/vg_local-var 100G 58G 43G 58% /var
/dev/mapper/vg_local-var_log 10G 3.7G 6.4G 37% /var/log
/dev/mapper/vg_local-tmp 2.0G 34M 2.0G 2% /tmp
/dev/mapper/wazuh-ossec 100G 24G 77G 24% /var/ossec
tmpfs 783M 0 783M 0% /run/user/297800546