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. Software Version Comments Apache 1.3.12 or later PHP 5.4.0 or later 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.

Deskjet 970Cse Windows 7 64 Bit. Besides a new maintainer, fping now also features a completely. The run time is now close to the. Debian patches until version 2. Modifications by Tobias Oetiker for Smoke. Reimplemented main loop for improved performance (me)See the latest Change. Fping Install Windows. File for details. Apr 03, 2013 fping is a ping(1)-like program which uses the (ICMP) echo request to determine if a host is up. Fping is different from ping in that you can specify any number of hosts on the command line, or specify a file containing the lists of hosts to ping.

Pgsql Required if PostgreSQL is used as Zabbix backend database. Data Backup 3 Mac Serial Box. Sqlite3 Required if SQLite is used as Zabbix backend database. If you obtained Zabbix from the source repository or an archive, then the necessary dependencies are already included in the source tree. If you obtained Zabbix from your distribution's package, then the necessary dependencies are already provided by the packaging system.

In both cases above, the software is ready to be used and no additional downloads are necessary. If, however, you wish to provide your versions of these dependencies (for instance, if you are preparing a package for some Linux distribution), below is the list of library versions that Java gateway is known to work with. Zabbix may work with other versions of these libraries, too. The following table lists JAR files that are currently bundled with Java gateway in the original code. Library License Website Comments logback-core-0.9.27.jar EPL 1.0, LGPL 2.1 Tested with 0.9.27, 1.0.13, and 1.1.1.

Logback-classic-0.9.27.jar EPL 1.0, LGPL 2.1 Tested with 0.9.27, 1.0.13, and 1.1.1. Slf4j-api-1.6.1.jar MIT License Tested with 1.6.1, 1.6.6, and 1.7.6. Android-json-4.3_r3.1.jar Apache License 2.0 Tested with 2.3.3_r1.1 and 4.3_r3.1. See src/zabbix_java/lib/README for instructions on creating a JAR file. Java gateway compiles and runs with Java 1.6 and above. It is recommended that those who provide a precompiled version of the gateway for others use Java 1.6 for compilation, so that it runs on all versions of Java up to the latest one.

Database size. Housekeeper settings for history Zabbix keeps values for a fixed period of time, normally several weeks or months. Each new value requires a certain amount of disk space for data and index. So, if we would like to keep 30 days of history and we receive 50 values per second, total number of values will be around ( )* 50 = 129.600.000, or about 130M of values. Depending on the database engine used, type of received values (floats, integers, strings, log files, etc), the disk space for keeping a single value may vary from 40 bytes to hundreds of bytes. Normally it is around 90 bytes per value for numeric items. In our case, it means that 130M of values will require 130M * 90 bytes = 10.9GB of disk space.

Parameter Formula for required disk space (in bytes) Zabbix configuration Fixed size. Normally 10MB or less. History days*(items/refresh rate)*24*3600*bytes items: number of items days: number of days to keep history refresh rate: average refresh rate of items bytes: number of bytes required to keep single value, depends on database engine, normally ~90 bytes. Trends days*(items/3600)*24*3600*bytes items: number of items days: number of days to keep history bytes: number of bytes required to keep single trend, depends on database engine, normally ~90 bytes.