zabbix-server 7.2.5

No way to edit...
Expected: > Unexpected:
Expected to see correct fs metrics.

The second issue you described — collecting history for a non-existent disk — is a duplicate of ZBX-18703. We plan to fix it in one of the upcoming releases.

Regarding the first issue: are all of these discovered disks currently mounted, or are some of them no longer available on the monitored system?
If some of the disks are no longer present, then it’s likely the same underlying problem.

If all of these disks are indeed mounted and present in the system, please provide some additional information so we can investigate further:

• The exact name of the template you are using
• The version of the monitored operating system
• A screenshot showing the current disk sizes on the monitored system

Thank you in advance!

yes, are all of these discovered disks currently mounted
Vmware template used: https://raw.githubusercontent.com/zabbix/zabbix/refs/heads/release/7.2/templates/app/vmware/template_app_vmware.yaml

Guest vm has windows 2019 server installed

for the linux vm there is no such bug, but on request for metrics for absent mountpoint path i`ll get some metrics.

Here is an fs items from zabbix-agent from this host by windows template:

Hi catroot,

We will fix the issue soon (within couple of weeks).

Is there possibility for you to test our dev build with the fix ?

hi there)
With dockerized image i can try it.