CN109194634B - Zabbix cluster architecture system supporting transverse expansion and application method - Google Patents

Zabbix cluster architecture system supporting transverse expansion and application method Download PDF

Info

Publication number
CN109194634B
CN109194634B CN201810960094.5A CN201810960094A CN109194634B CN 109194634 B CN109194634 B CN 109194634B CN 201810960094 A CN201810960094 A CN 201810960094A CN 109194634 B CN109194634 B CN 109194634B
Authority
CN
China
Prior art keywords
zabbix
server
zabbin
proxy
zookeeper
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201810960094.5A
Other languages
Chinese (zh)
Other versions
CN109194634A (en
Inventor
何慧虹
王勇
樊冬进
郭三川
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
National Computer Network and Information Security Management Center
Original Assignee
National Computer Network and Information Security Management Center
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by National Computer Network and Information Security Management Center filed Critical National Computer Network and Information Security Management Center
Priority to CN201810960094.5A priority Critical patent/CN109194634B/en
Publication of CN109194634A publication Critical patent/CN109194634A/en
Application granted granted Critical
Publication of CN109194634B publication Critical patent/CN109194634B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • H04L67/1097Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/08Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0876Network architectures or network communication protocols for network security for authentication of entities based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • H04L67/1001Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/1004Server selection for load balancing

Abstract

The application provides a Zabbix cluster architecture system supporting transverse expansion and an application method thereof, comprising the following steps: the Zabbin is used for sending identity information of all devices connected with the Zabbin to the Zookeeper, and is also used for: receiving the mapping relation of the identity information of all the devices sent by the Zookeeper; the Zookeeper is used for mapping the received identity information reported by the plurality of Zabbix and then sending the mapped identity information to the corresponding Zabbix; the identity information comprises: the registration ID, the upper management limit and the heartbeat state of each device are deeply integrated with the Zookeeper to manage the mapping relation among the Agent, the Proxy and the Server on the monitored Server, and the conditions of Proxy downtime offline and online again belonging to different Zabbix can be automatically processed by the system without manual intervention, so that the maintenance cost is low.

Description

Zabbix cluster architecture system supporting transverse expansion and application method
Technical field:
the application relates to the field of computer server management, in particular to a Zabbix cluster architecture system supporting transverse expansion and an application method.
The background technology is as follows:
in order to meet the requirements of continuously rising service complexity and continuously expanding scale, and simultaneously ensure high quality of externally provided services, more and more enterprises often introduce various emerging technologies such as cloud platforms, docker technologies and the like to develop, build and operate iterative service systems, so that the scale and the complexity of a distributed system are increased, and the high-efficiency monitoring of the system is also an urgent requirement. Zabbix (Zabbix: bix) is an enterprise-level open source solution providing distributed system monitoring and network monitoring functions based on a WEB interface, is used as an enterprise-level open source distributed monitoring solution, provides multiple functions such as multi-layer monitoring and custom monitoring, and becomes a common scheme for monitoring an enterprise system. However, with the continuous expansion of the monitoring scale, the performance and expansion bottleneck of Zabbix are also increasingly prominent. The Zabbix uses the traditional Mysql as a configuration management database, and the Mysql causes the performance bottleneck of the Mysql database to become the bottleneck of the whole system, which is characterized in that the Zabbix becomes longer when storing the acquired data and reading the monitoring index value and the acquired data item is configured and changed along with the continuous expansion of the monitoring scale, and the overall monitoring performance is greatly reduced.
Currently, enterprises using Zabbix mainly expand the monitoring scale by independently deploying multiple sets of Zabbix, each set of Zabbix being responsible for monitoring a portion of the devices. When the existing Zabbix reaches the upper monitoring limit, a new set of Zabbix is deployed to monitor the rest equipment, and so on. However such a solution presents an important problem: manual or third party intervention is required to record the mapping relationship between Zabbix and the monitored equipment, resulting in excessive maintenance costs in the later stage. For example, since the monitoring device is separately monitored by multiple sets of Zabbix, when the monitoring device is subject to dynamic changes such as offline or relocation, each set of Zabbix needs to be queried to find a corresponding device item for state change. It is even more unavoidable to maintain mid-span Zabbix operations, such as altering data acquisition items of devices of a specified range, while the devices are distributed among multiple sets of Zabbix.
The application comprises the following steps:
to overcome the above drawbacks, the present application provides a Zabbix cluster architecture system supporting lateral expansion, the system comprising: a plurality Zabbix, zookeeper and a plurality of devices;
the Zabbin is used for sending identity information of all devices connected with the Zabbin to the Zookeeper, and is also used for: receiving the mapping relation of the identity information of all the devices sent by the Zookeeper;
the Zookeeper is used for mapping the received identity information reported by the plurality of Zabbix and then sending the mapped identity information to the corresponding Zabbix;
the identity information comprises: the registration ID, upper management limit, and heartbeat status of each device.
Preferably, the Zabbix comprises: zabbix Server, zabbix Proxy and Zabbix Agent;
the Zabbin Server is used for reporting identity information of equipment, distributing agents to Zabbin Proxy, and receiving information sent by Zabbin agents and Zabbin Proxy and mapping relations of the Zabbin Server and the Zabbin Proxy and the Zabbin agents;
the Zabbix Proxy is used for reporting the identity information of the equipment, and is also used for collecting monitoring information and sending the monitoring information to the Zabbix Server and establishing a link with the Zabbix Server;
the Zabbix Agent is used for reporting the registration ID of the equipment, acquiring the identity information of the equipment, sending the identity information to the Zabbix Proxy and the Zabbix Server, and establishing a link with the Zabbix Server.
Preferably, the Zookeeper comprises: a Zookeeper data model tree, a registrar and an allocator;
the Zookeeper data model tree is used for registering the equipment identity information reported by the Zabbix, creating a data node of the equipment identity information, and recording the mapping relation between the Zabbix Server and the Zabbix Proxy and between the Zabbix Server and the Zabbix Agent;
the register is used for receiving the equipment identity information reported by the Zabbix Server, the Zabbix Proxy and the Zabbix Agent and registering the equipment identity information to the Zookeeper data model tree;
the distributor is used for processing the equipment identity information on the Zookeeper data model tree according to the minimum load and the latest registration algorithm to obtain Zabbin Server and Zabbin Proxy and the mapping relation between Zabbin Server and Zabbin Agent, and distributing the mapping relation between Zabbin Server and Zabbin Proxy and Zabbin Agent to Zabbin Server.
Preferably, the Zookeeper further comprises: a status monitor;
the state monitor is used for monitoring the heartbeat state of the equipment reported by the Zabbix Server and the Zabbix Proxy at preset time intervals;
the state monitor is further configured to mark the zabbin Server corresponding to the device as unavailable when the state monitor does not receive the heartbeat state of the device reported by the zabbin Server within a certain time, and meanwhile, the allocator of the Zookeeper does not allocate the zabbin Server and the zabbin Proxy corresponding to the device and the mapping relation between the zabbin Server and the zabbin Agent to the zabbin Server;
when the state monitor does not receive the heartbeat state of the equipment reported by the Zabbix Proxy within a certain time and does not replace the equipment with a new Proxy, the allocator of the Zookeeper interrupts the mapping relation between the Zabbix Proxy corresponding to the equipment and the Zabbix Server and notifies the Zabbix Server; distributing the Agent by Zabbix Agent to other Proxy
The heartbeat state includes: online, offline, and unknown.
Preferably, the Zabbix Server further comprises an Agent manager;
the Agent manager is used for distributing management agents for each Zabbix Proxy according to the connection relation between the Zabbix Proxy and the agents.
A method of application of a Zabbix cage supporting lateral expansion, the method comprising:
acquiring equipment identity mark information of each Zabbix connection;
registering the acquired equipment identity mark information of each Zabbix connection on a Zookeeper data model tree, and processing the identity mark information on the data model tree to obtain a mapping relation;
and distributing the mapping relation into Zabbix.
Preferably, the registering the acquired zabbin identity information on the Zookeeper data model tree, and processing the identity information on the Zookeeper data model tree to obtain a mapping relationship, includes:
registering the acquired Zabbix identity mark information on a data model tree through a registrar in a Zookeeper;
and the distributor in the Zookeeper processes the identity information on the data model tree according to the minimum load and the latest registration algorithm to obtain Zabbix Server and Proxy and the mapping relation of the Server and Agent.
Preferably, the allocating the mapping relationship to Zabbix includes:
and distributing the mapping relation to the Zabbix servers in the Zabbix by a distributor in the Zookeeper based on the obtained Zabbix servers and Proxy and the mapping relation of the servers and agents.
Preferably, the allocating the mapping relationship to Zabbix further includes: a status monitor;
when the Zabbix Server in the heartbeat information transmitted by the state monitor exceeds a preset time without heartbeat, the registrar marks the Zabbix Server as unavailable, and the distributor does not distribute the mapping relation of Proxy and Agent to the Zabbix Server;
when the Zabbix Proxy in the heartbeat information transmitted by the state monitor has no heartbeat beyond the preset time and no new Proxy is displaced within the preset time, the distributor interrupts the mapping relation between the Proxy and the Server, notifies the Server, and distributes the Agent to other Proxy by the Agent Server.
Compared with the prior art, the application has the following beneficial effects:
1. the application provides a cluster architecture supporting transverse expansion and an application method thereof, wherein Zabbix is used for sending identity information of all devices connected with the Zabbix to a Zookeeper and is also used for: receiving the mapping relation of the identity information of all the devices sent by the Zookeeper; the Zookeeper is used for mapping the received identity information reported by the plurality of Zabbix and then sending the mapped identity information to the corresponding Zabbix; the Zookeeper is deeply integrated to manage the mapping relation among the agents, proxy and Server on the monitored Server, and the situations of Proxy downtime offline and online again belonging to different Zabbix can be automatically processed by the system without manual intervention, so that the maintenance cost is low.
2. The cluster architecture and the application method supporting the transverse expansion can support operation and maintenance personnel to quickly adjust daily operations such as acquisition configuration items, state identifiers and the like of server clusters managed by different ZabbixServers, and the overall detection performance is greatly improved, so that the overall management efficiency of Zabbix and the efficiency of cross-Zabbix operation are improved.
Description of the drawings:
FIG. 1 is a diagram of the overall architecture of Zabbix and Zookeeper depth integration of the present application;
FIG. 2 is a diagram of the major elements of the data model tree of the present application and their relationships;
FIG. 3 is a main element diagram of a data model in the Zookeeper of the present application;
fig. 4 is a communication flow of the Zabbix main module and the Zookeeper of the application.
The specific embodiment is as follows:
for a better understanding of the present application, the technical solutions of the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments.
Example 1:
as shown in fig. 1, the present application proposes a zabbin architecture supporting lateral expansion, which reforms and encapsulates zabbin at an acquisition end and a display end, and simultaneously supports multiple sets of zabbin deployment and simultaneously shields multiple sets of independent zabbin modes therebetween, thereby improving the overall management efficiency of zabbin. According to the method, the Zabbin is deeply integrated with the Zabbin, the Zabbin main module connection related configuration items are efficiently managed by utilizing the Zabbin registration and management function, and the Zabbin records the Agent-Proxy-Zoobin-Server mapping relation on the monitored equipment, so that the efficiency of Zabbin crossing operation is improved. The method comprises the following steps:
the Zabbin is used for sending identity information of all devices connected with the Zabbin to the Zookeeper, and is also used for: receiving the mapping relation of the identity information of all the devices sent by the Zookeeper;
the Zookeeper is used for mapping the received identity information reported by the plurality of Zabbix and then sending the mapped identity information to the corresponding Zabbix.
Aiming at the mapping relation between each independent management and Proxy of a plurality of sets of Zabbix and agents, the application designs and realizes a set of reasonable data model tree in the Zookeeper, and supports each Zabbix to efficiently read and write the connection configuration items of the Zabbix to the Zookeeper, thereby providing a foundation for unified management of the Zabbix mapping relation of the Zookeeper.
Aiming at the problem that the connection relation between the Zabbix main module and the upper level/lower level is difficult to support by a static configuration file mode, the Zabbix key module is transformed to integrate the Zookeepers therebetween, so that a plurality of sets of Zabbix are uniformly uploaded from the Zookeepers to acquire the connection relation, and the overall architecture of the Zabbix key module is shown in figure 1. The left side of the figure is a reconstructed Zookeeper, and three modules of a register, a distributor and a state monitor are added on the basis of a Zookeeper core module. The right side of the figure is the reformed Zabbix, and the figure shows that the application reforms the three core modules ZabbixServer, proxy and Agent, wherein an Agent manager module is newly added in a Server module. The Zookeeper register module receives identity related information actively reported by the Zabbix Server, proxy and Agent modules and registers the information on the data model tree. The distributor processes the information on the data model tree according to the related algorithms such as the minimum load, the latest registration and the like, outputs the mapping relation between the Zabbix Server and the Proxy and the mapping relation between the Server and the Agent, and distributes the relations to the Zabbix related modules, namely the Agent manager in the Zabbix Server distributes the Agent to be managed for each Proxy. In the monitoring process, the Zabbix Server and Proxy can report heartbeat information to a Zookeeper state monitor at regular time, a register and a distributor are used for processing special conditions, when the Zabbix Server has no heartbeat for a long time, the register can mark the state as unavailable, and the distributor can not map the Proxy and the Agent registered later to the Server; when the Proxy has no heartbeat for a long time and no new Proxy is replaced during the period, the distributor interrupts the mapping relation between the Proxy and the Server and notifies the Server, and the Agent management module distributes the 'unconnected' agents to the rest of the Proxy. The method comprises the following steps:
as shown in fig. 2, the main elements of the data model tree and their relationships in the Zookeeper are shown. The Server domain is used for representing Zabbix Server information and comprises an identity mark of a Server, an allocated Proxy set, a heartbeat state of the Server and an allocated Agent set. The heartbeat state mainly comprises three states of online state, offline state and unknown state, and is updated by a state monitor. The Proxy is used for representing Zabbix Proxy information, and comprises the identity mark of the Proxy, the identity mark information of the Server and the heartbeat state of the Server. The Agent is used for representing Zabbix Agent information, and comprises an identity mark of the Agent and identity mark information of a Server to which the Agent belongs.
As shown in fig. 3, the main elements of the data model tree structure maintained by the Zookeeper at run-time are shown. Wherein, PSPair is used for recording the distribution relation between Zabbix Server and Proxy, SAPair is used for recording the distribution relation between ZabbixServer and Agent-created and filled by the distributor. ASPair is used for reversely recording the mapping relation between the agents and the Server, so that efficient reverse query is supported, and the operation of the Agent set crossing Zabbix is accelerated. When there is a new Agent registration, a new data node is created under the path. SState and PState are used to record the heartbeat status information of Zabbix Server and Proxy-when there is a new Zabbix or Proxy registration, a data node is created under the corresponding path, and thereafter updated periodically by the status monitor.
As shown in fig. 4, the main communication flow of the Zookeeper and zadbix main modules is shown, and the main communication flow mainly comprises three links of registration, allocation and status update. In the registration link, after the Zabbix main module is on line, the Zabbix main module actively transmits self-sign related information to the register, and the Server and the Proxy additionally transmit a management upper limit field which indicates the maximum number of the mapping agents which can be supported. In the distribution link, the Zookeeper distributor distributes Proxy and Agent for the least loaded Server preferentially according to the minimum load algorithm, and then an Agent manager in the Server distributes Agent for each Proxy, thereby realizing the Server-Proxy-Agent secondary link relation. In the state updating link, the Server and the Proxy periodically send heartbeat information to the Zabbix state monitor, when the state monitoring exceeds the specified times and the Server/Proxy heartbeat information is not received, the Server/Proxy is marked as offline, the distributor stops distributing new Proxy and Agent for the offline Server, deletes the offline Proxy and the mapping relation between the offline Proxy and the Server, informs an Agent manager in a Server module, and distributes the Agent managed by the offline Proxy to other Proxy.
Based on the same inventive concept, the application also provides an application method of the Zabbix cluster frame supporting the transverse expansion, wherein the method comprises the following steps:
acquiring equipment identity mark information of each Zabbix connection;
registering the acquired equipment identity mark information of each Zabbix connection on a Zookeeper data model tree, and processing the identity mark information on the data model tree to obtain a mapping relation;
and distributing the mapping relation into Zabbix.
Registering the acquired Zabbin identity mark information on a Zookeeper data model tree, and processing the identity mark information on the Zookeeper data model tree to obtain a mapping relation, wherein the method comprises the following steps of:
registering the acquired Zabbix identity mark information on a data model tree through a registrar in a Zookeeper;
and the distributor in the Zookeeper processes the identity information on the data model tree according to the minimum load and the latest registration algorithm to obtain Zabbix Server and Proxy and the mapping relation of the Server and Agent.
The allocation of the mapping relation to the Zabbix comprises the following steps:
and distributing the mapping relation to the Zabbix servers in the Zabbix by a distributor in the Zookeeper based on the obtained Zabbix servers and Proxy and the mapping relation of the servers and agents.
The allocation of the mapping relationship to the Zabbix further includes: a status monitor;
when the Zabbix Server in the heartbeat information transmitted by the state monitor exceeds a preset time without heartbeat, the registrar marks the Zabbix Server as unavailable, and the distributor does not distribute the mapping relation of Proxy and Agent to the Zabbix Server;
when the Zabbix Proxy in the heartbeat information transmitted by the state monitor has no heartbeat beyond the preset time and no new Proxy is displaced within the preset time, the distributor interrupts the mapping relation between the Proxy and the Server, notifies the Server, and distributes the Agent to other Proxy by the Agent Server.
It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and block diagrams of methods, systems, and computer program products according to embodiments of the application. It will be understood that each flowchart and block of the flowchart and block diagrams, and combinations of flowcharts and block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and block diagram block or blocks.
The foregoing is illustrative of the present application and is not to be construed as limiting thereof, but rather as providing for the use of additional embodiments and advantages of all such modifications, equivalents, improvements and similar to the present application are intended to be included within the scope of the present application as defined by the appended claims.

Claims (8)

1. A Zabbix cluster architecture system supporting lateral expansion, the system comprising: a plurality Zabbix, zookeeper and a plurality of devices;
the Zabbix is used for monitoring the equipment;
the Zabbix comprises: zabbix Server, zabbix Proxy and Zabbix Agent;
the Zabbix Server, zabbix Proxy and Zabbix Agent send respective identity information to the Zookeeper;
the Zabbix Server is also used for receiving the mapping relation between the Zabbix Server and the Zabbix Proxy sent by the Zookeeper;
the Zookeeper is used for mapping the received identity information reported by the plurality of Zabbix and then sending the mapped identity information to the corresponding Zabbix;
the identity information reported by the Zabbix Server and the Zabbix Proxy comprises: registration ID and upper management limit.
2. The zaybix cluster architecture system supporting lateral expansion of claim 1, wherein the zaybix Server is further configured to allocate agents to zaybix Proxy, receive information sent by the zaybix agents and the zaybix Proxy;
the Zabbix Proxy is also used for collecting monitoring information and sending the monitoring information to the Zabbix Server and establishing a link with the Zabbix Server;
the Zabbix Agent is also used for acquiring identity information of equipment, sending the identity information to the Zabbix Proxy and the Zabbix Server, and establishing a link with the Zabbix Server;
the Zabbix Server also comprises an Agent manager;
the Agent manager is used for distributing management agents for each Zabbix Proxy according to the connection relation between the Zabbix Proxy and the agents.
3. The Zabbix cluster architecture system supporting lateral expansion of claim 2, wherein the Zookeeper comprises: a Zookeeper data model tree, a registrar and an allocator;
the Zookeeper data model tree is used for registering identity information reported by the Zabbin Server, the Zabbin Proxy and the Zabbin Agent, creating a data node containing the identity information, and recording the mapping relation between the Zabbin Server, the Zabbin Proxy and the Zabbin Server and the Zabbin Agent;
the register is used for receiving the identity information reported by the Zabbix Server, the Zabbix Proxy and the Zabbix Agent and registering the identity information to the Zookeeper data model tree;
the distributor is used for processing the identity information on the Zookeeper data model tree according to the minimum load and the latest registration algorithm to obtain Zabbin servers and Zabbin Proxy and the mapping relation between the Zabbin servers and the Zabbin agents, and distributing the mapping relation between the Zabbin servers and the Zabbin Proxy and the mapping relation between the Zabbin servers and the Zabbin agents to the Zabbin servers.
4. The Zabbix cluster architecture system supporting lateral expansion of claim 3, wherein the Zookeeper further comprises: a status monitor;
the state monitor is used for monitoring the heartbeat state of the equipment reported by the Zabbix Server and the Zabbix Proxy at preset time intervals;
the state monitor is further configured to mark a zabbin Server corresponding to the device as unavailable when the state monitor does not receive a heartbeat state of the device reported by the zabbin Server within a certain time, and meanwhile, the allocator of the Zookeeper does not allocate the zabbin Server and zabbin Proxy corresponding to the device and a mapping relationship between the zabbin Server and zabbin Agent to the zabbin Server;
when the state monitor does not receive the heartbeat state of the equipment reported by the Zabbix Proxy within a certain time and does not replace the equipment with a new Proxy, the allocator of the Zookeeper interrupts the mapping relation between the Zabbix Proxy corresponding to the equipment and the Zabbix Server and notifies the Zabbix Server; distributing the Zabbix Proxy managed agents to other Zabbix Proxy by an Agent manager;
the heartbeat state includes: online, offline, and unknown.
5. An application method of a Zabbix cluster frame supporting transverse expansion, wherein the Zabbix comprises: zabbix Server, zabbixProxy and Zabbix Agent; characterized in that the method comprises:
the Zabbix Server, zabbix Proxy and Zabbix Agent send respective identity information to the Zookeeper; registering the acquired equipment identity information of each Zabbix connection on a Zookeeper data model tree, and processing the identity information on the data model tree to obtain a mapping relation;
the mapping relation is the mapping relation of Zabbix Server and Zabbix Proxy and Zabbix Agent;
and distributing the mapping relation to the Zabbix Server.
6. The method of claim 5, wherein the method comprises the steps of,
and the distributor in the Zookeeper processes the identity information on the data model tree according to the minimum load and the latest registration algorithm to obtain Zabbix Server and Zabbix Proxy and the mapping relation of the Zabbix Server and the Agent.
7. The method for applying the Zabbix cluster architecture supporting lateral expansion of claim 6, wherein the allocating the mapping relationship to the Zabbix Server comprises:
and the allocator in the Zookeeper allocates the mapping relation to the Zabbix servers in the Zabbix.
8. The method for applying Zabbin cluster architecture supporting lateral expansion as claimed in claim 7, wherein said allocating said mapping relation to Zabbin Server further comprises when a state listener in Zookeeper does not receive heartbeat information transmitted by Zabbin Server within a preset time, the registrar marking said Zabbin Server as unavailable, and said allocator not allocating Zabbin Server and Zabbin Proxy and the mapping relation of Zabbin Proxy and Zabbin Agent to Zabbin Server;
when the state monitor does not receive heartbeat information transmitted by the Zabbin Proxy and does not replace the new Zabbin Proxy in preset time, the distributor interrupts the mapping relation between the Zabbin Proxy and the Zabbin Server and notifies an Agent manager in the Zabbin Server to distribute the agents managed by the Zabbin Proxy to other Zabbin Proxy.
CN201810960094.5A 2018-08-22 2018-08-22 Zabbix cluster architecture system supporting transverse expansion and application method Active CN109194634B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201810960094.5A CN109194634B (en) 2018-08-22 2018-08-22 Zabbix cluster architecture system supporting transverse expansion and application method

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201810960094.5A CN109194634B (en) 2018-08-22 2018-08-22 Zabbix cluster architecture system supporting transverse expansion and application method

Publications (2)

Publication Number Publication Date
CN109194634A CN109194634A (en) 2019-01-11
CN109194634B true CN109194634B (en) 2023-10-13

Family

ID=64919054

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201810960094.5A Active CN109194634B (en) 2018-08-22 2018-08-22 Zabbix cluster architecture system supporting transverse expansion and application method

Country Status (1)

Country Link
CN (1) CN109194634B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112804291B (en) * 2020-12-21 2022-07-12 武汉虹旭信息技术有限责任公司 Remote equipment auditing method, device and system

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107070744A (en) * 2017-03-22 2017-08-18 上海合志信息技术有限公司 Server monitoring method
CN108111630A (en) * 2018-01-22 2018-06-01 北京奇艺世纪科技有限公司 A kind of Zookeeper group systems and attaching method thereof and system

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107070744A (en) * 2017-03-22 2017-08-18 上海合志信息技术有限公司 Server monitoring method
CN108111630A (en) * 2018-01-22 2018-06-01 北京奇艺世纪科技有限公司 A kind of Zookeeper group systems and attaching method thereof and system

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
分布式环境下基于Zookeeper服务的数据同步研究;何慧虹 等;《中国计算机学会计算机安全专业委员会会议论文集》;20150917(第9期);全文 *

Also Published As

Publication number Publication date
CN109194634A (en) 2019-01-11

Similar Documents

Publication Publication Date Title
CN112073265B (en) Internet of things monitoring method and system based on distributed edge computing
CN103685486B (en) Distributed system monitoring method stepping over data center clusters and system
CN106817408B (en) Distributed server cluster scheduling method and device
CN108282514B (en) Distributed service establishing method and device
CN102984012B (en) Management method and system for service resources
CN109739919B (en) Front-end processor and acquisition system for power system
CN102215123B (en) Multi-ring-network-topology-structure-based large-scale trunking system
CN105049268A (en) Distributed computing resource allocation system and task processing method
CN102882705B (en) Method for reporting log through terminal equipment and log reporting system
CN104202383A (en) Centralized configuration distribution and management method in distributed cluster environment
US10868581B2 (en) Data center management using device identification over power-line
CN103118130A (en) Cluster management method and cluster management system for distributed service
CN111966289A (en) Partition optimization method and system based on Kafka cluster
CN104270434A (en) Service state monitoring system based on cloud service
CN105827678B (en) Communication means and node under a kind of framework based on High Availabitity
CN111045811A (en) Task allocation method and device, electronic equipment and storage medium
CN104537045A (en) Service distribution method and device based on distributive system
CN105007311A (en) System and method for resource management based on cloud platform and cloud computing
CN103049527A (en) Large power grid oriented parallel real-time database master and slave switching management system
CN110855481B (en) Data acquisition system and method
CN109194634B (en) Zabbix cluster architecture system supporting transverse expansion and application method
CN106993022B (en) Identification management method for cluster, identification server and corresponding system
CN110519354A (en) A kind of distributed objects storage system and its method for processing business and storage medium
CN110795202B (en) Resource allocation method and device of virtualized cluster resource management system
CN113824801B (en) Intelligent integration terminal unified access management component system

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant