Flexible multiple hostnames on same ZabbixAgent2

[ivanco]

Hi Community,

I have tens of IoT devices publishing data to one MQTT broker. Devices are different by model, payload data, trigger thresholds... so they need to be created as hosts in Zabbix.
For now I can see only two options to provide data transition to hosts items:

1. Use of external converter that catches MQTT messages and sends data with zabbix_sender to specific host trapper items. The problem is that this option is not simple to make and maintain.
2. Use of mqtt.get with zabbix_agent2. The problem is every host name have to be pointed on 'Hostname' parameter in zabbix_agent2.conf. More devices, more comma separated values. Restart agent on any addition/deletion of device. So this option is non-scalable.

Actually, I use option 1.
But if there will be any scalable way to realise multiple Zabbix Agent hostnames (for example, with pattern in conf) on one Zabbix Agent I'll defenetely prefer to move to simple option 2.

[ivanco]

And by the way, after I added second hostname to zabbix_agent2.conf, Zabbix server stops receiving data on mqtt.get of the first hostname.
Removing second hostname from config resolves this issue.
But the possible cause of this is that in my configuration both zabbix hosts have to get data from the same MQTT-path:

1. model/+/device/+/packet - just to get all MQTT stats
2. model/+/device/21309810238/packet - data processing for the particular device

[CallanHector]

How critical is the simplicity and ease of maintenance when choosing between these options? Are you looking for a solution that can be easily managed by non-technical personnel?