Our previously mentioned setup has PG +timescale and has ~1T DB... I guess compression would save some...14d history+365d trends.
-
-
Still running 4.4.10...Originally posted by SpectatorThanks your answer.
How often are checks in your system (1 min, 5 min,...)?
Which version of Zabbix are running?
May I ask what hardware background your Zabbix system is running on? How many servers, how many proxies? How much CPU, RAM, HDD?
Are the Zabbix web front-end and Zabbix server running on the same ost?
Sorry my lot of questions. Surely you know that all the information is important when designing such a large system. Or if you have any more ideas, advice, which you would like to share with me, please share it with me
I have not done statistics about checks, not allowing less than a minute checks (except log items, which are active items). Maybe a third of it is SNMP checks, I think. No traps. 14 proxies.
All VM-s, pacemaker/corosync clusters for server and proxies. All parts of server separated and clustered, web, server, DB...
~8G /4 CPU-s for server and frontend hosts, DB hosts @ 128G/8 cpu-s , 12G/2cpus for proxy hosts...
I did not do setup, we had a very good guy working for us at the time, who built all this.. now I have to replicate it all for v6 or something, to get to newer OS etc... Need to polish my Linux skills a lot ..:P
Whatever you do, make your DB as fast as possible, every other component relies on DB... Separate functions, run them on different hosts...Comment
Comment