Loading...

XML

Word

Printable

Type: Change Request
Resolution: Fixed
Priority: Major
Fix Version/s: None
Affects Version/s: 2.2.1
Component/s: Frontend (F), Server (S)
Labels:
- interfaces
- lld
- usability
- vmware

As it stands right now, it seems that I would have to have two copies of almost every "host" in my environment as there would be one for the discovered VMware virtual machine and another one for the data pulled by the installed agent. I have marked this as major because training users that the host they are looking for may be listed twice will be a major issue. Additionally, naming of the agent-containing host will be difficult since there can only be one of each visible name.

There is a forum thread about this at https://www.zabbix.com/forum/showthread.php?t=43531

causes

ZBXNEXT-6269 Set IP to vmware HV and VM

Closed

ZBXNEXT-6272 Create template "VMWare FQDN"

Closed

is duplicated by

ZBXNEXT-1990 ability to edit host interface for LLD'd host

Closed

ZBXNEXT-2183 Ability to edit host created by LLD

Closed

ZBXNEXT-2876 Impossible to use Zabbix Agent Active with VMware discovered guest

Closed

ZBXNEXT-2950 Add VM.UUID as Macro for VMware Monitoring other then host

Closed

ZBXNEXT-2965 Addition of multiple templates to vmware discovered hosts

Closed

ZBX-11604 Fetching Host IP and directly getting fields from host

Closed

mentioned in: Page Loading...

(3 is duplicated by, 1 mentioned in)

Assignee:: Unassigned

Reporter:: Gene Liverman

Votes:: 103 Vote for this issue

Watchers:: 70 Start watching this issue

Created:: 2013 Dec 24 04:48

Updated:: 2022 Sep 13 18:58

Resolved:: 2022 Jul 08 18:11

Details

Description

Attachments

Issue Links

Activity

People

Dates