Environment requirements for Zabbix and zabbix

Environment requirements for Zabbix and zabbix

Environment requirements for Zabbix Configuration
Zabbix database selection, installation, creation, and upgrade
How to obtain ZABBIX
Find the current version and its download instructions on the Zabbix homepage.
Hardware and storage requirements
ZABBIX has requirements on both physical memory and hard disk storage capacity. 128 MB of physical memory and at least 256 MB of free hard disk space are a good start point. However, the size of the required disk space obviously depends on the number of hosts and the required monitoring parameters. If you want to keep a long history of monitoring parameters, you should consider at least 2 to 3 GB space to save the historical records in the database.
Each Zabbix daemon process requires several connections to the database server. The total memory allocated to connections also depends on the database engine configuration.
Note: The more physical memory you have, the faster your database (So Zabbix) runs!
CPU requirements:
ZABBIX, especially ZABBIX databases, may require a large amount of CPU resources, depending on the number of monitoring parameters and the engine of the selected database.
Other hardware:
To use Zabbix's built-in SMS notifications, a serial communication port and a serial GSM modulation are required.
Example of hardware configuration:
The following table provides some hardware configurations:
Name operating system CPU/Memory Database monitored host count
Small Ubuntu LinuxP2 350 MHz/256 MBMySQL MyISAM20
Mid Ubuntu Linux 64 bitAMD Athlon 3200 +/2 GBMySQL MyISAM500
Large Ubuntu Linux 64 bitIntel Dual Core 6400/4 GB/RAIDMySQL MyISAM or PostgreSQL> 1000
Very largeRedHat unzip iseintel Xeon 2 CPU/8 GB/RAIDMySQL MyISAM or PostgreSQL> 10000
Note: The actual configuration depends especially on the number of active monitoring items and the update rate. It is recommended to keep database engine on a separate box for large installations.
Supported operating systems:
To monitor server security requirements and determine critical tasks, Unix is the only operating system that can continuously provide the necessary performance, fault tolerance, and recovery capabilities. ZABBIX supports mainstream versions on the market. ZABBIX has been tested in the following operating systems:
AIX
FreeBSD
HP-UX
Linux
Mac OS/X
OpenBSD
SCO Open Server
Solaris
Note: ZABBIX may also be good luck in other Unix-like operating systems.
Software requirements:
ZABBIX is compiled based on the latest Apache Web server, mainstream database engines, and PHP scripting language.
The following software is required to run ZABBIX:
Software Version description
Apache1.3.12 or later
PHP4.3 or later
PHP module:
Php-gd php-bcmath 4.3 or a later version of the php gd module must support PNG Images
MySQL
Php-mysql 3.22 or later versions are required to use MySQL as the ZABBIX background database
Oracle
Required when php-sqlora8 9.2.0.4 or later uses Oracle as the zabbix background database
PostgreSQL
Php-pgsql 7.0.2 or later versions are required to use PostgreSQL as the ZABBIX background database. Use PostgreSQL 8.x or later for better performance.
SQLite
Php-sqlite3 3.3.5 or later versions are required when using SQLite as the ZABBIX background database
Note: ZABBIX may run properly in earlier versions of Apache, MySQL, Oracle, or PostgreSQL.
Client WEB Browser
HTML and PNG images are required. The MS Explorer (5.xx and 6.xx) and Mozilla 1.x run properly. Cookies and JavaScript must be supported. Other browsers also support Zabbix
Database Engine Selection
ZABBIX supports four database engines:
MySQL
Oracle
PostgreSQL
SQLite
Each database engine has its own advantages. We cannot say which one is the best.
The selection of a Database Engine mainly involves the following aspects:
Performance of your hardware
Free or commercial database engines
ZABBIX server busy
The following table provides general suggestions for database engine selection.
Database Engine Used by ZABBIX Server
Heavy load node/Single-host MySQL MyISAM
Lightweight node/Single-host PostgreSQL
MySQL MyISAM
Remote zero-management node PostgreSQL
SQLite
Separately light-load MySQL MyISAM