WO2019153532A1 - 监控系统的部署方法、装置、计算机设备及存储介质 - Google Patents

监控系统的部署方法、装置、计算机设备及存储介质 Download PDF

Info

Publication number
WO2019153532A1
WO2019153532A1 PCT/CN2018/084709 CN2018084709W WO2019153532A1 WO 2019153532 A1 WO2019153532 A1 WO 2019153532A1 CN 2018084709 W CN2018084709 W CN 2018084709W WO 2019153532 A1 WO2019153532 A1 WO 2019153532A1
Authority
WO
WIPO (PCT)
Prior art keywords
preset
component
deployment
monitoring system
monitoring
Prior art date
Application number
PCT/CN2018/084709
Other languages
English (en)
French (fr)
Inventor
高泗俊
Original Assignee
平安科技（深圳）有限公司
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 平安科技（深圳）有限公司 filed Critical 平安科技（深圳）有限公司
Publication of WO2019153532A1 publication Critical patent/WO2019153532A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • G06Q10/063—Operations research, analysis or management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
    • G06F11/3013—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system is an embedded system, i.e. a combination of hardware and software dedicated to perform a certain function in mobile devices, printers, automotive or aircraft systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
    • G06F11/3006—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
    • G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3089—Monitoring arrangements determined by the means or processing involved in sensing the monitored data, e.g. interfaces, connectors, sensors, probes, agents
    • G06F11/3093—Configuration details thereof, e.g. installation, enabling, spatial arrangement of the probes
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/20—Administration of product repair or maintenance
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3065—Monitoring arrangements determined by the means or processing involved in reporting the monitored data

Definitions

  • the present application relates to the field of computer technologies, and in particular, to a method, an apparatus, a computer device, and a storage medium for deploying a monitoring system.
  • monitoring systems for operation and maintenance on the market, such as Zabbix monitoring system and Open-falcon monitoring system.
  • monitoring systems are required to monitor these products in real time.
  • These monitoring systems generally include more than 30 component modules.
  • it is necessary to ensure the high availability of each component module to ensure the operating efficiency and monitoring quality of the entire monitoring system.
  • some management tools are used to quickly and easily deploy the monitoring system, such as Ansible tools, but this simple deployment method reduces the system availability and monitoring efficiency of the monitoring system.
  • the operation and maintenance complexity is improved, and the customer's demand for the monitoring system cannot be met.
  • the application provides a method, a device, a computer device and a storage medium for deploying a monitoring system, aiming at improving the availability of the monitoring system.
  • the application provides a method for deploying a monitoring system, including: acquiring component information of the monitoring system; and deploying the monitoring system in multiple preset deployment areas according to the component information according to a preset deployment rule. Deploying a preset monitoring tool in each of the preset deployment areas, wherein the preset monitoring tool is used to monitor the monitoring system; and monitoring the monitoring system by the preset monitoring tool to complete Deployment of the monitoring system.
  • the present application provides a device for deploying a monitoring system, including: an information acquiring unit, configured to acquire component information of the monitoring system; and a system deployment unit, configured to follow a preset deployment rule according to the component information.
  • the monitoring system is deployed in a plurality of preset deployment areas; the tool deployment unit is configured to deploy a preset monitoring tool in each of the preset deployment areas, where the preset monitoring tool is used to monitor the monitoring system; And a system monitoring unit, configured to monitor the monitoring system by using the preset monitoring tool to complete deployment of the monitoring system.
  • the present application also provides a computer device including a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor implementing the program
  • a computer device including a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor implementing the program
  • the present application also provides a storage medium, wherein the storage medium stores a computer program, the computer program comprising program instructions, the program instructions, when executed by a processor, causing the processor to execute the application A method of deploying the monitoring system of any of the foregoing.
  • a preset monitoring tool is also deployed to monitor the monitoring system when the monitoring system performs monitoring, thereby implementing dual monitoring and improving the monitoring. High availability of the system.
  • FIG. 1 is a schematic flowchart of a method for deploying a monitoring system according to an embodiment of the present application
  • FIG. 2 is a schematic flow chart showing the sub-steps of the deployment method of the monitoring system of FIG. 1;
  • FIG. 3 is a schematic flow chart showing the sub-steps of the deployment method of the monitoring system of FIG. 1;
  • FIG. 4 is a schematic diagram of the effect of the monitoring system layout provided by the embodiment of the present application.
  • FIG. 5 is a schematic flow chart showing sub-steps of the deployment method of the monitoring system of FIG. 1;
  • FIG. 6 is a schematic flow chart showing another sub-step of the method for deploying the monitoring system of FIG. 1;
  • FIG. 7 is a schematic block diagram of a deployment apparatus of a monitoring system according to another embodiment of the present application.
  • FIG. 8 is a schematic flow chart showing sub-steps of the method for deploying the monitoring system of FIG. 7;
  • FIG. 9 is a schematic flow chart showing sub-steps of the method for deploying the monitoring system of FIG. 7;
  • FIG. 10 is a schematic block diagram of a device for deploying a monitoring system according to an embodiment of the present application.
  • FIG. 11 is a schematic block diagram of a deployment apparatus of a monitoring system according to another embodiment of the present application.
  • FIG. 12 is a schematic block diagram of a computer device according to an embodiment of the present application.
  • FIG. 1 is a schematic flowchart of a method for deploying a monitoring system according to an embodiment of the present application. As shown in FIG. 1, the deployment method of the monitoring system includes steps S101 to S104.
  • the monitoring system is a monitoring system based on the secondary development of the Open-falcon monitoring system, and is called an Argus monitoring system.
  • the Argus monitoring system also includes a plurality of component modules, each component module performing different functions, such as an Agent component module, which is responsible for collecting machine performance data; a Transfer component module is responsible for data forwarding services, etc., different component modules have different functions and complete different functions. task.
  • Obtaining component information of the monitoring system specifically acquiring component information of a component module of the monitoring system.
  • the component information includes identifier information of component modules, component function information, API interface information, and the like. It can be understood that the monitoring system can also be other monitoring systems, such as Zabbix monitoring system and Open-falcon monitoring system.
  • the monitoring system is deployed in multiple preset deployment areas according to the preset information according to the component information.
  • the preset deployment area includes a central deployment area and a non-central deployment area.
  • the preset deployment area is an area where the user needs to deploy the monitoring system, and a server is set in the area to deploy the monitoring system to the server in the area to implement monitoring of other Internet products.
  • the preset deployment area may be a city of one country, a few areas of a city, or a different office location of a company.
  • step S102 includes sub-steps S1021 to S1023.
  • the component information includes component function information and API interface information, and the plurality of component modules are divided into a central component group and a non-central component group according to the preset component according to the component information, specifically according to the component information.
  • the component function information and the API interface information are divided into the component modules.
  • step S1021 includes sub-steps: S1021a to S1021d.
  • S1021a determining, according to the component function information, whether the component module needs to store information centrally, and determining, according to the API interface information, whether the component module needs to expose a unified API interface
  • S1021b if the component module needs to store information centrally And dividing the component module into the central component group
  • S1021c if the component module needs to expose a unified API interface, dividing the component module into the central component group
  • S1021d if the component The module does not need to centrally store information and does not need to expose a unified API interface, and then divides the component module into the non-central component group.
  • both the alarm component module and the redis component module need to centrally manage alarm data, so centralized storage of information is required; the mysql component module is used to centrally store configuration data, and also needs to store information centrally; therefore, the alarm component module, the redis component module, and The mysql component modules belong to the central component group.
  • the web component module needs to provide page access and API access, so the unified API interface is exposed; the query-proxy component module needs a unified entry for querying performance data, so the unified API interface is also exposed; so the web component module and the query-proxy Component modules also belong to the central component group.
  • the transfer component module that processes the performance data forwarding filter
  • the graph component module that stores the performance data
  • the judge component module that is the alarm judgment
  • the query component module that is responsible for the performance data query of the region
  • the meta component that is delivered by the agent version.
  • these component modules are basically distributed deployment, each area is managed independently, so there is no need to centrally store information or expose a unified API interface, so component modules such as transfer, graph, judge, query, and meta are all A non-central component group.
  • the component modules belonging to the non-central component group are deployed in the central deployment area and the non-central deployment area according to a preset logical partition, wherein the preset logical partition includes: an available area, a public service area, and a cloud management area.
  • the step S1022 includes: acquiring a preset relationship table, where the preset relationship table includes a correspondence between the component modules belonging to the non-central component group and the available area, the public service area, and the cloud management area;
  • the preset relationship table respectively allocates component modules belonging to the non-central component group in the available area, the public service area, and the cloud management area.
  • the preset logical partition adopts a three-layer architecture, and is divided into an available area, a public service area, and a cloud management area from the bottom to the top. Deployed according to the capabilities of the component modules, component modules with different functions are deployed in different areas. Corresponding relationship between the component modules belonging to the non-central component group and the available area, the public service area, and the cloud management area may be set by using a preset relationship table, and the non-central component group belonging to the non-central component group may be configured according to the corresponding relationship during deployment. Different component modules are respectively deployed in the available area, the public service area, and the cloud management area.
  • the corresponding component module that collects and reports the host information is deployed in the available area.
  • the agent module component is deployed in the public service area; the gateway component module and the proxy component module are used to process performance data, alarm data, or issue
  • the instructions are deployed in the cloud management area; component modules such as transfer, judge, graph, redis, mysql, and alarm are also deployed in the cloud management area.
  • the component modules belonging to the non-central component group are deployed in the central deployment area and the non-central deployment area according to a preset logical partition, so that the function division of the monitoring system is more clear; and also has better security.
  • the user's cloud host is deployed in the available area, and the public service area provides basic services for the available area, such as monitoring, deployment, yum (installation software service), ntp (time synchronization service), and dns (domain name resolution service).
  • the cloud node area deploys the application of the central node system of the cloud platform. Therefore, the platform service that directly interacts with the user is placed in the public service area close to the available area, and the core service of the cloud platform itself is placed in the cloud management area, thereby providing better security isolation, adding a logical isolation layer in the middle, and the user's host. It is not possible to interact directly with the core system of the cloud platform, so this helps to increase the security of the system, so that the core system is not vulnerable to direct attacks and illegal access from the user area.
  • a plurality of component modules belonging to the central component group are deployed in a central deployment area, such as a central area of Shenzhen and a central area of Shanghai.
  • the container cluster management system (Kubernetes, K8s for short) may also be used for deployment.
  • FIG. 4 is a schematic diagram of the deployment effect of the monitoring system deployed by using the deployment method in this embodiment.
  • the non-central deployment area and the central deployment area in FIG. 4 both include a cloud management area, a public service area, and an available area.
  • the logical partition is used to deploy component modules belonging to a non-central component group, and the central deployment area in FIG. 4 is also used for deployment to belong to the center.
  • the component module of a component group is deployed in a way that the component modules belonging to the central component group are not logically partitioned.
  • the monitoring of device performance of a plurality of the preset deployment areas uses an Argus monitoring system, but the monitoring of the availability cannot be completely dependent on the Argus monitoring system. If the availability monitoring of the Argus monitoring system depends on itself, then When there is a problem with the availability of the monitoring system itself, the monitoring of itself will be invalid, resulting in failure to find the problem in time. Therefore, the monitoring system is monitored by a preset monitoring tool.
  • the preset monitoring tool is an independent monitoring tool.
  • the preset monitoring tool is deployed in each preset deployment area by using a software package. Monitor the component modules of the monitoring system.
  • S104 Monitor the monitoring system by using the preset monitoring tool to complete deployment of the monitoring system.
  • the preset monitoring tool is started to monitor the component modules of the monitoring system when the monitoring system is started for operation and maintenance or development.
  • the scheduled task can be set to perform polling detection, and the detection result is sent to the relevant management personnel for alerting by means of a telephone number or an E-mail.
  • the availability report can be generated based on the test results, and the relevant person in charge can be sent by email.
  • An alarm center and a self-healing system are also provided.
  • the high-input center is configured to receive alarm data of a preset monitoring tool, and the alarm analysis module of the alarm center also filters out the alarm event of the monitoring system itself, and then sends the alarm event to the self-healing system.
  • the system automatically monitors system failures based on event automation, such as server expansion, restarting services, or limiting traffic.
  • the preset monitoring tool uses different monitoring modes for different component modules to complete monitoring of the monitoring system. As shown in Figure 5 and Figure 6, they are different monitoring methods.
  • one monitoring mode includes: S1041a, calling an API interface of a component module of the monitoring system by using the preset monitoring tool to obtain call result information; and S1041b, according to The call result information determines availability information of the component module.
  • the availability information includes the available and unavailable two result information
  • the API (Application Programming Interface) interface of the module component of the monitoring system is invoked by the preset monitoring tool, and the call result information is generated, and the module of the monitoring system is invoked.
  • the API interface of the component can determine whether there is two data transfer results in the API interface of the call or no data transfer in the API interface, and the availability information of the component module is determined to be available or not according to the result of the call, and the data is in the API interface. The transmission is available, and no data transmission in the API interface is unavailable.
  • each core component module transfer, graph, judge, alarm, and sender
  • the monitoring of each core component module (transfer, graph, judge, alarm, and sender) of Argus monitoring system can be found through the API interface to find the problem, start a container of Argus checker, and call the relevant API interface to check its availability.
  • another monitoring manner includes: S1042a, calling an IP port of a component module of the monitoring system by using the preset monitoring tool; and acquiring an interface module corresponding to the component module by S1042b Presetting a specific instruction; S1042c, transmitting the preset specific instruction to the component module to cause the component module to run the preset specific instruction and generating operation result information; and S1042d, determining according to the operation result information Availability information of the component module.
  • the IP port of the component module needs to be called, and the IP port is used to determine whether the component module is still in a communication state. If the component module is not in the communication state, the component module is detected. There is an abnormality; if it is still in a communication state, a preset specific instruction is sent to the component module, and the preset specific instruction is a specific instruction code for instructing the component module to perform a certain task, and the component module runs the preset
  • the specific instruction generates operation result information, and the operation result information includes that the preset specific instruction can be executed or the preset specific instruction cannot be executed, whereby the availability information of the component module can be determined accordingly. If the preset specific instruction can be executed, it can be determined that the component module is available; if the preset specific instruction is not executable, the component module can be determined to be unavailable.
  • the monitoring system when the monitoring system is deployed, the monitoring system is deployed not only according to the preset deployment rules in each preset deployment area, but also a preset monitoring tool is deployed in each preset deployment area, and the monitoring is performed by the monitoring tool.
  • the system monitors to monitor the component modules of the monitoring system to ensure proper operation of each component module of the monitoring system, thereby increasing the availability of the monitoring system.
  • FIG. 7 is a schematic flowchart of a method for deploying a monitoring system according to another embodiment of the present application. As shown in FIG. 7, the deployment method of the monitoring system includes steps S201 to S205.
  • the preset monitoring tool is deployed in each of the preset deployment areas, and is deployed by using the deployment method in FIG. 8 , specifically: S203a, acquiring a preset programming script; S203b, The programming script is deployed in the preset deployment area.
  • the preset programming script includes a custom operation, and the custom operation of the preset programming script is executed when the preset programming script is invoked, and the customized operation is used to start the preset monitoring tool pair.
  • the component module of the monitoring system performs monitoring, and the customized operation is used to instruct the preset monitoring tool to monitor different component modules according to different monitoring rules. For example, some component modules need to be monitored by using an API interface, and some component modules need to be monitored. Monitoring by means of IP port, which needs to be defined in advance on the preset programming script.
  • the monitoring system is monitored by the preset monitoring tool to complete the deployment of the monitoring system, and the method in FIG. 9 is adopted, specifically: S204a, calling the preset programming script; S204b The preset monitoring tool is started by the preset programming script to monitor component modules of the monitoring system.
  • the programming script in the Ansible tool can be used, and the programming script corresponding to Ansible is called playbook, and the user can define the batch action in the playbook.
  • Playbook related concepts include Tasks, Inventory, Environment, and Site.yml.
  • the Inventory defines the list of hosts to be remotely controlled. Ansible will log in to the host to perform operations based on the host information of the list. Tasks define the scripts to be copied, the commands to be executed remotely, the scripts and commands that monitor the components are defined here, and site.yml defines which hosts are to execute which tasks. Ansible will log in to the host one by one to perform the corresponding operations according to the operation defined by Site.yml. Therefore, the method of the Ansible script can be used to facilitate the monitoring of the component modules of the monitoring system by starting the preset monitoring tool by using the preset programming script.
  • the configuration preset dynamic loading function is mainly for component modules that occupy a large memory, such as a component module such as a graph and a judge.
  • the specific way to configure the preset dynamic loading function can be to register the semaphore to be received by the program, capture the SIGUSR1 semaphore of the system, and reload the configuration into the memory.
  • the SIGUSR1 semaphore implementation of the system taking the component module transfer of the Golang language as an example, the transfer component module needs to register the SIGUSERl of the system in the program.
  • the SIGUSER1 semaphore is generated, which can be read in the corresponding channel channel.
  • the program will re-read the configuration and put it into memory.
  • the new component module will use the new configuration information, so that the configuration cannot be restarted without restarting. In turn, the operating efficiency of the monitoring system is accelerated.
  • the deployment method of the monitoring system also deploys a preset monitoring tool during deployment to monitor the monitoring system in the monitoring system monitoring, thereby achieving dual monitoring and improving the high availability of the monitoring system.
  • FIG. 10 is a schematic block diagram of a device for deploying a monitoring system according to an embodiment of the present application.
  • the deployment device 400 of the monitoring system can be installed in a server or a terminal.
  • the deployment apparatus 400 of the monitoring system includes an information acquisition unit 401, a system deployment unit 402, a tool deployment unit 403, and a system monitoring unit 404.
  • the information obtaining unit 401 is configured to acquire component information of the monitoring system.
  • the system deployment unit 402 is configured to deploy the monitoring system in multiple preset deployment areas according to the preset deployment rules according to the component information.
  • the system deployment subunit 402 includes a component division subunit 4021, a first deployment subunit 4022, and a second deployment subunit 4023.
  • the component dividing sub-unit 4021 is configured to divide the plurality of component modules into a central component group and a non-central component group according to the preset dividing rule based on the component information.
  • the component information includes component function information and API interface information.
  • the component partitioning sub-unit 4021 is specifically configured to: determine, according to the component function information, whether the component module needs to store information centrally, and determine, according to the API interface information, Whether the component module needs to expose a unified API interface; if the component module needs to store information centrally, the component module is divided into the central component group; if the component module needs to expose a unified API interface, then The component module is divided into the central component group; and if the component module does not need to centrally store information and does not need to expose a unified API interface, the component module is divided into the non-central component group.
  • the first deployment sub-unit 4022 is configured to deploy component modules belonging to the non-central component group in the central deployment area and the non-central deployment area according to a preset deployment rule. Specifically, the component modules belonging to the non-central component group are deployed in the central deployment area and the non-central deployment area according to a preset logical partition.
  • the second deployment sub-unit 4023 is configured to deploy the component modules belonging to the central component group in the central deployment area.
  • the tool deployment unit 403 is configured to deploy a preset monitoring tool in each of the preset deployment areas, where the preset monitoring tool is used to monitor the monitoring system.
  • the system monitoring unit 404 is configured to monitor the monitoring system by using the preset monitoring tool to complete deployment of the monitoring system.
  • the system monitoring unit 404 includes a result information obtaining subunit 4041a and a first information determining subunit 4041b.
  • the result information obtaining sub-unit 4041a is configured to invoke an API interface of a component module of the monitoring system by using the preset monitoring tool to obtain call result information; and a first information determining sub-unit 4041b for using the call according to the call
  • the result information determines availability information of the component module.
  • the system monitoring unit 404 further includes a port invoking subunit 4042a, a specific instruction acquiring subunit 4042b, an instruction sending generating subunit 4042c, and a second information determining subunit 4042d.
  • the port calling subunit 4042a is configured to invoke an IP port of the component module of the monitoring system by using the preset monitoring tool;
  • the specific instruction acquiring subunit 4042b is configured to acquire a preset specificity corresponding to the component module.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • FIG. 12 is a schematic block diagram of a computer device according to an embodiment of the present application.
  • the computer device 700 device can be a terminal or a server.
  • the computer device 700 includes a processor 720, a memory, and a network interface 750 connected by a system bus 710, wherein the memory can include a non-volatile storage medium 730 and an internal memory 740.
  • the non-volatile storage medium 730 can store an operating system 731 and a computer program 732.
  • the processor 720 can be caused to perform a method of deploying the monitoring system.
  • the processor 720 is used to provide computing and control capabilities to support the operation of the entire computer device 700.
  • the internal memory 740 provides an environment for operation of a computer program in a non-volatile storage medium that, when executed by the processor 720, can cause the processor 720 to perform a method of deploying a monitoring system.
  • the network interface 750 is used for network communication, such as sending assigned tasks and the like. It will be understood by those skilled in the art that the structure shown in FIG. 12 is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation of the computer device 700 to which the solution of the present application is applied, and a specific computer device. 700 may include more or fewer components than shown, or some components may be combined, or have different component arrangements.
  • the processor 720 is configured to run the program code stored in the memory to implement the steps corresponding to the deployment method of the monitoring system provided by the foregoing embodiment.
  • the processor 720 may be a central processing unit, and may also be other general-purpose processors, digital signal processors, application specific integrated circuits, off-the-shelf programmable gate arrays or other programmable logic devices, and discrete gates. Or transistor logic devices, discrete hardware components, and so on.
  • the computer readable storage medium may be a medium that can store program code, such as a magnetic disk, an optical disk, a USB flash drive, a mobile hard disk, a magnetic disk, or an optical disk.

Abstract

本申请公开一种监控系统的部署方法、装置、计算机设备及存储介质。该方法包括：获取监控系统的组件信息；根据组件信息按照预设部署规则将监控系统部署在多个预设部署区域；将预设监控工具部署在每个预设部署区域，其中预设监控工具用于监控所述监控系统；以及通过预设监控工具对监控系统进行监控以完成对监控系统的部署。

Description

监控系统的部署方法、装置、计算机设备及存储介质
本申请要求于2018年2月7日提交中国专利局、申请号为201810123507.4、发明名称为“监控系统的部署方法、装置、计算机设备及存储介质”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及计算机技术领域，尤其涉及一种监控系统的部署方法、装置、计算机设备及存储介质。
背景技术
目前，市场上存在很多运维用的监控系统，比如Zabbix监控系统和Open-falcon监控系统。在互联网产品开发和运维均需要监控系统的对这些产品进行实时监控。这些监控系统一般包括30多个组件模块，在部署这些监控系统时，需要保证每个组件模块的高可用性，才能确保整个监控系统的运行效率和监控质量。然而在现有的监控系统的部署方式，多采用一些管理工具对所述监控系统进行简单快捷的部署，比如Ansible工具等，但是这种简单的部署方式降低了监控系统的系统可用性和监控效率，提升了运维复杂度，不能满足客户对监控系统的需求。
发明内容
本申请提供了一种监控系统的部署方法、装置、计算机设备及存储介质，旨在提高监控系统的可用性。
第一方面，本申请提供了一种监控系统的部署方法，包括：获取所述监控系统的组件信息；根据所述组件信息按照预设部署规则将所述监控系统部署在多个预设部署区域；将预设监控工具部署在每个所述预设部署区域，其中所述预设监控工具用于监控所述监控系统；以及通过所述预设监控工具对所述监控系统进行监控以完成对所述监控系统的部署。
第二方面，本申请提供了一种监控系统的部署装置，包括：信息获取单元，用于获取所述监控系统的组件信息；系统部署单元，用于根据所述组件信息按照预设部署规则将所述监控系统部署在多个预设部署区域；工具部署单元，用于将预设监控工具部署在每个所述预设部署区域，其中所述预设监控工具用于监控所述监控系统；以及系统监控单元，用于通过所述预设监控工具对所述监控系统进行监控以完成对所述监控系统的部署。
第三方面，本申请还提供了一种计算机设备，其包括存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述处理器执行所述程序时实现本申请提供的任一项所述的监控系统的部署方法。
第四方面，本申请还提供了一种存储介质，其中所述存储介质存储有计算机程序，所述计算机程序包括程序指令，所述程序指令当被处理器执行时使所述处理器执行本申请提供的任一项所述的监控系统的部署方法。
本申请实施例中的监控系统的部署方法在部署该监控系统时，同时还部署预设监控工具以实现在监控系统执行监控时对监控系统进行监控，由此实现了双重监控进而提高了该监控系统的高可用性。
附图说明
为了更清楚地说明本申请实施例技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是本申请一实施例提供的一种监控系统的部署方法的示意流程图；
图2是图1中监控系统的部署方法的子步骤示意流程图；
图3是图1中监控系统的部署方法的子步骤示意流程图；
图4是本申请实施例提供的监控系统布局的效果示意图；
图5是图1中监控系统的部署方法的子步骤示意流程图；
图6是图1中监控系统的部署方法的另一子步骤示意流程图；
图7是本申请另一实施例提供的一种监控系统的部署装置的示意性框图；
图8是图7中监控系统的部署方法的子步骤示意流程图；
图9是图7中监控系统的部署方法的子步骤示意流程图；
图10是本申请一实施例提供的一种监控系统的部署装置的示意性框图；
图11是本申请另一实施例提供的一种监控系统的部署装置的示意性框图；
图12是本申请一实施例提供的一种计算机设备的示意性框图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
请参阅图1，图1是本申请一实施例提供的一种监控系统的部署方法的示意流程图。如图1所示，该监控系统的部署方法包括步骤S101～S104。
S101、获取所述监控系统的组件信息。
在本实施例中，该监控系统为基于Open-falcon监控系统进行二次开发的监控系统，称为Argus监控系统。该Argus监控系统同样包括多个组件模块，每个组件模块完成不同的功能，比如Agent组件模块，负责采集机器性能数据；Transfer组件模块负责数据转发服务等，不同组件模块具有不同功能并完成不同的任务。获取所述监控系统的组件信息，具体为获取所述监控系统的组件模块的组件信息。其中，所述组件信息包括组件模块的标识信息、组件功能信息和API接口信息等。可以理解的是，该监控系统也可以为其他监控系统，比如Zabbix监控系统和Open-falcon监控系统。
S102、根据所述组件信息按照预设部署规则将所述监控系统部署在多个预设部署区域。
在本实施例中，该预设部署区域包括中心部署区域和非中心部署区域。该预设部署区域为用户需要部署该监控系统的区域，在该区域上设置服务器以将监控系统部署在该区域的服务器，实现对其他互联网产品的监控。该预设部署区域，具体可以为一个国家的几个城市，或者是一个城市的几个地区等，或者是一个公司不同的办公地点。
具体地，根据所述组件信息按照预设部署规则将所述监控系统部署在多个预设部署区域，采用如图2所示的部署方法，即步骤S102包括子步骤S1021～S1023。
S1021、基于所述组件信息根据预设划分规则将多个所述组件模块划分为中心组件组和非中心组件组；
其中，所述组件信息包括组件功能信息和API接口信息，基于所述组件信息根据预设划分规则将多个所述组件模块划分为中心组件组和非中心组件组，具体是根据所述组件信息中的组件功能信息和API接口信息对所述组件模块进行划分的。
在本实施例中，如图3所示，步骤S1021包括子步骤：S1021a至S1021d。
S1021a、根据所述组件功能信息判断所述组件模块是否需要集中存储信息，以及根据所述API接口信息判断所述组件模块是否需要暴露统一的API接口；S1021b、若所述组件模块需要集中存储信息，则将所述组件模块划分为所述中心组件组；S1021c、若所述组件模块需要暴露统一的API接口，则将所述组件模块划分为所述中心组件组；以及S1021d、若所述组件模块不需要集中存储信息且不需要暴露统一的API接口，则将所述组件模块划分为所述非中心组件组。
比如，alarm组件模块和redis组件模块均需要集中管理告警数据，因此需要集中存储信息；mysql组件模块用来集中存储配置数据，也需要集中存储信息；因此，所述alarm组件模块、redis组件模块和mysql组件模块均属于所述中心组件组。web组件模块需要提供页面访问和API访问，因此要暴露统一的API接口；query-proxy组件模块需要统一入口以供查询性能数据，因此也要暴露统一的API接口；所以web组件模块和query-proxy组件模块也属于所述中心组件组。
再比如，处理性能数据转发过滤的transfer组件模块，将性能数据存储的graph组件模块，告警判断的judge组件模块，负责该区域的性能数据查询的query组件模块，以及提供agent版本下发的meta组件模块，这些组件模块基本是分布式部署的，各个区域独立管理，因此既不需要集中存储信息，也不需要暴露统一的API接口，所以transfer、graph、judge、query和meta等组件模块均属于所述非中心组件组。
S1022、将属于所述非中心组件组的组件模块按照预设部署规则部署在所述中心部署区域和非中心部署区域；
具体地，将属于所述非中心组件组的组件模块按照预设逻辑分区部署在所述中心部署区域和非中心部署区域，其中预设逻辑分区包括：可用区、公共服 务区和云管区。
具体地，步骤S1022包括：获取预设关系表，其中所述预设关系表包括属于所述非中心组件组的组件模块与所述可用区、公共服务区和云管区的对应关系；根据所述预设关系表将属于所述非中心组件组的组件模块分别对应部署在所述可用区、公共服务区和云管区。
其中，该预设逻辑分区采用三层架构，从下而上分为可用区，公共服务区和云管区。根据组件模块的功能进行部署，具有不同功能的组件模块部署在不同区域。可通过预设关系表设置属于所述非中心组件组的组件模块与所述可用区、公共服务区和云管区的对应关系，在部署时可以根据该对应关系将属于所述非中心组件组的不同组件模块分别对应部署在所述可用区、公共服务区和云管区。
譬如，将主机信息采集和上报的对应的组件模块部署在可用区，比如：agent模块组件起代理转发功能部署在公共服务区；gateway组件模块和proxy组件模块为处理性能数据、告警数据或者下发指令部署在云管区；transfer、judge、graph、redis、mysql和alarm等组件模块也部署在云管区。将属于所述非中心组件组的组件模块按照预设逻辑分区部署在所述中心部署区域和非中心部署区域，使得监控系统的功能划分更加清晰；同时也具有更好的安全性。
具体地，用户的云主机部署在可用区，公共服务区为该可用区提供基础服务，如监控、部署、yum(安装软件服务)、ntp(时间同步服务)和dns(域名解析服务)等。云管区部署云平台的中心节点系统的应用。因此和用户有直接交互的平台服务放在靠近可用区的公共服务区，而云平台自身的核心服务放置在云管区，由此安全隔离性更好，中间多增加一个逻辑隔离层，用户的主机不能直接和云平台的核心系统做交互，因此这样有助于增加系统的安全性，这样核心系统不容易受到来自用户区域的直接攻击和非法访问。
S1023、将属于所述中心组件组的组件模块部署在所述中心部署区域。
在本实施例中，是将属于所述中心组件组的多个组件模块部署在中心部署区域，比如部署深圳中心区和上海中心区。具体也可采用所述容器集群管理系统(Kubernetes，简称K8s)进行部署。
请参照图4，图4是采用本实施例中的部署方法部署的监控系统的部署效果示意图。图4中非中心部署区域和中心部署区域均包括云管区、公共服务区 和可用区，该逻辑分区用于部署属于非中心组件组的组件模块，图4中中心部署区域还用于部署属于中心组件组的组件模块，对于属于中心组件组的组件模块不采用逻辑分区的方式进行部署。
S103、将预设监控工具部署在每个所述预设部署区域，其中所述预设监控工具用于监控所述监控系统。
在本实施例中，多个所述预设部署区域的设备性能的监控使用的是Argus监控系统，但是可用性的监控不能完全依赖于Argus监控系统，如果Argus监控系统的可用性监控依赖于自身，那么监控系统自身的可用性出现问题时，对自身的监控就会失效，导致无法及时发现问题。因此预设监控工具的方式对该监控系统进行监控，该预设监控工具是独立的监控工具，具体以软件包的方式在每个预设部署区域均部署一套该预设监控工具，用于对监控系统的组件模块进行监控。
S104、通过所述预设监控工具对所述监控系统进行监控以完成对所述监控系统的部署。
在本实施例中，在部署完该监控系统和预设监控工具后，在启动监控系统进行运维或开发时即启动该预设监控工具对该监控系统的各个组件模块进行监控。具体地可设置定时任务进行轮询检测，并将检测结果通过电话号码或E-mail的方式发送相关管理人员进行告警提示。同时还可根据检测结果生成可用性报表，并通过Email的方式发送相关的负责人。除了将这些检测结果中的异常现象通过手机号码或E-mail的方式发送相关管理人员外。还可以设置一个告警中心和自愈系统，该高进中心用于接收预设监控工具的告警数据，该告警中心的告警分析模块还会筛选出监控系统自身的告警事件，然后发送给自愈系统，愈系统会根据事件自动化的处理监控系统的故障，如服务器扩容，重启服务或限制流量等。其中，该预设监控工具对不同的组件模块采用不同的监控方式以完成对监控系统的监控。如图5和图6所示，分别为不同的监控方式。
在一实施例中，如图5所示，其中一种监控方式包括：S1041a、通过所述预设监控工具调用所述监控系统的组件模块的API接口以获取调用结果信息；以及S1041b、根据所述调用结果信息确定所述组件模块的可用性信息。
具体地，可用性信息包括可用和不可用两种结果信息，通过预设监控工具调用监控系统的模块组件的API(Application Programming Interface，应用程序 编程接口)接口并生成调用结果信息，调用监控系统的模块组件的API接口可确定调用的API接口中有数据传输或API接口中没有数据传输两种调用结果，具体可根据该调用结果来确定组件模块的可用性信息是可用还是不可用，API接口中有数据传输的即为可用，API接口中没有数据传输的即为不可用。比如Argus监控系统的各个核心组件模块(transfer、graph、judge、alarm和sender)的监控都可通过API接口调用来发现问题，启动一个Argus checker的容器，调用相关的API接口检查其可用性。
在一实施例中，如图6所示，另一种监控方式包括：S1042a、通过所述预设监控工具调用所述监控系统的组件模块的IP端口；S1042b、获取与所述组件模块相对应的预设特定指令；S1042c、将所述预设特定指令发送至所述组件模块以使所述组件模块运行所述预设特定指令并产生运行结果信息；以及S1042d、根据所述运行结果信息确定所述组件模块的可用性信息。
具体地，该Argus监控系统有些组件模块并没有API接口，因此需要调用该组件模块的IP端口，通过该IP端口判断该组件模块是否还处于通信状态，若不在通信状态，则检测出该组件模块存在异常；若还在通信状态，则向所述组件模块发送预设特定指令，预设特定指令为一特定指令代码，用于指示组件模块执行某种任务，所述组件模块运行所述预设特定指令并产生运行结果信息，该运行结果信息包括可以执行该预设特定指令或不可执行该预设特定指令，由此可以据此确定所述组件模块的可用性信息。如果可执行该预设特定指令，则可确定该组件模块为可用；如果不可执行该预设特定指令，则可确定该组件模块为不可用。
上述实施例在部署监控系统时，在每个预设部署区域不仅按照预设部署规则部署监控系统，同时还在每个预设部署区域部署一个预设监控工具，通过该监控工具对所述监控系统进行监控以监控所述监控系统的组件模块，以确保所述监控系统的每个组件模块的正常运行，由此提高了监控系统的可用性。
请参阅图7，图7是本申请另一实施例提供的一种监控系统的部署方法的示意流程图。如图7所示，该监控系统的部署方法包括步骤S201～S205。
S201、获取所述监控系统的组件信息。
S202、根据所述组件信息按照预设部署规则将所述监控系统部署在多个预 设部署区域。
S203、将预设监控工具部署在每个所述预设部署区域，其中所述预设监控工具用于监控所述监控系统。
在本实施例中，将预设监控工具部署在每个所述预设部署区域，采用图8中的部署方法进行部署，具体地为：S203a、获取预设编排脚本；S203b、将所述预设编排脚本部署在所述预设部署区域。
具体地，该预设编排脚本包括一些自定义操作，在调用该预设编排脚本时即可执行所述预设编排脚本的自定义操作，该自定义操作用于启动所述预设监控工具对所述监控系统的组件模块进行监控，该自定义操作用于指示预设监控工具根据不同的监控规则监控不同的组件模块，比如一些组件模块需要使用API接口的方式进行监控，而一些组件模块需要使用IP端口的方式进行监控，这些都需要在预设编排脚本上事先定义好才能实现。
S204、通过所述预设监控工具对所述监控系统进行监控以完成对所述监控系统的部署。
在本实施例中，通过所述预设监控工具对所述监控系统进行监控以完成对所述监控系统的部署，采用图9中方法，具体为：S204a、调用所述预设编排脚本；S204b、通过所述预设编排脚本启动所述预设监控工具对所述监控系统的组件模块进行监控。
其中，可以采用Ansible工具中的编排脚本，Ansible对应的编排脚本称为playbook，用户可以在playbook中定义批处理的动作。Playbook相关概念有Tasks、Inventory、Environment和Site.yml等。其中Inventory定义要远程控制的主机列表，Ansible会根据列表的主机信息登陆到主机上执行操作。Tasks里会定义要拷贝的脚本，要远程执行的命令，对组件进行监控的脚本和命令都在这里进行定义，而site.yml则定义哪些主机要执行什么task。Ansible会按照Site.yml定义的操作，逐一登陆到主机上执行相应的操作。由此可以借用Ansible脚本的方式，方便实现通过所述预设编排脚本启动所述预设监控工具对所述监控系统的组件模块进行监控。
S205、获取所述监控系统中占用内存大于预设内存值的组件模块，以及对所述组件模块配置预设动态加载功能。
具体地，所述配置预设动态加载功能主要针对是一些占用内存较大的组件 模块，如graph，judge等组件模块。配置预设动态加载功能的具体方式可采用程序注册要接收的信号量，捕获系统的SIGUSR1信号量，重新加载配置到内存中。使用系统的SIGUSR1信号量实现，以Golang语言类的组件模块transfer为例，transfer组件模块需要在程序中注册系统的SIGUSERl，一旦配置更新就会产生SIGUSER1信号量，在对应的通道channel中就能读取到，捕获到这个信号量后，程序就会重新读取配置放置到内存中，新的组件模块就会使用新的配置信息，从而做到不需重启加载配置。进而加快了监控系统的运行效率。
在本实施例中，该监控系统的部署方法在部署时还部署预设监控工具以实现在监控系统监控对监控系统进行监控，由此实现了双重监控进而提高了该监控系统的高可用性。
请参阅图10，图10是本申请实施例提供的一种监控系统的部署装置的示意性框图。该监控系统的部署装置400可以安装于服务器或终端中。如图10所示，监控系统的部署装置400包括：信息获取单元401、系统部署单元402、工具部署单元403和系统监控单元404。
信息获取单元401，用于获取所述监控系统的组件信息。
系统部署单元402，用于根据所述组件信息按照预设部署规则将所述监控系统部署在多个预设部署区域。
具体地，系统部署子单元402包括：组件划分子单元4021、第一部署子单元4022和第二部署子单元4023。其中，组件划分子单元4021，用于基于所述组件信息根据预设划分规则将多个所述组件模块划分为中心组件组和非中心组件组。所述组件信息包括组件功能信息和API接口信息；所述组件划分子单元4021具体用于：根据所述组件功能信息判断所述组件模块是否需要集中存储信息，以及根据所述API接口信息判断所述组件模块是否需要暴露统一的API接口；若所述组件模块需要集中存储信息，则将所述组件模块划分为所述中心组件组；若所述组件模块需要暴露统一的API接口，则将所述组件模块划分为所述中心组件组；以及若所述组件模块不需要集中存储信息且不需要暴露统一的API接口，则将所述组件模块划分为所述非中心组件组。
第一部署子单元4022，用于将属于所述非中心组件组的组件模块按照预设部署规则部署在所述中心部署区域和非中心部署区域。具体用于：将属于所述 非中心组件组的组件模块按照预设逻辑分区部署在所述中心部署区域和非中心部署区域。
第二部署子单元4023，用于将属于所述中心组件组的组件模块部署在所述中心部署区域。
工具部署单元403，用于将预设监控工具部署在每个所述预设部署区域，其中所述预设监控工具用于监控所述监控系统。
系统监控单元404，用于通过所述预设监控工具对所述监控系统进行监控以完成对所述监控系统的部署。
在一实施例中，系统监控单元404包括：结果信息获取子单元4041a和第一信息确定子单元4041b。其中，结果信息获取子单元4041a，用于通过所述预设监控工具调用所述监控系统的组件模块的API接口以获取调用结果信息；以及第一信息确定子单元4041b，用于根据所述调用结果信息确定所述组件模块的可用性信息。
在一实施例中，如图11所示，系统监控单元404还包括：端口调用子单元4042a、特定指令获取子单元4042b、指令发送产生子单元4042c和第二信息确定子单元4042d。其中，端口调用子单元4042a，用于通过所述预设监控工具调用所述监控系统的组件模块的IP端口；特定指令获取子单元4042b，用于获取与所述组件模块相对应的预设特定指令；指令发送产生子单元4042c，用于将所述预设特定指令发送至所述组件模块以使所述组件模块运行所述预设特定指令并产生运行结果信息；以及第二信息确定子单元4042d，用于根据所述运行结果信息确定所述组件模块的可用性信息。
所属领域的技术人员可以清楚地了解到，为了描述的方便和简洁，上述描述的监控系统的部署装置和单元的具体工作过程，可以参考前述部署方法实施例中的对应过程，在此不再赘述。
本申请实施例方法中的步骤可以根据实际需要进行顺序调整、合并和删减。申请实施例装置中的单元可以根据实际需要进行合并、划分和删减。另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以是两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
上述装置可以实现为一种计算机程序的形式，计算机程序可以在如图12所 示的计算机设备上运行。请参阅图12，图12是本申请实施例提供的一种计算机设备的示意性框图。该计算机设备700设备可以是终端或服务器。
参照图12，该计算机设备700包括通过系统总线710连接的处理器720、存储器和网络接口750，其中，存储器可以包括非易失性存储介质730和内存储器740。该非易失性存储介质730可存储操作系统731和计算机程序732。该计算机程序732被执行时，可使得处理器720执行一种监控系统的部署方法。该处理器720用于提供计算和控制能力，支撑整个计算机设备700的运行。该内存储器740为非易失性存储介质中的计算机程序的运行提供环境，该计算机程序被处理器720执行时，可使得处理器720执行一种监控系统的部署方法。该网络接口750用于进行网络通信，如发送分配的任务等。本领域技术人员可以理解，图12中示出的结构，仅仅是与本申请方案相关的部分结构的框图，并不构成对本申请方案所应用于其上的计算机设备700的限定，具体的计算机设备700可以包括比图中所示更多或更少的部件，或者组合某些部件，或者具有不同的部件布置。
其中，所述处理器720用于运行存储在存储器中的程序代码以实现上述实施例提供的监控系统的部署方法对应的步骤。
应当理解，在本申请实施例中，处理器720可以是中央处理单元，还可以是其他通用处理器、数字信号处理器、专用集成电路、现成可编程门阵列或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。
本领域普通技术人员可以理解的是实现上述实施例方法中的全部或部分流程，是可以通过计算机程序来指令相关的硬件来完成，程序可存储于一存储介质中，该存储介质为计算机可读存储介质。如本发明实施例中，该程序可存储于计算机系统的存储介质中，并被该计算机系统中的至少一个处理器执行，以实现包括如上述各监控系统的部署方法的实施例的流程步骤。该计算机可读存储介质可以是磁碟、光盘、U盘、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到各种等效的修改或替换，这些修改或替换都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以权利要求的保护范围为准。

Claims (20)

  1. 一种监控系统的部署方法，其包括：
    获取所述监控系统的组件信息；
    根据所述组件信息按照预设部署规则将所述监控系统部署在多个预设部署区域；
    将预设监控工具部署在每个所述预设部署区域，其中所述预设监控工具用于监控所述监控系统；以及
    通过所述预设监控工具对所述监控系统进行监控以完成对所述监控系统的部署。
  2. 根据权利要求1所述的监控系统的部署方法，其中，所述将预设监控工具部署在每个所述预设部署区域，包括：
    获取预设编排脚本；以及将所述预设编排脚本部署在所述预设部署区域；
    所述通过所述预设监控工具对所述监控系统进行监控，包括：
    调用所述预设编排脚本；以及
    通过所述预设编排脚本启动所述预设监控工具对所述监控系统的组件模块进行监控。
  3. 根据权利要求1所述的监控系统的部署方法，其中，所述通过所述预设监控工具对所述监控系统进行监控，包括：
    通过所述预设监控工具调用所述监控系统的组件模块的API接口以获取调用结果信息；以及
    根据所述调用结果信息确定所述组件模块的可用性信息。
  4. 根据权利要求1所述的监控系统的部署方法，其中，所述通过所述预设监控工具对所述监控系统进行监控，包括：
    通过所述预设监控工具调用所述监控系统的组件模块的IP端口；
    获取与所述组件模块相对应的预设特定指令；
    将所述预设特定指令发送至所述组件模块以使所述组件模块运行所述预设特定指令并产生运行结果信息；以及
    根据所述运行结果信息确定所述组件模块的可用性信息。
  5. 根据权利要求1所述的监控系统的部署方法，其中，所述预设部署区域 包括中心部署区域和非中心部署区域；
    所述根据所述组件信息按照预设部署规则将所述监控系统部署在多个预设部署区域，包括：
    基于所述组件信息根据预设划分规则将多个所述组件模块划分为中心组件组和非中心组件组；
    将属于所述非中心组件组的组件模块按照预设部署规则部署在所述中心部署区域和非中心部署区域；以及
    将属于所述中心组件组的组件模块部署在所述中心部署区域。
  6. 根据权利要求5所述的监控系统的部署方法，其中，所述将属于所述非中心组件组的组件模块按照预设部署规则部署在所述中心部署区域和非中心部署区域，包括：
    将属于所述非中心组件组的组件模块按照预设逻辑分区部署在所述中心部署区域和非中心部署区域，其中预设逻辑分区包括：可用区、公共服务区和云管区。
  7. 根据权利要求5所述的监控系统的部署方法，其中，所述组件信息包括组件功能信息和API接口信息；
    所述基于所述组件信息根据预设划分规则将多个所述组件模块划分为中心组件组和非中心组件组，包括：
    根据所述组件功能信息判断所述组件模块是否需要集中存储信息，以及根据所述API接口信息判断所述组件模块是否需要暴露统一的API接口；
    若所述组件模块需要集中存储信息，则将所述组件模块划分为所述中心组件组；
    若所述组件模块需要暴露统一的API接口，则将所述组件模块划分为所述中心组件组；以及
    若所述组件模块不需要集中存储信息且不需要暴露统一的API接口，则将所述组件模块划分为所述非中心组件组。
  8. 一种监控系统的部署装置，其包括：
    信息获取单元，用于获取所述监控系统的组件信息；
    系统部署单元，用于根据所述组件信息按照预设部署规则将所述监控系统部署在多个预设部署区域；
    工具部署单元，用于将预设监控工具部署在每个所述预设部署区域，其中所述预设监控工具用于监控所述监控系统；以及
    系统监控单元，用于通过所述预设监控工具对所述监控系统进行监控以完成对所述监控系统的部署。
  9. 一种计算机设备，其中，包括存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述处理器执行所述计算机程序时实现：获取所述监控系统的组件信息；根据所述组件信息按照预设部署规则将所述监控系统部署在多个预设部署区域；将预设监控工具部署在每个所述预设部署区域，其中所述预设监控工具用于监控所述监控系统；通过所述预设监控工具对所述监控系统进行监控以完成对所述监控系统的部署。
  10. 根据权利要求9所述的计算机设备，其中，所述处理器执行所述计算机程序以实现将预设监控工具部署在每个所述预设部署区域时，具体实现：获取预设编排脚本；以及将所述预设编排脚本部署在所述预设部署区域；所述处理器执行所述计算机程序以实现通过所述预设监控工具对所述监控系统进行监控时，具体实现：调用所述预设编排脚本；以及通过所述预设编排脚本启动所述预设监控工具对所述监控系统的组件模块进行监控。
  11. 根据权利要求9所述的计算机设备，其中，所述处理器执行所述计算机程序以实现通过所述预设监控工具对所述监控系统进行监控时，具体实现：通过所述预设监控工具调用所述监控系统的组件模块的API接口以获取调用结果信息；以及根据所述调用结果信息确定所述组件模块的可用性信息。
  12. 根据权利要求9所述的计算机设备，其中，所述处理器执行所述计算机程序以实现通过所述预设监控工具对所述监控系统进行监控时，具体实现：通过所述预设监控工具调用所述监控系统的组件模块的IP端口；获取与所述组件模块相对应的预设特定指令；将所述预设特定指令发送至所述组件模块以使所述组件模块运行所述预设特定指令并产生运行结果信息；以及根据所述运行结果信息确定所述组件模块的可用性信息。
  13. 根据权利要求9所述的计算机设备，其中，所述预设部署区域包括中心部署区域和非中心部署区域；所述处理器执行所述计算机程序以实现根据所述组件信息按照预设部署规则将所述监控系统部署在多个预设部署区域时，具体实现：基于所述组件信息根据预设划分规则将多个所述组件模块划分为中心组 件组和非中心组件组；将属于所述非中心组件组的组件模块按照预设部署规则部署在所述中心部署区域和非中心部署区域；以及将属于所述中心组件组的组件模块部署在所述中心部署区域。
  14. 根据权利要求13所述的计算机设备，其中，所述处理器执行所述计算机程序以实现将属于所述非中心组件组的组件模块按照预设部署规则部署在所述中心部署区域和非中心部署区域时，具体实现：将属于所述非中心组件组的组件模块按照预设逻辑分区部署在所述中心部署区域和非中心部署区域，其中预设逻辑分区包括：可用区、公共服务区和云管区。
  15. 一种存储介质，其中，所述存储介质存储有计算机程序，所述计算机程序包括程序指令，所述程序指令当被处理器执行时使所述处理器执行：获取所述监控系统的组件信息；根据所述组件信息按照预设部署规则将所述监控系统部署在多个预设部署区域；将预设监控工具部署在每个所述预设部署区域，其中所述预设监控工具用于监控所述监控系统；通过所述预设监控工具对所述监控系统进行监控以完成对所述监控系统的部署。
  16. 根据权利要求15所述的存储介质，其中，所述程序指令当被处理器执行将预设监控工具部署在每个所述预设部署区域时，使所述处理器执行：获取预设编排脚本；以及将所述预设编排脚本部署在所述预设部署区域；所述程序指令当被处理器执行通过所述预设监控工具对所述监控系统进行监控时，使所述处理器执行：调用所述预设编排脚本；以及通过所述预设编排脚本启动所述预设监控工具对所述监控系统的组件模块进行监控。
  17. 根据权利要求15所述的存储介质，其中，所述程序指令当被处理器执行通过所述预设监控工具对所述监控系统进行监控时，使所述处理器执行：通过所述预设监控工具调用所述监控系统的组件模块的API接口以获取调用结果信息；以及根据所述调用结果信息确定所述组件模块的可用性信息。
  18. 根据权利要求15所述的存储介质，其中，所述程序指令当被处理器执行通过所述预设监控工具对所述监控系统进行监控时，使所述处理器执行：通过所述预设监控工具调用所述监控系统的组件模块的IP端口；获取与所述组件模块相对应的预设特定指令；将所述预设特定指令发送至所述组件模块以使所述组件模块运行所述预设特定指令并产生运行结果信息；以及根据所述运行结果信息确定所述组件模块的可用性信息。
  19. 根据权利要求15所述的存储介质，其中，所述预设部署区域包括中心部署区域和非中心部署区域；所述程序指令当被处理器执行根据所述组件信息按照预设部署规则将所述监控系统部署在多个预设部署区域时，使所述处理器执行：基于所述组件信息根据预设划分规则将多个所述组件模块划分为中心组件组和非中心组件组；将属于所述非中心组件组的组件模块按照预设部署规则部署在所述中心部署区域和非中心部署区域；以及将属于所述中心组件组的组件模块部署在所述中心部署区域。
  20. 根据权利要求19所述的存储介质，其中，所述程序指令当被处理器执行将属于所述非中心组件组的组件模块按照预设部署规则部署在所述中心部署区域和非中心部署区域时，使所述处理器执行：将属于所述非中心组件组的组件模块按照预设逻辑分区部署在所述中心部署区域和非中心部署区域，其中预设逻辑分区包括：可用区、公共服务区和云管区。
PCT/CN2018/084709 2018-02-07 2018-04-27 监控系统的部署方法、装置、计算机设备及存储介质 WO2019153532A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810123507.4A CN108363653B (zh) 2018-02-07 2018-02-07 监控系统的部署方法、装置、计算机设备及存储介质
CN201810123507.4 2018-02-07

Publications (1)

Publication Number Publication Date
WO2019153532A1 true WO2019153532A1 (zh) 2019-08-15

Family

ID=63004795

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/084709 WO2019153532A1 (zh) 2018-02-07 2018-04-27 监控系统的部署方法、装置、计算机设备及存储介质

Country Status (2)

Country Link
CN (1) CN108363653B (zh)
WO (1) WO2019153532A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110855473A (zh) * 2019-10-16 2020-02-28 平安科技（深圳）有限公司 一种监控方法、装置、服务器及存储介质

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108845916B (zh) * 2018-07-03 2022-02-22 中国联合网络通信集团有限公司 平台监控与告警方法、装置、设备与计算机可读存储介质
CN109451047B (zh) * 2018-12-13 2021-05-18 深圳前海微众银行股份有限公司 监控告警系统的数据传送方法、装置、设备及存储介质
CN109800254A (zh) * 2018-12-28 2019-05-24 易票联支付有限公司 一种业务性能巡检报表生成方法、系统及装置
CN110377294A (zh) * 2019-07-23 2019-10-25 上海金融期货信息技术有限公司 一种基于DevOps的多环境配置系统和方法
CN117135050B (zh) * 2023-10-26 2024-02-09 建信金融科技有限责任公司 应用部署方法和装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105656685A (zh) * 2016-02-26 2016-06-08 浪潮通信信息系统有限公司 一种基于zabbix系统oracle的自动部署及运维监控方法
CN106549829A (zh) * 2016-10-28 2017-03-29 北方工业大学 大数据计算平台监控系统及方法
CN106789284A (zh) * 2016-12-28 2017-05-31 郑州云海信息技术有限公司 一种基于Zabbix和Docker的监控系统和方法
CN107528751A (zh) * 2017-09-30 2017-12-29 南京卓盛云信息科技有限公司 一种动态分发Zabbix监控数据的系统及其管理方法

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120173717A1 (en) * 2010-12-31 2012-07-05 Vince Kohli Cloud*Innovator
CN104601673B (zh) * 2014-12-23 2018-01-30 中国电子科技集团公司第三十二研究所 可扩展的高可用服务器分层监控系统
CN107491371B (zh) * 2016-06-13 2021-03-16 阿里巴巴集团控股有限公司 一种监控部署的方法以及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105656685A (zh) * 2016-02-26 2016-06-08 浪潮通信信息系统有限公司 一种基于zabbix系统oracle的自动部署及运维监控方法
CN106549829A (zh) * 2016-10-28 2017-03-29 北方工业大学 大数据计算平台监控系统及方法
CN106789284A (zh) * 2016-12-28 2017-05-31 郑州云海信息技术有限公司 一种基于Zabbix和Docker的监控系统和方法
CN107528751A (zh) * 2017-09-30 2017-12-29 南京卓盛云信息科技有限公司 一种动态分发Zabbix监控数据的系统及其管理方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
LIU YUAN-CHAO ET AL.: "Research and Implementation of Network Monitoring Based on Zabbix and WeChat Enterprise Accounts", SHANDONG SCIENCE, vol. 30, no. 4, 15 August 2017 (2017-08-15), pages 124 - 130, XP055630563, ISSN: 1002-4026 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110855473A (zh) * 2019-10-16 2020-02-28 平安科技（深圳）有限公司 一种监控方法、装置、服务器及存储介质
WO2021073433A1 (zh) * 2019-10-16 2021-04-22 平安科技（深圳）有限公司 一种监控方法、装置、服务器及存储介质

Also Published As

Publication number Publication date
CN108363653B (zh) 2020-08-07
CN108363653A (zh) 2018-08-03

Similar Documents

Publication Publication Date Title
WO2019153532A1 (zh) 监控系统的部署方法、装置、计算机设备及存储介质
US11940965B2 (en) Data migration method and apparatus
EP2838228B1 (en) Alarm correlation analysis method, apparatus, and system
US8910138B2 (en) Hot pluggable extensions for access management system
WO2020248507A1 (zh) 基于容器云的系统资源监控方法及相关设备
US10798218B2 (en) Environment isolation method and device
WO2016184175A1 (zh) 数据库处理方法及装置
CN109788068B (zh) 心跳状态信息上报方法、装置和设备及计算机存储介质
CN111431740A (zh) 数据的传输方法、装置、设备及计算机可读存储介质
WO2016161605A1 (zh) 基于网络功能虚拟化的故障处理方法和装置
US11706080B2 (en) Providing dynamic serviceability for software-defined data centers
CN110620676B (zh) 一种故障管理方法和相关装置
WO2019153524A1 (zh) 监控系统的部署方法、装置、计算机设备及存储介质
US20200065085A1 (en) Containerized systems and methods for customer premises equipment
CN114884838A (zh) Kubernetes组件的监控方法及服务器
WO2021218036A1 (zh) 信息监控方法、系统及计算机可读存储介质
CN110795202B (zh) 一种虚拟化集群资源管理系统的资源分配方法以及装置
US9032014B2 (en) Diagnostics agents for managed computing solutions hosted in adaptive environments
WO2021213171A1 (zh) 一种服务器切换方法、装置、管理节点及存储介质
CN111488163B (zh) 一种固件更新方法、装置及电子设备和存储介质
KR20220104241A (ko) 네트워크 작업 방법, 장치, 설비 및 저장매체
CN114979286A (zh) 容器服务的访问控制方法、装置、设备及计算机存储介质
CN112130900B (zh) 一种bmc的用户信息管理方法、系统、设备以及介质
US11592997B2 (en) Systems, methods and computer readable media for software defined storage security protection
CN107783855B (zh) 虚拟网元的故障自愈控制装置及方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18905700

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 02.11.2020)

122 Ep: pct application non-entry in european phase

Ref document number: 18905700

Country of ref document: EP

Kind code of ref document: A1