zabbix database require much hard disk?
The finished article " zabbix installation ", were missing zabbix explain the calculation method of the database hard disk capacity, I would like to read this section we can know their zabbix in the end to how much hard drive.
The Case: 100 servers, each server has 30 monitoring items, each monitoring item 60 seconds to refresh, how much hard drive it?
As we all know, zabbix basically through the web configuration, configuration data is stored in the database, but it requires hard disk capacity can be basically negligible, zabbix have decisive factor hard disk 4, as follows:
1. The amount of data processed per second
The problem is not that we all understand. Only an average, for example, I have a 3000 entry side of the monitor every second, every 60 seconds refresh, then an average of 50 per second (3000/60) data to be processed. That data per second 50 to be inserted MySQL
2. History save time
zabbix should be recorded for each monitored item down, these records are generally retained a few weeks to a few months, specifically to see you configured. Each value required for temporary use of hard disk space. If a data you want to keep for 30 days, and 50 values per second to be retained, then we are a total of 129,600,000 (30 days * 24 * 3600 seconds) * 50 value, a record much by your database engine and your stored data to determine the type (float, plastic, character, etc.), in general, a record needs to occupy 50 bytes (a rough value), approximately 129,600,000 record in this case ( 129 600 000 * 50 bytes) 6.5G disk space
3. trend data retention time
What are the trends in the data it? When you see a week or month chart, you can see on the chart MAX / MIN / AVG / COUNT data are taken from the trend, trend data acquisition time one hour, under normal circumstances, probably a record trend data occupies 128 bytes, If we want to save the 5-year trend data, 3000 to monitor lines need to 2.4GB (3000 * 24 hours * 356 days * 128 bytes) per year, a total of five years 16.8G
4. Event Log duration
Alarm, warning, recovery and so on things, an event taking up about 130 bytes, not too much under normal circumstances, unless doing too bad operation and maintenance, or operation and maintenance requirements are too strict, the threshold is very low tone. If this operation and maintenance animal year this year, neither did burn incense and pray there, let alone to the server attached to magic, so every second year an event occurs, the event this year for the space occupied by the data: 1 year 365 * days * 24 * 130 * 3600 seconds was about 4.1G bytes of space.
The spatial database formula
zabbix configuration: a fixed size, typically <10MB
historical data: Days * (Total / monitored item refresh rate) * 24 * 3600 seconds * 50 bytes
Trend data: number of days * (to monitor the total number of items / 3600) * 24 * 3600 seconds * 128 bytes
event data: * number of events number of days (approx.) * 24 * 130 bytes * 3600 seconds
6. Finally
See here, we all have in mind the data, the database disk space profile size = + History + + trend recorded event record. Although the hard disk will not stop growth, but will one day stop growing, the space has remained the same, why? Read through this also ask why, you see it again from scratch. I hope you continue to support the operation and maintenance of survival time, the students hope zabbix tutorials, stay tuned, next we talk about how to upgrade existing zabbix .