Method and device for continuous collection of paas platform indicators

Abstract

The embodiment of the present application provides a kind of PAAS platform index continuous collection method and device, comprising: based on the first monitoring channel real-time acquisition first container list;Based on the second monitoring channel real-time acquisition second container list;The second container list is the container list of the application needing to be scaled according to custom index;According to the first container list and the second container list, the service needing to collect index is found by preset service discovery rule, and the collection of the index is completed.The embodiment of the present application is by means of double-channel service discovery mechanism, and the application container needing to use custom index dynamic scaling is found by the second monitoring channel, so that when dynamic scaling configuration changes, monitoring module configuration does not need to be reloaded, and then the continuity of PAAS platform monitoring module index collection is guaranteed.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computer, and particularly relates to a PAAS platform index continuous collection method and device. BACKGROUND

[0002] PAAS platform (Platform-as-a-Service) is a business model that provides the running and development environment of application service as a service. The running of application service in the PAAS platform is based on a container orchestration module, and the application service runs in the form of a container in a container cluster. The container orchestration module is responsible for the scheduling and elastic scaling of containers in the cluster.

[0003] A user deploys a microservice in the container orchestration module, and the user can specify the number of replicas when deploying the microservice. The platform automatically implements distributed deployment of the microservice according to the specified number of replicas.

[0004] In actual application, the business pressure of the microservice changes greatly at different time periods and business stages. If the number of replicas of the microservice is directly specified, resource waste may occur at a business low peak, and the number of replicas may not meet the needs at a business high peak.

[0005] The container orchestration module provides a container elastic scaling function. Generally, the container orchestration module supports automatic scaling of the number of containers according to the cpu and memory occupancy rate of the containers, and can expand the function by connecting a monitoring module. The container orchestration module supports scaling according to custom indicators exposed by an application.

[0006] The monitoring module obtains the indicator values exposed by the monitoring target by pulling, and stores the collection results in a time series database for subsequent analysis. The monitoring system calls the API exposed by the monitored target at a set time interval to obtain the exposed indicator values. When the monitoring system is configured to be fixed and does not have problems such as insufficient resources and network delay, the continuity of platform indicator collection can be ensured.

[0007] However, for each application that needs to be dynamically scaled according to the custom index, a task needs to be configured in the monitoring module configuration file, and when the dynamically scaled application changes, the configuration file needs to be modified, and then the monitoring module (such as calling the hot update interface) is reloaded to take effect. The monitoring module configuration reload will have a great impact on the work of the monitoring module itself. For example, Prometheus, the hot update interface needs to be called, and the hot update configuration will reload the entire configuration file and the related rule file. When the configuration file is large or the Prometheus configuration file is frequently hot-loaded, Prometheus may be temporarily unresponsive, affecting the grabbing of indicators, and causing some indicators to be lost. Therefore, the existing container orchestration module based on the monitoring module service discovery according to the application custom index for scaling scheme will cause an impact on the work of the monitoring module when modifying the scaling configuration, which may cause the loss of monitoring indicators. SUMMARY

[0008] In view of the problems in the prior art, the embodiments of the present application provide a PAAS platform index continuous collection method and device.

[0009] In a first aspect, the embodiments of the present application provide a PAAS platform index continuous collection method, comprising:

[0010] Real-time acquisition of a first container list based on a first listening channel;

[0011] Real-time acquisition of a second container list based on a second listening channel; the second container list is a container list of an application that needs to be scaled according to a custom index;

[0012] Discovery of a service that needs to collect indicators according to a preset service discovery rule based on the first container list and the second container list, and completion of the collection of the indicators.

[0013] Further, the discovery of the service that needs to collect indicators according to the preset service discovery rule based on the first container list and the second container list, and the completion of the collection of the indicators, comprises:

[0014] Collection of indicator values exposed by a container according to the second container list.

[0015] Further, before the collection of the indicator values exposed by the container according to the second container list, further comprising:

[0016] Writing the second container list into a service discovery file.

[0017] Further, further comprising:

[0018] Reading the service discovery file to obtain container information of an application that needs to be scaled according to a custom index.

[0019] In a second aspect, an embodiment of the present application provides a device for continuous collection of PAAS platform indexes, comprising:

[0020] a first obtaining module, configured to obtain a first container list in real time based on a first listening channel;

[0021] a second obtaining module, configured to obtain a second container list in real time based on a second listening channel; the second container list is a container list of an application that needs to be scaled according to a custom index;

[0022] an index collecting module, configured to discover a service that needs to collect an index according to the first container list and the second container list through a preset service discovery rule, and complete collection of the index.

[0023] Further, the index collecting module is configured to:

[0024] collect an index value exposed by a container according to the second container list.

[0025] Further, the device further comprises a writing module,

[0026] the writing module is configured to write the second container list into a service discovery file before collecting the index value exposed by the container according to the second container list.

[0027] Further, the device further comprises a reading module,

[0028] the reading module is configured to read the service discovery file and obtain container information of the application that needs to be scaled according to the custom index.

[0029] In a third aspect, an embodiment of the present application further provides an electronic device, comprising a memory, a processor, and a computer program stored in the memory and capable of running on the processor, wherein the processor implements steps of the method for continuous collection of PAAS platform indexes according to the first aspect when executing the program.

[0030] In a fourth aspect, an embodiment of the present application further provides a non-transitory computer readable storage medium, which stores a computer program, wherein the computer program is executed by a processor to implement steps of the method for continuous collection of PAAS platform indexes according to the first aspect.

[0031] From the above technical solutions, the method and device for continuous collection of PAAS platform indexes provided by the embodiments of the present application can realize real-time acquisition of a first container list based on a first monitoring channel, real-time acquisition of a second container list based on a second monitoring channel, the second container list being a container list of an application that needs to be scaled according to a custom index, discovery of a service that needs to collect indexes according to a preset service discovery rule based on the first container list and the second container list, and completion of the collection of the indexes. The embodiments of the present application use a double-channel service discovery mechanism to discover application containers that need to be dynamically scaled according to custom indexes from the second monitoring channel, so that when dynamic scaling configuration changes, the monitoring module configuration does not need to be reloaded, thereby ensuring the continuity of the collection of indexes by the PAAS platform monitoring module. BRIEF DESCRIPTION OF DRAWINGS

[0032] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the drawings needed to be used in the embodiments or the prior art description will be briefly introduced. Obviously, the drawings in the following description are some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative labor.

[0033] Figure 1 The flowchart of the method for continuous collection of PAAS platform indexes provided by an embodiment of the present application is shown in the figure.

[0034] Figure 2 The traditional architecture diagram of container scaling based on custom indexes provided by the PAAS platform of the prior art is shown in the figure.

[0035] Figure 3 The timing sequence diagram of the interaction between modules when the PAAS platform based on custom indexes performs container scaling provided by an embodiment of the prior art is shown in the figure.

[0036] Figure 4 The service discovery rule configuration example diagram in the configuration file of the monitoring module Prometheus provided by an embodiment of the prior art is shown in the figure.

[0037] Figure 5 The traditional architecture diagram of container scaling based on custom indexes provided by the PAAS platform of another embodiment of the prior art is shown in the figure.

[0038] Figure 6 The architecture diagram of container scaling based on custom indexes provided by an embodiment of the present application is shown in the figure.

[0039] Figure 7 The deployment architecture diagram of container scaling based on custom indexes provided by an embodiment of the present application is shown in the figure.

[0040] Figure 8 A structural schematic diagram of a device for continuous collection of PAAS platform indexes provided by an embodiment of the present application is shown in the figure.

[0041] Figure 9 An entity structural schematic diagram of an electronic device in an embodiment of the present application is shown in the figure. DETAILED DESCRIPTION

[0042] To make the objectives, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be described clearly below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are some but not all of the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative work fall within the scope of protection of the present application. The method for continuous collection of PAAS platform indexes provided by the present application will be explained and described in detail below through specific embodiments.

[0043] Figure 1 A flowchart of the method for continuous collection of PAAS platform indexes provided by an embodiment of the present application is shown in the figure. As shown in the figure, the method comprises the following steps. Figure 1

[0044] Step 101: Real-time acquisition of a first container list based on a first listening channel.

[0045] Step 102: Real-time acquisition of a second container list based on a second listening channel. The second container list is a container list of an application that needs to be scaled according to a custom index.

[0046] Step 103: Discovery of a service that needs to collect an index according to a preset service discovery rule based on the first container list and the second container list, and completion of the collection of the index.

[0047] In the embodiment, it is necessary to note that PAAS platform (Platform-as-a-Service: platform as a service) is a business model that provides the running and development environment of an application service as a service. The running of the application service in the PAAS platform is based on a container orchestration module, and the application service runs in a container cluster in the form of a container. The container orchestration module is responsible for the scheduling, elastic scaling and other functions of the containers in the cluster.

[0048] A user deploys a microservice in the container orchestration module, and the user can specify the number of replicas when deploying the microservice. The platform automatically realizes the distributed deployment of the microservice according to the specified number of replicas.

[0049] ​In practical application, the business pressure of microservices changes greatly in different periods and business stages. If the number of microservice replicas is directly specified, it may cause resource waste in business low peak and the number of replicas may not meet the needs in business peak.

[0050] The container orchestration module provides container elasticity scaling function, generally supports automatic scaling of the number of containers according to the CPU and memory occupancy rate of the container, and can be expanded through the interface of the monitoring module. It supports scaling according to the custom indicators exposed by the application.

[0051] The monitoring module obtains the exposed indicator values of the monitoring target by pulling, and stores the collection results in the time series database for subsequent analysis. The monitoring system calls the exposed API of the monitored target at a set time interval to obtain the exposed indicator values. When the monitoring system configuration is fixed and does not change, there is no resource shortage, network delay and other problems, which can ensure the continuity of platform indicator collection.

[0052] The container orchestration module collects container custom indicators based on the monitoring module to realize traditional architecture for container scaling according to custom indicators, as shown in Figure 2 .

[0053] The container cluster in the PAAS platform provides several computing nodes for deploying and running microservices. Microservices run in the form of containers in the container cluster. A container group is a group of containers, and the containers in the group can share some resources.

[0054] The container orchestration module is responsible for the scheduling, arrangement, and scaling (including manual and automatic elasticity scaling) of containers in the container.

[0055] The monitoring module in the PAAS application is responsible for monitoring various resources of the PAAS platform. In this scenario, the monitoring module is used to capture application custom indicator values, and the elasticity scaling controller dynamically scales the number of application containers according to the indicator values.

[0056] As shown in Figure 3 , in the traditional architecture, the elasticity scaling controller in the container orchestration module dynamically scales the number of application container groups according to the exposed indicator values of the application container groups, which needs the following steps:

[0057] Step 1, the monitoring system adapter registers its service in the container orchestration module custom indicator API for the elasticity scaling controller to call;

[0058] Step 2, the monitoring module captures the exposed indicator values of the application container group;

[0059] Step 3, the monitoring module adapter obtains the indicator values from the monitoring module and converts them into a format that the container orchestration module can recognize;

[0060] Step 4, the elastic scaling controller accesses the monitoring module adapter to obtain the custom index value by calling the custom index API;

[0061] Step 5, according to the custom index value, the number of application containers is scaled (actual implementation may be asynchronous, the elastic scaling controller adjusts the container number target value by calling the API service, and the platform implements asynchronous container creation / destruction).

[0062] Before monitoring the container index of an application, it is necessary to know which containers the application currently has, and then access these containers to obtain the index value. To achieve this function, the service discovery rule needs to be configured in the configuration file of the monitoring module. Figure 4 The service discovery rule configuration example in the Prometheus configuration file of the monitoring module.

[0063] In the PAAS platform, after the user deploys an application on the platform, if the user needs to perform custom index scaling on the application, the PAAS backend service needs to call the container orchestration module API to create a dynamic scaling configuration, and create a corresponding task in the monitoring module, so that the monitoring module can discover the container list of the application and access the corresponding container to obtain the custom index. The main flow chart is shown in Figure 5 The index acquisition module in the monitoring module needs to call the service discovery module to obtain the target list for monitoring, and pull the index according to the obtained target list.

[0064] The service discovery module obtains the target list in real time by establishing a long connection with the container orchestration module API according to the configured rule, for use by the index acquisition module.

[0065] After deploying a custom scaling application and configuring a custom scaling rule, the monitoring module needs to add a task and the corresponding service discovery rule in the monitoring module configuration, so that the monitoring module can obtain the container information of the application in real time. After modifying the monitoring module configuration, the monitoring module needs to be reloaded (such as calling a specified API) to take effect.

[0066] In this embodiment, to solve the problem of interruption in PaaS platform index collection in the prior art, a dual-channel mechanism is used to realize the continuity of PaaS platform index collection, that is, a first container list is obtained in real time based on a first listening channel; a second container list is obtained in real time based on a second listening channel; the second container list is the container list of an application that needs to be scaled according to a custom index; and a service that needs to collect an index is discovered through a preset service discovery rule according to the first container list and the second container list, and the collection of the index is completed.

[0067] Specifically, for example, see Figure 6The provided architecture diagram for container scaling based on custom indicators shows that the embodiment adds an elastic scaling control module to the traditional architecture. This service is responsible for listening to the container orchestration module API interface to obtain the container list of the application that needs to be scaled based on custom indicators in real time (i.e., obtaining the second container list based on the second listening channel), and writing to the service discovery file. Further, the elastic scaling control module supports configuration reloading. When the elastic scaling configuration changes, the elastic scaling module can be reloaded without reloading the entire monitoring module, preventing the impact on the monitoring module's index grabbing. The elastic scaling control module container and the monitoring module container are bound as a container group deployment, and efficient service discovery file interaction is achieved through shared mounting.

[0068] The monitoring module server calls the service discovery module to obtain the monitoring target. In the service discovery module, the container orchestration module service discovery rule is used to discover the services that need to collect indicators in the cluster, such as the container orchestration module core service and various middleware indicator exposure services. The target list of the application that needs to be dynamically scaled is discovered by the file service discovery rule, which reads the container list file output by the elastic scaling control module, thereby obtaining the container information of the application that needs to be scaled based on custom indicators.

[0069] In this embodiment, the service discovery logic for discovering custom scaling applications in the monitoring module is extracted, and a dual-channel mechanism service discovery is formed by the elastic scaling control module and the monitoring module itself service discovery, which is responsible for the service discovery of custom scaling applications, replacing part of the service discovery function of the monitoring module. The container list of the application is obtained in real time by listening to the container orchestration module API interface. Since a listening interface is used, a long connection is established, and when the container changes, the container orchestration module will immediately send the container change increment to the elastic scaling control module. The elastic scaling control module writes the discovered container list to a file, and the monitoring module only needs to configure a task based on file service discovery to read the container list file output by the elastic scaling control module, thereby obtaining the container list that needs to pull the indicator value, and pulling the indicator value exposed by the container based on this list.

[0070] When the elastic scaling configuration changes and the scaled application needs to be modified, the elastic scaling control module application can be reloaded to dynamically modify the monitored application, without reloading the monitoring module.

[0071] In this embodiment, the monitoring module and the elastic scaling control module are deployed in the same container group with multiple containers. The service discovery file is shared and mounted by the monitoring module and the elastic scaling control module container. The elastic scaling control module writes the container list file, and the monitoring module reads it. The monitoring module accesses the container to pull the indicator value based on the read container list. The provided deployment architecture diagram for container scaling based on custom indicators is shown in FIG. Figure 7 .

[0072] In the embodiment, it can be understood that the method for continuously collecting PAAS platform indexes provided by the embodiment provides a double-channel service discovery mechanism for the function of the PAAS platform expanding and shrinking the capacity according to the custom indexes collected by the monitoring module. The mechanism improves the mechanism of the monitoring module dynamically obtaining the application container information in the traditional scheme, and adds a service discovery channel (i.e., a second listening channel) to the existing service discovery channel, which is specially responsible for discovering services of the application container that needs to be dynamically expanded and shrunk in capacity. When the dynamic expansion and shrink configuration changes, the monitoring module configuration does not need to be reloaded, thereby guaranteeing the continuity of the monitoring module of the PAAS platform collecting indexes.

[0073] From the above technical solution, it can be understood that the method for continuously collecting PAAS platform indexes provided by the embodiment comprises the following steps: acquiring a first container list in real time based on a first listening channel; acquiring a second container list in real time based on a second listening channel; the second container list is a container list of an application that needs to be expanded and shrunk in capacity according to custom indexes; discovering services that need to collect indexes according to the first container list and the second container list through a preset service discovery rule, and completing the collection of the indexes. The embodiment uses the double-channel service discovery mechanism to discover the application container that needs to be dynamically expanded and shrunk in capacity using custom indexes from the second listening channel, so that when the dynamic expansion and shrink configuration changes, the monitoring module configuration does not need to be reloaded, thereby guaranteeing the continuity of the monitoring module of the PAAS platform collecting indexes.

[0074] On the basis of the above embodiment, in the embodiment, discovering services that need to collect indexes according to the first container list and the second container list through a preset service discovery rule, and completing the collection of the indexes, comprises the following steps:

[0075] Collecting the index values exposed by the container according to the second container list.

[0076] In the embodiment, it can be understood that collecting the index values exposed by the container according to the second container list provides an independent service discovery method to assist the monitoring module of the PAAS platform in service discovery. The process takes over part of the service discovery function of the monitoring module, and is specially responsible for discovering services of the application that is dynamically expanded and shrunk in capacity. The monitoring module only needs a file service discovery rule with fixed configuration, thereby reducing the configuration amount of the monitoring module, reducing the configuration data amount that needs to be maintained when the monitoring module works, reducing the number of network links maintained and the memory occupation when the monitoring module discovers services, and thereby reducing the work load of the monitoring module.

[0077] On the basis of the above embodiment, in the embodiment, before collecting the index values exposed by the container according to the second container list, the following step is further included:

[0078] write the second container list into a service discovery file.

[0079] On the basis of the above-mentioned embodiments, in this embodiment, further comprising:

[0080] read the service discovery file to obtain container information of an application that needs to be scaled according to a custom index.

[0081] In this embodiment, it can be understood that the method for continuously collecting indexes of a PAAS platform provided by the embodiments avoids the modification of the monitoring module configuration caused by the modification of the custom index dynamic scaling strategy configuration, thereby avoiding the service interruption problem caused by the reloading of the configuration.

[0082] From the above technical solution, it can be understood that the method for continuously collecting indexes of a PAAS platform provided by the embodiments obtains container information of an application that needs to be scaled according to a custom index by reading the service discovery file, so that the monitoring module only needs to have a configuration-fixed file service discovery rule, thereby reducing the configuration amount of the monitoring module, expanding the capability of the monitoring module, and enabling the independent service discovery process to be flexibly developed again according to platform business, so as to realize the flexible service discovery related business function.

[0083] Figure 8 The structure diagram of the device for continuously collecting indexes of a PAAS platform provided by an embodiment of the present application is shown in FIG. 2, which comprises a first obtaining module 201, a second obtaining module 202, and an index collecting module 203. Figure 8

[0084] The first obtaining module 201 is configured to obtain a first container list in real time based on a first listening channel.

[0085] The second obtaining module 202 is configured to obtain a second container list in real time based on a second listening channel; the second container list is a container list of an application that needs to be scaled according to a custom index.

[0086] The index collecting module 203 is configured to discover a service that needs to collect an index according to the first container list and the second container list through a preset service discovery rule, and complete the collection of the index.

[0087] The device for continuously collecting indexes of a PAAS platform provided by the embodiments can be specifically used to execute the method for continuously collecting indexes of a PAAS platform provided by the above-mentioned embodiments, and has similar technical principles and beneficial effects, which can be referred to the above-mentioned embodiments, and will not be described here.

[0088] Based on the same inventive concept, an electronic device is provided, as shown in FIG. 3. Figure 9 ​The electronic device specifically comprises the following: a processor 301, a communication interface 303, a memory 302, and a communication bus 304.

[0089] The processor 301, the communication interface 303, and the memory 302 are in communication with each other through the communication bus 304; the communication interface 303 is configured to realize information transmission between the modeling software, the intelligent manufacturing equipment module library, and other related devices; the processor 301 is configured to call a computer program in the memory 302, and the processor realizes the method provided by each method embodiment described above when executing the computer program, for example, the processor realizes the following steps when executing the computer program: obtaining a first container list in real time based on a first monitoring channel; obtaining a second container list in real time based on a second monitoring channel; the second container list is a container list of an application that needs to be scaled according to a custom index; discovering a service that needs to collect an index according to a preset service discovery rule based on the first container list and the second container list, and completing collection of the index.

[0090] Based on the same inventive concept, another embodiment of the present application further provides a non-transitory computer-readable storage medium having a computer program stored thereon, the computer program being executed by a processor to realize the method provided by each method embodiment described above, for example, obtaining a first container list in real time based on a first monitoring channel; obtaining a second container list in real time based on a second monitoring channel; the second container list is a container list of an application that needs to be scaled according to a custom index; discovering a service that needs to collect an index according to a preset service discovery rule based on the first container list and the second container list, and completing collection of the index.

[0091] The device embodiments described above are only schematic, wherein the units shown as separate components can or can not be physically separate, and the components shown as units can or can not be physical units, that is, they can be located in one place, or distributed on multiple network units. Part or all of the modules can be selected to achieve the purpose of the present embodiment scheme according to actual needs. Those skilled in the art can understand and implement it without creative labor.

[0092] Those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus a necessary universal hardware platform, and of course can also be implemented by hardware. Based on such an understanding, the above technical solutions, essentially or in other words, the part that contributes to the prior art, can be embodied in the form of a software product, which can be stored in a computer readable storage medium, such as a ROM / RAM, a magnetic disk, an optical disk, and the like, and includes a number of instructions to make a computer device (which can be a personal computer, a server, or a network device, etc.) execute the methods of each embodiment or some parts of the embodiments.

[0093] In addition, in the present application, terms such as "first" and "second" are used only for the purpose of description, and should not be understood as indicating or implying relative importance or implicitly indicating the number of the technical features indicated. Therefore, the features defined with "first" and "second" can explicitly or implicitly include at least one of the features. In the description of the present application, the meaning of "a plurality of" is at least two, such as two, three, etc., unless otherwise specifically limited.

[0094] In addition, in the present application, relationship terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between the entities or operations. Moreover, the terms "include", "contain" or any other variants thereof are intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements not only includes those elements, but also includes other elements not explicitly listed or inherent to such process, method, article or device. Without more limitations, the element defined by the statement "including a" does not exclude the presence of other identical elements in the process, method, article or device including the element.

[0095] In addition, in the description of the present application, the description of the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. In the present application, the illustrative description of the above terms does not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described can be combined in any suitable manner in any one or more embodiments or examples. In addition, those skilled in the art can combine and combine different embodiments or features of different embodiments or examples described in the present application without contradiction.

[0096] It should be pointed out finally that the above embodiments are only used to illustrate the technical solutions of the present application, but not to limit the same; and although the present application has been described in detail with reference to the foregoing embodiments, it should be appreciated by those skilled in the art that the technical solutions recorded in the foregoing embodiments can be modified, or some technical features thereof can be replaced equivalently; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

1. A method for continuous collection of PAAS platform indicators, characterized in that, The method comprises the following steps: The monitoring module acquires a first container list in real time based on a first monitoring channel; The elastic scaling control module acquires a second container list in real time based on a second monitoring channel, and writes the second container list into a service discovery file, the monitoring module reads the second container list based on a pre-configured file service discovery rule, the elastic scaling control module can be reloaded when the elastic scaling configuration changes, the second container list is a container list of an application that needs to be scaled according to a custom index, and the second container list is discovered by the file service discovery rule of the monitoring module and output by the elastic scaling control module; Services that need to collect indexes are discovered according to the first container list and the second container list through a preset service discovery rule, and the indexes are collected. 2.The method for continuous collection of PAAS platform indicators according to claim 1, characterized in that, Services that need to collect indexes are discovered according to the first container list and the second container list through a preset service discovery rule, and the indexes are collected, which comprises the following steps: Index values exposed by a container are collected according to the second container list. 3.The method of claim 2, wherein, Before the index values exposed by the container are collected according to the second container list, the following step is further included: The second container list is written into a service discovery file.

4. The method for continuous collection of PAAS platform indicators according to claim 3, wherein, Further included are the following steps: The service discovery file is read to acquire container information of an application that needs to be scaled according to a custom index.

5. A device for continuous collection of PAAS platform indicators, characterized in that, The method comprises the following steps: A first acquisition module is configured to acquire a first container list in real time by a monitoring module based on a first monitoring channel; A second acquisition module is configured to acquire a second container list in real time by an elastic scaling control module based on a second monitoring channel, and write the second container list into a service discovery file, the monitoring module reads the second container list based on a pre-configured file service discovery rule, the elastic scaling control module can be reloaded when the elastic scaling configuration changes, the second container list is a container list of an application that needs to be scaled according to a custom index, and the second container list is discovered by the file service discovery rule of the monitoring module and output by the elastic scaling control module; An index collection module is configured to discover services that need to collect indexes according to the first container list and the second container list through a preset service discovery rule, and collect the indexes.

6. The device for continuous collection of PAAS platform indicators according to claim 1, wherein, The index collection module is configured to: Collect index values exposed by a container according to the second container list.

7. The device for continuous collection of PAAS platform indicators according to claim 6, wherein, Further included are the following steps: A writing module is configured to write the second container list into a service discovery file before the index values exposed by the container are collected according to the second container list. Further included are the following steps:

8. The method for continuous collection of PAAS platform indicators according to claim 7, wherein, A reading module is configured to read the service discovery file to acquire container information of an application that needs to be scaled according to a custom index. The processor executes the program to implement the method for continuous collection of indexes of a PAAS platform according to any one of claims 1-4. The computer program is executed by the processor to implement the method for continuous collection of indexes of a PAAS platform according to any one of claims 1-4.

9. An electronic device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, characterized in that, ​ 10.A non-transitory computer-readable storage medium having stored thereon a computer program, characterized in that, ​

Images