--enable-static does not work in Solaris. Attention: Using --enable-static option is not recommended when building server. In order to build the server statically you must have a static version of every external configuring and running Java gateway. See also 1. How to configure shared memory for Zabbix daemons Building Zabbix agent on macOS Overview This section demonstrates how to build Zabbix macOS agent binaries libraries that are provided by Homebrew. These are typically macOS machines that use Homebrew for building Zabbix agent binaries or for other purposes. If agent binaries will be used on macOS machines

some C code of Zabbix agent reused). A configured Go version 1.12+ environment is required for building Zabbix agent 2. Zabbix agent 2 is available in pre-compiled Zabbix packages. To compile Zabbix some C code of Zabbix agent reused). A configured Go version 1.12+ environment is required for building Zabbix agent 2. Agent 2 does not support daemonization. Passive checks work similarly to Zabbix --enable-static does not work in Solaris. Attention: Using --enable-static option is not recommended when building server. In order to build the server statically you must have a static version of every external

not included in official Zabbix distributions, but can be found in build output directory after building Zabbix agent on Windows platform. 22 5.20.6 TCP connection timeout on Windows platforms The configured Linux 2.6.14 and upward kernel systems now tries to make use of the kernel’s NETLINK interface. When building from source, this code is only compiled if netlink.h and inet_diag.h headers are found in the include supported in Zabbix pre-4.0 versions. We recommend using the MariaDB Connector/C library for building server/proxy regardless of whether you use a MySQL or MariaDB database server. Oracle 10g or

This is useful because, when testing SNMP items, problems are often associated with a wrong SNMPv2 community or SNMPv3 security credentials. The values of these fields are pre-filled by the values of the some C code of Zabbix agent reused). A configured Go version 1.13+ environment is required for building Zabbix agent 2. Agent 2 does not support daemonization on Linux; it can be run as a Windows service 0.37 or later) also works with Zabbix. We recommend using the MariaDB Connector/C library for building server/proxy regardless of whether you use a MySQL or MariaDB database server. Oracle 11.2 or

to implement any logic, modules have the potential to be developed and shared within the Zabbix community. Supported for Unix-like systems, a loadable module is basically a shared library used by Zabbix dynamic indexes benefit from both of these improvements: one for index verification and another for building of the cache. See more information about SNMP bulk processing. 8.2 Frontend improvements 8.2.1 does not work in Solaris. 61 Attention: Using --enable-static option is not recommended when building server.// // In order to build the server statically you must have a static version of every external

agent reused). A configured Go environment with a currently supported Go version is required for building Zabbix agent 2. Agent 2 does not have built-in daemonization support on Linux; it can be run as Zabbix 6.0.21; - 8.2 since Zabbix 6.0.26. We recommend using the C API (libmysqlclient) library for building server/proxy. For MySQL versions 8.0.0-8.0.28, see also: Possible deadlocks. 57 Software Mandatory required. The recommended version is 10.5. We recommend using the MariaDB Connector/C library for building server/proxy. Added support for MariaDB versions: - 10.7.X since Zabbix 6.0.6; - 10.8.X since

agent reused). A configured Go environment with a currently supported Go version is required for building Zabbix agent 2. Agent 2 does not have built-in daemonization support on Linux; it can be run as Connector/C library for building server/proxy. MariaDB 10.0.37-10.6.X 10.5.X InnoDB engine is required. We recommend using the MariaDB Connector/C library for building server/proxy. Oracle 12 are compiled using OpenJDK. The table below provides information about OpenJDK versions used for building Zabbix packages by distribution: Distribution OpenJDK version RHEL/CentOS 8 1.8.0 RHEL/CentOS

agent reused). A configured Go environment with a currently supported Go version is required for building Zabbix agent 2. Agent 2 does not have built-in daemonization support on Linux; it can be run as database. InnoDB engine is required. We recommend using the C API (libmysqlclient) library for building server/proxy. For MySQL versions 8.0.0-8.0.28, see also: Possible deadlocks. MariaDB 10.5.00- 00- 10.11.X InnoDB engine is required. We recommend using the MariaDB Connector/C library for building server/proxy. Added support for MariaDB versions: - 10.8.X since Zabbix 6.2.1; - 10.10.X since

can be provided in the item key parameters directly. See also: • Zabbix agent 2 • Plugins • Building Zabbix agent 2 on Windows Macros Ability to mask macro content in the frontend Macro value field been redesigned visually and it now includes SNMP interface details such as the SNMP version and community string allowing to see a difference between otherwise identical interfaces. Similarly, such interface agent reused). A configured Go environment with a currently supported Go version is required for building Zabbix agent 2. Agent 2 does not have built-in daemonization support on Linux; since Zabbix 5.0

agent reused). A configured Go environment with a currently supported Go version is required for building Zabbix agent 2. Agent 2 does not have built-in daemonization support on Linux; it can be run as library for building server/proxy. MariaDB 10.5.00- 11.1.X InnoDB engine is required. The recommended version is 10.5. We recommend using the MariaDB Connector/C library for building server/proxy Required if TimescaleDB is used as a PostgreSQL database extension. Make sure to install TimescaleDB Community Edition, which supports compression. Note that PostgreSQL 15 is supported since TimescaleDB 2