Hello,
we run Zabbix Agent2 on multiple Ubuntu servers and use the "HostnameItem" parameter in the agent configuration (instead of "Hostname") so that a single configuration file can be applied to all machines. However, when attempting to use autoupgrade for the Zabbix Agent2, the upgrade process fails due to a configuration file prompt—the customized config file is blacklisted.
To work around this issue, I moved all my custom settings to a separate file at /etc/zabbix/zabbix_agent2.d/x.conf and restored the original agent configuration file. Unfortunately, because the original file still contains the "Hostname" parameter set to "Zabbix Server", the "HostnameItem" setting in my custom file is ignored.
It would be really helpful if this behavior could be addressed in a future release.
we run Zabbix Agent2 on multiple Ubuntu servers and use the "HostnameItem" parameter in the agent configuration (instead of "Hostname") so that a single configuration file can be applied to all machines. However, when attempting to use autoupgrade for the Zabbix Agent2, the upgrade process fails due to a configuration file prompt—the customized config file is blacklisted.
To work around this issue, I moved all my custom settings to a separate file at /etc/zabbix/zabbix_agent2.d/x.conf and restored the original agent configuration file. Unfortunately, because the original file still contains the "Hostname" parameter set to "Zabbix Server", the "HostnameItem" setting in my custom file is ignored.
It would be really helpful if this behavior could be addressed in a future release.
Comment