You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During discovery of vSphere objects Zabbix creates 'Zabbix hosts' using a host profile.
While that is powerful feature of Zabbix the resulting Zabbix hosts have read-only attributes, thus modifying/updating a discovered host is not possible with host profiles.
Simple things such as adding a host to another group is not possible and the only way to do this is at the host profile, which is kinda limited and not very flexible.
This seems to be an issue of Zabbix by design, which creates any discovered objects as read-only.
Using vPoller with the Zabbix API we should be able to create any discovered vSphere object as a regular Zabbix host, thus being able to modify/update a discovered host in Zabbix.
This ticket is to track the progress of creating a tool which would allow creation of vSphere objects as regular Zabbix hosts in order to provide more flexibility and easier management of the hosts in Zabbix.
The text was updated successfully, but these errors were encountered:
During discovery of vSphere objects Zabbix creates 'Zabbix hosts' using a host profile.
While that is powerful feature of Zabbix the resulting Zabbix hosts have read-only attributes, thus modifying/updating a discovered host is not possible with host profiles.
Simple things such as adding a host to another group is not possible and the only way to do this is at the host profile, which is kinda limited and not very flexible.
This seems to be an issue of Zabbix by design, which creates any discovered objects as read-only.
Using vPoller with the Zabbix API we should be able to create any discovered vSphere object as a regular Zabbix host, thus being able to modify/update a discovered host in Zabbix.
This ticket is to track the progress of creating a tool which would allow creation of vSphere objects as regular Zabbix hosts in order to provide more flexibility and easier management of the hosts in Zabbix.
The text was updated successfully, but these errors were encountered: