Public cloud resource anomaly monitoring method and device and electronic equipment

Abstract

The embodiment of the application provides a public cloud resource abnormality monitoring method and device and electronic equipment. In the embodiment, the public cloud resources in a specified business scenario are classified into different grades, and the unit resource indicators of the resources in each grade are calculated. The abnormality of the entire system is measured based on the fluctuation abnormality of the unit resource indicators, so that the management of the public cloud resources is realized. Further, in the embodiment, the abnormality of the entire system is measured based on the fluctuation abnormality of the unit resource indicators, so that the accuracy and timeliness of the abnormality discovery are improved, and the data basis for further optimizing the decision of the computing resource cost and the computing resource cost budget control is provided.

Description

Technical Field

[0001] This application relates to data processing, and in particular to a method, apparatus, and electronic device for monitoring abnormal public cloud resources. Background Technology

[0002] Public cloud typically refers to a cloud service provided by a third-party provider to users. Public clouds are generally accessible via the Internet and may be free or inexpensive. The core attribute of a public cloud is shared resource services. Public cloud is considered a major form of cloud computing. Currently, many enterprises are deploying public clouds on a large scale.

[0003] However, for enterprises deploying public clouds, the large scale and resources they use bring problems such as management chaos, increased costs, and complexity to public cloud resource management. Summary of the Invention

[0004] This application provides a method, apparatus, and electronic device for monitoring public cloud resource anomalies, which measures the anomalies of the entire system by determining unit resource indicators and measuring the fluctuation anomalies of unit resource indicators, thereby realizing the management of public cloud resources.

[0005] This application provides a method for monitoring public cloud resource anomalies, the method comprising:

[0006] Public cloud resources under a specified business scenario are classified into N different levels of resources. Among them, N is greater than 1. The highest level of resources is represented by the resource characteristics of all public cloud resources under the specified business scenario in each dimension. Other levels of resources include the resource characteristics of at least one public cloud resource under the specified business scenario in the dimension corresponding to the level of resources. The dimension corresponding to any other level of resources is obtained by splitting at least one dimension corresponding to the level of resources of the previous level.

[0007] For resources of the highest level, the unit resource index under that level is determined based on the resource characteristics of all public cloud resources under the specified business scenario; for other levels of resources, the unit resource index corresponding to that public cloud resource under that level is determined based on the resource characteristics of the public cloud resource under the specified business scenario contained in that other level of resource under the dimension corresponding to that level of resource.

[0008] The system monitors the unit resource indicators of each resource level in descending order of level. If an abnormal unit resource indicator is detected in one of the resource levels, the public cloud resource corresponding to the abnormal unit resource indicator in that resource level is identified as the target public cloud resource. Based on the unit resource indicators of the target public cloud resource in other resource levels with lower levels than that resource level, the information of the abnormal public cloud resource is determined.

[0009] This embodiment provides a public cloud resource anomaly monitoring device, which includes:

[0010] The partitioning unit is used to classify public cloud resources under a specified business scenario into N different levels of resources. Among them, N is greater than 1. The highest level of resources is represented by integrating the resource characteristics of all public cloud resources under the specified business scenario in each dimension. Other levels of resources include the resource characteristics of at least one public cloud resource under the specified business scenario in the dimension corresponding to the level of resources. The dimension corresponding to any other level of resources is obtained by splitting at least one dimension corresponding to the level of resources of the previous level.

[0011] The indicator determination unit is used to determine the unit resource indicator for the highest level resource based on the resource characteristics of all public cloud resources in the specified business scenario; and for other level resources, to determine the unit resource indicator for the public cloud resource in the specified business scenario under the dimension corresponding to the level resource.

[0012] The monitoring unit is used to monitor the unit resource indicators of each resource level in descending order of level. If an abnormal unit resource indicator is detected under one resource level, the public cloud resource corresponding to the abnormal unit resource indicator under that resource level is identified as the target public cloud resource. Based on the unit resource indicators corresponding to the target public cloud resource under other resource levels with lower levels than that resource level, the information of the abnormal public cloud resource is determined.

[0013] This embodiment provides an electronic device, which includes: a processor and a machine-readable storage medium; the machine-readable storage medium stores machine-executable instructions that can be executed.

[0014] The machine-executable instructions are executed to perform the steps of the method described above.

[0015] As can be seen from the above technical solutions, in this embodiment, by classifying public cloud resources under a specified business scenario into different levels and calculating the unit resource index under each level of resources, the anomalies of the entire system are measured by the fluctuation anomalies of the unit resource index, thus realizing the management of public cloud resources.

[0016] Furthermore, in this embodiment, anomalies in the entire system are measured by measuring the fluctuation anomalies based on unit resource indicators, which improves the accuracy and timeliness of anomaly detection and provides data basis for further optimization decisions on computing resource costs and computing resource cost budget control. Attached Figure Description

[0017] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure.

[0018] Figure 1 A flowchart illustrating the method provided in this application embodiment;

[0019] Figure 2 A flowchart illustrating the implementation of step 103 provided in this application embodiment;

[0020] Figure 3 This is a structural diagram of the device provided in the embodiments of this application;

[0021] Figure 4 Provided for the embodiments of this application Figure 3 The hardware structure diagram of the device shown is shown. Detailed Implementation

[0022] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0023] The terminology used in this application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. The singular forms “a,” “the,” and “the” used in this application and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise.

[0024] To enable those skilled in the art to better understand the technical solutions provided in the embodiments of this application, and to make the above-mentioned objectives, features and advantages of the embodiments of this application more apparent and understandable, the technical solutions in the embodiments of this application will be further described in detail below with reference to the accompanying drawings.

[0025] In public cloud applications, simply using public cloud resource (also known as computing resource) usage and fees for any given business scenario cannot objectively reflect cost fluctuations within that scenario. This embodiment calculates unit resource metrics for public cloud resources and uses anomalies in these metrics to measure overall system anomalies, thus enabling public cloud resource management and making cost optimization more objective. See details... Figure 1 The process shown is as follows:

[0026] See Figure 1 , Figure 1 This is a flowchart illustrating a method provided in an embodiment of this application. The method is applied to an electronic device. As an example, the electronic device can be any device, such as a device connected to a public cloud management platform, or a device hosted on a public cloud management platform, etc., and this embodiment is not specifically limited to any particular device.

[0027] like Figure 1 As shown, the process may include the following steps:

[0028] Step 101: Classify public cloud resources under the specified business scenario into different levels to obtain N different levels of resources.

[0029] In this embodiment, there are many ways to implement the specified business scenario, such as a product line of a certain enterprise, and this embodiment does not specifically limit it.

[0030] In this embodiment, public cloud resources can broadly refer to cloud servers and associated resources within the specified business scenarios described above. Optionally, a cloud server refers to a device provided by a third-party cloud provider for cloud computing services. Users can deploy their own service applications on it. Cloud servers have different specifications (e.g., 4 cores 8GB, 2 cores 2GB) in different regions, and different specifications also have different configurations (e.g., 4 cores 8GB standard, 4 cores 8GB compute…). The prices of cloud servers with different specifications and configurations in different regions are different. Cloud servers are generally charged based on usage time during billing.

[0031] As an example, there are many associated resources with cloud servers, such as databases, block storage, load balancers, and NAT gateways. Optionally, block storage is used to implement data storage services provided by third-party clouds. Users can store their data in block storage. Block storage has different types in different regions (e.g., SSD cloud disks, high-efficiency cloud disks, ESSD cloud disks), and different types of cloud disks have different prices in different regions, generally charged according to the amount of capacity used. Optionally, load balancers are used to implement traffic distribution and scheduling services provided by third-party clouds. By using load balancers, access traffic can be distributed and scheduled to multiple cloud servers. Load balancers have different types in different regions (e.g., Layer 4 (TCP / UDP) traditional load balancers, Layer 7 (HTTP / HTTPS) application load balancers), and different types of load balancers have different prices in different regions, generally charged according to the number of instances used and the traffic. Optionally, NAT gateways are used to implement network address translation services provided by third-party clouds. Users can configure NAT gateways to expose their services to the public internet. NAT gateway prices vary in different regions, generally charged according to the number of instances used and the traffic.

[0032] Optionally, in this embodiment, public cloud resources in a specified business scenario can be classified into N different levels of resources according to actual business needs. Here, N can be greater than 1.

[0033] In this embodiment, each level of resource may have a corresponding level value. As one embodiment, a smaller level value indicates a higher level of resource, and vice versa. Of course, as another embodiment, a larger level value indicates a higher level of resource, and vice versa. This embodiment is not specifically limited.

[0034] In this embodiment, the highest-level resource is represented by integrating the resource characteristics of all public cloud resources under a specified business scenario across various dimensions. In other words, the highest-level resource encompasses the resource characteristics of all public cloud resources under a specified business scenario across various dimensions. For example, the first-level resources shown in Table 1 below.

[0035] In this embodiment, other resource levels include the resource characteristics of at least one public cloud resource under the dimension corresponding to that resource level in a specified business scenario. Optionally, the dimension corresponding to any other resource level is obtained by splitting at least one dimension corresponding to the resource level of the previous level, such as the second to fourth resource levels shown in Table 1 below.

[0036] Step 102: For the highest-level resource, determine the unit resource index under that resource level based on the resource characteristics of all public cloud resources under the specified business scenario; for other resource levels, determine the unit resource index corresponding to the public cloud resource under that resource level based on the resource characteristics of the public cloud resource under the specified business scenario contained in the other resource level under the dimension corresponding to that resource level.

[0037] Optionally, in this embodiment, the resource with the highest level may include: the total cost of all public cloud resources under a specified business scenario within a specified time period. Here, the specified time period may be a day, a week, a month, etc., and this embodiment is not specifically limited to this.

[0038] Based on this, determining the unit resource index for this resource level by integrating the resource characteristics of all public cloud resources under the specified business scenario may include: dividing the total cost by the total number of CPUs on the cloud hosts under the specified business scenario, and determining the unit resource index for this resource level based on the result. For example, the result can be used as the unit resource index for this resource level.

[0039] Optionally, in this embodiment, the resource characteristics of a public cloud resource in a specified business scenario under the dimension corresponding to the graded resource may include: the cost of a public cloud resource in a specified business scenario under the billing item dimension corresponding to the graded resource within a specified time period.

[0040] In this implementation, the lower the resource level, the more granular the corresponding billing item dimensions. The billing item dimensions corresponding to higher-level resources include those corresponding to lower-level resources. The billing item dimensions corresponding to any other resource level are obtained by subdividing the billing item dimensions corresponding to the resource of the previous level. For example, the highest-level resource (taking the first wind turbine resource as an example) may include: the total cost of all public cloud resources under a specified business scenario within a specified time period. The second-level resource may include: the cost of at least one public cloud resource under the specified business scenario within the specified time period under a specific billing item dimension. The third-level resource may include: the cost of at least one public cloud resource under the specified business scenario within the specified time period under a further subdivided billing item dimension corresponding to the second-level resource. And so on.

[0041] For example, N different levels of resources include: four levels of resources from level one to level four; the levels of resources from level one to level four are arranged from highest to lowest; Table 1 shows an example of resources from level one to level four:

[0042]

[0043]

[0044] Table 1

[0045] It should be noted that, in this embodiment, the first to fourth level resources shown in Table 1 are merely examples for ease of description and are not intended to limit the scope of the resource.

[0046] Based on this, the above-mentioned resource characteristics of a public cloud resource under a specified business scenario within another resource level, and the determination of the unit resource indicators corresponding to that public cloud resource under that resource level, include:

[0047] For a public cloud resource within the specified business scenario, the unit resource metric for that public cloud resource is determined based on the collected costs under the billing item dimension corresponding to that resource level within the specified time period. Finally, the unit resource metric for each public cloud resource under that resource level can be calculated.

[0048] Corresponding to Table 1 above, after step 102, Table 1 can be updated to Table 2 as follows:

[0049]

[0050]

[0051] Table 2

[0052] Step 103: Monitor the unit resource indicators of each resource level in descending order of level. If an abnormal unit resource indicator is detected under one resource level, determine the public cloud resource corresponding to the abnormal unit resource indicator under that resource level as the target public cloud resource. Based on the unit resource indicators corresponding to the target public cloud resource under other resource levels with lower levels than that resource level, determine the public cloud resource information that has an abnormality.

[0053] In this embodiment, by monitoring the unit resource indicators of each resource level in descending order of level, if an abnormality is found in the unit resource indicator of the highest level resource (taking the first level resource as an example), it can be traced back to the lower level resource (such as the second level resource, the third level resource, etc.), and finally the fluctuating resource characteristics (that is, the abnormal public cloud resource information) can be located.

[0054] The resource levels are still categorized into N different levels: from Level 1 to Level 4, a total of 4 levels. These levels are arranged from highest to lowest. The unit resource metrics for each level are as described above. In this embodiment, when the unit price of a Level 1 resource is abnormal (e.g., excessively high cost), the analysis traces back to Level 2 and Level 3 resources to pinpoint the fluctuating billing item (i.e., the abnormal public cloud resource information). For example, if the unit price of a Level 1 resource increases, the analysis can determine which public cloud resources caused the increase based on Level 2 resources. From Level 2 resources, the analysis identifies the specific public cloud resource, and further, from Level 3 resources, it identifies which billing item dimension of the public cloud resource experienced the increase. Based on the specific billing item dimension identified from Level 3 resources, the analysis can then trace back to the specific billing item from Level 4 resources, enabling targeted cost optimization.

[0055] Regarding how to determine the abnormal public cloud resource information based on the unit resource indicators of public cloud resources corresponding to the abnormal unit resource indicators under other resource levels with lower resource levels, the following will explain. Figure 2 Examples have been given, but will not be repeated here.

[0056] This concludes the process. Figure 1 The process is shown below.

[0057] pass Figure 1 As can be seen from the process shown, in this embodiment, public cloud resources are classified into different levels under a specified business scenario, and the unit resource index under each level of resources is calculated. By measuring the anomalies of the entire system based on the fluctuation anomalies of the unit resource index, the management of public cloud resources is realized.

[0058] Furthermore, in this embodiment, anomalies in the entire system are measured by measuring the fluctuation anomalies based on unit resource indicators, which improves the accuracy and timeliness of anomaly detection and provides data basis for further optimization decisions on computing resource costs and computing resource cost budget control.

[0059] The following describes how, in step 103 of this application embodiment, the abnormal public cloud resource information is determined based on the unit resource index of the public cloud resource corresponding to the abnormal unit resource index under other resource levels with lower levels:

[0060] See Figure 2 , Figure 2 A flowchart illustrating the implementation of step 103 in an embodiment of this application. Figure 2 As shown, the process may include the following steps:

[0061] Step 201: The resource level of the unit resource indicator that shows abnormality is taken as the current resource level.

[0062] For example, if the unit price of the aforementioned first-level resource increases, then the first-level resource can be considered as the current level resource.

[0063] Step 202: Locate the dimension of the target public cloud resource from the current level resource. If the cause of the anomaly is determined based on the located dimension, the current process ends. Otherwise, if the current level resource is not the last level resource, find the next level resource of the current level resource in descending order of level, determine the next level resource of the current level resource as the current level resource, and return to the step of locating the dimension of the target public cloud resource from the current level resource.

[0064] As described above, if the unit price of Tier 1 resources increases, then we can determine which public cloud resources caused the increase based on Tier 2 resources. From Tier 2 resources, we can pinpoint the specific public cloud resources, and then from Tier 3 resources, we can pinpoint which billing item of the public cloud resources has increased. Based on the specific billing item identified from Tier 3 resources, we can then pinpoint the specific billing item from Tier 4 resources, thereby optimizing costs accordingly.

[0065] This concludes the process. Figure 2 The process is shown below.

[0066] pass Figure 2 The illustrated process demonstrates how to determine the public cloud resource information that has experienced an anomaly by comparing the unit resource indicators of public cloud resources at other resource levels with lower resource levels that correspond to the anomaly's unit resource indicator. It should be noted that... Figure 2 This is just an example and is not intended to be limiting.

[0067] The methods provided in the embodiments of this application have been described above. The apparatus provided in the embodiments of this application is described below:

[0068] See Figure 3 , Figure 3 This is a structural diagram of the device provided in an embodiment of this application. Figure 3 As shown, the device may include:

[0069] The partitioning unit is used to classify public cloud resources under a specified business scenario into N different levels of resources. Among them, N is greater than 1. The highest level of resources is represented by integrating the resource characteristics of all public cloud resources under the specified business scenario in each dimension. Other levels of resources include the resource characteristics of at least one public cloud resource under the specified business scenario in the dimension corresponding to the level of resources. The dimension corresponding to any other level of resources is obtained by splitting at least one dimension corresponding to the level of resources of the previous level.

[0070] The indicator determination unit is used to determine the unit resource indicator for the highest level resource based on the resource characteristics of all public cloud resources in the specified business scenario; and for other level resources, to determine the unit resource indicator for the public cloud resource in the specified business scenario under the dimension corresponding to the level resource.

[0071] The monitoring unit is used to monitor the unit resource indicators of each resource level in descending order of level. If an abnormal unit resource indicator is detected under one resource level, the public cloud resource corresponding to the abnormal unit resource indicator under that resource level is identified as the target public cloud resource. Based on the unit resource indicators corresponding to the target public cloud resource under other resource levels with lower levels than that resource level, the information of the abnormal public cloud resource is determined.

[0072] Optionally, the public cloud resources under the specified business scenario include at least the cloud host under the specified business scenario and the associated resources associated with the cloud host;

[0073] The associated resources include at least one of the following: database, block storage, load balancer, and NAT gateway.

[0074] Optionally, the highest-level resources include at least: the total cost of all public cloud resources in the specified business scenario within the specified time period;

[0075] The step of determining the unit resource index under the specified resource level based on the resource characteristics of all public cloud resources under the specified business scenario includes: dividing the total cost by the total number of CPUs of the cloud host under the specified business scenario; and determining the unit resource index under the specified resource level based on the result of the calculation.

[0076] The resource characteristics of a public cloud resource in a specified business scenario within the graded resource, under the dimension corresponding to that graded resource, include: the cost of the public cloud resource in the specified business scenario within a specified time period under the billing item dimension corresponding to that graded resource; wherein, the lower the grade of the graded resource, the more refined the corresponding billing item dimension, the billing item dimension corresponding to a higher graded resource includes the billing item dimension corresponding to a lower graded resource, and the billing item dimension corresponding to any other graded resource is obtained by splitting the billing item dimension corresponding to the graded resource of the previous grade.

[0077] The determination of the unit resource index corresponding to the public cloud resource under the specified business scenario contained in the other resource level, based on the resource characteristics of the public cloud resource under the dimension corresponding to the resource level, includes:

[0078] For a public cloud resource in the specified business scenario, the unit resource index corresponding to the public cloud resource is determined based on the cost of the billing item dimension corresponding to the resource level within the specified time period.

[0079] Optionally, the step of determining the abnormal public cloud resource information based on the unit resource indicators corresponding to other public cloud resources of a lower level includes:

[0080] The resource level of the unit resource indicator that shows abnormality will be used as the current resource level.

[0081] If the cause of the anomaly is determined based on the located dimension, the current process ends. Otherwise, if the current level resource is not the last level resource, the next level resource of the current level resource is found in descending order of level, and the next level resource of the current level resource is determined as the current level resource. Then, the process returns to the step of locating the dimension of the target public cloud resource from the current level resource.

[0082] Optionally, the N different levels of resources include: four levels of resources from the first level to the fourth level; the levels of the first level to the fourth level resources are arranged from high to low.

[0083] The first-tier resources are characterized by the cost of cloud hosts, block storage, load balancers, and NAT gateways over a specified period of time; the unit resource metric under the first-tier resources is expressed as follows: the total cost of the cloud hosts, block storage, load balancers, and NAT gateways over a specified period of time / the total number of CPUs in the cloud hosts;

[0084] The second-tier resources include at least the costs of cloud hosts and block storage, block storage, load balancers, and NAT gateways for a specified time period; the unit resource indicators corresponding to public cloud resources under the second-tier resources include at least the unit price per CPU for cloud hosts, the unit price per CPU for databases, the unit price per CPU for load balancers, the unit price per block storage, and the unit price per NAT gateway.

[0085] The third-tier resources include at least cloud server specifications, cloud server traffic, load balancer instances, load balancer traffic, and the cost of each type of block storage during the specified time period; the unit resource indicators corresponding to the public cloud resources under the third-tier resources include at least the unit price per CPU under the cloud server specifications, the unit price per cloud server traffic, the unit price per load balancer instance, the unit price per load balancer traffic, and the unit price per type of block storage.

[0086] The fourth-tier resources include at least the costs of cloud servers of different specifications during the specified time period; the unit resource indicators corresponding to the public cloud resources under the fourth-tier resources include at least the unit price per CPU under different cloud server specifications.

[0087] This concludes the process. Figure 3 The diagram shows the structure of the device.

[0088] This application also provides embodiments that... Figure 3 The hardware structure diagram of the device shown is as follows: Figure 4 As shown. Figure 4 As shown, the hardware architecture includes a processor and a machine-readable storage medium.

[0089] The machine-readable storage medium is used to store machine-executable instructions;

[0090] The processor is configured to read and execute machine-executable instructions stored in the memory to implement the method embodiment shown above.

[0091] This application also provides a machine-readable storage medium storing a plurality of computer instructions, which, when executed by a processor, can implement the methods disclosed in the above examples of this application.

[0092] For example, the aforementioned machine-readable storage medium can be any electronic, magnetic, optical, or other physical storage device that can contain or store information such as executable instructions, data, etc. For instance, machine-readable storage media can be: RAM (Random Access Memory), volatile memory, non-volatile memory, flash memory, storage drives (such as hard disk drives), solid-state drives, any type of storage disk (such as optical discs, DVDs, etc.), or similar storage media, or combinations thereof.

[0093] The systems, devices, modules, or units described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer, which can take the form of a personal computer, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email sending and receiving device, game console, tablet computer, wearable device, or any combination of these devices.

[0094] For ease of description, the above devices are described separately by function as various units. Of course, in implementing this application, the functions of each unit can be implemented in one or more software and / or hardware.

[0095] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, embodiments of this application can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0096] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0097] Furthermore, these computer program instructions can also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in the process. Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0098] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0099] The above description is merely an embodiment of this application and is not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A public cloud resource anomaly monitoring method, characterized in that, The method comprises: grading public cloud resources under a specified business scenario to obtain N different levels of level resources; wherein N is greater than 1, the level resource with the highest level is represented by fusing resource characteristics of all public cloud resources under the specified business scenario in each dimension, other level resources contain resource characteristics of at least one public cloud resource under the specified business scenario in the dimension corresponding to the level resource, and the dimension corresponding to any other level resource is obtained by splitting at least one dimension corresponding to the level resource of the previous level; the level resource with the highest level at least includes the total cost of all public cloud resources under the specified business scenario within a specified time period; for the level resource with the highest level, performing division operation on the total cost and the total CPU number of the cloud host under the specified business scenario; determining the unit resource index under the level resource according to the obtained operation result; for other level resources, determining the unit resource index corresponding to the public cloud resource under the level resource according to the resource characteristics of the public cloud resource under the specified business scenario contained in the other level resource in the dimension corresponding to the level resource; monitoring the unit resource index under each level resource in the order from high to low, if an abnormal unit resource index under one of the level resources is monitored, determining the public cloud resource corresponding to the abnormal unit resource index under the level resource as the target public cloud resource, and determining the abnormal public cloud resource information according to the unit resource index corresponding to the target public cloud resource under other level resources with a lower level than the level resource.

2. The method of claim 1, wherein the public cloud resources under the specified business scenario at least include cloud hosts under the specified business scenario and associated resources associated with the cloud hosts; the associated resources at least include at least one of the following: databases, block storage, load balancing, and NAT gateway.

3. The method of claim 1, wherein, The resource characteristics of a public cloud resource under the specified business scenario contained in the level resource in the dimension corresponding to the level resource include: the cost of the public cloud resource under the specified business scenario in the billing item dimension corresponding to the level resource within a specified time period; wherein the lower the level of the level resource, the more detailed the corresponding billing item dimension, and the billing item dimension corresponding to any level resource other than the level resource with the highest level is obtained by splitting the billing item dimension corresponding to the level resource of the previous level; determining the unit resource index corresponding to the public cloud resource under the level resource according to the resource characteristics of the public cloud resource under the specified business scenario contained in the other level resource in the dimension corresponding to the level resource includes: for the public cloud resource under the specified business scenario, determining the unit resource index corresponding to the public cloud resource according to the cost in the billing item dimension corresponding to the level resource within the specified time period collected.

4. The method of claim 3, wherein, determining the abnormal public cloud resource information according to the unit resource index corresponding to the target public cloud resource under other level resources with a lower level than the level resource includes: The level resource of which an abnormal unit resource index is monitored is taken as a current level resource; If the cause of the abnormality is determined according to the located dimension, the current process is ended, otherwise, if the current level resource is not the last level resource, the next level resource of the current level resource is found in descending order of level, the next level resource of the current level resource is determined as the current level resource, and the step of locating the dimension of the target public cloud resource from the current level resource is returned.

5. The method according to claim 1 or 2, characterized in that, The N different level resources include four level resources from a first level resource to a fourth level resource; The first level resource is characterized by the fees of cloud hosts, block storage, load balancing and NAT gateways in a specified time period; and a unit resource index under the first level resource is represented by total fees of the cloud hosts, block storage, load balancing and NAT gateways in the specified time period / the total CPU quantity of the cloud hosts; The second level resource at least includes the fees of cloud hosts and block storage, block storage, load balancing and NAT gateways in a specified time period; and a unit resource index corresponding to a public cloud resource under the second level resource at least includes a cloud host single CPU unit price index, a database single CPU unit price index, a load balancing unit price index, a block storage unit price index and a NAT gateway index unit price; The third level resource at least includes cloud host specifications, cloud host traffic, load balancing instances, load balancing traffic and fees of various types of block storage in the specified time period; and a unit resource index corresponding to a public cloud resource under the third level resource at least includes a cloud host specification single CPU unit price index, a cloud host traffic unit price index, a load balancing instance unit price index, a load balancing traffic unit price index and various types of block storage unit price indexes; The fourth level resource at least includes the fees of cloud hosts of different cloud host specifications in the specified time period; and a unit resource index corresponding to a public cloud resource under the fourth level resource at least includes a single CPU unit price index under different cloud host specifications. 6.A public cloud resource anomaly monitoring apparatus, characterized by comprising: The apparatus comprises: A division unit is configured to divide public cloud resources in a specified business scenario into level resources of N different levels, wherein N is greater than 1, a level resource with the highest level is represented by fusing resource characteristics of all public cloud resources in the specified business scenario in each dimension, other level resources include resource characteristics of at least one public cloud resource in the corresponding dimension of the level resource in the specified business scenario, and the dimension corresponding to any other level resource is obtained by splitting at least one dimension corresponding to a level resource of a previous level; and the level resource with the highest level at least includes total fees of all public cloud resources in the specified business scenario in a specified time period. The index determining unit is configured to divide the total cost by the total CPU quantity of the cloud host in the specified business scenario for the level resource with the highest level; and determine the unit resource index of the level resource according to the obtained operation result; and determine the unit resource index corresponding to a public cloud resource in the level resource according to the resource feature of the public cloud resource in the specified business scenario included in the other level resource in the dimension corresponding to the level resource. The monitoring unit is configured to monitor the unit resource index in each level resource in descending order of level; if an abnormal unit resource index in one level resource is monitored, determine the public cloud resource corresponding to the abnormal unit resource index in the level resource as the target public cloud resource; and determine the abnormal public cloud resource information according to the unit resource index corresponding to the target public cloud resource in the other level resource with a lower level than the level resource.

7. The apparatus of claim 6, wherein, The resource feature of a public cloud resource in the specified business scenario included in the level resource in the dimension corresponding to the level resource includes: the cost of the public cloud resource in the billing item dimension corresponding to the level resource in the specified time period; wherein the lower the level of the level resource, the more detailed the corresponding billing item dimension; and the billing item dimension corresponding to any level resource other than the level resource with the highest level is obtained by splitting the billing item dimension corresponding to the level resource with the previous level. The index determining unit determines the unit resource index corresponding to the public cloud resource in the level resource according to the resource feature of the public cloud resource in the specified business scenario included in the other level resource in the dimension corresponding to the level resource, including: determining the unit resource index corresponding to the public cloud resource according to the cost of the public cloud resource in the billing item dimension corresponding to the level resource in the specified time period.

8. The apparatus of claim 7, wherein, The monitoring unit determines the abnormal public cloud resource information according to the unit resource index corresponding to the target public cloud resource in the other level resource with a lower level than the level resource, including: taking the level resource with the abnormal unit resource index as the current level resource; locating the dimension corresponding to the target public cloud resource from the current level resource; if the reason causing the abnormality is determined according to the located dimension, ending the current process; otherwise, if the current level resource is not the last level resource, finding the next level resource of the current level resource in descending order of level; determining the next level resource of the current level resource as the current level resource; and returning to the step of locating the dimension corresponding to the target public cloud resource from the current level resource; and / or The N level resources of different levels include: four level resources from the first level resource to the fourth level resource; and the levels of the first level resource to the fourth level resource are arranged in descending order. The first level resource is represented by the cost of cloud host, block storage, load balancing, and NAT gateway in a specified time period; the unit resource index under the first level resource is represented by the total cost of cloud host, block storage, load balancing, and NAT gateway in a specified time period / the total CPU quantity of cloud host; The second level resource at least includes the cost of cloud host and block storage, block storage, load balancing, and NAT gateway in a specified time period; the unit resource index corresponding to the public cloud resource under the second level resource at least includes cloud host single CPU unit price index, database single CPU unit price index, load balancing unit price index, block storage unit price index, and NAT gateway index unit price; The third level resource at least includes the cost of cloud host specification, cloud host traffic, load balancing instance, load balancing traffic, and each type of block storage in a specified time period; the unit resource index corresponding to the public cloud resource under the third level resource at least includes cloud host specification single CPU unit price index, cloud host traffic unit price index, load balancing instance unit price index, load balancing traffic unit price index, and each type of block storage unit price index; The fourth level resource at least includes the cost of cloud host of different cloud host specifications in a specified time period; the unit resource index corresponding to the public cloud resource under the fourth level resource at least includes single CPU unit price index under different cloud host specifications.

9. An electronic device, comprising: The electronic device comprises a processor and a machine readable storage medium; the machine readable storage medium stores machine executable instructions capable of being executed; The machine executable instructions are executed by the processor to implement the method steps of any one of claims 1-5.

Images