zabbix_proxy搭配sqlite3部署

前言

由於本身公司服務器環境比較複雜，很多服務器都在不同的區域，因此需要在各區域部署一個zabbix_proxy做中轉。zabbix_proxy本身算半個服務端，agent的數據都會發送到proxy存儲，因此跟agent不同，會依賴到數據庫，大家一般都是用mysql。但是肯定不能跟業務數據庫放一塊，單獨爲了這個服務搭一個mysql又覺得太浪費，因此想到用sqlite來做數據庫，既輕便又簡單。網上很少相關教程，所以寫一個方便大家。

環境

系統：centos7.5
版本：sqlite-3.7.17 zabbix-proxy-sqlite3-3.2.9-1 zabbix-release-3.2-1
centos7自帶sqlite,不用另外安裝。
zabbix相關包都可以在下面的地址裏下載。
官方下載地址：http://repo.zabbix.com/zabbix/3.2/rhel/7/x86_64/

安裝

安裝zabbix-proxy

[root@localhost ~]# rpm -ivh zabbix-release-3.2-1.el7.noarch.rpm
[root@localhost ~]# yum -y install zabbix-proxy-sqlite3-3.2.9-1.el7.x86_64.rpm

創建空的數據文件，導入數據庫，這裏要注意數據庫文件所在目錄需要有zabbix用戶的寫權限，不然會報錯。

[root@localhost ~]# touch /tmp/sqlite3/zabbix_proxy.db
[root@localhost ~]# chown zabbix:zabbix /tmp/sqlite3/zabbix_proxy.db
[root@localhost ~]# zcat /usr/share/doc/zabbix-proxy-sqlite3-3.2.9/schema.sql.gz |sqlite3 /tmp/sqlite3/zabbix_proxy.db

修改zabbix_proxy.conf，默認目錄/etc/zabbix/

Server=XX.XX.XX.XX              //  服務端IP
Hostname=xxxx                    //  proxy代理名稱
DBName=/tmp/sqlite3/zabbix_proxy.db // SQLite 數據庫文件位置。
ConfigFrequency=60            // proxy 和 server 同步週期60

啓動proxy

[root@localhost ~]# systemctl enable zabbix-proxy
[root@localhost ~]# systemctl start zabbix-proxy

查看日誌,出現以下日誌表示成功啓動

[root@localhost zabbix]#  tailf  /var/log/zabbix/zabbix_proxy.log
21656:20191010:112744.632 proxy #7 started [poller #4]
 21651:20191010:112744.642 proxy #2 started [heartbeat sender #1]
 21652:20191010:112744.644 proxy #3 started [data sender #1]
 21653:20191010:112744.649 proxy #4 started [poller #1]
 21654:20191010:112744.658 proxy #5 started [poller #2]
 21650:20191010:112744.668 proxy #1 started [configuration syncer #1]
 21657:20191010:112744.692 proxy #8 started [poller #5]
 21658:20191010:112744.703 proxy #9 started [unreachable poller #1]
 21659:20191010:112744.713 proxy #10 started [trapper #1]
 21665:20191010:112744.717 proxy #16 started [housekeeper #1]
 21667:20191010:112744.717 proxy #18 started [discoverer #1]
 21668:20191010:112744.728 proxy #19 started [history syncer #1]
 21670:20191010:112744.731 proxy #21 started [history syncer #3]
 21666:20191010:112744.734 proxy #17 started [http poller #1]
 21662:20191010:112744.737 proxy #13 started [trapper #4]
 21660:20191010:112744.741 proxy #11 started [trapper #2]
 21661:20191010:112744.745 proxy #12 started [trapper #3]
 21664:20191010:112744.749 proxy #15 started [icmp pinger #1]
 21669:20191010:112744.749 proxy #20 started [history syncer #2]
 21671:20191010:112744.752 proxy #22 started [history syncer #4]
 21663:20191010:112744.755 proxy #14 started [trapper #5]
 21672:20191010:112744.759 proxy #23 started [self-monitoring #1]