Hardware
Memory
Zabbix requires both physical and disk memory. 128 MB of physical memory and 256 MB of free disk space could be a good starting point. However, the amount of required disk memory obviously depends on the number of hosts and parameters that are being monitored. If you’re planning to keep a long history of monitored parameters, you should be thinking of at least a couple of gigabytes to have enough space to store the history in the database. Each Zabbix daemon process requires several connections to a database server. Amount of memory allocated for the connection depends on configuration of the database engine.
The more physical memory you have, the faster the database (and therefore Zabbix) works!
CPU
Zabbix and especially Zabbix database may require significant CPU resources depending on number of monitored parameters and chosen database engine.
Other hardware
A serial communication port and a serial GSM modem are required for using SMS notification support in Zabbix. USB-to-serial converter will also work.
Examples of hardware configuration
The table provides several examples of hardware configurations:
Name | Platform | CPU/Memory | Database | Monitored hosts |
---|---|---|---|---|
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 Enterprise Linux | 8 CPU cores/16GB | Fast RAID10 MySQL InnoDB or PostgreSQL | >10000 |
Actual configuration depends on the number of active items and refresh rates very much. It is highly recommended to run the database on a separate box for large installations.
Software
Zabbix is built around a modern Apache web server, leading database engines, and PHP scripting language.
Database management system
Software | Version | Comments |
---|---|---|
MySQL | 5.0.3 or later | Required if MySQL is used as Zabbix backend database. InnoDB engine is required. MariaDB is also known to work with Zabbix. |
Oracle | 10g or later | Required if Oracle is used as Zabbix backend database. |
PostgreSQL | 8.1 or later | Required if PostgreSQL is used as Zabbix backend database. It is suggested to use at least PostgreSQL 8.3, which introduced much better VACUUM performance. |
SQLite | 3.3.5 or later | Required if SQLite is used as Zabbix backend database. |
IBM DB2 | 9.7 or later | Required if IBM DB2 is used as Zabbix backend database. |
Frontend
The following software is required to run Zabbix frontend:
Software | Version | Comments |
---|---|---|
Apache | 1.3.12 or later | |
PHP | 5.4.0 or later | PHP v7 is not supported yet. |
PHP extensions: | ||
gd | 2.0 or later | PHP GD extension must support PNG images (–with-png-dir), JPEG (–with-jpeg-dir) images and FreeType 2 (–with-freetype-dir). |
bcmath | php-bcmath (–enable-bcmath) | |
ctype | php-ctype (–enable-ctype) | |
libXML | 2.6.15 or later | php-xml or php5-dom, if provided as a separate package by the distributor. |
xmlreader | php-xmlreader, if provided as a separate package by the distributor. | |
xmlwriter | php-xmlwriter, if provided as a separate package by the distributor. | |
session | php-session, if provided as a separate package by the distributor. | |
sockets | php-net-socket (–enable-sockets). Required for user script support. | |
mbstring | php-mbstring (–enable-mbstring) | |
gettext | php-gettext (–with-gettext). Required for translations to work. | |
ldap | php-ldap. Required only if LDAP authentication is used in the frontend. | |
ibm_db2 | Required if IBM DB2 is used as Zabbix backend database. | |
mysqli | Required if MySQL is used as Zabbix backend database. | |
oci8 | Required if Oracle is used as Zabbix backend database. | |
pgsql | Required if PostgreSQL is used as Zabbix backend database. | |
sqlite3 | Required if SQLite is used as Zabbix backend database. |
Zabbix may work on previous versions of Apache, MySQL, Oracle, and PostgreSQL as well.
However, the amount of required disk memory obviously depends on the number of hosts and parameters that are being monitored. If you’re planning to keep a long history of monitored parameters, you should be thinking of at least a couple of gigabytes to have enough space to store the history in the database.
Source:https://www.zabbix.com/documentation/3.0/manual/installation/requirements
Author is a passionate Blogger and Writer at Dlightdaily . Dlightdaily produces self researched quality and well explained content regarding HowToGuide, Technology and Management Tips&Tricks.