Zabbix distributed monitoring application of automatic operation and maintenance tools (V)

Distributed monitoring overview
Proxy and Node
Zabbix 3 types of architectures commonly used
-->server-agent
-->server-node-agent
-->server-proxy-agent

Zabbix enables efficient monitoring of distributed it architectures
Zabbix offers two solutions in large environments
--Use Agent (proxy)
-Using nodes (node)
Proxy or Node?
-Agent for data collection in the region and send data to the server
--node provides the full Zabbix server to build the hierarchy of distributed monitoring

	Proxy	Node
Lightweight	Yes	No
Gui	No	Yes
Works independently	Yes	Yes
Easy Maintenance	Yes	No
Automatic DB Creation	Yes	No
Local Administration	No	Yes
Ready for embedded hardware	Yes	No
One-to-one-to-TCP connections	Yes	Yes
Centralised configuration	Yes	No
Generates notifications	No	Yes

Proxy mode and Node mode

Node itself is a server, it has a complete Web page, a complete database, it will stream data to master.

Proxy only a proxy daemon process, proxy also has its own database, but its database will only save a certain amount of time of data, it and master communication is to pack a batch of information sent to master, Master merges the data into the master database.

Master-proxy compared to master-node a bit has the following:

-->proxy pressure is small, the database only stores a certain time data;

-->master pressure becomes smaller, the data is not continuously acquired, reducing IO pressure;

-The architecture is clearer and easier to maintain;

Server-node-client characteristics

--Solve the performance bottleneck of single server when host is too large

--Using multiple instance

-each instance is a separate set of Zabbix, with database and frontend (optional)

--Hot-swappable, node and server connections can be disconnected at any time, but do not affect node's normal operation.

-->node timed to send configuration,history,event to server

-->server periodically sends a configuration to node

-All configuration changes can only be performed on node nodes and not in server operations.

Tree-like structure, node can be a server

Server-proxy-client Working characteristics

--proxy does not synchronize the configuration to the server, it only receives

--proxy database Timing transfers data to the Server,proxy local database to save only the data that has not been sent recently

Configure the Zabbix_proxy server as follows:

(1) Configure MySQL database as follows:

mysql> CREATE DATABASE zabbix_proxy CHARACTER SET utf8;mysql> GRANT all on zabbix_proxy.* to ' zbxuser ' @ ' 172.16.%.% ' Identified by ' Redhat ';mysql> FLUSH privileges;

(2) Installing Zabbix components

# lszabbix-2.0.8-3.el6.x86_64.rpm zabbix-proxy-mysql-2.0.8-3.el6.x86_64.rpmzabbix-proxy-2.0.8-3.el6.x86_64.rpm# Yum-y Localinstall *.rpm

(3) Create a zabbix_proxy table

# mysql-uzbxuser-predhat-h172.16.100.3 zabbix_proxy</usr/share/doc/zabbix-proxy-mysql-2.0.8/create/schema.sql

(4) Configure the Zabbix_proxy configuration file as follows:

# Cat/etc/zabbix/zabbix_proxy.conf | Grep-e ' (server| Dbhost| dbname| dbuser| Dbpassword) ' server=172.16.100.2hostname=172.16.100.101dbhost=172.16.100.3dbname=zabbix_proxydbuser= Zbxuserdbpassword=redhat

(5) Start Zabbix-proxy service

# service Zabbix-proxy Start

(6) Add Proxy in Zabbix Web interface:

Administration-->gm-->proxies[create Proxy]

650) this.width=650; "src=" Http://s1.51cto.com/wyfs02/M02/89/C9/wKiom1gcPj7iuTD7AABTmvXyYUY584.png "title=" Create Dm.png "alt=" Wkiom1gcpj7iutd7aabtmvxyyuy584.png "/>

(7) The zabbix_agentd.conf configuration of the monitored host under proxy, as follows:

Vim/etc/zabbix/zabbix_agentd.conf server=172.16.100.101--Change to proxy address serveractive=172.16.100.101userparameter= Memory.free,/usr/bin/free |awk '/^mem:/{print $4} ' userparameter=memory.usage[*],/bin/cat/proc/meminfo | awk '/^$1:/{print $$2} ' Restart Agent Services # service Zabbix-agent restart

(8) Create a host and item in Zabbix Web interface as follows

650) this.width=650; "src=" Http://s4.51cto.com/wyfs02/M00/89/C7/wKioL1gcQ_bD7qeSAADDOEriFps926.png "style=" float: none; "Title=" is created using proxy monitoring host. png "alt=" Wkiol1gcq_bd7qesaaddoerifps926.png "/>

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/89/C7/wKioL1gcQ_eQzeuxAADTAK0aEBE036.png "style=" float: none; "title=" created using proxy monitoring host 2.png "alt=" Wkiol1gcq_eqzeuxaadtak0aebe036.png "/>

Zabbix-agent installation and management of clients within a Windows environment
Installation of clients in Windows environment
1) Create a new directory under the C:\windows directory on the target machine, such as the zabbix--> (bin/conf/logs) directory;

2) Copy (Zabbix_agents_2.0.8.win) file to the created directory;

3) Create a new Zabbix_agentd.log file in the new logs directory;

As shown below:

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/89/C7/wKioL1gcSjSw6C-eAAAnhxvIZRg072.png "style=" float: none; "title=" Windows1.png "alt=" Wkiol1gcsjsw6c-eaaanhxvizrg072.png "/>

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/89/C7/wKioL1gcSjSSHtcgAAAvxHBPJUo128.png "style=" float: none; "title=" Windows2.png "alt=" Wkiol1gcsjsshtcgaaavxhbpjuo128.png "/>

650) this.width=650; "src=" Http://s4.51cto.com/wyfs02/M00/89/CA/wKiom1gcSjXBhk8vAAAqDESoVVk056.png "style=" float: none; "title=" Windows3.png "alt=" Wkiom1gcsjxbhk8vaaaqdesovvk056.png "/>

4) Configure the zabbix_agentd.win.conf file with the following options:

Logfile=c:\windows\zabbix\logs\zabbix_agentd.log
Server=172.16.100.101
Hostname=windows Host

5) Enter the CMD interface on the target machine;
6) Enter the new directory in the CMD interface: CD \windows\zabbix\bin;
7) Enter the following command to install:

>CD c:\windows\zabbix\bin>zabbix_agentd.exe-c C:\WINDOWS\zabbix\conf\zabbix_agentd.win.conf-i

8) in "Run" enter "Services.msc", in the inside find "Zabbixagent", and start the service.

9) Finally in Zabbix Web interface as follows:

650) this.width=650; "src=" Http://s5.51cto.com/wyfs02/M01/89/C8/wKioL1gcVSbSGP8pAABpoFONURM170.png "style=" float: none; "title=" Monitoring Windows Discovery creates a. png "alt=" Wkiol1gcvsbsgp8paabpofonurm170.png "/>

650) this.width=650; "src=" Http://s5.51cto.com/wyfs02/M00/89/C8/wKioL1gcVSez7Ld_AACIbq0zaB0940.png "style=" float: none; "title=" Monitoring Windows Discovery creates 2.png "alt=" Wkiol1gcvsez7ld_aacibq0zab0940.png "/>

650) this.width=650; "src=" Http://s4.51cto.com/wyfs02/M01/89/CA/wKiom1gcVSixLZAUAACASMRb3x4669.png "style=" float: none; "title=" Monitoring Windows Discovery creates 3.png "alt=" Wkiom1gcvsixlzauaacasmrb3x4669.png "/>

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/89/C8/wKioL1gcVSmxIDEUAABNqkgyQJM825.png "style=" float: none; "title=" Monitoring Windows Discovery creates 4.png "alt=" Wkiol1gcvsmxideuaabnqkgyqjm825.png "/>

The above is the Zabbix distributed monitoring application of the automated operation and maintenance tools.

This article is from the "Opensamlee" blog, make sure to keep this source http://gzsamlee.blog.51cto.com/9976612/1869555

Zabbix distributed monitoring application of automatic operation and maintenance tools (V)