【Zabbix】Zabbix 分布式监控—创建Proxy主机

本文涉及的产品
云数据库 RDS MySQL,集群系列 2核4GB
推荐场景:
搭建个人博客
RDS MySQL Serverless 基础系列,0.5-2RCU 50GB
云数据库 RDS MySQL,高可用系列 2核4GB
简介: 【Zabbix】Zabbix 分布式监控—创建Proxy主机

Zabbix三种架构

Server-Agent

Server-Node-Agent

Server-Proxy-Agent


配置介绍

Zabbix Proxy的配置

  • Server-Node-Agent
  • Server-Proxy-Agent


1、配置proxy主机

① 安装相应的zabbix包
zabbix-proxy-mysql zabbix-get zabbix-agent zabbix-sender
② 准备数据库
创建、授权用户、导入schema.sql
③ 修改配置文件
④ 在server端添加此Proxy
Administration ——> Proxies
⑤ 在Server端配置通过此Proxy监控的主机

注意:zabbix agent端要允许zabbix proxy主机执行数据采集操作


实战演练—分布式监控

实验部署架构

主机名称 IP地址 服务角色 架构类型
zabbix-server 192.168.200.60 Zabbix 监控端 /

zabbix-agent-centos 192.168.200.70 Zabbix 客户端 Server-Agent
zbxproxy 192.168.200.90 Zabbix Proxy /

zabbix-agent-02 192.168.200.100 Zabbix 客户端 Server-Proxy-Agent


1、实验前期准备(Server端、Proxy端)

配置服务端和代理端时间同步

# 服务端和代理端安装ntpdate服务包
yum install -y ntpdate
# 服务端和代理端同步阿里云时间服务器
ntpdate ntp1.aliyun.com

关闭防火墙、SELinux安全模式

systemctl stop firewalld
systemctl disable firewalld
setenforce 0
getenforce
iptables -nL

设置主机名

[root@zabbix-server ~]# hostnamectl set-hostname zabbix-server 
[root@zabbix-proxy ~]# hostnamectl set-hostname zbxproxy.xybdiy.com
[root@zabbix-agent-02 ~]# hostnamectl set-hostname zabbix-agent-02

配置域名解析

[root@zabbix-agent-02 ~]# cat /etc/hosts
127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
192.168.200.60  zabbix-server
192.168.200.90  zbxproxy.xybdiy.com zbxproxy
192.168.200.100 zabbix-agent-02

zabbix-server 直接监控一台主机zabbix-agent-centos

zabbix-server 通过代理zbproxy 监控zabbix-agent-02

2、在代理服务器上配置MySQL

  • 创建MariaDB.repo
[root@zbproxy yum.repos.d]# vim mariadb.repo
[root@zbproxy yum.repos.d]# cat mariadb.repo
[mariadb]
name = MariaDB
baseurl = http://mirrors.ustc.edu.cn/mariadb/yum/10.2/centos7-amd64/
gpgkey=http://mirrors.ustc.edu.cn/mariadb/yum/RPM-GPG-KEY-MariaDB
gpgcheck=1
  • 安装mariadb
[root@zbproxy ~]# yum install -y MariaDB-server MariaDB-client

cf379a8aa2d5c43c30fd84a3f0a24cdb.png

  • 修改数据库配置文件
[root@zbproxy ~]# vim /etc/my.cnf.d/server.cnf 
[mysqld]
skip_name_resolve = ON      # 跳过主机名解析
innodb_file_per_table = ON    # 开启独立表空间
innodb_buffer_pool_size = 256M  # 缓存池大小
max_connections = 2000      # 最大连接数
log-bin = master-log      # 开启二进制日志
  • 启动数据库服务
[root@zbproxy ~]# systemctl start mariadb
[root@zbproxy ~]# systemctl enable mariadb

  • 初始化数据库
[root@zbproxy ~]# mysql_secure_installation 
NOTE: RUNNING ALL PARTS OF THIS SCRIPT IS RECOMMENDED FOR ALL MariaDB
      SERVERS IN PRODUCTION USE!  PLEASE READ EACH STEP CAREFULLY!
In order to log into MariaDB to secure it, we'll need the current
password for the root user.  If you've just installed MariaDB, and
you haven't set the root password yet, the password will be blank,
so you should just press enter here.
Enter current password for root (enter for none): 
OK, successfully used password, moving on...
Setting the root password ensures that nobody can log into the MariaDB
root user without the proper authorisation.
Set root password? [Y/n] y     
New password: 
Re-enter new password: 
Password updated successfully!
Reloading privilege tables..
 ... Success!
By default, a MariaDB installation has an anonymous user, allowing anyone
to log into MariaDB without having to have a user account created for
them.  This is intended only for testing, and to make the installation
go a bit smoother.  You should remove them before moving into a
production environment.
Remove anonymous users? [Y/n] y
 ... Success!
Normally, root should only be allowed to connect from 'localhost'.  This
ensures that someone cannot guess at the root password from the network.
Disallow root login remotely? [Y/n] n
 ... skipping.
By default, MariaDB comes with a database named 'test' that anyone can
access.  This is also intended only for testing, and should be removed
before moving into a production environment.
Remove test database and access to it? [Y/n] y
 - Dropping test database...
 ... Success!
 - Removing privileges on test database...
 ... Success!
Reloading the privilege tables will ensure that all changes made so far
will take effect immediately.
Reload privilege tables now? [Y/n] y
 ... Success!
Cleaning up...
All done!  If you've completed all of the above steps, your MariaDB
installation should now be secure.
Thanks for using MariaDB!
[root@zbproxy ~]# mysql -uroot -p000
  • 创建数据库 和 授权用户
# 创建数据库zbxproxydb
MariaDB [(none)]> create database zbxproxydb character set 'utf8';
Query OK, 1 row affected (0.00 sec)
# 授权用户zbxproxydb
MariaDB [(none)]> grant all on zbxproxydb.* to 'zbxproxyuser'@'192.168.200.%' identified by 'zbxproxypass';
Query OK, 0 rows affected (0.00 sec)
# 刷新,重新加载
MariaDB [(none)]> flush privileges;
Query OK, 0 rows affected (0.00 sec)
# 退出
MariaDB [(none)]> exit
Bye
[root@zbproxy ~]# 

3、在代理服务器上下载zabbix相应的包。

主要是代理proxy的包

[root@zbproxy src]# yum localinstall zabbix-agent-5.0.20-1.el7.x86_64.rpm zabbix-p

d905e9c44ba0c3a574c1bbfc3b554638.png

  • 初始化数据库
#查询数据库包
[root@zbproxy src]# rpm -ql zabbix-proxy-mysql
/etc/logrotate.d/zabbix-proxy
/etc/zabbix/zabbix_proxy.conf
/usr/lib/systemd/system/zabbix-proxy.service
/usr/lib/tmpfiles.d/zabbix-proxy.conf
/usr/lib/zabbix/externalscripts
/usr/sbin/zabbix_proxy_mysql
/usr/share/doc/zabbix-proxy-mysql-5.0.20
/usr/share/doc/zabbix-proxy-mysql-5.0.20/AUTHORS
/usr/share/doc/zabbix-proxy-mysql-5.0.20/COPYING
/usr/share/doc/zabbix-proxy-mysql-5.0.20/ChangeLog
/usr/share/doc/zabbix-proxy-mysql-5.0.20/NEWS
/usr/share/doc/zabbix-proxy-mysql-5.0.20/README
/usr/share/doc/zabbix-proxy-mysql-5.0.20/schema.sql.gz
/usr/share/man/man8/zabbix_proxy.8.gz
/var/log/zabbix
/var/run/zabbix

zabbix-proxymysql 包里带有导入数据的文件schema.sql.gz

# 复制schema.sql.gz
[root@zbproxy ~]# cp /usr/share/doc/zabbix-proxy-mysql-5.0.20/schema.sql.gz .
[root@zbproxy ~]# ls
anaconda-ks.cfg  schema.sql.gz
# 解压
[root@zbproxy ~]# gzip -d schema.sql.gz 
[root@zbproxy ~]# ls
anaconda-ks.cfg  schema.sql
# 导入数据,出现以下问题
[root@zbproxy ~]# mysql -uroot -p000 < schema.sql 
ERROR 1046 (3D000) at line 1: No database selected
解决办法:
[root@zbproxy ~]# vim schema.sql 
在首部添加如下内容:
USE zbxproxydb;
按:wq保存退出
[root@zbproxy ~]# mysql -uroot -p000 < schema.sql 
  • 查看数据已经生成
MariaDB [(none)]> show databases;
+--------------------+
| Database           |
+--------------------+
| information_schema |
| mysql              |
| performance_schema |
| zbxproxydb         |
+--------------------+
4 rows in set (0.00 sec)
MariaDB [(none)]> use zbxproxydb;
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A
Database changed
MariaDB [zbxproxydb]> show tables;
+----------------------------+
| Tables_in_zbxproxydb       |
+----------------------------+
| acknowledges               |
| actions                    |
| alerts                     |
| application_discovery      |
| application_prototype      |
| application_template       |
| applications               |
| auditlog                   |
| auditlog_details           |
| autoreg_host               |
| conditions                 |
| config                     |
| config_autoreg_tls         |
| corr_condition             |
| corr_condition_group       |
| corr_condition_tag         |
| corr_condition_tagpair     |
| corr_condition_tagvalue    |
| corr_operation             |
| correlation                |
| dashboard                  |
| dashboard_user             |
| dashboard_usrgrp           |
| dbversion                  |
| dchecks                    |
| dhosts                     |
| drules                     |
| dservices                  |
| escalations                |
| event_recovery             |
| event_suppress             |
| event_tag                  |
| events                     |
| expressions                |
| functions                  |
| globalmacro                |
| globalvars                 |
| graph_discovery            |
| graph_theme                |
| graphs                     |
| graphs_items               |
| group_discovery            |
| group_prototype            |
| history                    |
| history_log                |
| history_str                |
| history_text               |
| history_uint               |
| host_discovery             |
| host_inventory             |
| host_tag                   |
| hostmacro                  |
| hosts                      |
| hosts_groups               |
| hosts_templates            |
| housekeeper                |
| hstgrp                     |
| httpstep                   |
| httpstep_field             |
| httpstepitem               |
| httptest                   |
| httptest_field             |
| httptestitem               |
| icon_map                   |
| icon_mapping               |
| ids                        |
| images                     |
| interface                  |
| interface_discovery        |
| interface_snmp             |
| item_application_prototype |
| item_condition             |
| item_discovery             |
| item_preproc               |
| item_rtdata                |
| items                      |
| items_applications         |
| lld_macro_path             |
| lld_override               |
| lld_override_condition     |
| lld_override_opdiscover    |
| lld_override_operation     |
| lld_override_ophistory     |
| lld_override_opinventory   |
| lld_override_opperiod      |
| lld_override_opseverity    |
| lld_override_opstatus      |
| lld_override_optag         |
| lld_override_optemplate    |
| lld_override_optrends      |
| maintenance_tag            |
| maintenances               |
| maintenances_groups        |
| maintenances_hosts         |
| maintenances_windows       |
| mappings                   |
| media                      |
| media_type                 |
| media_type_message         |
| media_type_param           |
| module                     |
| opcommand                  |
| opcommand_grp              |
| opcommand_hst              |
| opconditions               |
| operations                 |
| opgroup                    |
| opinventory                |
| opmessage                  |
| opmessage_grp              |
| opmessage_usr              |
| optemplate                 |
| problem                    |
| problem_tag                |
| profiles                   |
| proxy_autoreg_host         |
| proxy_dhistory             |
| proxy_history              |
| regexps                    |
| rights                     |
| screen_user                |
| screen_usrgrp              |
| screens                    |
| screens_items              |
| scripts                    |
| service_alarms             |
| services                   |
| services_links             |
| services_times             |
| sessions                   |
| slides                     |
| slideshow_user             |
| slideshow_usrgrp           |
| slideshows                 |
| sysmap_element_trigger     |
| sysmap_element_url         |
| sysmap_shape               |
| sysmap_url                 |
| sysmap_user                |
| sysmap_usrgrp              |
| sysmaps                    |
| sysmaps_elements           |
| sysmaps_link_triggers      |
| sysmaps_links              |
| tag_filter                 |
| task                       |
| task_acknowledge           |
| task_check_now             |
| task_close_problem         |
| task_data                  |
| task_remote_command        |
| task_remote_command_result |
| task_result                |
| timeperiods                |
| trends                     |
| trends_uint                |
| trigger_depends            |
| trigger_discovery          |
| trigger_tag                |
| triggers                   |
| users                      |
| users_groups               |
| usrgrp                     |
| valuemaps                  |
| widget                     |
| widget_field               |
+----------------------------+
166 rows in set (0.00 sec)
MariaDB [zbxproxydb]> 

4、配置proxy端

[root@zbproxy ~]# vim /etc/zabbix/zabbix_proxy.conf 
Server=192.168.200.60     # server 的IP
ServerPort=10051        # server 的端口
Hostname=zbxproxy.xybdiy.com  # 主机名
ListenPort=10051        # proxy自己的监听端口
EnableRemoteCommands=1      # 允许远程命令
LogRemoteCommands=1       # 记录远程命令的日志
DBHost=192.168.200.90
DBName=zbxproxydb
DBUser=zbxproxyuser
DBPassword=zbxproxypass
ConfigFrequency=30        # 意思是多长时间去服务端拖一次有自己监控的操作配置,为了实验更快的生效。这里设置30秒,默认3600s
DataSenderFrequency=1     # 每一秒向server 端发一次数据,发送频度

开启proxy服务

[root@zbxproxy zabbix]# systemctl start zabbix-proxy
[root@zbxproxy zabbix]# systemctl enable zabbix-proxy

5、配置Agent端允许proxy代理监控

[root@zabbix-agent-02 ~]# vim /etc/zabbix/zabbix_agentd.conf 
Server=192.168.200.60,192.168.200.90
ServerActive=192.168.200.60,192.168.200.90
[root@zabbix-agent-02 ~]# systemctl restart zabbix-agent

6、把代理加入监控server 创建配置agent代理

  • 创建agent代
  • e11d337d1cfcbf17069032dcbf023d2f.png
  • 配置

28fe4e0fae37ae9562f05a2798c8d5e6.png

524b9e29a1f59320b2f6143e155e98f1.png

  • 创建agent端主机并采用代理监控

9586759bf286407d4a1b9cbab808634b.png

497ef3408cf486a42e7daba88244d5da.png

f354000a7b0a7d452f972cdf17784fff.png

相关实践学习
如何在云端创建MySQL数据库
开始实验后,系统会自动创建一台自建MySQL的 源数据库 ECS 实例和一台 目标数据库 RDS。
全面了解阿里云能为你做什么
阿里云在全球各地部署高效节能的绿色数据中心,利用清洁计算为万物互联的新世界提供源源不断的能源动力,目前开服的区域包括中国(华北、华东、华南、香港)、新加坡、美国(美东、美西)、欧洲、中东、澳大利亚、日本。目前阿里云的产品涵盖弹性计算、数据库、存储与CDN、分析与搜索、云通信、网络、管理与监控、应用服务、互联网中间件、移动服务、视频服务等。通过本课程,来了解阿里云能够为你的业务带来哪些帮助 &nbsp; &nbsp; 相关的阿里云产品:云服务器ECS 云服务器 ECS(Elastic Compute Service)是一种弹性可伸缩的计算服务,助您降低 IT 成本,提升运维效率,使您更专注于核心业务创新。产品详情: https://www.aliyun.com/product/ecs
相关文章
|
21天前
|
监控 Java Shell
监控堆外第三方监控工具Zabbix
监控堆外第三方监控工具Zabbix
33 5
|
18天前
|
监控 安全 前端开发
使用 Zabbix 监控堆外应用
使用 Zabbix 监控堆外应用
37 9
|
17天前
|
监控 数据可视化 Java
zabbix全面的监控能力
zabbix全面的监控能力
44 7
|
1月前
|
SQL 监控 数据库
OceanBase社区版可以通过Zabbix监控
OceanBase社区版可以通过Zabbix监控
84 7
|
1月前
|
数据采集 存储 监控
公司监控软件:基于 PHP 的分布式监控系统设计
本文介绍了基于 PHP 的分布式监控系统的设计与实现。该系统包括监控节点、数据采集模块、数据传输模块和监控中心,能够高效地收集、传输和分析各节点的数据,确保系统的稳定运行和安全防护。通过示例代码展示了数据采集、传输及存储的具体实现方法,并强调了安全与可靠性的重要性。
46 3
|
2月前
|
SQL 监控 数据库
OceanBase社区版可以通过Zabbix监控
【10月更文挑战第5天】随着OceanBase社区版的广泛应用,企业纷纷采用这一高性能、高可用的分布式数据库系统。为了确保系统的稳定运行,使用成熟的Zabbix监控工具进行全面监控至关重要。本文通过具体示例介绍了如何配置Zabbix监控OceanBase,包括安装配置、创建监控模板和监控项、编写脚本、设置触发器及图形展示等步骤,帮助读者快速上手,及时发现并解决问题,确保业务始终处于最佳状态。
84 2
|
3月前
|
监控 关系型数据库 MySQL
zabbix agent集成percona监控MySQL的插件实战案例
这篇文章是关于如何使用Percona监控插件集成Zabbix agent来监控MySQL的实战案例。
81 2
zabbix agent集成percona监控MySQL的插件实战案例
|
7月前
|
存储 SQL 监控
修改Zabbix源码实现监控数据双写,满足业务需求!
虽然对接Elasticsearch后有诸多好处,但是它不往数据库写历史数据了,同时还不再计算趋势数据了。有这么一个场景...
修改Zabbix源码实现监控数据双写,满足业务需求!
|
7月前
|
数据采集 监控 数据库
OceanBase社区版可以通过Zabbix监控
OceanBase社区版可以通过Zabbix监控
279 4
|
4月前
|
监控 安全 Linux
在Linux中,zabbix如何监控脑裂?
在Linux中,zabbix如何监控脑裂?

推荐镜像

更多