Ad Widget

**tritsako** · 02-11-2016, 13:24

Hi Frederico,

I believe that Zabbix monitoring for > 1000 hosts can work fine with the following requirements:

All Virtual machine

1 VM - Centos - For webserver
1 VM - Centos - Zabbix Server
1 VM - Centos - MySQL server

All VMs can have:

Memory: 4GB
CPU: 4
Disk size for Web server and Zabbix Server can be up to 100GB
Disk size for MySQL database is explained below as it depends on many factors:

ZABBIX configuration data requires fixed amount of disk space and does not
grow much.

ZABBIX database size mainly depends on these variables, which define amount
of stored historical data:
 Number of processed values per second

This is average number of new values ZABBIX server receives every second.
For example, if we have 3000 items for monitoring with refresh rate of 60
seconds, number of values per seconds is calculated as 3000/60 = 50.
It means that 50 new values are added to ZABBIX database every second.

ZABBIX keeps values for a fixed period of time, normally several weeks or
months. Each new value required 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 (30*24*3600)*50 = 129.600.000, or about 130M of values.

Depending on used database engine, type of received values (floats, integers,
strings, log files, etc), disk space for keeping a single value may vary from 40
bytes to hundreds of bytes. Normally it is around 50 bytes per value.
In our case, it means that 130M of values will require 130M * 50 bytes = 6.5GB of disk space.

ZABBIX keeps 1 hour max/min/avg/count statistics for each item in table
trends. The data is used for trending and long period graphs.
ZABBIX database, depending on database type, requires about 128 bytes per
each total.
Suppose we would like to keep trend data for 5 years. 3000 values will require
(3000/1800)*(24*3600*365)*128 = 6.3GB per year, or 31.5GB for 5 years.

Each ZABBIX event requires approximately 130 bytes of disk space. It is hard
number of events generated by ZABBIX daily. In worst case scenario, we may
assume that ZABBIX generates one event per second. It means that if we want to keep 3 years of events, this would require

3*365*24*3600*130 = 11GB

Keep in mind that for 1000 hosts you will have much more that 3000 Items for monitoring.

Hope it helps.
Costas

**nick0909** · 03-11-2016, 21:07

It really depends how much data you want to monitor and keep, and how many people you have browsing the frontend looking at graphs and data all day long. Here is an example of my current setup:

Main server, it is database, web frontend and zabbix server all in one.
520 hosts with 46,000 items monitored. We check items between 1 and 10 minutes, depending on their importance, which works out for us to be about 220nvps. We keep most history for 7-14 days and then trend data for 1 year. We have 5-10 people on the front end all day long looking at triggers or graphs. We use 4 proxies to collect all the data and send it in to the main server.

Our database size in mysql is about 25gb. It runs on a physical server (HP Gen 8), 8x CPU and 64gb RAM with 6 drives in a RAID10. I just migrated from a much older server (HP Gen 5) that was a 4 core, 32gb RAM, 8 drive RAID10. Our backup time to dump the entire database on the old server was about 35 minutes, it is down to 8 minutes on the new hardware.

**michael.weber** · 07-11-2016, 14:29

Please see the Screenshot:
Version 3.2
~400 active Hosts
~13k items
~ 6k triggers
~70nvps

It is running on a virtual maschine:
Debian 8 64Bit
2vCPU (2 Cores, 1 CPU)
3GB RAM
Normal HDD Drives.

CPU usage is ~10%
RAM usage ~ 80% (1,6GB SQL Database in complete in the RAM)

Attached Files

Ad Widget

Hardware Requirements

Hardware Requirements

Comment

Comment

Comment