It is very similar to ZBXNEXT-6222

<mprihodko> ZBXNEXT-6222 was closed as a duplicate.

dimitri.bellini, Could you please describe a use case for this functionality? Do we need to expand the field in the action conditions or leave it as it is - 255 characters?

Hi Alexander,
thanks for the question!
I real use case is coming from one of our customer.
VMWare environment with 3k Vms using the latest VMWare integration on Zabbix 6.0 (and above) we can have a single Host that reppresent a VM with some Items coming from the VMWare monitoring and some other from the Zabbix Agent (better with Agent2) in Active mode (WMVare FQDN Template).
Now how we can link the right Application template to all VMs? If we can use a Processes Discovery or if we can use something like "system.sw.packages" or a dedicated wmi.get we can forward this information on hostmetadataitem and during the Auto-registration link the right Software/Application template (MySQL/Oracle/Apache/Etc..).
Maybe is not the "cleanest" solution to achieve this purpose but is what we can have for now with a small "change"
Best regards and thanks for your work

PS: Is something similar to the Zabbix 7.0 roadmap topic "Next-generation discovery of services and applications"

Then I see no reason to increase the size of the condition field in the auto-registration action. Most likely, the "contains" operator will be used here.

@alexander I do not know if there is no need to extend the "condition field" in auto-registration form, How much it is bigger now?

From Agent side there is a limit of 255 characters? If yes, could be useful to extend it

Thanks so much

The condition field is currently limited to 255 characters. I think this will be enough.

Available in

• 6.4.0alpha1 in 2e003ae7645

Updated documentation:

• What's new in 6.4
• Host metadata in autoregistration
• Agent configuration files: Zabbix agent, Zabbix agent 2, Windows Zabbix agent, Windows Zabbix agent 2 (HostMetadata and HostMetadataItem parameters)