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

How does zabbix work? What is zabbix's surveillance system? In general, everyone's understanding of zabbix monitoring may stay at the conceptual level, while there is relatively little knowledge about the working principle of zabbix. Today with zabbix operating conditions, working principles and monitoring system.

profile

Zabbix is an enterprise-class open source distributed monitoring solution, written in C language, the underlying architecture (server side and agent side) is continuously maintained and updated by a team, the software can be downloaded freely, and the operating team earns money by providing technical support for a fee.

1. Zabbix collects data through C/S mode, and displays and configures it on the web side through B/S mode.

2, monitored end: the host through the installation of agent data collection, network equipment through SNMP data collection

Server side: Collect data sent by SNMP and agent, write it to MySQL database, and then display it on the web front end 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, Agent** Currently existing agents basically support common OS in the market, including Linux, HPUX, Solaris, Sun, windows, etc. **3, SNMP** Support various common network devices working principle

Agentd is installed on the monitored host. Agent is responsible for regularly collecting local data from the client and sending it to Zabbix Server. Zabbix Server receives the data and stores the data in the database. Users can see the data displayed on the front end based on Zabbix WEB. When Zabbix monitors a specific item, it sets a trigger threshold. When the monitored indicator exceeds the trigger threshold, it will take some necessary actions, including sending messages (email, WeChat, SMS) and sending commands (SHELL command, Reboot, Restart, Install, etc.).

Active mode: The agent side actively collects information and sends it to the server side. The tool is zabbix_sender. Passive mode: The server side actively pulls information. The tool is zabbix_get. Role component Zabbix agent: responsible for deploying on the monitored host and transmitting the monitored host data to zabbix serverZabbix server: responsible for receiving information sent by the agent, organizing configuration information, counting configuration information and operation data. Zabbix database: database for storing all configuration information of zabbix and monitoring data. Zabbix web: zabbix web interface, management can manage zabbix configuration and view zabbix monitoring information through zabbix web interface, can be deployed independently on a server Zabbix proxy: used in distributed environment, zabbix proxy on behalf of the server side manages information collection in the area, and finally unified to zabbix server Communication agent: monitoring through dedicated agent ssh/Telnet: communication through remote control protocol SNMP: Communication with monitored objects via SNMP protocol, routers and switches support SNMP, which is actually an agentIPMI: monitoring via IPMI interface, monitoring via IPMI hardware interface, voltage, temperature, fan, and power status JMX: monitoring JVM virtual machines via Java management extensions

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

Monitoring architecture

In the actual monitoring architecture, zabbix divides 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 zabbix's simplest architecture, between the monitor and monitored machine without any agent, directly by zabbix server and zabbix agentd data interaction. Suitable for monitoring environment with simple network and few equipment. ** 2, server-proxy-client architecture ** where proxy is a bridge between server and client communication, proxy itself has no front end, and it does not store data itself, but temporarily stores the data sent by agentd, and then submits it to the server. This architecture is often compared to master-node-client architecture and is generally suitable for monitoring medium-sized network architectures across computer rooms and networks. ** 3, master-node-client architecture ** This architecture is zabbix's most complex monitoring architecture, suitable for cross-network, cross-room, large-scale environment with more equipment. Each node is also a server, node can be connected to proxy, can also be directly connected to client. A node has its own configuration files and databases, and all it has to do is synchronize configuration information and monitor data to the master, and master failures or corruptions to the integrity of the node's underlying architecture.

After reading the above, do you have any further understanding of zabbix monitoring? If you still want to learn more skills or want to know more related content, welcome to pay attention to 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.