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

People's understanding of Zabbix monitoring may stay at the conceptual level, but there is relatively little understanding of the working principle and application scenarios of Zabbix monitoring. Today I will talk to you about the theoretical knowledge of Zabbix monitoring.

Zabbix Overview Zabbix is an enterprise-class open source distributed monitoring solution, an underlying architecture (server side and Agent side) written in C language, which is continuously maintained by a team, the software can be downloaded and used freely, and the operation team makes money by providing technical support for a fee. Zabbix collects data through Cramp S mode, and displays and configures it on the web side through Bamp S mode. The monitored side: the host collects data by installing agent, and the network equipment collects data by SNMP: the server collects the data sent by SNMP and agent, writes it to MySQL database, and then displays it in the front end of web through php+apache. Zabbix operating condition ServerZabbix Server needs to run in LAMP (Linux+Apache+Mysql+PHP) environment with low hardware requirements. The existing agent of Agent basically supports the common OS in the market. SNMP including Linux, HPUX, Solaris, Sun, windows supports all kinds of common network devices Zabbix functions with common commercial monitoring software functions (host performance monitoring, network equipment performance monitoring, database performance monitoring, FTP and other common protocol monitoring, multiple alarm methods, detailed report chart drawing) support automatic discovery of network devices and servers, support distributed Can centrally display and manage distributed monitoring points, strong expansibility, server provides a general interface, can develop and improve all kinds of monitoring. Zabbix advantages and disadvantages open source, no software cost input; Server has low requirements for device performance (actual test environment: virtual machine Redhat EL AS5,2GCPU 1G memory, monitoring 5 devices, CPU utilization is basically kept below 10%, memory surplus is more than 400m); many devices are supported; support distributed centralized management; open interface, strong scalability When the monitored item is larger than the server queue, you can use the passive state. The monitored client actively downloads the item to be monitored from the server and then takes the data to upload to the server. This method puts less load on the server. The disadvantage is not supported by the manufacturer, it is more troublesome to install agent on the monitored host, all the data are stored in the database, the resulting data is very large, and the bottleneck is mainly in the database. The working principle of Zabbix Agentd is installed on the monitored host, and Agent is responsible for collecting local data on the client side regularly and sending it to the Zabbix Server side. 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.). Zabbix 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_getZabbix 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 serverZabbix 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)

The monitoring data of Zabbix distributed monitoring system is submitted to zabbix proxy and then to zabbix server.

Zabbix monitoring architecture in the actual monitoring architecture, zabbix is divided into three kinds of architecture according to the network environment and monitoring scale: server-client, master-node-client, server-proxy-client. Server-client architecture is also the simplest architecture of zabbix. There is no agent between the monitor computer and the monitored computer, and the data exchange is carried out directly between zabbix server and zabbix agentd. It is suitable for monitoring environment where the network is relatively simple and the equipment is relatively few. 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 itself, but 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. Master-node-client architecture this architecture is the most complex monitoring architecture of zabbix, which is suitable for large-scale environments with more devices and across networks and computer rooms. 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.

After reading the above, do you have a general understanding of Zabbix monitoring? If you want to know more about the content of the article, welcome to follow the industry information channel, thank you for reading!

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.