I have described the issue in detail here: https://support.zabbix.com/browse/ZBXNEXT-8232
To summarize. Currently there are Zabbix agent(passive) and Zabbix agent(active) item types. Can there be a Zabbix agent(auto) type?
Why? So we will not need same but different templates line "Linux by Zabbix agent" and "Linux by Zabbix agent active". There can be a single "Linux by zabbix agent" template which can work with agent passive or agent active by flip of a setting.
Yes, there are a few exception items which can only work in active mode for example. But those seem to be the edge cases.
There are so many official templates which does not have an "active" counterpart. With the invention of UUIDs it is hard to convert existing passive templates to active ones and maintain in the same system anymore.
Thanks!
To summarize. Currently there are Zabbix agent(passive) and Zabbix agent(active) item types. Can there be a Zabbix agent(auto) type?
Why? So we will not need same but different templates line "Linux by Zabbix agent" and "Linux by Zabbix agent active". There can be a single "Linux by zabbix agent" template which can work with agent passive or agent active by flip of a setting.
Yes, there are a few exception items which can only work in active mode for example. But those seem to be the edge cases.
There are so many official templates which does not have an "active" counterpart. With the invention of UUIDs it is hard to convert existing passive templates to active ones and maintain in the same system anymore.
Thanks!