Shulou(Shulou.com)06/02 Report--

Brief introduction

Zabbix is an enterprise-level open source distributed monitoring solution, which is an underlying architecture written in C language (server side and Agent side). Updates are continuously maintained by a team, the software can be downloaded and used freely, and the operation team makes a profit by providing paid technical support.

1. Zabbix collects data through Cramp S mode, and displays and configures it on the web side through Bamp S mode.

2. The monitored side: the host collects data by installing agent, and the network equipment collects data by SNMP.

3. Server side: by collecting the data sent by SNMP and agent, writing it to MySQL database, and then displaying it in the front end of web through php+apache.

Zabbix operating conditions * * 1. Server**Zabbix Server needs to run in LAMP (Linux+Apache+Mysql+PHP) environment with low hardware requirements * * 2. The existing agent of Agent** basically supports common OS in the market, including Linux, HPUX, Solaris, Sun, windows, etc. * 3. SNMP** supports all kinds of common network equipment working principles.

Agentd is installed on the monitored host, and Agent is responsible for collecting local data on the client side regularly and sending it to Zabbix Server. Zabbix Server receives the data and stores the data in the database. Users can see the data showing the image at the front end based on Zabbix WEB. When Zabbix monitors a specific project, the modified project will set a trigger threshold. When the monitored index exceeds the threshold set by the trigger, it will take some necessary actions, including: sending messages (email, Wechat, SMS), sending commands (SHELL commands, Reboot, Restart, Install, etc.).

Working mode active mode: the agent side actively collects information and sends it to the server side tool is the zabbix_sender passive mode; the server side active pull information tool is the zabbix_get role component Zabbix agent: responsible for deploying on the monitored host, transmitting the data of the monitored host to zabbix serverZabbix server: responsible for receiving the information sent by agent, organizing configuration information Zabbix database, such as statistical configuration information and operation data: used to store all configuration information of zabbix, database of monitoring data Zabbix web: web interface of zabbix, management can manage zabbix configuration and view monitoring information of zabbix through web interface of zabbix, can be deployed on a single server Zabbix proxy: used in distributed environment, zabbix proxy manages information collection in this area on behalf of server Finally, it is uniformly sent to zabbix server communication mode agent: monitor through dedicated agents: communicate through remote control protocol SNMP: communicate with monitored objects through SNMP protocol, routers and switches support SNMP, but it is also a kind of agentIPMI: monitoring through IPMI interface, monitoring through IPMI hardware interface, voltage, temperature, fan. And Power status JMX: monitor JVM virtual machines through (java management extensions Java Management extension)

Zabbix distributed monitoring system * * Monitoring data is submitted to zabbix proxy and then to zabbix server**

Monitoring architecture

In the actual monitoring architecture, zabbix is divided into three architectures according to the network environment and monitoring scale: server-client, master-node-client and server-proxy-client.

* * 1. Server-client architecture * * is also the simplest architecture of zabbix. Data is exchanged directly between zabbix server and zabbix agentd without any agent between the monitor and the monitored computer. It is suitable for monitoring environment where the network is relatively simple and the equipment is relatively few. * * 2. Server-proxy-client architecture * * in which proxy is a bridge between server and client. Proxy itself does not have a front end, and it does not store data. It only temporarily stores the data sent by agentd, and then submits it to server. This architecture is often compared with the master-node-client architecture, and is generally suitable for the monitoring of medium-sized network architecture across computer rooms and networks. * * 3. Master-node-client architecture * * this architecture is the most complex monitoring architecture of zabbix, and is suitable for large-scale environments with more devices across networks and data centers. Each node is also a server, which can be connected to proxy or client directly under node. Node has its own configuration file and database, and what it needs to do is to synchronize configuration information and monitoring data to master. The failure of master may damage the integrity of the underlying architecture of node.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.