Dimitri Bellini and Pietro Antonacci - Manage Zabbix Proxies in Remote Networks | ZabConf2016
0 likes1,136 views
This document discusses how an IT company called QUADRATA handled managing multiple remote Zabbix proxies in geographically distributed locations. They initially had issues with huge queues and busy sender processes due to network latency. They addressed this by installing NTP on all machines to synchronize time, optimizing the MySQL databases on proxies to use Percona Server and the innodb_file_per_table setting, and adjusting the DataSenderFrequency and ProxyOfflineBuffer settings to optimize sender processes. They also replicated the Zabbix frontend to account for multiple timezones and eventually migrated to Zabbix 3.0 for performance improvements in server-proxy communication.
Dimitri Bellini and Pietro Antonacci - Manage Zabbix Proxies in Remote Networks | ZabConf2016
- 1. Master and Servants Help Zabbix handle remote proxy network
- 2. QUADRATA ➔ IT company with long experience in supporting small/med Enterprise ➔ Proud to accomplish tasks using exclusively Open-Source software ➔ Been using Zabbix since 2004, version 1.0 ➔ Main partners: HP, IBM and EMC
- 3. The Case: Manage multiple geo-spread proxies
- 4. Brazil: remote proxies FURTHEST remote proxies: Betim, Minas Gerais Goiana, Pernambuco Italy: server + remote proxies Zabbix server in Turin, Piedmont. Server and DB on separated nodes. Remote proxies: Verrone, Lombardy Melfi, Basilicata The Infrastructure
- 5. The Infrastructure: Initial Setup SERVER ★ Server ○ Virtual, Centos 6, 4GB Ram ○ Zabbix 2.2.8 ★ Database ○ Physical, Centos 6, 8GB Ram ○ DBMS Percona Server 5.6.32 ★ Frontend ○ Apache 2.2 PROXIES ★ Proxy + Database ○ Virtual, Centos 6, 4GB Ram ○ Zabbix 2.2.8 ○ MySQL 5.6.30 ○ Default DB configuration
- 6. The Problems Huge Queue Busy Sender Processes
- 7. Could only be a matter of NETWORK LATENCY ?
- 8. https://www.zabbix.com/forum/ showthread.php?t=43522 TIME SYNCHRONIZATION This thread gave us a precious tip about installing NTP on all infrastructure machines, in order to synchronize times between SERVER and PROXIES
- 9. PROXIES DATABASE I/O Percona Server + innodb_file_per_table We decided to optimize proxies disk operations with two changes: ➔ Switch from MySQL to Percona Server, a more performance enhanced engine ➔ Reconfigure DB to a file-per-table setup, useful in environments with not-too-fast or shared storage
- 10. SENDER PROCESSES DataSenderFrequency + ProxyOfflineBuffer We needed to optimize proxies active connections in which they sent data: ➔ DataSenderFrequency just above the max time needed by senders to complete their batch ➔ ProxyOfflineBuffer at minimum, to avoid data overloading in sending queue
- 11. The final touch Multiple Timezones Zabbix frontend replicated, adapting web-server configuration for each one with the right user timezone
- 12. The final touch Migration to 3.0 New Zabbix version brings performance improvement on server-proxy “handshake” https://www.zabbix.com/documentation/3.0/manual/ introduction/whatsnew300#performance_improvements1
- 13. The final touch Migration to 3.2 (future) Upcoming version will (maybe) bring remote commands on proxies
- 14. Questions? THANKS FOR WATCHING ! info@quadrata.it - www.quadrata.it