[ZBX-26514] vmware.vm.snapshot.get - 1st snapshot size is vm size, not snapshot size Created: 2025 Jun 02  Updated: 2025 Jun 04  Resolved: 2025 Jun 04

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Templates (T)
Affects Version/s: 7.0.12
Fix Version/s: None

Type: Problem report Priority: Trivial
Reporter: Rob Quinn Assignee: Michael Veksler
Resolution: Won't fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: 5h
Original Estimate: Not Specified
Environment:

Zabbix 7.0.12, Ubuntu 24.04, VMware EXSi 7.0.3

Attachments: PNG File image-2025-06-02-13-09-32-301.png     PNG File image-2025-06-02-13-17-58-664.png     PNG File image-2025-06-02-13-18-32-713.png     PNG File image-2025-06-02-13-19-08-646.png     PNG File image-2025-06-02-13-20-15-403.png     PNG File image-2025-06-04-13-21-02-356.png     PNG File image-2025-06-04-13-21-55-619.png     PNG File image-2025-06-04-13-22-10-621.png     PNG File image-2025-06-04-13-22-26-861.png     PNG File image-2025-06-04-13-22-38-358.png    

 Description   

Steps to reproduce:

  1. Create a new template to using discovery to monitor snapshots on a ESXi host. Use vmware.vm.discovery to discover the host's VMs and use vmware.vm.snapshot.get to create an item prototype to get the snapshot data for each of those VMs. 
  2. Use this template to discover snapshots on an ESXi 7.0.3 host that has at least 1 VM with multiple snapshots. 
  3. Examine the data from the snapshot item and observe that the first snapshot size is actually the size of the VM, create time is correct.  The second snapshot size is actually the size of the first snapshot, again create time is correct for the second snapshot. Third snapshot is actually the size of the second snapshot,. The last snapshot size is not show by the item. 
  4.  

Result:

From Zabbix snapshot Item:

**

First snapshot is ~20G

Second snapshot is ~865M

Third snapshot is ~540M

From ESXi:
First snapshot:

Second snapshot:

Third snapshot:

vmdk of the server showing that it is 20G:

:

Expected:
Expecting that the first snapshot size would be ~860M, 2nd snapshot ~535M, and the 3rd snapshot would be ~6.46G.

 Comments   
Comment by Michael Veksler [ 2025 Jun 04 ]

It is not correct to do such type of direct comparison. (mapping of vmdk file name to snapshots)

For example:

{
  "snapshot": [
    {
      "name": "(first )VM Snapshot 6%2f3%2f2025, 5:10:25 PM",
      "description": "ZBX-26514",
      "createtime": "2025-06-03T14:11:01.245594Z",
      "size": 14222246248,
      "uniquesize": 14222246248
    },
    {
      "name": "(second) VM Snapshot 6%2f3%2f2025, 6:17:01 PM",
      "description": "+0.5GB",
      "createtime": "2025-06-03T15:17:27.75019Z",
      "size": 7114693519,
      "uniquesize": 7114693519
    },
    {
      "name": "(thriday)VM Snapshot 6%2f3%2f2025, 6:19:36 PM",
      "description": "+1Gb",
      "createtime": "2025-06-03T15:20:33.623588Z",
      "size": 3893461520,
      "uniquesize": 3893461520
    },
    {
      "name": "(fourth) VM Snapshot 6%2f3%2f2025, 6:23:15 PM",
      "description": "+1.5Gb",
      "createtime": "2025-06-03T15:23:43.893633Z",
      "size": 5067873174,
      "uniquesize": 5067873174
    }
  ],
  "count": 4,
  "latestdate": "2025-06-03T15:23:43.893633Z",
  "latestage": 61365,
  "oldestdate": "2025-06-03T14:11:01.245594Z",
  "oldestage": 65727,
  "size": 30298274461,
  "uniquesize": 30298274461
}

where I have the following vmdks:

which is mapping to following snapshots:

and we see that json is fully consistent with vc snapshots representation

Comment by Michael Veksler [ 2025 Jun 04 ]

The latest vmdk has become the current storage and will grow
That is why vmware does not recommend overusing snapshots.

Comment by Michael Veksler [ 2025 Jun 04 ]

Closing this for now, if you have any more questions, feel free to reopen this ticket!

Generated at Sat Jan 31 07:06:47 EET 2026 using Jira 10.3.13#10030013-sha1:56dd970ae30ebfeda3a697d25be1f6388b68a422.