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

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

Info

Publication number
WO2019153524A1
WO2019153524A1 PCT/CN2018/084529 CN2018084529W WO2019153524A1 WO 2019153524 A1 WO2019153524 A1 WO 2019153524A1 CN 2018084529 W CN2018084529 W CN 2018084529W WO 2019153524 A1 WO2019153524 A1 WO 2019153524A1
Authority
WO
WIPO (PCT)
Prior art keywords
component
central
area
deployment
preset
Prior art date
Application number
PCT/CN2018/084529
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 WO2019153524A1 publication Critical patent/WO2019153524A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/12—Network monitoring probes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H04L67/025—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1097—Protocols 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]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 

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.
  • These monitoring systems have a large number of component modules and generally include nearly 30 component modules.
  • it is necessary to ensure the high availability of each component module to ensure the operational 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 embodiment of the present application provides a method, a device, a computer device, and a storage medium for deploying a monitoring system, which are intended to improve the availability of the monitoring system.
  • an embodiment of the present application provides a method for deploying a monitoring system, including:
  • the preset deployment area includes a central deployment area and a non-central deployment area
  • a component module belonging to the central component group is deployed in the central deployment area to complete deployment of the monitoring system.
  • an embodiment of the present application provides a deployment apparatus for a monitoring system, including:
  • An information acquiring unit configured to acquire component information corresponding to a component module of the monitoring system, where the monitoring system includes multiple component modules;
  • a component dividing unit configured to divide the plurality of component modules into a central component group and a non-central component group according to the preset partitioning rule according to the component information
  • An area obtaining unit configured to acquire a preset deployment area, where the preset deployment area includes a central deployment area and a non-central deployment area;
  • a first deployment unit 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
  • a second deployment unit configured to deploy component modules belonging to the central component group in the central deployment area to complete deployment of the monitoring system.
  • the embodiment of the present application further provides a computer device, including a memory, a processor, and a computer program stored on the memory and executable on the processor, where the processor executes the program
  • a computer device including a memory, a processor, and a computer program stored on the memory and executable on the processor, where the processor executes the program
  • the embodiment of the present application further provides a storage medium, wherein the storage medium stores a computer program, where the computer program includes program instructions, and the program instructions, when executed by the processor, cause the processor to execute
  • the storage medium stores a computer program, where the computer program includes program instructions, and the program instructions, when executed by the processor, cause the processor to execute
  • the deployment method of the embodiment of the present application can implement a deployment manner of two centers in three places, and the deployment mode is advantageous for distributed storage of data, thereby improving the availability of the monitoring 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 deployment effects of the monitoring system
  • FIG. 5 is a schematic block diagram of a device for deploying a monitoring system according to an embodiment of the present application.
  • FIG. 6 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 includes steps S101 to S106.
  • the monitoring system is a monitoring system based on the secondary development of the Open-falcon monitoring system, the monitoring system includes a plurality of component modules, each component module performs different functions, such as an Agent component module, and is responsible for collecting the machine. Performance data; the Transfer component module is responsible for data forwarding services, etc. Different component modules have different functions and perform different tasks.
  • the component information includes identifier information of component modules, component function information, API interface information, and the like.
  • all the component modules are divided according to the component information of the component modules of the monitoring system, and are specifically divided into a central component group and a non-central component group.
  • the component modules belonging to the central component group include a config-server, Component modules such as redis, mysql, alarm, sender, pa-portal, and query-proxy;
  • component modules belonging to the non-central component group include component modules such as transfer, graph, hbs, query, config-proxy, meta, and gitlab.
  • the division of the central component group and the non-central component group facilitates distributed storage of monitoring data to improve the availability of the monitoring system.
  • 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 component function information and API interface information in the component information. Dividing the component modules.
  • step S102 includes sub-steps: S102a to S102d.
  • S102 determining, according to the component function information, whether the component module needs to centrally store information, and determining, according to the API interface information, whether the component module needs to expose a unified API interface; S102b, if the component module needs to centrally store information And dividing the component module into the central component group; S102c, if the component module needs to expose a unified API interface, dividing the component module into the central component group; and S102d, 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 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.
  • the preset deployment area includes a central deployment area and a non-central deployment area, wherein the central deployment area includes Shenzhen and Shanghai, and the non-central deployment area may be an area such as Guangzhou, Langfang or Qingdao. It should be noted that the central deployment area can also be used as a non-central deployment area.
  • Shenzhen, Shanghai, and Langfang are non-central deployment areas and also a central deployment area, and thus the preset deployment area is three. The two centers, the specific three places refer to Shenzhen, Shanghai and Langfang, and the two centers refer to Shenzhen and Shanghai.
  • the component modules that belong to the non-central component group are deployed in the central deployment area and the non-central deployment area according to a preset deployment rule.
  • the preset deployment rule is a pre-set deployment rule according to a function of a plurality of component modules belonging to the non-central component group, so that the deployment logic of the component modules belonging to the non-central component group is further improved.
  • the function division is more clear.
  • 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 deployment rule, and the component modules belonging to the non-central component group are deployed according to a preset logical partition.
  • the central deployment area and the non-central deployment area are deployed in the central deployment area and the non-central deployment area according to a preset deployment rule, and the component modules belonging to the non-central component group are deployed according to a preset logical partition.
  • step S104 includes sub-steps S104a and S104b.
  • S104a the 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; S104b, according to the preset relationship
  • the component modules corresponding to the non-central component group are respectively deployed 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 bottom to 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.
  • the component modules of the non-central component group of the monitoring system may be deployed by using a container cluster management system (Kubernetes, K8s for short) according to the foregoing deployment method, and of course, other management systems may be used. Deployment, such as the Ansible management system.
  • 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 preset deployment area includes two central deployment areas and at least one non-central deployment area, and the two central deployment areas are a production data center area and a disaster recovery data center area, respectively.
  • it is specifically the Shenzhen Generating Data Center and the Shanghai Disaster Recovery Data Center Area, as well as non-central deployment areas such as Shenzhen, Shanghai and Langfang.
  • the component modules belonging to the non-central component group are deployed in logical partition deployment in Shenzhen, Shanghai and Langfang.
  • the component modules belonging to the central component group are only deployed in the Shenzhen Generating Data Center and the Shanghai Disaster Recovery Data Center.
  • the deployment method of the foregoing embodiment divides the component module into a central component group and a non-central component group according to component information of the component module of the monitoring system, and then deploys the component modules belonging to the non-central component group according to a preset deployment rule. a central deployment area and a non-central deployment area; and component modules belonging to the central component group are deployed in the central deployment area to complete deployment of the monitoring system.
  • the deployment method can realize the deployment mode of the two centers in three places, and the deployment mode is advantageous for distributed storage of data and high availability of the monitoring system.
  • FIG. 5 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.
  • the deployment apparatus 400 of the monitoring system includes an information acquisition unit 401, a component division unit 402, an area acquisition unit 403, a first deployment unit 404, and a second deployment unit 405.
  • the information obtaining unit 401 is configured to acquire component information corresponding to a component module of the monitoring system, where the monitoring system includes a plurality of component modules.
  • the component dividing unit 402 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 dividing unit 402 includes: a component determining sub-unit 4021, a first dividing sub-unit 4022, a second dividing sub-unit 4023, and a third dividing sub-unit 4024.
  • the component determining sub-unit 4021 is 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;
  • the subunit 4022 is configured to divide the component module into the central component group if the component module needs to store information in a centralized manner, and the second partitioning subunit 4023 is configured to expose a unified API interface if the component module needs to be exposed. And dividing the component module into the central component group; and the third dividing sub-unit 4024, configured to: if the component module does not need to centrally store information and does not need to expose a unified API interface, then the component module is Divided into the non-central component group.
  • the area obtaining unit 403 is configured to acquire a preset deployment area, where the preset deployment area includes a central deployment area and a non-central deployment area.
  • the first deployment unit 404 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.
  • the first deployment unit 404 is specifically 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 logical partition.
  • the first deployment unit 404 includes a relationship table obtaining subunit 4041 and a component deployment subunit 4042.
  • the relationship table obtaining sub-unit 4041 is configured to obtain 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 component deployment sub-unit 4042 is configured to respectively allocate component modules belonging to the non-central component group in the available area, the public service area, and the cloud management area according to the preset relationship table.
  • the second deployment unit 405 is configured to deploy component modules belonging to the central component group in the central deployment area to complete deployment of the monitoring system.
  • the disclosed apparatus and method for deploying the monitoring system may be implemented in other manners.
  • the deployment device embodiments of the monitoring system described above are merely illustrative.
  • the division of each unit is only a logical function division, and there may be another division manner in actual implementation.
  • multiple units or components may be combined or integrated into another system, or some features may be omitted or not implemented.
  • the above apparatus may be embodied in the form of a computer program that can be run on a computer device as shown in FIG.
  • FIG. 6 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 server.
  • the computer device 700 includes a processor 720, a memory, and a network interface 750 coupled 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. 6 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 program code stored in the memory to implement the following steps: acquiring component information corresponding to a component module of the monitoring system, where the monitoring system includes multiple component modules; And dividing the plurality of component modules into a central component group and a non-central component group according to a preset division rule; acquiring a preset deployment area, where the preset deployment area includes a central deployment area and a non-central deployment area; The component modules of the non-central component group are deployed in the central deployment area and the non-central deployment area according to a preset deployment rule; and component modules belonging to the central component group are deployed in the central deployment area to complete the monitoring system Deployment.
  • the processor 720 performs the following steps when the component module that belongs to the non-central component group is deployed in the central deployment area and the non-central deployment area according to a preset deployment rule:
  • 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 preset logical partition specifically includes: an available area, a common service area, and a cloud management area
  • the processor 720 is configured to execute the component module that belongs to the non-central component group according to a preset logical partition.
  • 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 component modules belonging to the non-central component group are respectively deployed in the available area, the public service area, and the cloud management area according to the preset relationship table.
  • the component information includes component function information and API interface information
  • the processor 720 performs, according to the component information, the plurality of the component modules according to the preset division rule into the central component group and the non- When the central component group is executed, the following steps are performed:
  • the component module needs to expose a unified API interface, the component module is divided into the central component group;
  • 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 processor 720 may be a central processing unit (CPU), and the processor 720 may also be another general-purpose processor, a digital signal processor (DSP), Application Specific Integrated Circuit (ASIC), Field-Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, etc.
  • the general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
  • computer device 700 architecture illustrated in FIG. 6 does not constitute a limitation to computer device 700, may include more or fewer components than illustrated, or may combine certain components, or different components. Arrangement.
  • 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.
  • 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.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as a standalone product, can be stored in a computer readable storage medium.
  • the technical solution of the present application may be in essence or part of the contribution to the prior art, or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium.
  • There are a number of instructions for causing a computer device (which may be a personal computer, terminal, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present application.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Debugging And Monitoring (AREA)
  • Alarm Systems (AREA)

Abstract

本申请公开一种监控系统的部署方法、装置、计算机设备及存储介质。该方法在获取监控系统的组件模块对应的组件信息后，基于组件信息将多个组件模块分为中心组件组和非中心组件组；部署非中心组件组的组件模块至预设部署区域中的中心部署区域和非中心部署区域，部署中心组件组的组件模块至预设部署区域中的中心部署区域。

Description

监控系统的部署方法、装置、计算机设备及存储介质
本申请要求于2018年2月7日提交中国专利局、申请号为201810125003.6、发明名称为“监控系统的部署方法、装置、计算机设备及存储介质”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及计算机技术领域，尤其涉及一种监控系统的部署方法、装置、计算机设备及存储介质。
背景技术
目前，市场上存在很多运维用的监控系统，比如Zabbix监控系统和Open-falcon监控系统。这些监控系统的组件模块数量较多，一般包括将近30多个组件模块。在部署这些监控系统时，需要保证每个组件模块的高可用性，才能确保整个监控系统的运行效率和监控质量。然而在现有的监控系统的部署方式，多采用一些管理工具对所述监控系统进行简单快捷的部署，比如Ansible工具等，但是这种简单的部署方式降低了监控系统的系统可用性和监控效率，提升了运维复杂度，不能满足客户对监控系统的需求。
发明内容
本申请实施例提供了一种监控系统的部署方法、装置、计算机设备及存储介质，旨在提高监控系统的可用性。
第一方面，本申请实施例提供了一种监控系统的部署方法，其包括：
获取监控系统的组件模块对应的组件信息，其中所述监控系统包括多个组件模块；
基于所述组件信息根据预设划分规则将多个所述组件模块划分为中心组件组和非中心组件组；
获取预设部署区域，其中所述预设部署区域包括中心部署区域和非中心部 署区域；
将属于所述非中心组件组的组件模块按照预设部署规则部署在所述中心部署区域和非中心部署区域；以及
将属于所述中心组件组的组件模块部署在所述中心部署区域以完成对所述监控系统的部署。
第二方面，本申请实施例提供了一种监控系统的部署装置，其包括：
信息获取单元，用于获取监控系统的组件模块对应的组件信息，其中所述监控系统包括多个组件模块；
组件划分单元，用于基于所述组件信息根据预设划分规则将多个所述组件模块划分为中心组件组和非中心组件组；
区域获取单元，用于获取预设部署区域，其中所述预设部署区域包括中心部署区域和非中心部署区域；
第一部署单元，用于将属于所述非中心组件组的组件模块按照预设部署规则部署在所述中心部署区域和非中心部署区域；以及
第二部署单元，用于将属于所述中心组件组的组件模块部署在所述中心部署区域以完成对所述监控系统的部署。
第三方面，本申请实施例还提供了一种计算机设备，其包括存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述处理器执行所述程序时实现本申请提供的任一项所述的监控系统的部署方法。
第四方面，本申请实施例还提供了一种存储介质，其中所述存储介质存储有计算机程序，所述计算机程序包括程序指令，所述程序指令当被处理器执行时使所述处理器执行本申请提供的任一项所述的监控系统的部署方法。
本申请实施例的部署方法可以实现三地两中心的部署方式，这种部署方式有利于数据的分布式存储，进而提高了监控系统的可用性。
附图说明
为了更清楚地说明本申请实施例技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是本申请一实施例提供的一种监控系统的部署方法的示意流程图；
图2是图1中监控系统的部署方法的子步骤示意流程图；
图3是图1中监控系统的部署方法的子步骤示意流程图；
图4是所述监控系统的部署效果示意图；
图5是本申请一实施例提供的一种监控系统的部署装置的示意性框图；
图6是本申请一实施例提供的一种计算机设备的示意性框图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
应当理解，当在本说明书和所附权利要求书中使用时，术语“包括”和“包含”指示所描述特征、整体、步骤、操作、元素和/或组件的存在，但并不排除一个或多个其它特征、整体、步骤、操作、元素、组件和/或其集合的存在或添加。
还应当理解，在此本申请说明书中所使用的术语仅仅是出于描述特定实施例的目的而并不意在限制本申请。如在本申请说明书和所附权利要求书中所使用的那样，除非上下文清楚地指明其它情况，否则单数形式的“一”、“一个”及“该”意在包括复数形式。
还应当进一步理解，在本申请说明书和所附权利要求书中使用的术语“和/或”是指相关联列出的项中的一个或多个的任何组合以及所有可能组合，并且包括这些组合。
请参阅图1，图1是本申请一实施例提供的一种监控系统的部署方法的示意流程图。如图1所示，该部署方法包括步骤S101～S106。
S101、获取监控系统的组件模块对应的组件信息，其中所述监控系统包括多个组件模块。
在本实施例中，该监控系统为基于Open-falcon监控系统进行二次开发的监控系统，该监控系统包括多个组件模块，每个组件模块完成不同的功能，比如Agent组件模块，负责采集机器性能数据；Transfer组件模块负责数据转发服务等，不同组件模块具有不同功能并完成不同的任务。
其中，所述组件信息包括组件模块的标识信息、组件功能信息和API接口信息等。
S102、基于所述组件信息根据预设划分规则将多个所述组件模块划分为中心组件组和非中心组件组。
在本实施例中，根据该监控系统的组件模块的组件信息对所有组件模块进行划分，具体分为中心组件组和非中心组件组，比如属于所述中心组件组的组件模块包括config-server、redis、mysql、alarm、sender、pa-portal和query-proxy等组件模块；属于所述非中心组件组的组件模块包括transfer、graph、hbs、query、config-proxy、meta和gitlab等组件模块。该中心组件组和非中心组件组的划分方便对监控数据进行分布式存储，以提高监控系统的可用性。
在本实施例中，基于所述组件信息根据预设划分规则将多个所述组件模块划分为中心组件组和非中心组件组，具体是根据所述组件信息中的组件功能信息和API接口信息对所述组件模块进行划分的。
在一实施例，例如本实施例中，如图2所示，步骤S102包括子步骤：S102a至S102d。
S102a、根据所述组件功能信息判断所述组件模块是否需要集中存储信息，以及根据所述API接口信息判断所述组件模块是否需要暴露统一的API接口；S102b、若所述组件模块需要集中存储信息，则将所述组件模块划分为所述中心组件组；S102c、若所述组件模块需要暴露统一的API接口，则将所述组件模块划分为所述中心组件组；以及S102d、若所述组件模块不需要集中存储信息且不需要暴露统一的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等组件模块均属于所述非中心组件组。
S103、获取预设部署区域，其中所述预设部署区域包括中心部署区域和非中心部署区域。
其中，该预设部署区域为用户需要部署该监控系统的区域，并在该区域上设置服务器，以将监控系统部署在该区域的服务器，实现对其他互联网产品的监控。该预设部署区域，具体可以为一个国家的几个城市，或者是一个城市的几个地区等，或者是一个公司不同的办公地点。
在本实施例中，该预设部署区域包括中心部署区域和非中心部署区域，其中，该中心部署区域包括深圳和上海，该非中心部署区域可以为广州、廊坊或青岛等地区。需要说明的是，该中心部署区域也可以作为非中心部署区域，比如，如图4所示，深圳、上海和廊坊即是非中心部署区域，也是中心部署区域，由此该预设部署区域为三地两中心，具体三地是指深圳、上海和廊坊，两中心是指深圳和上海。
S104、将属于所述非中心组件组的组件模块按照预设部署规则部署在所述中心部署区域和非中心部署区域。
在本实施例中，该预设部署规则是根据属于所述非中心组件组中的多个组件模块的功能进行预先设定的部署规则，目的使得属于非中心组件组的组件模块的部署逻辑更加合理，功能划分更加清晰。
具体地，将属于所述非中心组件组的组件模块按照预设部署规则部署在所述中心部署区域和非中心部署区域，是将属于所述非中心组件组的组件模块按照预设逻辑分区部署在所述中心部署区域和非中心部署区域。
在本实施例中，所述预设逻辑分区具体包括：可用区、公共服务区和云管区。如图3所示，步骤S104包括：子步骤S104a和S104b。
S104a、获取预设关系表，其中所述预设关系表包括属于所述非中心组件组的组件模块与所述可用区、公共服务区和云管区的对应关系；S104b、根据所述预设关系表将属于所述非中心组件组的组件模块分别对应部署在所述可用区、公共服务区和云管区。
具体地，该预设逻辑分区采用三层架构，从下而上分为可用区，公共服务区和云管区。根据组件模块的功能进行部署，具有不同功能的组件模块部署在不同区域。可通过预设关系表设置属于所述非中心组件组的组件模块与所述可用区、公共服务区和云管区的对应关系，在部署时可以根据该对应关系将属于所述非中心组件组的不同组件模块分别对应部署在所述可用区、公共服务区和云管区。
譬如，将主机信息采集和上报的对应的组件模块部署在可用区，比如：agent模块组件起代理转发功能部署在公共服务区；gateway组件模块和proxy组件模块为处理性能数据、告警数据或者下发指令部署在云管区；transfer、judge、graph、redis、mysql和alarm等组件模块也部署在云管区。将属于所述非中心组件组的组件模块按照预设逻辑分区部署在所述中心部署区域和非中心部署区域，使得监控系统的功能划分更加清晰；同时也具有更好的安全性。
具体地，用户的云主机部署在可用区，公共服务区为该可用区提供基础服务，如监控、部署、yum(安装软件服务)、ntp(时间同步服务)和dns(域名解析服务)等。云管区部署云平台的中心节点系统的应用。因此和用户有直接交互的平台服务放在靠近可用区的公共服务区，而云平台自身的核心服务放置在云管区，由此安全隔离性更好，中间多增加一个逻辑隔离层，用户的主机不能直接和云平台的核心系统做交互，因此这样有助于增加系统的安全性，这样核心系统不容易受到来自用户区域的直接攻击和非法访问。
需要说明的是，在具体部署时可以根据上述部署方法借助容器集群管理系统(Kubernetes，简称K8s)对所述监控系统的非中心组件组的组件模块进行部署，当然也可以采用其他的管理系统进行部署，比如Ansible管理系统。
S105、将属于所述中心组件组的组件模块部署在所述中心部署区域以完成对所述监控系统的部署。
在本实施例中，是将属于所述中心组件组的多个组件模块部署在中心部署区域，比如部署深圳中心区和上海中心区。具体也可采用所述容器集群管理系统(Kubernetes，简称K8s)进行部署。
请参照图4，图4是采用本实施例中的部署方法部署的监控系统的部署效果示意图。图4中非中心部署区域和中心部署区域均包括云管区、公共服务区和可用区，该逻辑分区用于部署属于非中心组件组的组件模块，图4中中心部 署区域还用于部署属于中心组件组的组件模块，对于属于中心组件组的组件模块不采用逻辑分区的方式进行部署。
在本实施例中，所述预设部署区域包括两个中心部署区域和至少一个非中心部署区域，两个所述中心部署区域分别为生产数据中心区和灾备数据中心区。如图4所示，具体为深圳生成数据中心和上海灾备数据中心区，以及深圳、上海和廊坊等非中心部署区域。属于非中心组件组的组件模块在深圳、上海和廊坊均采用逻辑分区部署进行部署，属于中心组件组的组件模块只部署在深圳生成数据中心和上海灾备数据中心区。
上述实施例的部署方法根据监控系统的组件模块的组件信息将组件模块划分为中心组件组和非中心组件组，再将属于所述非中心组件组的组件模块按照预设部署规则部署在所述中心部署区域和非中心部署区域；以及将属于所述中心组件组的组件模块部署在所述中心部署区域以完成对所述监控系统的部署。该部署方法可以实现三地两中心的部署方式，这种部署方式有利于数据的分布式存储，以及提高了监控系统的高可用性。
请参阅图5，图5是本申请实施例提供的一种监控系统的部署装置的示意性框图。该监控系统的部署装置400可以安装于服务器中。如图5所示，监控系统的部署装置400包括：信息获取单元401、组件划分单元402、区域获取单元403、第一部署单元404和第二部署单元405。
信息获取单元401，用于获取监控系统的组件模块对应的组件信息，其中所述监控系统包括多个组件模块。
组件划分单元402，用于基于所述组件信息根据预设划分规则将多个所述组件模块划分为中心组件组和非中心组件组。
具体地，组件划分单元402，包括：组件判断子单元4021、第一划分子单元4022、第二划分子单元4023和第三划分子单元4024。
其中，组件判断子单元4021，用于根据所述组件功能信息判断所述组件模块是否需要集中存储信息，以及根据所述API接口信息判断所述组件模块是否需要暴露统一的API接口；第一划分子单元4022，用于若所述组件模块需要集中存储信息，则将所述组件模块划分为所述中心组件组；第二划分子单元4023，用于若所述组件模块需要暴露统一的API接口，则将所述组件模块划分为所述 中心组件组；以及第三划分子单元4024，用于若所述组件模块不需要集中存储信息且不需要暴露统一的API接口，则将所述组件模块划分为所述非中心组件组。
区域获取单元403，用于获取预设部署区域，其中所述预设部署区域包括中心部署区域和非中心部署区域。
第一部署单元404，用于将属于所述非中心组件组的组件模块按照预设部署规则部署在所述中心部署区域和非中心部署区域。
其中，第一部署单元404，具体用于将属于所述非中心组件组的组件模块按照预设逻辑分区部署在所述中心部署区域和非中心部署区域。
具体地，第一部署单元404，包括：关系表获取子单元4041和组件部署子单元4042。其中，关系表获取子单元4041，用于获取预设关系表，其中所述预设关系表包括属于所述非中心组件组的组件模块与所述可用区、公共服务区和云管区的对应关系；组件部署子单元4042，用于根据所述预设关系表将属于所述非中心组件组的组件模块分别对应部署在所述可用区、公共服务区和云管区。
第二部署单元405，用于将属于所述中心组件组的组件模块部署在所述中心部署区域以完成对所述监控系统的部署。
所属领域的技术人员可以清楚地了解到，为了描述的方便和简洁，上述描述的监控系统的部署装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的监控系统的部署装置和方法，可以通过其它的方式实现。例如，以上所描述的监控系统的部署装置实施例仅仅是示意性的。例如，各个单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。
上述装置可以实现为一种计算机程序的形式，计算机程序可以在如图6所示的计算机设备上运行。
请参阅图6，图6是本申请实施例提供的一种计算机设备的示意性框图。该计算机设备700设备可以是服务器。
参照图6，该计算机设备700包括通过系统总线710连接的处理器720、存 储器和网络接口750，其中，存储器可以包括非易失性存储介质730和内存储器740。
该非易失性存储介质730可存储操作系统731和计算机程序732。该计算机程序732被执行时，可使得处理器720执行一种监控系统的部署方法。
该处理器720用于提供计算和控制能力，支撑整个计算机设备700的运行。
该内存储器740为非易失性存储介质中的计算机程序的运行提供环境，该计算机程序被处理器720执行时，可使得处理器720执行一种监控系统的部署方法。
该网络接口750用于进行网络通信，如发送分配的任务等。本领域技术人员可以理解，图6中示出的结构，仅仅是与本申请方案相关的部分结构的框图，并不构成对本申请方案所应用于其上的计算机设备700的限定，具体的计算机设备700可以包括比图中所示更多或更少的部件，或者组合某些部件，或者具有不同的部件布置。
其中，所述处理器720用于运行存储在存储器中的程序代码，以实现如下步骤：获取监控系统的组件模块对应的组件信息，其中所述监控系统包括多个组件模块；基于所述组件信息根据预设划分规则将多个所述组件模块划分为中心组件组和非中心组件组；获取预设部署区域，其中所述预设部署区域包括中心部署区域和非中心部署区域；将属于所述非中心组件组的组件模块按照预设部署规则部署在所述中心部署区域和非中心部署区域；以及将属于所述中心组件组的组件模块部署在所述中心部署区域以完成对所述监控系统的部署。
在一实施例中，处理器720在执行所述将属于所述非中心组件组的组件模块按照预设部署规则部署在所述中心部署区域和非中心部署区域时，具体执行如下步骤：
将属于所述非中心组件组的组件模块按照预设逻辑分区部署在所述中心部署区域和非中心部署区域。
在一实施例中，所述预设逻辑分区具体包括：可用区、公共服务区和云管区，处理器720在执行所述将属于所述非中心组件组的组件模块按照预设逻辑分区部署在所述中心部署区域和非中心部署区域时，具体执行如下步骤：
获取预设关系表，其中所述预设关系表包括属于所述非中心组件组的组件模块与所述可用区、公共服务区和云管区的对应关系；以及
根据所述预设关系表将属于所述非中心组件组的组件模块分别对应部署在所述可用区、公共服务区和云管区。
在一实施例中，所述组件信息包括组件功能信息和API接口信息，处理器720在执行所述基于所述组件信息根据预设划分规则将多个所述组件模块划分为中心组件组和非中心组件组时，具体执行如下步骤：
根据所述组件功能信息判断所述组件模块是否需要集中存储信息，以及根据所述API接口信息判断所述组件模块是否需要暴露统一的API接口；
若所述组件模块需要集中存储信息，则将所述组件模块划分为所述中心组件组；
若所述组件模块需要暴露统一的API接口，则将所述组件模块划分为所述中心组件组；以及
若所述组件模块不需要集中存储信息且不需要暴露统一的API接口，则将所述组件模块划分为所述非中心组件组。
应当理解，在本申请实施例中，处理器720可以是中央处理单元(Central Processing Unit，CPU)，该处理器720还可以是其他通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现成可编程门阵列(Field-Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。其中，通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
本领域技术人员可以理解，图6中示出的计算机设备700结构并不构成对计算机设备700的限定，可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置。
本领域普通技术人员可以理解的是实现上述实施例方法中的全部或部分流程，是可以通过计算机程序来指令相关的硬件来完成，程序可存储于一存储介质中，该存储介质为计算机可读存储介质。如本发明实施例中，该程序可存储于计算机系统的存储介质中，并被该计算机系统中的至少一个处理器执行，以实现包括如上述各监控系统的部署方法的实施例的流程步骤。
该计算机可读存储介质可以是磁碟、光盘、U盘、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示 例的单元及算法步骤，能够以电子硬件、计算机软件或者二者的结合来实现，为了清楚地说明硬件和软件的可互换性，在上述说明中已经按照功能一般性地描述了各示例的组成及步骤。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例方法中的步骤可以根据实际需要进行顺序调整、合并和删减。申请实施例装置中的单元可以根据实际需要进行合并、划分和删减。另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以是两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
该集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分，或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，终端，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到各种等效的修改或替换，这些修改或替换都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以权利要求的保护范围为准。

Claims (20)

  1. 一种监控系统的部署方法，其包括：
    获取监控系统的组件模块对应的组件信息，其中所述监控系统包括多个组件模块；
    基于所述组件信息根据预设划分规则将多个所述组件模块划分为中心组件组和非中心组件组；
    获取预设部署区域，其中所述预设部署区域包括中心部署区域和非中心部署区域；
    将属于所述非中心组件组的组件模块按照预设部署规则部署在所述中心部署区域和非中心部署区域；以及
    将属于所述中心组件组的组件模块部署在所述中心部署区域以完成对所述监控系统的部署。
  2. 根据权利要求1所述的监控系统的部署方法，其中，所述将属于所述非中心组件组的组件模块按照预设部署规则部署在所述中心部署区域和非中心部署区域，包括：
    将属于所述非中心组件组的组件模块按照预设逻辑分区部署在所述中心部署区域和非中心部署区域。
  3. 根据权利要求2所述的监控系统的部署方法，其中，所述预设逻辑分区具体包括：可用区、公共服务区和云管区；
    所述将属于所述非中心组件组的组件模块按照逻辑分区部署在所述中心部署区域和非中心部署区域，包括：
    获取预设关系表，其中所述预设关系表包括属于所述非中心组件组的组件模块与所述可用区、公共服务区和云管区的对应关系；以及
    根据所述预设关系表将属于所述非中心组件组的组件模块分别对应部署在所述可用区、公共服务区和云管区。
  4. 根据权利要求1所述的监控系统的部署方法，其中，所述预设部署区域包括两个中心部署区域和至少一个非中心部署区域，两个所述中心部署区域分别为生产数据中心区和灾备数据中心区。
  5. 根据权利要求1所述的监控系统的部署方法，其中，所述组件信息包括 组件功能信息和API接口信息；
    所述基于所述组件信息根据预设划分规则将多个所述组件模块划分为中心组件组和非中心组件组，包括：
    根据所述组件功能信息判断所述组件模块是否需要集中存储信息，以及根据所述API接口信息判断所述组件模块是否需要暴露统一的API接口；
    若所述组件模块需要集中存储信息，则将所述组件模块划分为所述中心组件组；
    若所述组件模块需要暴露统一的API接口，则将所述组件模块划分为所述中心组件组；以及
    若所述组件模块不需要集中存储信息且不需要暴露统一的API接口，则将所述组件模块划分为所述非中心组件组。
  6. 根据权利要求1所述的监控系统的部署方法，其中，所述将属于所述非中心组件组的组件模块按照预设部署规则部署在所述中心部署区域和非中心部署区域，包括：
    借助容器集群管理系统对所述监控系统的非中心组件组的组件模块进行部署。
  7. 根据权利要求1所述的监控系统的部署方法，其中，所述组件信息包括组件模块的标识信息、组件功能信息和API接口信息。
  8. 一种监控系统的部署装置，其包括：
    信息获取单元，用于获取监控系统的组件模块对应的组件信息，其中所述监控系统包括多个组件模块；
    组件划分单元，用于基于所述组件信息根据预设划分规则将多个所述组件模块划分为中心组件组和非中心组件组；
    区域获取单元，用于获取预设部署区域，其中所述预设部署区域包括中心部署区域和非中心部署区域；
    第一部署单元，用于将属于所述非中心组件组的组件模块按照预设部署规则部署在所述中心部署区域和非中心部署区域；以及
    第二部署单元，用于将属于所述中心组件组的组件模块部署在所述中心部署区域以完成对所述监控系统的部署。
  9. 根据权利要求8所述的监控系统的部署装置，其中，第一部署单元，具 体用于将属于所述非中心组件组的组件模块按照预设逻辑分区部署在所述中心部署区域和非中心部署区域。
  10. 根据权利要求9所述的监控系统的部署装置，其中，所述预设逻辑分区具体包括：可用区、公共服务区和云管区；
    所述第一部署单元，包括：
    关系表获取子单元，用于获取预设关系表，其中所述预设关系表包括属于所述非中心组件组的组件模块与所述可用区、公共服务区和云管区的对应关系；
    组件部署子单元，用于根据所述预设关系表将属于所述非中心组件组的组件模块分别对应部署在所述可用区、公共服务区和云管区。
  11. 一种计算机设备，其中，包括存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述处理器执行所述计算机程序时实现：获取监控系统的组件模块对应的组件信息，其中所述监控系统包括多个组件模块；基于所述组件信息根据预设划分规则将多个所述组件模块划分为中心组件组和非中心组件组；获取预设部署区域，其中所述预设部署区域包括中心部署区域和非中心部署区域；将属于所述非中心组件组的组件模块按照预设部署规则部署在所述中心部署区域和非中心部署区域；以及将属于所述中心组件组的组件模块部署在所述中心部署区域以完成对所述监控系统的部署。
  12. 根据权利要求11所述的计算机设备，其中，所述处理器执行所述计算机程序以实现将属于所述非中心组件组的组件模块按照预设部署规则部署在所述中心部署区域和非中心部署区域时，具体实现：将属于所述非中心组件组的组件模块按照预设逻辑分区部署在所述中心部署区域和非中心部署区域。
  13. 根据权利要求12所述的计算机设备，其中，所述预设逻辑分区具体包括：可用区、公共服务区和云管区；所述处理器执行所述计算机程序以实现将属于所述非中心组件组的组件模块按照逻辑分区部署在所述中心部署区域和非中心部署区域时，具体实现：获取预设关系表，其中所述预设关系表包括属于所述非中心组件组的组件模块与所述可用区、公共服务区和云管区的对应关系；以及根据所述预设关系表将属于所述非中心组件组的组件模块分别对应部署在所述可用区、公共服务区和云管区。
  14. 根据权利要求11所述的计算机设备，其中，所述预设部署区域包括两个中心部署区域和至少一个非中心部署区域，两个所述中心部署区域分别为生 产数据中心区和灾备数据中心区。
  15. 根据权利要求11所述的计算机设备，其中，所述组件信息包括组件功能信息和API接口信息；所述处理器执行所述计算机程序以实现基于所述组件信息根据预设划分规则将多个所述组件模块划分为中心组件组和非中心组件组时，具体实现：根据所述组件功能信息判断所述组件模块是否需要集中存储信息，以及根据所述API接口信息判断所述组件模块是否需要暴露统一的API接口；若所述组件模块需要集中存储信息，则将所述组件模块划分为所述中心组件组；若所述组件模块需要暴露统一的API接口，则将所述组件模块划分为所述中心组件组；以及若所述组件模块不需要集中存储信息且不需要暴露统一的API接口，则将所述组件模块划分为所述非中心组件组。
  16. 一种存储介质，其中，所述存储介质存储有计算机程序，所述计算机程序包括程序指令，所述程序指令当被处理器执行时使所述处理器执行：获取监控系统的组件模块对应的组件信息，其中所述监控系统包括多个组件模块；基于所述组件信息根据预设划分规则将多个所述组件模块划分为中心组件组和非中心组件组；获取预设部署区域，其中所述预设部署区域包括中心部署区域和非中心部署区域；将属于所述非中心组件组的组件模块按照预设部署规则部署在所述中心部署区域和非中心部署区域；以及将属于所述中心组件组的组件模块部署在所述中心部署区域以完成对所述监控系统的部署。
  17. 根据权利要求16所述的存储介质，其中，所述程序指令当被处理器执行将属于所述非中心组件组的组件模块按照预设部署规则部署在所述中心部署区域和非中心部署区域时，使所述处理器执行：将属于所述非中心组件组的组件模块按照预设逻辑分区部署在所述中心部署区域和非中心部署区域。
  18. 根据权利要求17所述的存储介质，其中，所述预设逻辑分区具体包括：可用区、公共服务区和云管区；所述程序指令当被处理器执行将属于所述非中心组件组的组件模块按照逻辑分区部署在所述中心部署区域和非中心部署区域时，使所述处理器执行：获取预设关系表，其中所述预设关系表包括属于所述非中心组件组的组件模块与所述可用区、公共服务区和云管区的对应关系；以及根据所述预设关系表将属于所述非中心组件组的组件模块分别对应部署在所述可用区、公共服务区和云管区。
  19. 根据权利要求16所述的存储介质，其中，所述预设部署区域包括两个 中心部署区域和至少一个非中心部署区域，两个所述中心部署区域分别为生产数据中心区和灾备数据中心区。
  20. 根据权利要求16所述的存储介质，其中，所述组件信息包括组件功能信息和API接口信息；所述程序指令当被处理器执行基于所述组件信息根据预设划分规则将多个所述组件模块划分为中心组件组和非中心组件组时，使所述处理器执行：根据所述组件功能信息判断所述组件模块是否需要集中存储信息，以及根据所述API接口信息判断所述组件模块是否需要暴露统一的API接口；若所述组件模块需要集中存储信息，则将所述组件模块划分为所述中心组件组；若所述组件模块需要暴露统一的API接口，则将所述组件模块划分为所述中心组件组；以及若所述组件模块不需要集中存储信息且不需要暴露统一的API接口，则将所述组件模块划分为所述非中心组件组。
PCT/CN2018/084529 2018-02-07 2018-04-26 监控系统的部署方法、装置、计算机设备及存储介质 WO2019153524A1 (zh)

Applications Claiming Priority (2)

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

Publications (1)

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

Family

ID=62928340

Family Applications (1)

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

Country Status (2)

Country Link
CN (1) CN108337315B (zh)
WO (1) WO2019153524A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113238928A (zh) * 2021-04-23 2021-08-10 杭州电子科技大学 一种音视频大数据任务的端云协同评测系统
CN113596185A (zh) * 2021-06-23 2021-11-02 阿里巴巴新加坡控股有限公司 基于可用区的域名解析方法、装置、设备和机器可读介质

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109451047B (zh) * 2018-12-13 2021-05-18 深圳前海微众银行股份有限公司 监控告警系统的数据传送方法、装置、设备及存储介质
CN110012088B (zh) * 2019-03-29 2022-05-24 浪潮云信息技术股份公司 一种基于Kubernets的Redis主从集群自动化部署方案
CN110413286B (zh) * 2019-07-31 2023-08-22 创新先进技术有限公司 一种应用部署方法、装置及设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102724057A (zh) * 2012-02-23 2012-10-10 北京市计算中心 一种面向云计算平台的分布式层次化自主管理方法
US8301759B2 (en) * 2008-10-24 2012-10-30 Microsoft Corporation Monitoring agent programs in a distributed computing platform
CN105739412A (zh) * 2016-04-16 2016-07-06 张晓晓 具远程监控功能的基于物联网技术的电力调度装置
CN105975378A (zh) * 2016-05-11 2016-09-28 国网江苏省电力公司 一种面向超级计算机的分布式层次化自主监控管理系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8301759B2 (en) * 2008-10-24 2012-10-30 Microsoft Corporation Monitoring agent programs in a distributed computing platform
CN102724057A (zh) * 2012-02-23 2012-10-10 北京市计算中心 一种面向云计算平台的分布式层次化自主管理方法
CN105739412A (zh) * 2016-04-16 2016-07-06 张晓晓 具远程监控功能的基于物联网技术的电力调度装置
CN105975378A (zh) * 2016-05-11 2016-09-28 国网江苏省电力公司 一种面向超级计算机的分布式层次化自主监控管理系统

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113238928A (zh) * 2021-04-23 2021-08-10 杭州电子科技大学 一种音视频大数据任务的端云协同评测系统
CN113238928B (zh) * 2021-04-23 2022-05-06 杭州电子科技大学 一种音视频大数据任务的端云协同评测系统
CN113596185A (zh) * 2021-06-23 2021-11-02 阿里巴巴新加坡控股有限公司 基于可用区的域名解析方法、装置、设备和机器可读介质

Also Published As

Publication number Publication date
CN108337315A (zh) 2018-07-27
CN108337315B (zh) 2019-10-08

Similar Documents

Publication Publication Date Title
WO2019153524A1 (zh) 监控系统的部署方法、装置、计算机设备及存储介质
EP2879060B1 (en) Cloud application disaster recovery method, system and device
CN110737442A (zh) 一种边缘应用管理方法及系统
WO2019184164A1 (zh) 自动部署Kubernetes从节点的方法、装置、终端设备及可读存储介质
JP2020510384A (ja) ネットワークスライス管理方法、ユニット、及びシステム
WO2019153532A1 (zh) 监控系统的部署方法、装置、计算机设备及存储介质
CN104718723A (zh) 用于虚拟网络中的联网和安全服务的框架
KR20170024606A (ko) 소프트웨어 정의 네트워크 중의 서비스 편성 방법 및 장치, 저장 매체
CN103607430A (zh) 一种网络处理的方法和系统及网络控制中心
CN104956332A (zh) 主自动化服务
JP2017503421A (ja) ネットワーク機能仮想化ｎｆｖ障害管理の装置、デバイス、および方法
CA2975242A1 (en) System, virtualization control apparatus, method for controlling a virtualization control apparatus, and program
WO2017121153A1 (zh) 软件升级方法及装置
CN112202853B (zh) 数据同步方法、系统、计算机设备和存储介质
CN109714188A (zh) 基于Zookeeper的配置数据管理方法、设备和存储介质
CN109976941A (zh) 一种数据恢复方法和装置
CN109525590B (zh) 数据包的传输方法及装置
CN106330546A (zh) 一种在私有云环境中应用集群部署的系统和方法
CN115150419B (zh) 一种混合云对象存储的配置和访问方法及系统
WO2014193879A1 (en) Improved deployment of virtual machines by means of differencing disks
CN111045802B (zh) Redis集群组件调度系统及方法、平台设备
CN108234587B (zh) 一种基于OpenStack多region镜像资源共享的方法
CN104516744A (zh) 软件更新方法及系统
CN110839007B (zh) 一种云网络安全处理方法、设备和计算机存储介质
JP2016126364A (ja) システムのバックアップ装置及びバックアップ方法

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: 18904603

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 03.11.2020)

122 Ep: pct application non-entry in european phase

Ref document number: 18904603

Country of ref document: EP

Kind code of ref document: A1