Small CentOS Virtual Appliance MySQL InnoDB 100 Medium CentOS 2 CPU cores/2GB MySQL InnoDB 500 Large RedHat Enterprise Linux 4 CPU cores/8GB RAID10 MySQL InnoDB or PostgreSQL >1000 Very large RedHat RedHat Enterprise Linux 8 CPU cores/16GB Fast RAID10 MySQL InnoDB or PostgreSQL >10000 Note: Actual configuration depends on the number of active items and refresh rates very much. It is highly recommended Software Version Comments MySQL 5.0.3 - 5.7.x Required if MySQL is used as Zabbix backend database. InnoDB engine is required. MariaDB also works with Zabbix. Note that MySQL 8.0 is not supported in Zabbix

Small CentOS Virtual Appliance MySQL InnoDB 100 Medium CentOS 2 CPU cores/2GB MySQL InnoDB 500 Large RedHat Enterprise Linux 4 CPU cores/8GB RAID10 MySQL InnoDB or PostgreSQL >1000 Very large RedHat RedHat Enterprise Linux 8 CPU cores/16GB Fast RAID10 MySQL InnoDB or PostgreSQL >10000 Note: Actual configuration depends on the number of active items and refresh rates very much (see database size Software Version Comments MySQL 5.0.3 - 5.7.x Required if MySQL is used as Zabbix backend database. InnoDB engine is required. MariaDB also works with Zabbix. Note that MySQL 8.0 is not supported in Zabbix

Small CentOS Virtual Appliance MySQL InnoDB 100 Medium CentOS 2 CPU cores/2GB MySQL InnoDB 500 Large RedHat Enterprise Linux 4 CPU cores/8GB RAID10 MySQL InnoDB or PostgreSQL >1000 Very large RedHat RedHat Enterprise Linux 8 CPU cores/16GB Fast RAID10 MySQL InnoDB or PostgreSQL >10000 Note: Actual configuration depends on the number of active items and refresh rates very much. It is highly recommended Software Version Comments MySQL 5.0.3 or later Required if MySQL is used as Zabbix backend database. InnoDB engine is required. Oracle 10g or later Required if Oracle is used as Zabbix backend database

Small CentOS Virtual Appliance MySQL InnoDB 100 Medium CentOS 2 CPU cores/2GB MySQL InnoDB 500 Large RedHat Enterprise Linux 4 CPU cores/8GB RAID10 MySQL InnoDB or PostgreSQL >1000 Very large RedHat RedHat Enterprise Linux 8 CPU cores/16GB Fast RAID10 MySQL InnoDB or PostgreSQL >10000 Note: Actual configuration depends on the number of active items and refresh rates very much. It is highly recommended Software Version Comments MySQL 5.0.3 or later Required if MySQL is used as Zabbix backend database. InnoDB engine is required. Oracle 10g or later Required if Oracle is used as Zabbix backend database

SharePont Microsoft SharePoint by HTTP - see setup instructions for HTTP templates. MongoDB • MongoDB cluster by Zabbix agent 2 • MongoDB node by Zabbix agent 2 See setup instructions for Zabbix agent 2 templates monitoring of TiDB server of TiDB cluster via HTTP; • TiDB PD by HTTP - monitoring of PD server of TiDB cluster via HTTP; • TiDB TiKV by HTTP - monitor TiKV server of TiDB cluster via HTTP. See setup instructions Small CentOS Virtual Appliance MySQL InnoDB 100 Medium CentOS 2 CPU cores/2GB MySQL InnoDB 500 Large RedHat Enterprise Linux 4 CPU cores/8GB RAID10 MySQL InnoDB or PostgreSQL >1000 Very large RedHat

setupfor more information. Items VMware cluster performance counters A new vmware.cl.perfcounter[,,,] item allows to retrieve VMware cluster performance counter metrics. JMX items Small CentOS Virtual Appliance MySQL InnoDB 100 Medium CentOS 2 CPU cores/2GB MySQL InnoDB 500 Large RedHat Enterprise Linux 4 CPU cores/8GB RAID10 MySQL InnoDB or PostgreSQL >1000 Very large RedHat RedHat Enterprise Linux 8 CPU cores/16GB Fast RAID10 MySQL InnoDB or PostgreSQL >10000 Note: Actual configuration depends on the number of active items and refresh rates very much (see database size

Small CentOS Virtual Appliance MySQL InnoDB 100 Medium CentOS 2 CPU cores/2GB MySQL InnoDB 500 Large RedHat Enterprise Linux 4 CPU cores/8GB RAID10 MySQL InnoDB or PostgreSQL >1000 Very large RedHat RedHat Enterprise Linux 8 CPU cores/16GB Fast RAID10 MySQL InnoDB or PostgreSQL >10000 Note: Actual configuration depends on the number of active items and refresh rates very much. It is highly recommended Software Version Comments MySQL 5.0.3 - 5.7.x Required if MySQL is used as Zabbix backend database. InnoDB engine is required. MariaDB also works with Zabbix. Note that MySQL 8.0 is not supported in Zabbix

Small CentOS Virtual Appliance MySQL InnoDB 100 Medium CentOS 2 CPU cores/2GB MySQL InnoDB 500 Large RedHat Enterprise Linux 4 CPU cores/8GB RAID10 MySQL InnoDB or PostgreSQL >1000 Very large RedHat RedHat Enterprise Linux 8 CPU cores/16GB Fast RAID10 MySQL InnoDB or PostgreSQL >10000 Note: Actual configuration depends on the number of active items and refresh rates very much (see database size Software Version Comments MySQL 5.0.3 - 8.0.x Required if MySQL is used as Zabbix backend database. InnoDB engine is required. MariaDB also works with Zabbix. For MySQL we recommend using the C API (libmysqlclient)

New official templates are available for monitoring: Elasticsearch • Template App Elasticsearch Cluster by HTTP - native template to monitor Elasticsearch. ClickHouse • Template DB ClickHouse - collects Zabbix agent 2 active See setup instructions for Zabbix agent 2 templates. MongoDB • MongoDB cluster by Zabbix agent 2 • MongoDB node by Zabbix agent 2 See setup instructions for Zabbix agent 2 templates Small CentOS Virtual Appliance MySQL InnoDB 100 Medium CentOS 2 CPU cores/2GB MySQL InnoDB 500 Large RedHat Enterprise Linux 4 CPU cores/8GB RAID10 MySQL InnoDB or PostgreSQL >1000 Very large RedHat

RabbitMQ cluster by Zabbix agent and Template App RabbitMQ node by Zabbix agent - collect metrics by polling RabbitMQ management plugin with Zabbix agent locally; • Template App RabbitMQ cluster by HTTP Small CentOS Virtual Appliance MySQL InnoDB 100 Medium CentOS 2 CPU cores/2GB MySQL InnoDB 500 Large RedHat Enterprise Linux 4 CPU cores/8GB RAID10 MySQL InnoDB or PostgreSQL >1000 Very large RedHat RedHat Enterprise Linux 8 CPU cores/16GB Fast RAID10 MySQL InnoDB or PostgreSQL >10000 Note: Actual configuration depends on the number of active items and refresh rates very much (see database size