Peer-to-peer drift detection in cloud computing systems
Through the cloud peer drift detection system, compares the information of the cloud system, generates peer reports and provides alerts, solving the inefficiency and inaccurate problems of peer drift detection and processing in the cloud computing system, and improving the efficiency and flexibility of the system. Ensures the peer state and security of the system.
Patent Information
- Application Number
- CN202380035954.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-05-13
- Filing Date
- 2023-03-20
- Publication Date
- 2024-12-03
AI Technical Summary
The existing cloud computing system has problems of inefficiency, inaccuracy and inflexibility in resource management, especially in peer-to-peer drift detection and processing between private cloud computing systems and public systems, resulting in inaccuracies and Inefficient, even vulnerable, wrong and outdated services.
Using a cloud peer drift detection system, it provides alerts to facilitate resolution by comparing the information of the reference cloud system with the information of the target cloud system, generating peer reports, and determining the peer drift instances that need to be processed based on the peer score threshold. Wait for drift.
It improves the computing efficiency, accuracy and flexibility of the cloud computing system, and can effectively identify and process peer drift instances in the target cloud system, ensure the peer state of the system, and prevent the emergence of vulnerabilities and outdated services.
Smart Images

Figure CN119072681A_ABST
Abstract
Description
Background Art
[0001] Recent years have witnessed significant advances in hardware and software platforms that implement network devices, such as those found in cloud computing systems. Indeed, cloud computing systems are continually evolving in terms of the features, functions, and services they provide. Additionally, cloud computing systems are continually evolving in terms of redundancy protection, complexity, and security features. For example, different types of cloud computing systems provide different levels of access and security. For example, cloud computing systems include publicly available systems as well as private systems, such as on-premises systems that provide limited access and air-gapped security systems that are isolated from the Internet.
[0002] Despite these and other advances, existing cloud computing systems face several technical deficiencies that result in inefficient, inaccurate, and inflexible operations, particularly in the area of cloud computing system resource management. For example, when private cloud computing systems are created, it is expected that they will operate similarly to public systems in terms of features, functions, and services. However, as public systems are updated, developed, and evolved, many private systems are slow to follow. As a result, these private systems begin to "drift" from those public systems they correspond to.
[0003] In many cases, parity drift—when a target cloud computing system deviates from a source or reference cloud computing system—is often not detected. For example, due to the complexity and sheer size of most cloud computing systems, it is not feasible to continuously identify each feature and service across cloud computing systems and verify whether a feature or service has deviated from parity. In addition, the architecture of many private cloud computing systems prevents external systems from gaining the access needed to perform parity drift assessments and provide critical updates. In fact, some cloud computing systems, such as air-gapped systems, are completely isolated from external communications. In particular, these systems often suffer from various levels of parity drift.
[0004] Furthermore, instances of peer drift in cloud computing systems may cause several problems if not addressed immediately. For example, a cloud computing system that has lost peers may suffer from inaccuracies and inefficiencies (e.g., bugs, errors, and outdated services) that are not found in the corresponding reference cloud computing system. In various cases, some instances of peer drift in cloud computing systems are not that important to handle, such as services undergoing minor interface updates. However, existing cloud computing systems lack reliable mechanisms to identify instances of peer drift with respect to a reference cloud computing system, let alone determine when peer drift requires prompt action.
[0005] These and other problems cause significant inefficiencies, inaccuracies, and inflexibility of existing cloud computing systems with respect to peer drift. BRIEF DESCRIPTION OF THE DRAWINGS
[0006] The detailed description provides one or more implementations with additional specificity and detail as briefly described below through use of the accompanying drawings.
[0007] Figure 1A to Figure 1B A schematic diagram of a computing system environment for implementing a cloud peer-to-peer drift detection system in accordance with one or more implementations is shown.
[0008] Figure 2 An example workflow for determining peer drift for a target cloud computing system is shown in accordance with one or more implementations.
[0009] Figure 3 An architectural diagram of a reference cloud computing system and a target cloud computing system according to one or more implementations is shown.
[0010] FIG. 4A to FIG. 4C A flow chart of a sequence for determining peer drift for a target cloud computing system is shown in accordance with one or more implementations.
[0011] Figure 5 Providing an indication of peer drift on a computing device is illustrated in accordance with one or more implementations.
[0012] FIG. 6A to FIG. 6B A series of example actions for determining peer drift for a target cloud computing system according to one or more embodiments are shown.
[0013] Figure 7 Some components that may be included in a computer system are shown. DETAILED DESCRIPTION
[0014] Implementations of the present disclosure provide advantages and / or solve one or more of the foregoing or other problems in the art, having systems, non-transitory computer-readable media, and methods for utilizing a cloud peer drift detection system to determine peer drift instances in a target cloud computing system and to determine when peer drift instances need to be processed. More specifically, a cloud peer drift detection system (or simply "peer drift system") compiles information about services, configurations, versions, etc., together with additional data from a reference cloud system into a job package, and provides the job package to one or more target cloud computing systems. The peer drift system can then use the job package to compare the reference cloud system information with the corresponding information on the target cloud system to determine the peer drift instances on the target cloud system. In addition, the peer drift system can determine when one or more peer drift instances need to be processed and take action to correct the peer drift.
[0015] To illustrate, in one or more implementations, a peer drift system receives a job package at a target cloud computing system, the job package including a query set and a reference data set generated by running the query set on a feature configuration of a reference cloud computing system. In response, the peer drift system may generate a target data set by running the same query set from the job package on the target cloud computing system (e.g., on the feature configuration of a service on the target cloud computing system). Additionally, the peer drift system may generate a peer report based on comparing the reference data set and the target data set, and determine a peer score for the target cloud computing system by comparing the peer report to one or more peer score thresholds. Furthermore, the peer drift system may provide peer alerts based on the peer scores to facilitate resolving peer drift.
[0016] In the context of cloud computing systems, the term "peer" refers to comparing one cloud computing system (e.g., a target cloud computing system or simply the "target cloud system") to another cloud computing system (e.g., a reference cloud computing system or simply the "reference cloud system"). Typically, the reference cloud system is a public cloud system that is continuously maintained and updated. Additionally, the target cloud system can be another public system, but more often is a private or semi-private system that includes various access restrictions that prevent it from being updated in the same manner as the reference cloud system.
[0017] In some cases, the peer drift system can determine whether the features, services, and / or functions on the target cloud system match those on the reference cloud system. If not, the peer drift system can determine the amount of drift (i.e., change or difference) between the cloud systems. In various implementations, the peer drift system can measure peer drift based on configuration settings (e.g., system and service settings), features (e.g., services and functions provided), user experience (e.g., customer-facing tools), quality (e.g., system uptime, scalability, and elasticity), and / or other metrics.
[0018] In some cases, peer drift refers to the degree to which a target cloud system deviates from a peer state compared to a reference cloud system. In one or more implementations, the peer drift system determines a simple binary peer metric that indicates whether a system (or a portion thereof, such as a service) is in a peer state. In some implementations, the peer drift system determines multiple dimensions of peer drift across cloud systems. For example, the peer drift system determines that a target cloud system is in a non-peer state based on determining the number of specific peer drift instances.
[0019] As provided below, the peer-to-peer drift system disclosed herein provides several technical advantages in terms of computational efficiency, accuracy, and flexibility compared to conventional systems. In fact, the peer-to-peer drift system provides several practical applications that realize advantages and / or solve problems associated with peer-to-peer drift on cloud computing systems.
[0020] To elaborate, in one or more implementations, a peer drift system provides a solution for determining peer drift instances in a cloud computing system. In particular, the peer drift system provides a solution for determining peer drift instances in private cloud computing systems, such as locally deployed, fully independent, and air-gapped cloud computing systems. In practice, the peer drift system can determine peer drift instances for cloud computing systems that restrict incoming traffic and / or prohibit outgoing traffic.
[0021] In various implementations, the peer drift system provides significant efficiency and accuracy gains to cloud computing systems by identifying and handling peer drift instances. In practice, the peer drift system can identify systems, services, functions, features, configurations, etc. in a target cloud system that have drifted beyond a threshold peer amount, which may affect the operation of the target cloud system. In some implementations, the peer drift system can automatically handle one or more peer drift instances at the target cloud system.
[0022] As previously described, in various implementations, a peer drift system improves the accuracy of a cloud computing system by utilizing a job package that aggregates a query set having multiple data sets and additional peer drift information. For example, in one or more implementations, a peer drift system receives a job package that includes a reference data set indicating configuration settings on a reference cloud system and a query set for generating the reference data set. The peer drift system can then use the same query set to generate a target data set on a target cloud system. By including the query set in the job package, the peer drift system ensures that equivalent data sets are generated on different cloud systems. In fact, unlike existing systems, which may themselves drift due to the default query set used, the peer drift system improves accuracy by ensuring that the same query set is used to generate all data sets that are compared to each other.
[0023] In additional implementations, the peer drift system continues to aggregate information into job packages. For example, when a peer report is generated by comparing a reference data set and a target data set, the peer drift system adds the peer report to the job package. Similarly, when a peer grade and / or score is determined from a peer report, the peer drift system can add the peer grade to the job package. Additionally, in some implementations, the peer drift system can archive the job package and reference it when determining future peer reports (e.g., when determining trends in peer drift). In this way, the peer drift system improves accuracy by keeping correct records, which enables the peer drift system to accurately determine peer drift instances in the target cloud system.
[0024] In various implementations, the peer drift system provides improved flexibility by providing customization of peer drift detection. For example, while the peer drift system provides a generic configuration for detecting peer drift instances at a target cloud system, in one or more implementations, the peer drift system utilizes customized peer drift thresholds for specific services. Similarly, the peer drift system can flexibly provide customization in determining whether to alert and / or correct detected peer drift instances.
[0025] As indicated in the foregoing discussion, the present disclosure utilizes various terms to describe features and advantages of one or more implementations described herein. For example, as used herein, a "cloud computing system" refers to a network of connected computing devices (e.g., network devices) that provide various services to client devices. For example, a cloud computing system can be a distributed computing system that includes a collection of physical server devices (e.g., server nodes) organized in a hierarchical structure, including computing zones, clusters, virtual local area networks (VLANs), racks, load balancers, fault domains, etc.
[0026] In addition, the features and functions described in connection with the cloud computing system may similarly relate to racks, fault domains, or other hierarchical structures of physical server devices. The cloud computing system may relate to a private or public cloud computing system. In some implementations, the cloud computing system may include an orchestrator that manages servers, server clusters, server racks, server nodes, and / or other server groups of computing devices. In various implementations, a computing device including one or more virtual machines (e.g., a "host device") may include a hypervisor that facilitates hosting the virtual machines on the host device.
[0027] As described above, a cloud computing system may refer to a reference cloud computing system or a target cloud computing system. As used herein, a reference cloud computing system (or simply a reference cloud system) may refer to a source cloud computing system, a model cloud computing system, a base cloud computing system, a public cloud computing system, or another type of cloud computing system used as a template for establishing configuration settings. In some implementations, the reference cloud computing system may be a private cloud computing system. Additionally, as used herein, a target cloud computing system (or simply a target cloud system) refers to a private cloud computing system, a completely independent cloud computing system, a locally deployed cloud computing system, an air-gapped cloud computing system, a restricted cloud computing system, or another cloud computing system that is being checked for peer drift instances. In some implementations, the target cloud system is a public cloud computing system.
[0028] As used herein, "virtual machine" refers to a simulation of a computer system on a server node that provides the functionality of one or more applications on a cloud computing system. In various implementations, a host device allocates computing cores and / or memory to a virtual machine running on the host device. A virtual machine can provide the functionality required to execute one or more operating systems. In addition, a virtual machine can utilize a hypervisor on a processor of a server device that supports hardware virtual replication. It should be understood that although the specific examples and features and functions of the virtual machines described herein may also apply to virtual machine groups and / or computing instance types.
[0029] As used herein, the term "query set" refers to one or more queries that request data from a database or another storage device. In various implementations, a query set refers to queries about configuration settings (e.g., query configurations) for services, functions, and features of a cloud computing system. In various implementations, a query set includes queries written in structured query language (SQL), Kusto query language (KQL), or other structured query languages. Additionally, a query set may refer to requests for system-based settings and data rather than requests for user-based data. In various implementations, the peer-to-peer drift system generates a data set based on responses to executing the query set.
[0030] As used herein, the term "dataset" or "cloud data set" may refer to a collection of data about a cloud computing system or a portion thereof based on a system configuration system. For example, a data set may include version information about various services, functions, and features of a cloud computing system. In various implementations, a data set includes information about various dimensions of a cloud computing system or a portion thereof. For example, a data set includes a schema indicating state information and / or version information of a network function on a cloud computing system, but does not include user data.
[0031] As used herein, the term "job package" refers to a collection of configuration information about one or more cloud computing systems. For example, a job package may initially include a query set and a data set. In addition, the job package may additionally include information components, such as a second data set, a peer report between two data sets, and / or a peer level based on the peer report. In addition, the job package may contain additional elements, such as metadata and hashes to identify, verify, and utilize the job package.
[0032] In various implementations, the term "peer report" or "peer dimension report" refers to a collection of information indicating differences between cloud computing systems or parts thereof. For example, a peer report indicates a comparison between corresponding systems or services in two (or more) cloud computing systems. In various implementations, the peer report is included in a larger table, data set, or cloud computing system information collection. In some implementations, the peer report can include a peer score or peer rating based on the importance or one or more parts of the peer report, as further provided below.
[0033] Additional details about the peer drift system for detecting peer drift of a cloud computing system will now be provided. For example, Figures 1A to 1B A schematic diagram of an environment 100 (ie, a digital media system environment) for implementing a peer drift system 106 (ie, a cloud peer drift detection system) is depicted. In particular, Figure 1A includes environment 100, and Figure 1B More details are provided regarding the peer drift system 106 .
[0034] like Figure 1A As shown, environment 100 includes a reference cloud computing system 102 that provides data to a target cloud computing system 112 via a network 111. In various implementations, the cloud computing systems share similar architectures, systems, services, features, and / or functions. For example, in many implementations, the target cloud computing system 112 is designed and / or modeled after the reference cloud computing system 102. In various implementations, environment 100 includes multiple target cloud computing systems (e.g., linked or separate cloud systems managed by the same or different entities). In some implementations, the multiple target cloud computing systems are competing cloud computing system providers. In an example implementation, the target cloud computing system is operated by an entity different from the one that operates the reference cloud computing system.
[0035] As shown, both the reference cloud computing system 102 and the target cloud computing system 112 include various devices. For example, the reference cloud computing system 102 includes a server device 104 having a peer drift system 106 (or a portion thereof). The reference cloud computing system 102 also includes a reference data source 108, which may include one or more storage devices for storing system-based and / or user-based data. In some implementations, the reference data source 108 includes an additional server device for hosting a virtual machine.
[0036] Similar to the reference cloud computing system 102, the target cloud computing system 112 includes a server device 114 having a peer drift system 106 (or a portion thereof) and a target data source 118. The server device 114 may include one or more server devices and / or other computing devices. Similarly, the target data source 118 may include various computing devices that support the functions of the target cloud computing system 112.
[0037] As shown, environment 100 includes network 111, which facilitates communication between cloud computing systems. In some implementations, network 111 is a private network. In some implementations, network 111 is a public network, such as the Internet. In fact, in one or more implementations, network 111 allows open communication between cloud computing systems, for example, when both cloud computing systems are public cloud systems.
[0038] In various implementations, network 111 is restricted by a network wall 116 that regulates network traffic. For example, in some implementations, network wall 116 is a network device, such as a firewall, that filters incoming data to target cloud computing system 112 and / or restricts outgoing data from target cloud computing system 112. For example, if target cloud computing system 112 is an air-gapped cloud system, network wall 116 blocks all outgoing network traffic from target cloud computing system 112. In some implementations, network 111 does not include network wall 116.
[0039] In addition, the environment 100 includes a client device 110 that communicates with a target cloud computing system 112. For example, the reference data source 108 interfaces with an API of the target cloud computing system 112 to utilize the functionality of the target cloud computing system 112. In some implementations, the peer drift system 106 on the target cloud computing system 112 can send and / or receive communications regarding peer drift in the target cloud computing system 112. Depending on the architecture and security requirements of the target cloud computing system 112, the client device 110 can be connected to a network 111, or can be isolated by a network wall 116 and / or other constraints.
[0040] As described above, target cloud computing system 112 is modeled after reference cloud computing system 102. Therefore, when components and elements of reference cloud computing system 102 are updated, the corresponding components and elements of target cloud computing system 112 should also be updated to maintain parity. Due to the huge scale and complexity of cloud systems, it is difficult to maintain parity across different cloud systems. In addition, the deployment and replication of services are largely independent of each other and are irregularly scheduled.
[0041] Additionally, this problem is further complicated when target cloud computing system 112 is a private and / or restricted cloud system. In fact, while cloud system engineers who create the cloud system can maintain and update reference cloud computing system 102, they are typically restricted from accessing target cloud computing system 112. As a result, target cloud computing system 112 can quickly, easily, and unknowingly deviate from a peer state with reference cloud computing system 102, and instances of peer drift cannot be directly handled by cloud system engineers who maintain reference cloud computing system 102.
[0042] In detail, in some cases, target cloud computing system 112 includes very sensitive data. For example, target cloud computing system 112 is contracted by a state department, a financial institution, the military, etc. For example, target cloud computing system 112 operates as a weapon guidance and defense system for a battlecruiser (which would be an example of an air-gapped cloud system that does not require or allow external communication). Therefore, in various implementations, by being isolated from public cloud computing systems, target cloud computing system 112 can easily and unknowingly deviate from a peer state with reference cloud computing system 102.
[0043] To combat peer drift, peer drift system 106 facilitates peer drift detection and, in some cases, automatically corrective actions. As shown, peer drift system 106 may be included on reference cloud computing system 102 or target cloud computing system 112. In some implementations, peer drift system 106 (or portions thereof) are located on both cloud systems. For example, peer drift system 106 executes a query set on reference cloud computing system 102 to generate a reference data set. In addition, peer drift system 106 generates a job package containing a query set and a reference data set, and then sends the job package to target cloud computing system 112.
[0044] Additionally, the peer drift system 106 (e.g., a different instance of the peer drift system 106) receives the job package on the target cloud computing system 112 and executes the same query set from the job package to generate the target data set. Then, based on the reference data set and the target data set, the peer drift system 106 determines the peer drift instance on the target cloud computing system 112. Figure 1B Additional details regarding the peer drift system 106 are provided.
[0045] With respect to the components of environment 100, in one or more implementations, the computing devices included in environment 100 represent one or more types of computing devices including, for example, mobile devices, portable devices, wearable devices, desktop computers, server devices, server nodes, server clusters, or other types of computing devices. Additionally, although Figure 1A A specific arrangement of cloud computing systems, reference cloud computing system 102, target cloud computing system 112, client devices 110, network wall 116, and network 111 is shown, but environment 100 may include any number of systems, computing devices, and / or networks. For example, one or more additional client devices may communicate with reference cloud computing system 102.
[0046] In addition, the network 111 may include one or more networks that use one or more communication platforms or technologies for transmitting data. For example, in addition to the above disclosure, the network 111 may include the Internet or other data links that can transmit electronic data between corresponding client devices and devices of the cloud computing system. Figure 7 Additional details about these computing devices and networks are provided.
[0047] As mentioned above, Figure 1B Details about the peer drift system 106 are described. Specifically, Figure 1BA target cloud computing system 112 is shown having a server device 114 and a target data source 118. In addition, as shown, the peer drift system 106 (i.e., cloud peer drift detection system) includes various components and elements. For example, the peer drift system 106 includes a job package manager 120, a query service manager 122, a report service manager 124, an alarm service manager 126, and a storage manager 128. As also shown, the storage manager 128 may include a job package 130 having a query 132, a cloud configuration data set 134, a cloud configuration peer report 136, and a peer level 138; a report configuration 140; a peer level configuration 142; and an alarm configuration 144.
[0048] As shown, the peer drift system 106 includes a job package manager 120. In one or more implementations, the job package manager 120 receives, accesses, provides, edits, modifies, identifies, creates, or otherwise manages a job package 130. For example, the job package manager 120 creates a job package that includes a query 132 in a query set, a cloud configuration data set 134 (e.g., a reference data set and a target data set), a cloud configuration peer report 136 of a target cloud computing system 112, and a peer level 138 of the target cloud computing system 112. For example, the data set includes one or more schemas indicating state information and / or version information of network functions on the cloud computing system, but does not include user data. In various implementations, the job package manager 120 gradually builds the job package 130 by adding and / or supplementing various elements in the job package 130 over time. Additionally, in some implementations, the job package manager 120 archives the job package 130 for future use by the peer drift system 106.
[0049] As shown, the peer-to-peer drift system 106 includes a query service manager 122. In various implementations, the query service manager 122 facilitates creating, executing, modifying, storing, adding, deleting, identifying, accessing, or otherwise managing queries 132. In various implementations, the query service manager 122 runs a query set of queries 132 on both the reference cloud computing system 102 and the target cloud computing system 112 to generate a cloud configuration data set 134. In addition, the query service manager 122 can interact with a user through a client device to receive, edit, execute, and / or reconfigure the query 132.
[0050] As shown, the peer drift system 106 includes a reporting service manager 124. In various implementations, the reporting service manager 124 compares, identifies, edits, modifies, receives, accesses, provides, or otherwise manages cloud configuration peer reports 136 and / or peer ratings 138. For example, the reporting service manager 124 determines peer drift instances in the target cloud computing system 112 and peer ratings for one or more peer drift instances. In some implementations, the reporting service manager 124 utilizes a reporting configuration 140 to generate the cloud configuration peer report 136. In certain implementations, the reporting service manager 124 enables the reporting configuration 140 to be customized on a per-service or per-feature level to determine peer drift for the corresponding service or feature.
[0051] As shown, the peer drift system 106 includes an alarm service manager 126. In various implementations, the alarm service manager 126 manages peer drift alarms. For example, in some implementations, the peer drift system 106 determines to provide an alarm indicating a peer drift instance at the target cloud computing system 112. In these implementations, the alarm service manager 126 can provide the alarm to a client device or an alarm system. In various implementations, the alarm service manager 126 utilizes the alarm configuration 144 to determine when to issue an alarm for a detected peer drift instance. In some implementations, the alarm service manager 126 permits modification of the alarm configuration 144.
[0052] Additionally, the peer drift system 106 includes a storage manager 128. In various implementations, the storage manager 128 may include any data used by any component of the peer drift system 106 in performing the features and functions described herein. For example, the storage manager 128 may include a job package 130 with a query 132, a cloud configuration data set 134, a cloud configuration peer report 136, and a peer rating 138; a report configuration 140; a peer rating configuration 142; and an alert configuration 144.
[0053] Additional details regarding an example implementation of the peer drift system 106 are as follows: Figure 2 For example, Figure 2 An example workflow for determining peer drift for a target cloud computing system according to one or more implementations is shown. Figure 2 Depicted is a series of actions 200 of the peer drift system 106 for determining a peer drift instance at a target cloud computing system.
[0054] like Figure 2As shown, a series of actions 200 includes an action 202 of generating a reference data set of a reference cloud computing system using a query set. For example, in various implementations, the peer drift system 106 accesses the query set and executes the query set on a data source of the reference cloud computing system 102 to generate a reference data set (e.g., a public data set). Figure 4B Additional details are provided on using query sets to generate reference datasets.
[0055] also, Figure 2 A series of actions 200 are shown including an action 204 of providing a job package including a reference data set and a query set to a target cloud computing system. For example, in various implementations, the peer drift system 106 can generate a job package including a reference data set and a query set. Additionally, the peer drift system 106 can provide the job package to the target cloud computing system. In some implementations, the peer drift system 106 provides the job package to multiple target cloud systems. Figure 4B Provides additional details about generating and delivering job packages.
[0056] like Figure 2 As shown, a series of actions 200 includes an action 206 of generating a target data set of a reference cloud computing system using a query set. For example, in various implementations, the peer drift system 106 extracts the query set from the received job package and executes it on the data source of the target cloud computer system to generate a target data set (e.g., a private data set). In practice, the peer drift system 106 runs the same query set on both the reference cloud system and the target cloud system to ensure that the corresponding data sets are aligned with each other. Figure 4C Provides additional details about generating a target data set on a target computing system.
[0057] As shown, a series of actions 200 includes an action 208 of determining a peer problem based on a reference data set and a target data set. For example, in various implementations, the peer drift system 106 compares a portion of the reference data set with a corresponding portion of the target data set to determine whether peer drift has occurred. In some implementations, when an instance of peer drift is detected, the peer drift system 106 determines an amount of peer drift that has occurred. Figure 4C Provides additional details on determining peer drift instances.
[0058] also, Figure 2The series of actions 200 are shown to include an action 210 of providing an alert indicating a peer drift problem on a target computing system. For example, in various implementations, the peer drift system 106 determines when an alert is needed, and in response, provides a corresponding alert. In various implementations, the peer drift system 106 identifies a peer problem but determines that an alert is not needed. In various implementations, by sending an alert, the peer drift system 106 can facilitate correction of the identified peer problem. Figure 5 Provides additional details about providing alerts for peer drift.
[0059] As mentioned above, Figure 3 Depicts an architecture diagram of a reference cloud computing system and a target cloud computing system according to one or more implementations. Specifically, Figure 3 It illustrates how peer drift system 106 operates by components of reference cloud computing system 102 and target cloud computing system 112 to determine a peer drift instance at target cloud computing system 112 .
[0060] As shown in the figure, Figure 3 Including the above Figure 1A For example, Figure 3 The reference cloud computing system 102, the target cloud computing system 112, the client device 110 and the network wall 116 are included. Figure 3 It includes a network gateway device 311 that can limit or prevent network services from entering or exiting the target cloud computing system 112.
[0061] It is also shown that the peer drift system 106 (i.e., the cloud peer drift detection system) on the reference cloud computing system 102 includes a query service 322a and a job packager 320a. In some implementations, the query service 322a and the job packager 320a correspond to the above-mentioned Figure 1B The associated query service manager 122 and job package manager 120. In addition, the peer drift system 106 on the target cloud computing system 112 includes a job packager 320b, a query service 322b, an alert service 326, and a reporting service 324. In one or more implementations, these components correspond to similar components described above and are similar to those described above. Figure 1B Connection (eg, reporting service 324 corresponds to reporting service manager 124).
[0062] In various implementations, the peer-to-peer drift system 106 includes a collection of functions and services that work together to create an event-based pipeline, such as Figure 3 In some cases, each function in the pipeline is responsible for one or more transformations of the data.
[0063] As a high-level illustration, the peer drift system 106 on the reference cloud computing system 102 utilizes query services 322a to execute onboard queries (i.e., query set 304) to obtain a reference data set 306, which is replicated into each target cloud. Once replicated, the peer drift system 106 on the target cloud computing system 112 executes equivalent queries to generate local data (e.g., the peer drift system 106 utilizes query services 322b to execute query set 304 to generate target data set 316). In addition, the peer drift system 106 utilizes reporting services 324 to compare the reference data set 306 and the target data set 316 to calculate peer reports 318 including peer dimensions and peer levels based on various peer settings and thresholds. Then, once the peer dimensions have been generated and the levels have been assigned, the peer drift system 106 can utilize alert services 326 to analyze the peer reports and / or peer levels and notify the client device 110 (e.g., via alert 319) according to the alert policy.
[0064] In various implementations, the peer drift system 106 accesses, generates and / or onboards various configurations (e.g., configuration files) for generating peer drift in a target cloud computing system. In one or more implementations, the peer drift system 106 identifies and / or onboards one or more configuration files for configurations of various aspects of the peer drift system 106. For example, the configuration file is created during the onboard phase and provided to the peer drift system 106. In some implementations, it is stored in each cloud computing system. In an example implementation, the configuration file is a JSON file that can be validated according to a schema. In various implementations, the configuration file can be stored as other file types.
[0065] In some implementations, the configuration file includes various configuration options (e.g., reporting configuration 140, peer level configuration 142, and / or alert configuration 144). For example, the configuration file includes a query configuration with a query (i.e., a query set) and supporting metadata (e.g., connection information), a list of supplemental reporting services and / or alert services, cloud-specific coverage settings, and / or inputs for the query. In some cases, the query will be called once for each input.
[0066] Additionally, the configuration file includes a reporting configuration indicating rating and / or peer dimension thresholds, other overrides, supplemental reporting services, custom rating definitions, and / or references to other ratings with configurable weights. In various implementations, the configuration file includes an alert configuration with an alert policy and / or supplemental alert services.
[0067] Additional details about the components and services of the peer drift system 106 will now be provided. For example, with respect to a query service 322a (e.g., a public query service) on the reference cloud computing system 102, in one or more implementations, the query service 322a is responsible for communicating with the reference data source 108 to obtain data to be processed (e.g., the reference data set 306). For example, the query service 322a provides the query set 304 to the reference data source 108. In some implementations, the reference data source 108 is a KQL database or another type of structured database that facilitates query requests.
[0068] In various implementations, query set 304 includes configuration settings so that responses to query set 304 conform to input patterns that each of the reporting service and the alerting service is familiar with. In detail, if a first reporting engine requires columns A and B, and a second reporting engine requires columns B and C, then the query must result in columns A, B, and C.
[0069] In some implementations, once the query service 322a obtains the reference data set 306, it can validate it against an input schema. For example, schemas derived by the reporting service and the alerting service can be used to validate the data in the reference data set 306. In this way, the peer drift system 106 can enforce that the query data in the reference data set 306 complies with the appropriate services and engines, as well as reduce runtime errors through pre-validation. In addition, in various implementations, the reference data set includes a schema indicating state information and / or version information of the network functions on the reference cloud system (excluding user data stored on the reference cloud system).
[0070] In some implementations, after validating the reference data set 306 according to the input schema, the peer drift system 106 can create a job package 310. For example, the peer drift system 106 creates the job package as a folder and / or file named based on the query and date and / or time (e.g., the current date and / or time). In addition, the query service 322a can place the output file (e.g., the reference data set 306) in the job package 310 along with the query set 304 and / or query configuration.
[0071] As described above, the peer drift system 106 sends the job bundle 310 from the reference cloud computing system 102 to the target cloud computing system 112. In various implementations, the peer drift system 106 utilizes replication services (e.g., part of the job bundler 320a) to send the job bundle 310. For example, the peer drift system 106 provides the job bundle 310 to the target cloud computing system 112 using replication and duplication services.
[0072] In some implementations, the replication service can be critical to ensuring that the job package 310 arrives safely at the target cloud computing system 112. For example, where the target cloud computing system 112 is an air-gapped cloud system or another restricted cloud system, the replication service facilitates secure delivery despite having only a one-way or restricted communication channel. For example, the replication service on the reference cloud computing system 102 generates a manifest and hash of the files to be sent along with the query set 304 and the reference data set 306. Then, on the target cloud computing system 112, a corresponding replication service (e.g., part of the job packager 320b) receives the transmission and utilizes the manifest and hash to ensure that all files have been replicated without errors.
[0073] like Figure 3 As shown, the job package 310 is provided to the target cloud computing system 112 through the network wall 116. For example, the replication service utilizes encrypted one-way communication through the network gateway device 311 to provide the job package 310 to the corresponding replication service on the target cloud computing system 112. For example, the job packager 320b on the target cloud computing system 112 can receive the job package 310, and unpack and store the query set 304 (e.g., query configuration file) and the reference data set 306 indicating the configuration settings of the reference cloud computing system 102. In some implementations, the job package 310 is sent to the target cloud computing system 112 using an offline process.
[0074] As shown, the target cloud computing system 112 includes a query service 322b. Once the job packager 320b receives the job package 310, the query service 322b can consume the same query set 304 (e.g., query configuration) and use it to generate a target data set 316. As described above, the target data set can include a schema indicating state information and / or version information of network functions on the target cloud system (excluding user data).
[0075] In various implementations, by providing replication of the query set 304 and the reference data set 306, the query service 322b ensures that exactly the same query configuration is used to generate the target data set 316. Thus, in the event that the query on the reference cloud computing system 102 is changed (e.g., a new column is added), the peer drift system 106 does not have to wait for the updated query to be deployed to the target cloud computing system 112, or risk running a different query, as is the case with existing systems (e.g., services are deployed and replicated largely independently of each other, diverge, and often become out of sync). Instead, the most recent query configuration is replicated and available for use by the query service 322b.
[0076] In various implementations, once the query service 322b generates the target dataset 316, the peer drift system 106 can store the target dataset 316 in a dataset storage device along with the reference dataset 306. In some implementations, the peer drift system 106 adds the target dataset 316 to the job package 310 stored on the target cloud computing system 112. In many implementations, the query service 322b does not send the target dataset 316 to the reference cloud computing system 102. In one implementation, the query service 322b sends the target dataset 316 to the reference cloud computing system 102 or to another computing device.
[0077] As shown, the target cloud computing system 112 includes a reporting service 324. In various implementations, the reporting service 324 obtains the generated data sets (e.g., the reference data set 306 and the target data set 316). In some implementations, the peer drift system 106 notifies the reporting service 324 when the reference data set 306 and the target data set 316 become available. In some implementations, the reporting service 324 sends a request to the data set storage on the target cloud computing system 112 to determine when both data sets are available. For example, the reporting service 324 monitors the data set storage for file creation events indicating when both data sets have been created.
[0078] In one or more implementations, reporting service 324 ingests the data set and begins generating peer reports 318. In some implementations, reporting service 324 performs transformations on one or more data sets (or creates new files, columns, tables, or data sets containing the transformations). For example, reporting service 324 generates a set of "peer dimension" columns that indicate instances and magnitudes of peer drift between different services, features, and functions of the cloud computing system. In some cases, reporting service 324 generates one or more columns for each service, feature, or function.
[0079] In various implementations, reporting service 324 represents multiple reporting services or reporting engines that compare different corresponding portions of a data set. For example, in an implementation utilizing multiple reporting engines, reporting service 324 can orchestrate a processing flow so that the reporting engines can transform the data sets one by one. In additional implementations, reporting service 324 enables the output of one reporting engine to be passed on and / or utilized by a subsequent reporting engine.
[0080] In some implementations, peer dimensions represent columns that are calculated using a set of input columns from both reference dataset 306 and target dataset 316. In one or more implementations, a set of default reporting engines are utilized to calculate multiple dimensions. In various implementations, customized reporting engines calculate specific dimensions corresponding to specific services, features, and functions of the cloud computing system. For example, reporting service 324 utilizes a complex customized reporting engine to handle key services of the cloud computing system.
[0081] To illustrate, in one or more implementations, reporting service 324 may utilize a default set of reporting engines that include a distance reporting engine that indicates the difference between corresponding values in reference data set 306 and target data set 316 (e.g., the difference between version labels, which may be represented as integers), a freshness reporting engine that indicates the time since the last target cloud system deployment (e.g., without regard to the reference cloud system deployment date), a deployment count reporting engine that indicates the number of deployments in reference cloud computing system 102 since the last corresponding deployment in target cloud computing system 112, and / or an age reporting engine that indicates the time since a value on reference cloud computing system 102 was moved from target cloud computing system 112.
[0082] By way of example of the reporting service 324 utilizing the deployment count reporting engine, consider the following scenario. On October 23, service A on the target cloud system is at version A. The reference cloud system was upgraded from version A to version B on October 20, to version C on October 22, and to version D on October 23. Therefore, as shown in Table 1 below, on October 23, the value of "Total deployment Since" is 3 because there are 3 (e.g., DD+3) unique build tags in the reference cloud system (e.g., versions B, C, and D) between October 20 and October 23.
[0083]
[0084]
[0085] Table 1 for Service A
[0086] After the reporting service 324 generates the peer dimensions, the reporting service 324 may also generate a peer rating (e.g., a peer score). In some implementations, the reporting service 324 supplements the peer report 318 with a "rating" column set corresponding to the peer columns. In one or more implementations, the reporting service 324 utilizes the peer rating configuration to obtain the rating thresholds for determining the peer rating. For example, the peer rating configuration includes general peer rating thresholds and peer rating thresholds for specific services, features, and functions. In various implementations, the reporting service 324 determines the peer rating based on the values (e.g., grading criteria) provided by each peer dimension in the peer rating configuration.
[0087] To illustrate, the distance and weighted ranking listing shown below provides an example ranking criteria for a peer dimension having values generated by a distance reporting engine.
[0088]
[0089]
[0090] Distance tiers and weighted tier lists
[0091] As shown in the above list, reporting service 324 assigns a "green" rating to services, features, or functions that are within 6 versions of the peer dimension value, a "yellow" rating to services, features, or functions that are between 5-10 versions of the peer dimension value, and a "red" rating to outdated services, features, or functions that are more than 11 versions away from the peer dimension value (i.e., green is good and red is bad). In some implementations, the above list includes customizing the ratings by weighting different combinations of the ratings in the overall rating for the services, features, or functions.
[0092] In some implementations, reporting service 324 provides peer reports 318 in final form to report archive 312, which can be a storage container, and / or provides (e.g., uploads) peer reports 318 to a structured database to facilitate programmatic access (e.g., query calls).
[0093] As described above, the reporting service 324 may include multiple reporting engines. In some implementations, the reporting engine is a cloud computing system function that ingests file data according to a specific input mode and exports reports that conform to a specific output mode. In some cases, the reporting service 324 adds one or more report information columns to an existing table.
[0094] In additional implementations, reporting engines can declare sets of peer dimensions. In addition, reporting engines can link their outputs to the inputs of other reporting engines so that one or more reporting engines can be multiplexed and combined to generate a final report.
[0095] The following is a list of example modes including a reporting engine that the peer drift system 106 may execute.
[0096]
[0097]
[0098] Report Engine Mode Engine
[0099] Additionally, the listing below provides an example reporting engine that calculates the "distance" and "freshness" peer dimensions and associated peer ratings based on a "red / yellow / green" grading scheme.
[0100]
[0101]
[0102]
[0103] Distance and freshness reporting engine
[0104] As shown, the target cloud computing system 112 includes an alert service 326. In various implementations, the alert service 326 provides alerts based on the level. For example, the alert service 326 receives the levels in the peer report 318 and propagates alerts to one or more computing devices for each level that matches the alert condition. In some implementations, the alert service 326 traverses each row in the peer report 318 and compares the values therein with the corresponding alert policies (e.g., the rating policies and rating thresholds). Additionally, the alert service 326 can provide alerts to each triggered alert policy.
[0105] In some implementations, unlike the reporting service 324 that runs in a serial chain, the alerting service 326 can run in parallel. In this way, multiple alerting engines can concurrently analyze the peer report 318 to determine when corresponding rows contain peer levels that trigger actions associated with alert policies.
[0106] In various implementations, the alert service 326 prioritizes alerts based on specificity, importance, and / or severity. For example, the alert service 326 saves one or more alerts to be sent. In some implementations, the alert service 326 provides the most critical alerts first. In various implementations, the alert service 326 provides the most specific alerts first. In fact, in one or more implementations, the alert actions can be defined and / or specified in a configurable alert policy set (e.g., an alert configuration), such as included in the above-mentioned onboard configuration file.
[0107] The alert policy list shown below provides examples of alert policies.
[0108]
[0109] ]
[0111] Alert Policy List
[0112] In the alert policy list shown above, the alert service 326 provides various alerts based on various peer levels or scores (e.g., peer levels) that meet the grading conditions. For example, if the weighted level for any service, feature, or function is red, an alert is sent. If all levels are yellow, a different alert is sent, which can be the same alert for an unweighted red level. In addition, for a specified yellow level, a different alert is sent.
[0113] In various implementations, the peer drift system 106 provides alerts directly to the computing device. In some implementations, the peer drift system 106 utilizes a third-party service to send alerts (e.g., alert 319). For example, the target data set 316 utilizes an incident management (ICM) alert engine or another type of alert system to manage alerts and send alerts to end-user computing devices.
[0114] In various implementations, the alert service 326 (i.e., the peer drift system 106) provides an alert 319 to the client device 110 so that a cloud system administrator (or another authorized user) is notified of one or more instances of peer drift. In various implementations, the alert 319 preferably takes automatic action because the administrator is in a better position to determine whether to correct a particular instance of peer drift. For example, upgrading a service to the latest version that matches the corresponding service on the reference cloud system may cause compatibility issues or problems on the target cloud system, and the administrator may choose to temporarily forgo the upgrade. However, by being notified of instances of peer drift on the target cloud system, the administrator can prepare and respond appropriately to identified instances of peer drift.
[0115] In some implementations, the alert 319 triggers an automatic upgrade of the service (or feature or function). For example, if the alert 319 corresponds to a critical security patch or update that fixes a zero-day vulnerability, the peer drift system 106 can respond to the alert 319 by automatically upgrading the service that was in a non-peer state to bring it into parity with the reference cloud system. In various implementations, the peer drift system 106 automatically repairs the peer drift at the target cloud system, and the alert 319 indicates that the instance of the peer drift has been upgraded to match the corresponding service on the reference cloud system.
[0116] In one or more implementations, alert 319 indicates multiple instances of peer drift on the target reference cloud system. For example, alert 319 is a peer drift report (or a link to a report) indicating different instances of peer drift. In these implementations, the peer drift report sorts the instances of peer drift by magnitude (e.g., green, yellow, or red services). In some implementations, alert 319 provides a link to quickly fix one or more instances of peer drift. For example, alert 319 provides a link to start, download, or schedule an upgrade of a service that is not peer to the reference cloud system.
[0117] In various implementations, the client device 110 allows modification of the alert 319. For example, the client device 110 provides input to the peer drift system 106 to pause, mute, and / or postpone one or more peer drift instances in future alerts. In an example implementation, the client device 110 provides input to disable alerts for a particular service. In some implementations, the client device 110 provides input to customize alerts for a particular service. For example, the peer drift system 106 receives input to not provide an alert to a particular service until a set of conditions (e.g., based on alert level and timing) is met.
[0118] Now go to FIG. 4A to FIG. 4C In , additional details are provided on detecting peer drift instances on a target cloud computing system. In particular, FIG. 4A to FIG. 4C Depicted is a sequence flow diagram showing the timing and actions between the various components of the peer drift system 106 to determine a peer drift instance at a target cloud system.
[0119] As shown in the figure, FIG. 4A to FIG. 4C A series of actions 400 are depicted that are performed by the peer drift system 106 (eg, components of the peer drift system 106). In particular, Figure 4A A high-level overview of a series of actions 400 is depicted and includes peer-to-peer drift system 106 operating on reference cloud computing system 102 and target cloud computing system 112 .
[0120] Additionally, Figure 4A 102 and then a portion of a series of actions 400 occurring on the target cloud computing system 112. Thus, as shown, the series of actions 400 includes an action 402 of generating a reference cloud data set to verify equivalence with one or more target cloud computing systems. Action 402 is combined with Figure 4B Additionally, the series of actions 400 includes an action 404 of determining a peer drift instance on a target cloud system, which in combination Figure 4C is further described.
[0121] Although the present disclosure mainly describes the peer drift system 106 determining peer drift within the target cloud system, in one or more embodiments, the reference cloud system can determine instances of peer drift occurring on the target cloud system. For example, the peer drift system 106 generates a target data set on the target cloud computing system 112 and provides a job package of the target data set and the query set to the reference cloud computing system 102. Then, the peer drift system 106 on the reference cloud computing system 102 performs the functions of the reporting service and the alerting service to determine and notify the instance of peer drift at the target cloud computing system 112.
[0122] In some embodiments, the peer drift system 106 is located on another computing device and determines a peer drift instance occurring on the target cloud system based on receiving data sets from both the reference cloud system and the target cloud system. In these implementations, the peer drift system 106 can continue to use the job package including at least the query set to ensure that both the reference cloud system and the target cloud system use the same query set to generate their respective data sets.
[0123] As mentioned above, Figure 4B Corresponding to the action 402 of generating a reference cloud data set and the peer drift system 106. As shown, Figure 4B The reference cloud computing system 102 in includes a reference data source 108 and a peer drift system 106. In particular, Figure 4B The peer-to-peer drift system 106 in includes the query service 322a and the job packager 320a introduced above.
[0124] like Figure 4B As shown, a series of actions 400 includes an action 410 of triggering peer verification. For example, in various implementations, the query service 322a includes a scheduler or timer that triggers or starts the peer verification process. For example, a regular (e.g., hourly, daily, weekly, etc.) event (e.g., a scheduled task job or script) that starts the peer verification process is scheduled to run. In one or more implementations, the query service 322a triggers peer verification based on receiving user input (e.g., through execution based on HTTP triggers). In some implementations, the scheduler triggers different sets of queries at different times to check whether peer drift occurs in different parts of the cloud computing system.
[0125] In one or more implementations, the query service 322a retrieves a query set from a storage container or storage device as part of initiating a peer verification process. For example, as part of onboarding, one or more query sets are added to a storage container from which the query service 322a can retrieve. In some implementations, the query set includes a query profile having one or more queries.
[0126] As shown, a series of actions 400 includes an action 412 of executing a query set for a service (or function or feature) and an action 414 of adding service configuration data to a data set. In various implementations, the query service 322a provides a query to the reference data source 108 to retrieve one or more inputs returned to the query service 322a. As shown in action 416 in the series of actions 400, the query service 322a can repeat (e.g., loop) the query search for each service being accessed according to the query set and / or query configuration. In this way, the query service 322a can generate a reference data set, as further described above.
[0127] As shown, the series of actions 400 includes an action 418 of providing the query set to the job bundler 320a. For example, in various implementations, upon receiving or accessing the query set, the query service 322a provides a copy of the query set to the job bundler 320a for inclusion in the job bundle. In addition, the series of actions 400 includes an action 420 of providing the reference data set to the job bundler 320a.
[0128] As shown, a series of actions 400 includes an action 422 of generating a job bundle using a query set and a reference data set. For example, in multiple implementations, a job bundler 320a generates a job bundle that includes a query set and a reference data set. In some implementations, the job bundle also includes metadata or other information that distinguishes the job bundle from other job bundles. For example, the job bundler 320a includes information about the date and / or time when the job bundle was created and / or whether the job bundle is specific to a service group.
[0129] As shown, a series of actions 400 includes an action 424 of sending a job package to one or more target cloud systems, such as the target cloud computing system 112. In practice, the reference cloud system can send a job package to serve as a truth set for other cloud systems to be modeled and / or used to detect peer drift. In various implementations, the peer drift system 106 sends the job package to a single target cloud system. In other implementations, the peer drift system sends the job package to multiple cloud target cloud systems. In various implementations, the target cloud computing system is a locally deployed cloud computing system operated by an entity different from the operating reference cloud computing system. In an example implementation, the target cloud computing system is an air gap cloud computing system. In some implementations, the target cloud computing system includes a cloud computing system operated by competing cloud computing system providers.
[0130] In some implementations, the peer drift system 106 uses a replication service or another type of transport service to provide the job package to the target cloud system. In various implementations, the peer drift system 106 sends the job package through an encrypted channel or another type of secure communication channel. According to some implementations, the target cloud computing system 112 requests or extracts the job package from the reference cloud computing system 102.
[0131] like Figure 4C As shown, the series of actions 400 includes an action 426 of receiving a job package at the target cloud system. Figure 4C As shown, the target cloud computing system 112 includes the target data source 118 and the peer drift system 106. As shown, the peer drift system 106 includes a job packager 320b, a query service 322b, a reporting service 324, and an alert service 326. In various implementations, action 426 includes receiving a copy of the job package from the reference cloud computing system 102.
[0132] like Figure 4C As further shown in FIG. 4 , the series of actions 400 includes an action 428 of providing the reference data set to the reporting service 324. For example, the job packager 320 b provides the reference data set received in the job package to the reporting service 324. In some implementations, the job packager 320 b performs one or more verification functions to confirm that a valid job package has been received. For example, the job packager 320 b utilizes hashes and / or metadata in the newly received job package to confirm that the data in the job package has not been damaged or corrupted.
[0133] As shown, the series of actions 400 includes an action 430 of providing a query set to a query service 322b. For example, the job packager 320b provides the query set including the query configuration or a copy of the query set to the query service 322b. In this way, the query service 322b can utilize the query set to construct an equivalent data set on the target cloud system as done on the reference cloud system.
[0134] For illustration, a series of actions 400 includes an action 432 of executing a query set for a service (or feature or function) and an action 434 of adding service configuration data to a data set. For example, the query set 322b issues a query for one or more inputs to the target data source 118, and includes the requested configuration data in the target data set. In various implementations, the peer drift system 106 extracts from an equivalent data source file on the target cloud system, as is done on the reference cloud system. In this way, the reference data set and the target data set are compatible and comparable. As shown, actions 432 and 434 can be repeated for each query from the query set (e.g., for each requested input), as shown in action 436.
[0135] Additionally, as previously described, the data set of the cloud system does not include user-based data. Instead, the data set includes system-based data. In this way, the peer drift system 106 focuses on the configuration and operation issues of the cloud system, rather than the data stored by the cloud system.
[0136] As shown, the sequence of actions 400 includes an action 438 of providing the target data set to the job packager 320b. In one or more implementations, the query service 322b generates the target data set and provides it to the job packager 320b. The job packager 320b can supplement the received job package with the target data set, as shown in action 440 in the sequence of actions 400. In some embodiments, the peer drift system 106 can store the target data set in a storage container associated with the target cloud computing system 112.
[0137] As shown, sequence of actions 400 includes an action 442 of providing the job bundle to reporting service 324 on target cloud computing system 112. For example, in various implementations, job bundler 320b provides the job bundle, link, or indication of the job bundle to reporting service 324. In some implementations, a trigger based on a storage event notifies reporting service 324 that both data sets are available. In other implementations, reporting service 324 can detect when the target data set is added to the job bundle along with the reference data set (e.g., reporting service 324 is triggered when both data sets appear).
[0138] As described above, in various implementations, reporting service 324 is a collection of reporting engines that compare and analyze data vectors between two data sets. For example, a reporting engine can compare a column of data in a reference data set to a corresponding column of data in a target data set according to a schema established by the reporting engine. In addition, reporting service 324 can traverse a list of reporting engines and call each engine, as described above.
[0139] To elaborate, for each reporting engine, the reporting service 324 can access the data set, utilize the reporting engine schema to identify the appropriate columns in the data set that serve as input for the reporting engine, and perform calculations to generate output (e.g., peer dimensions of a service, feature, or function). In practice, the reporting service 324 generates output according to the reporting engine schema. For example, the reporting service 324 generates a peer report that includes a new column of vector data that indicates various peer dimensions. In some implementations, the reporting service 324 generates the peer report as part of one or both data sets, or as a new data structure.
[0140] As described above, the reporting service 324 can process various reporting engines in a chained or serial manner so that the output of the previous reporting engine can serve as the input of the subsequent reporting engine. In some implementations, the reporting service 324 executes different reporting engines in parallel. Therefore, as shown in the figure, a series of actions 400 includes an action 444 of generating a peer report.
[0141] In various implementations, different reporting engines use the same schema. For example, many reporting engines use default schemas that indicate the input and output formats required by the reporting engine. In some implementations, the reporting engine uses custom schemas that change the input, output, operating mode, and / or other formats of the reporting engine. For example, in one or more implementations, the reporting engine is customized to perform complex calculations on multiple columns from a reference data set and a target data set. In fact, in some implementations, the peer drift system 106 provides a common schema to the reporting engine while also providing customization options for specific services, features, or functions. In fact, in many cases, the peer drift system 106 allows different services to be measured with different reports.
[0142] In some implementations, the reporting service 324 facilitates reporting different peer dimensions for services. For example, in one or more implementations, the peer dimension includes a simple binary peer metric that indicates whether the system (or part thereof (e.g., a service)) is at a peer (e.g., has the same version, tools, or scripts). In some implementations, the peer dimension includes different configuration versions (e.g., differences in service configurations, dependency configurations (e.g., Geneva Logs configurations), ARM manifests, etc.). In various implementations, the peer dimension includes different environment versions (e.g., differences in operating systems, patches, virtual machine extensions, shared services, etc.). In practice, detecting peer drift can range from detecting differences between two cloud systems on one end to detecting differences between specific markers of services on the other end.
[0143] In an example implementation, the peer drift system 106 also utilizes time to indicate a "distance" dimension for measuring peer drift (e.g., generating a peer dimension for peer services in a peer report). For example, the peer drift system 106 can measure services with different configuration settings between a reference cloud system and a target cloud system over time, which increases the "distance" dimension that can be measured by a threshold. For example, service versions can be "equal" one day and "unequal" the next day.
[0144] As shown, sequence of acts 400 includes an act 446 of generating a peer rating. In various implementations, reporting service 324 compares the peer dimensions in the peer report to the grading policy and grading thresholds to determine a peer rating for the services, features, and functions of target cloud computing system 112, as described above. In one or more implementations, reporting service 324 determines the peer rating based on multiple peer dimensions in the peer report for the services, features, or functions of target cloud computing system 112. Additionally, in some implementations, the peer rating is added to the peer report (e.g., as an additional column).
[0145] The peer drift system 106 can use various types of grading systems to indicate peer ratings. For example, as described above, the peer drift system 106 can use a red, yellow, and green grading model that indicates good, problematic, and bad peer ratings, respectively. In some cases, the peer drift system uses a numerical scale (e.g., 1 to 10, 1 to 100, etc.). According to other examples, the peer system uses a letter rating system.
[0146] In one or more implementations, the reporting service 324 accesses archived job reports to determine the peer drift trend of the service by comparing how the service deviates from the peer over a period of time. For example, if the reporting service 324 detects that the peer drift for service A increases over a period of time (e.g., one week, 15 days, one month, three months, etc.), then the reporting service 324 can determine that there is a problem with the deployment technology or target technology for service A. The tracking trend of peer drift can also serve as a weather vane (e.g., an indicator or predictor) for the overall health of the target cloud system. For example, the peer drift trend can indicate a deployment conflict for the upgrade of each node deployed to the target cloud system, which would otherwise not be detected. In this way, the reporting service 324 can determine the urgency based on the peer drift of the service. In fact, in some implementations, the reporting service 324 can determine a more critical peer level based on the peer drift pattern of the service over time. Similarly, the reporting service 324 can determine that the peer drift of the service is more likely to be an abnormal event, and therefore less critical, resulting in a less critical peer level. Additionally, reporting service 324 can utilize peer drift as a long-term tool to measure peer drift trends and behaviors as tools are developed and updates are made to the cloud system.
[0147] In various implementations, the peer drift system 106 provides default and customizable rating policies and rating thresholds for each service, function, and feature. In this way, some services (e.g., services associated with the security of the target cloud system) may require closer monitoring and greater sensitivity to peer drift, while other less critical services may be able to experience instances of peer drift with little direct consequence.
[0148] To further illustrate, some services are deployed very frequently, such as multiple times a week, while other services may deploy updates a few times a year. Therefore, the peer drift system 106 allows for the use of different grading thresholds to determine peer drift for these different services, as a 30-day drift for one service (e.g., a frequently updated service) indicates a more critical peer drift than a 30-day drift for another service (e.g., a rarely updated service).
[0149] Additionally, in various implementations, the peer drift system 106 allows for user customization and modification of peer rating policies and thresholds. For example, the peer drift system 106 facilitates user input to increase or decrease rating sensitivity by increasing or decreasing the rating threshold for that service (e.g., reducing the number of days before a service is rated critical or red). In effect, the peer drift system 106 facilitates user input of generic and / or general policies to provide specific exemptions to specific services.
[0150] As shown, sequence of actions 400 includes an action 448 of adding peer reports and ratings to the job package. For example, in one or more implementations, reporting service 324 adds the peer reports to the job package. In various embodiments, reporting service 324 provides the peer reports and / or peer ratings to job packager 320b, and job packager 320b appends or supplements the reports (including the peer ratings for each service, feature, and function of target cloud computing system 112) to the job package.
[0151] As shown, sequence of actions 400 includes an action of archiving peer reports 450. For example, in various implementations, job packager 320b stores peer reports in an indexable format that facilitates simple and more efficient query retrieval of past peer drift information of target cloud computing system 112. In some cases, peer reports are archived in a structured database, as described above.
[0152] As shown, series of actions 400 includes an action 452 of detecting peer drift by the alert service 326. For example, in various implementations, the alert service 326 of the peer drift system 106 detects one or more instances of peer drift based on peer ratings in peer reports. For example, if the peer rating of a service triggers an alert threshold (e.g., service A has a red rating), the alert service 326 can send a corresponding alert. As another example, if a set of services has a peer rating that triggers an alert threshold (e.g., five services have a yellow rating), the alert service 326 can send the same or different alerts. Examples of peer alerts and alert thresholds are provided above.
[0153] Furthermore, in various implementations, the peer drift system 106 implements a simplified alarm detection system because complex calculations are typically performed by the reporting service 324 (e.g., at the peer reporting and / or classification level). Thus, in many implementations, the alarm service 326 can follow a simplified set of alarm thresholds to determine when to send an alarm, what type of alarm to send, and to which computing devices to send the alarm. Thus, the series of actions 400 includes an action 454 of notifying a peer drift (e.g., providing an alarm indicating an instance of peer drift on the target cloud system to a client device).
[0154] However, in some implementations, the peer drift system 106 can customize alerts based on specific services, features, or functions. For example, the alert service 326 provides alerts to certain services with a given peer rating, but does not provide alerts to other services with the same given peer rating. As described above, the peer drift system can interpret this at a hierarchical level in some cases. In other cases, the peer drift system promotes this action at the alert level. In fact, the peer drift system 106 can promote customization to enable a user to specify at which level to apply one or more customizations.
[0155] In a similar manner, in one or more implementations, the peer drift system 106 can provide an alert when a combination of peer ratings triggers an alert threshold. For example, the alert service 326 determines that a combination of related services has a combined peer rating score below an alert threshold (e.g., the sum of the peer scores of the related services is below a minimum alert threshold corresponding to the related services). In practice, the peer drift system facilitates several types of alert policies and alert thresholds for sending alerts.
[0156] Turning to the next picture, Figure 5 Providing an indication of peer drift on a computing device according to one or more implementations is shown. Figure 5 As shown, Figure 5 Included is a computer device 500 having a graphical user interface 502. As also shown, the graphical user interface 502 includes an alert 504 indicating an instance of peer drift on a target cloud system.
[0157] In various implementations, alert 504 allows user interaction. For example, as shown by confirmation selectable element 506 (e.g., "ok" at the bottom), alert 504 allows the user to confirm receipt of alert 504. In other cases, alert 504 provides several different options. For example, alert 504 provides the option of having peer drift system 106 automatically correct peer drift (e.g., update the service to the latest version). In another example, alert 504 provides information on how to resolve peer drift at the user's discretion.
[0158] Although the alerts are displayed as a graphical user interface, in many implementations, the alerts are provided in different formats. For example, in some implementations, the alerts are part of the peer drift report. In various implementations, the alerts are included in the system log file. In other implementations, the alerts are provided as electronic messages. Additional details about providing and responding to alerts indicating instances of peer drift in the target cloud system are provided above.
[0159] Now turn to Figures 6A to 6B , which illustrate example flow diagrams including a series of actions 600, 655 for utilizing the peer drift system 106 according to one or more implementations. Figures 6A to 6B Actions according to one or more implementations are shown, and alternative implementations may omit, add, reorder, and / or modify any of the actions shown. Figures 6A to 6B The actions of may be performed as part of a method. Alternatively, the non-transitory computer readable medium may include a program that, when executed by one or more processors, causes a computing device to perform Figures 6A to 6B In a further implementation, the system may execute Figures 6A to 6B action.
[0160] For example, Fig. 6A A series of actions 600 for determining peer drift for a target cloud computing system is shown. The series of actions 600 includes an action 610 of receiving a cloud system configuration job package including a query and a reference data set. For example, action 610 may involve receiving a job package at the target cloud computing system and from a reference cloud computing system, the job package including the query set and the reference data set generated by running the query set on a feature configuration of the reference cloud computing system.
[0161] In some implementations, action 610 includes adding the target data set to a job package stored on the target cloud computing system in response to generating the target data set. In some implementations, the reference data set includes a schema indicating state information and version information of network functions on the reference cloud computing system, but does not include user data. Indeed, in example implementations, the reference data set includes control data and omits user data. In one or more implementations, action 610 includes receiving the job package via a unidirectional communication channel, wherein return communication to the reference cloud computing system is prohibited, restricted, and / or otherwise limited.
[0162] As also shown, the series of actions 600 includes an action 620 of generating a target data set by running queries on the target cloud system. For example, action 620 may involve generating a target data set by running a set of queries from the job package on the target cloud computing system in response to receiving the job package at the target cloud computing system. In some implementations, action 620 includes running the set of queries from the job package on a feature configuration of a service on the target cloud computing system.
[0163] As also shown, a series of actions 600 includes an action 630 of determining a peer report between a reference data set and a target data set. For example, action 630 may include determining a peer dimension report between the reference data set and the target data set. In various implementations, action 630 includes utilizing multiple reporting engines to determine multiple peer dimensions based on inputs from the reference data set and the target data set. In some implementations, the peer dimension report includes a table of columns that includes output for each reporting engine executed.
[0164] As also shown, a series of actions 600 includes an action 640 of determining a peer score (e.g., a peer level) based on the peer report. For example, action 640 may involve determining a peer score at a target cloud computing system based on a job package including a query set, a reference data set, and a target data set stored on the target cloud computing system. In some implementations, action 640 includes determining a peer score based on a peer dimension report and one or more peer score thresholds.
[0165] In one or more implementations, act 640 includes utilizing multiple reporting engines to determine multiple peer dimensions based on input from the reference dataset and the target dataset. In some implementations, act 640 also includes generating a peer dimension report including a column for each peer dimension in the multiple peer dimensions.
[0166] In various implementations, action 640 includes generating a peer dimension report between the reference data set and the target data set, and determining one or more peer scores based on the peer dimension report and one or more peer score thresholds. In some implementations, action 640 also includes determining the peer dimension report between the reference data set and the target data set based on the peer configuration settings of the target cloud computing system. In various implementations, in response to determining the peer score, action 640 includes adding the peer score to the job package and archiving the job package including the query set, the target data set, the reference data set, the peer dimension report, and the peer score on the target cloud computing system. In some implementations, action 640 also includes determining one or more peer scores based on the reference data set, the target data set, and one or more archived job packages.
[0167] As also shown, a series of actions 600 includes an action 650 of providing a peer alert based on a peer score. For example, action 650 may include one or more peer alerts provided by a target cloud computing system based on a peer score. In various implementations, action 650 includes detecting one or more feature configurations of a target cloud computing system that triggers a peer alert threshold based on a peer score. In some implementations, providing one or more peer alerts is based on a peer alert threshold being triggered. In various implementations, action 650 includes appending one or more peer scores to a peer dimension report.
[0168] Figure 6B Also shown is a series of actions 655 for determining a peer drift for a target cloud computing system. The series of actions 655 includes an action 660 of generating a cloud system configuration job package having a query and a reference data set. For example, action 660 may involve generating a job package by a reference cloud computing system, the job package including a feature configuration query set and a reference data set generated by running the feature configuration query set on the reference cloud computing system.
[0169] As also shown, a series of actions 655 includes an action 670 of providing a cloud system configuration job package to a target cloud system. For example, action 670 may include providing the job package to multiple target cloud computing systems. In various implementations, one of the target cloud computing systems is a locally deployed cloud computing system operated by a different entity than the reference cloud computing system. In some implementations, the multiple target cloud computing systems include cloud computing systems operated by competing cloud computing system providers. In an example implementation, the target cloud computing system is an air-gapped cloud computing system.
[0170] In addition, if Figure 6B As shown, the action includes various sub-actions. For illustration, action 670 includes sub-action 671 of supplementing the cloud system configuration job package with a target data set generated at the target cloud system. For example, sub-action 671 may involve supplementing the job package with a target data set generated by running a feature configuration query set on the target cloud computing system.
[0171] As also shown, action 670 includes a sub-action 672 of generating a peer score based on the reference data set and the target data set. For example, sub-action 672 may involve generating a peer score based on a supplemental job package including the query set, the reference data set, and the target data set.
[0172] As also shown, action 670 includes a sub-action 673 of providing a peer alert based on the peer score. For example, sub-action 673 can involve providing one or more peer alerts within the target cloud computing system based on the peer score. In various implementations, sub-action 673 includes multiple target cloud computing systems receiving and processing the job package to determine one or more peer alerts without providing the one or more peer alerts to the reference cloud computing system.
[0173] A "network" is defined as one or more data links that enable electronic data to be transmitted between computer systems and / or modules and / or other electronic devices. When information is transmitted or provided to a computer via a network or another communication connection (hardwired, wireless, or a combination of hardwired and wireless), the computer properly views the connection as a transmission medium. Transmission media may include networks and / or data links that may be used to carry the required program code in the form of computer-executable instructions or data structures, and which may be accessed by general-purpose or special-purpose computers. Combinations of the above should also be included within the scope of computer-readable media.
[0174] In addition, the network described herein may represent a network or a collection of networks (e.g., the Internet, an intranet, a virtual private network (VPN), a local area network (LAN), a wireless local area network (WLAN), a cellular network, a wide area network (WAN), a metropolitan area network (MAN), or a combination of two or more such networks) through which one or more computing devices can access the peer-to-peer drift system 106. In practice, the network described herein may include one or more networks using one or more communication platforms or technologies for transmitting data. For example, a network may include the Internet or other data links that enable the transmission of electronic data between respective client devices and components (e.g., server devices and / or virtual machines thereon) of a cloud computing system.
[0175] In addition, upon reaching various computer system components, program code in the form of computer executable instructions or data structures can be automatically transferred from the transmission medium to the non-transitory computer readable storage medium (device) (or vice versa). For example, computer executable instructions or data structures received via a network or data link can be buffered in RAM within a network interface module (NIC) and then ultimately transferred to the computer system RAM and / or a less volatile computer storage medium (device) at the computer system. Therefore, it should be understood that non-transitory computer readable storage media (devices) can be included in computer system components that also (or even primarily) utilize transmission media.
[0176] Computer executable instructions include, for example, when executed by a processor, instructions and data that cause a general-purpose computer, a special-purpose computer, or a special-purpose processing device to perform a certain function or group of functions. In some implementations, computer executable instructions are executed by a general-purpose computer to transform a general-purpose computer into a special-purpose computer that implements the disclosed elements. For example, computer executable instructions can be binary, intermediate format instructions (such as assembly language), or even source code. Although the subject matter has been described in a language specific to structural features and / or method actions, it is understood that the subject matter defined in the appended claims is not necessarily limited to the features or actions described above. On the contrary, the described features and actions are disclosed as an example form of implementing the claims.
[0177] Figure 7 Some of the components that may be included in computer system 700 are shown. Computer system 700 may be used to implement the various computing devices, components, and systems described herein.
[0178] In various implementations, the computer system 700 may represent one or more of the above-mentioned one or more client devices, server devices, or other computing devices. For example, the computer system 700 may refer to various types of client devices that can access data on a cloud computing system. For example, a client device may refer to a mobile device, such as a mobile phone, a smart phone, a personal digital assistant (PDA), a tablet computer, a notebook computer, or a wearable computing device (e.g., a headset or a smart watch). A client device may also refer to a non-mobile device, such as a desktop computer, a server node (e.g., from another cloud computing system), or another non-portable device.
[0179] Computer system 700 includes processor 701. Processor 701 may be a general purpose single-chip or multi-chip microprocessor (e.g., Advanced RISC (Reduced Instruction Set Computer) Machine (ARM)), a special purpose microprocessor (e.g., a digital signal processor (DSP)), a microcontroller, a programmable gate array, etc. Processor 701 may be referred to as a central processing unit (CPU). Although processor 701 is shown as Figure 7 A single processor is used in the computer system 700, but in an alternative configuration, a combination of processors (e.g., an ARM and DSP) may be used.
[0180] The computer system 700 also includes a memory 703 in electronic communication with the processor 701. The memory 703 can be any electronic component capable of storing electronic information. For example, the memory 703 can be implemented as a random access memory (RAM), a read-only memory (ROM), a disk storage medium, an optical storage medium, a flash memory device in a RAM, an onboard memory included in a processor, an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM) memory, a register, etc., including combinations thereof.
[0181] Instructions 705 and data 707 may be stored in memory 703. Instructions 705 may be executed by processor 701 to implement some or all of the functionality disclosed herein. Executing instructions 705 may involve the use of data 707 stored in memory 703. Any of the various examples of modules and components described herein may be implemented in part or in whole as instructions 705 stored in memory 703 and executed by processor 701. Any of the various examples of data described herein may be in data 707 stored in memory 703 and used during execution of instructions 705 by processor 701.
[0182] The computer system 700 may also include one or more communication interfaces 709 for communicating with other electronic devices. The one or more communication interfaces 709 may be based on wired communication technology, wireless communication technology, or both. Some examples of the one or more communication interfaces 709 include a universal serial bus (USB), an Ethernet adapter, a wireless adapter operating according to the Institute of Electrical and Electronics Engineers (IEEE) 702.11 wireless communication protocol, Wireless communication adapter and infrared (IR) communication port.
[0183] The computer system 700 may also include one or more input devices 711 and one or more output devices 713. Some examples of the one or more input devices 711 include keyboards, mice, microphones, remote control devices, buttons, joysticks, trackballs, touchpads, and light pens. Some examples of the one or more output devices 713 include speakers and printers. A specific type of output device that is typically included in the computer system 700 is a display device 715. The display device 715 used with the implementations disclosed herein may utilize any suitable image projection technology, such as a liquid crystal display (LCD), a light emitting diode (LED), gas plasma, electroluminescence, and the like. A display controller 717 may also be provided for converting the data 707 stored in the memory 703 into text, graphics, and / or moving images (as appropriate) displayed on the display device 715.
[0184] The various components of the computer system 700 may be coupled together via one or more buses, which may include a power bus, a control signal bus, a status signal bus, a data bus, etc. For the purpose of clarity, the various buses are referred to in Figure 7 Shown in FIG. 7 is bus system 719 .
[0185] Those skilled in the art will appreciate that the present disclosure can be implemented in a network computing environment with many types of computer system configurations, including personal computers, desktop computers, notebook computers, message processors, handheld devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, mobile phones, PDAs, tablet computers, pagers, routers, switches, etc. The present disclosure can also be implemented in a distributed system environment, where local and remote computer systems that are linked (by a hardwired data link, a wireless data link, or a combination of a hardwired and wireless data link) through a network all perform tasks. In a distributed system environment, program modules can be located in local and remote memory storage devices.
[0186] The techniques described herein may be implemented in hardware, software, firmware, or any combination thereof, unless specifically described as being implemented in a particular manner. Any features described as modules, components, or the like may also be implemented together in an integrated logic device, or separately as discrete but interoperable logic devices. If implemented in software, the techniques may be implemented at least in part by a non-transient processor-readable storage medium that includes instructions that, when executed by at least one processor, perform one or more methods described herein. Instructions may be organized into routines, programs, objects, components, data structures, and the like that may perform specific tasks and / or implement specific data types, and that may be combined or distributed in various implementations as desired.
[0187] Computer readable media can be any available media that can be accessed by a general or special purpose computer system. Computer readable media that store computer executable instructions are non-transitory computer readable storage media (devices). Computer readable media that carry computer executable instructions are transmission media. Therefore, by way of example and not limitation, implementations of the present disclosure may include at least two distinct computer readable media: non-transitory computer readable storage media (devices) and transmission media.
[0188] As used herein, non-transitory computer-readable storage media (devices) may include RAM, ROM, EEPROM, CD-ROM, solid-state drives (“SSD”) (e.g., RAM-based), flash memory, phase change memory (“PCM”), other types of memory, other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of computer-executable instructions or data structures and that can be accessed by a general or special purpose computer.
[0189] The steps and / or actions of the methods described herein may be interchanged without departing from the scope of the claims. In other words, unless a specific order of steps or actions is required for the correct operation of the method being described, the order and / or use of specific steps and / or actions may be modified without departing from the scope of the claims.
[0190] The term "determining" encompasses a wide variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, a database, or another data structure), ascertaining, etc. "Determining" may also include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), etc. "Determining" may also include resolving, selecting, choosing, establishing, etc.
[0191] The terms "comprising," "including," and "having" are intended to be inclusive and broad, and mean that there may be additional elements in addition to the listed elements. Additionally, it should be understood that reference to "an implementation" or "multiple implementations" of the present disclosure is not intended to be interpreted as excluding the existence of additional implementations that also include the described features. For example, any element or feature described with respect to an implementation herein may be combinable with any element or feature of any other implementation described herein, where compatible.
[0192] The present disclosure may be embodied in other specific forms without departing from its spirit or characteristics. The implementation is considered to be illustrative rather than restrictive. Therefore, the scope of the present disclosure is indicated by the appended claims rather than by the foregoing description. Changes that occur within the meaning and equivalent range of the claims will be accepted within their scope.
Claims
1. A computer-implemented method for detecting instances of peer drift in a cloud computing system, comprising: receiving, at a target cloud computing system, a job package from a reference cloud computing system, the job package comprising a query set and a reference data set generated by running the query set on the reference cloud computing system; In response to receiving the job package, generating a target data set at the target cloud computing system by running the query set from the job package on the target cloud computing system; determining, at the target cloud computing system, a peer score based on the job package stored on the target cloud computing system and including the query set, the reference data set, and the target data set; as well as One or more peer alerts are provided by the target cloud computing system based on the peer score.
2. The computer-implemented method of claim 1 , wherein the reference data set includes a schema indicating state information and version information of network functions on the reference cloud computing system, but does not include user data.
3. The computer-implemented method of any one of claims 1 or 2, wherein determining the peer score further comprises utilizing a plurality of reporting engines to determine a plurality of peer dimensions based on inputs from the reference dataset and the target dataset. 4 . The computer-implemented method of claim 3 , wherein determining the peer score further comprises generating a peer report including a column for each peer dimension of the plurality of peer dimensions.
5. The computer-implemented method of claim 1 , wherein determining the peer score comprises: generating a equivalence report between the reference dataset and the target dataset; as well as One or more peer scores are determined based on the peer report and one or more peer score thresholds. 6 . The computer-implemented method of claim 5 , wherein determining the peer score further comprises determining the peer report between the reference data set and the target data set based on peer configuration settings of the target cloud computing system.
7. The computer-implemented method of claim 5, further comprising: In response to determining the peer score, adding the peer score to the job package; as well as The job package including the query set, the target data set, the reference data set, the peer report, and the peer score is archived on the target cloud computing system.
8. The computer-implemented method of claim 6, wherein determining the peer score further comprises determining one or more peer scores based on the reference dataset, the target dataset, and one or more archived job packages.
9. The computer-implemented method of claim 1 , wherein: The target cloud computing system is an air-gapped cloud computing system; and Receiving the job package from a reference cloud computing system includes receiving the job package via a unidirectional communication channel.
10. The computer-implemented method of claim 1 , further comprising: In response to generating the target data set, the target data set is added to the job bundle stored in the target cloud computing system.
11. The computer-implemented method of claim 1 , further comprising: One or more characteristic configurations of the target cloud computing system that trigger a peer alert threshold are detected based on the peer score, wherein providing one or more of the peer alerts is based on the peer alert threshold being triggered.
12. The computer-implemented method of claim 1, wherein the target cloud computing system is an on-premises cloud computing system operated by a different entity than an entity operating the reference cloud computing system.
13. A target cloud computing system, comprising: at least one processor; as well as A computer memory comprising instructions which, when executed by the at least one processor, cause the target cloud computing system to perform a computer-implemented method according to any one of claims 1 to 12.
14. A computer-implemented method for detecting peer drift instances in a cloud computing system, comprising: Generate a job package by a reference cloud computing system, the job package including a feature configuration query set and a reference data set generated by running the feature configuration query set on the reference cloud computing system; as well as Providing the job package to multiple target cloud computing systems, wherein providing the job package to each target cloud computing system enables the target cloud computing system to: supplementing the job package with a target data set generated by running the feature configuration query set on the target cloud computing system; generating a peer score based on the supplemented job package including the query set, the reference data set, and the target data set; as well as One or more peer alerts are provided within the target cloud computing system based on the peer score.
15. The computer-implemented method of claim 14, wherein: The plurality of target cloud computing systems include cloud computing systems operated by competing cloud computing system providers; or The plurality of target cloud computing systems receive and process the job bundle to determine the one or more peer alerts without providing the one or more peer alerts to the reference cloud computing system.
