Recommended: If you utilize multiple IP addresses on your monitored hosts, it’s always a good idea to restrict listening to relevant addresses only.ListenIP – List of comma delimited IP addresses that the agent should listen on.Recommended: Should contain the IP addresses or host names of the Zabbix Servers or Proxies that should be able to query data from the agent.Incoming connections will be accepted only from the hosts listed here. Server – List of comma delimited IP addresses, optionally in CIDR notation, or hostnames of Zabbix Servers.Values in shipped configuration files for your OS might differ. Do also note, that the defaults listed below are daemon defaults. Certain options do deserve a closer look though. The default agent configuration is relatively secure.
We will go through a list of recommended settings as well as how to enable agent encryption with TLS PSK. If the configuration option is enabled, agents are even capable of executing remote commands, given to them by the Zabbix Server! Additional item keys can be created using User Parameters with which you can create custom script snippets that gather data for you. It usually runs (at least under Linux) under the ‘zabbix’ user, with relatively restricted permissions. Zabbix Agents are a key part of your monitoring infrastructure and a secure configuration ensures safe and reliable operation.Ī native Zabbix agent, developed in C language, may run on various supported platforms, including Linux, UNIX and Windows, and collect data such as CPU, memory, disk and network interface usage from a device.Īn agent, by default, keeps track of a huge assortment of metrics, like the ones mentioned above.