[ZBXNEXT-9058] Create VMware template for standalone ESXi hypervisor monitoring Created: 2024 Mar 01  Updated: 2024 Oct 29  Resolved: 2024 Oct 29

Status: Closed
Project: ZABBIX FEATURE REQUESTS
Component/s: None
Affects Version/s: None
Fix Version/s: 6.0.36rc1, 7.0.6rc1, 7.2.0beta1

Type: New Feature Request Priority: Minor
Reporter: Tomass Janis Bross Assignee: Aleksandr Kotsegubov
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File VMware_Edit_7.0_Oct 2024.md    
Issue Links:
Duplicate
Team: Team INT
Story Points: 0.3

 Description   

At the moment we have a VMware template, which is already able to monitor standalone ESXi hypervisors, however, when using this template Zabbix essentially has to create two hosts, one where you attach the template which also will discover the hypervisor with the "Discover VMware hypervisors" discovery rule, you will end up with two hosts.
As highlighted by one of our customers, this can create issues with their ServiceNow integration, as they have to have two different hosts on the Zabbix GUI, and ServiceNow can only take one of them as a valid host with the correct hostname.

Attaching the "VMware hypervisors" template directly (which is a part of the VMware template as a whole), also does not work, as then there is a missing LLD macro that doesn't allow the template to function properly.



 Comments   
Comment by Aleksandr Kotsegubov [ 2024 Oct 24 ]

Available in:

Comment by Marianna Zvaigzne [ 2024 Oct 25 ]

Documentation updated:

  • What's new in Zabbix (6.0.36)
  • Template changes (6.0, 7.0)
  • Virtual machine monitoring (6.0) and VMware template operation (7.0, 7.2)
Generated at Sat Apr 19 03:56:32 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.