Confused on this, Zabbix agent 2 seems better in every way from the description and my perception. I am using Zabbix Agent 2 and all seems well. But it is confusing to have a Zabbix agent 1 and 2. Is 2 better? Is 2 the future of Zabbix? Will Zabbix 1 be replaced by Zabbix Agent 2?
-
-
im new in zabbix and only used zabbix agent 1 is there a difference between each other? i thinked that zabbix agent 2 was for applications like apache or mysql -
Agent 1 is the original agent, agent 2 is new. I think as of now, agent2 can do everything agent1 can do and more. If you're starting now, I think agent2 is the better choice. Those of us with glactic mass of legacy are still using agent1 with no problems.
I'd highly recommend deploying either agent with your management tool of choice, puppet, ansible, whatever. Manage the tool, don't manage individual servers.Comment
-
There is one feature in agent2 that I don't like: it is not possible to use "StartAgents=0", meaning that it will always listen to port 10050 even though you wouldn't use it. I don't use passive items so I'd like the agent to not listen to a port that is not used.
MarkkuComment
-
Comment
-
Well, you seem to be correct: adding this in /etc/zabbix/zabbix_agent2.d/local.conf (to avoid touching the stock zabbix_agent2.conf) helps:
Server=
even though the latest LTS documentation says it is mandatory:
MarkkuList of comma-delimited IP addresses, optionally in CIDR notation, or DNS names of Zabbix servers and Zabbix proxies.
Incoming connections will be accepted only from the hosts listed here.
If IPv6 support is enabled then '127.0.0.1', '::ffff:127.0.0.1' are treated equally and '::/0' will allow any IPv4 or IPv6 address.
'0.0.0.0/0' can be used to allow any IPv4 address.
Example: Server=127.0.0.1,192.168.1.0/24,::1,2001:db8::/32,zabbix.example.com
Spaces are allowed.Comment
Comment