BNS-based configuration checking method and device, electronic equipment and storage medium

Abstract

The invention provides a BNS-based configuration checking method and device, electronic equipment and a storage medium, and relates to the technical field of network operation and maintenance. In the application, in response to a configuration check request for a target service, a BNS identifier set by a BNS for the target service is acquired; obtaining at least one configuration set of at least one service instance from an operation and maintenance platform related to at least one service instance of the target service based on the BNS identifier; wherein each configuration set comprises instance configuration of at least one service instance on the corresponding operation and maintenance platform; constructing a configuration state graph based on the BNS identifier, the at least one operation and maintenance platform and the at least one configuration set; and performing configuration check on the target service based on the configuration state atlas and a preset standard configuration check rule set. Therefore, the efficiency and accuracy of configuration check are improved while the operation and maintenance cost is reduced.

Description

Technical Field

[0001] This application relates to the field of network operation and maintenance technology, and in particular to a configuration checking method, device, electronic device and storage medium based on BNS. Background Technology

[0002] Currently, operations (OP) personnel typically rely on static checklists to manually log into multiple independent OP platforms, querying and comparing each configuration set for the service instance of the target service to perform configuration checks. However, for specific configurations, customized check scripts can be used to perform configuration checks.

[0003] However, the configuration checking methods described above are extremely inefficient due to the time-consuming nature of manual checks. Furthermore, since checking the configuration of a target service requires manually verifying multiple configurations on the checklist item by item, manual operation is prone to fatigue, making it easy to miss or misidentify configurations. In addition, semi-automated (or fragmented) checks based on check scripts can only cover partial checks and require maintenance personnel to maintain the check scripts, resulting in high maintenance costs. Therefore, how to improve the efficiency and accuracy of configuration checks while reducing maintenance costs is a pressing issue that needs to be addressed. Summary of the Invention

[0004] This application provides a configuration checking method, apparatus, electronic device, and storage medium based on BNS, which can improve the efficiency and accuracy of configuration checking while reducing operation and maintenance costs.

[0005] In a first aspect, embodiments of this application provide a configuration checking method based on BNS, the method comprising: In response to a configuration check request for the target service, obtain the BNS identifier set by Baidu naming service (BNS) for the target service; Based on the BNS identifier, obtain at least one configuration set of at least one service instance from the operation and maintenance platform associated with at least one service instance of the target service; wherein, each configuration set includes: instance configuration of at least one service instance on the corresponding operation and maintenance platform; Construct a configuration status graph based on BNS identifiers, at least one operation and maintenance platform, and at least one configuration set; The configuration of the target service is checked based on the configuration state graph and the preset set of standard configuration check rules; the set of standard configuration check rules includes standard configuration check rules set separately for various instance configurations.

[0006] In one optional embodiment, based on the BNS identifier, at least one configuration set of at least one service instance is obtained from the operation and maintenance platform associated with at least one service instance of the target service, including: Based on the BNS identifier, determine the instance configuration mapping corresponding to at least one service instance; Obtain configuration data corresponding to at least one instance configuration mapping from the operation and maintenance data of at least one operation and maintenance platform; Perform data cleaning and standardization on at least one configuration data set to obtain at least one configuration set.

[0007] In one optional embodiment, a configuration state graph is constructed based on the BNS identifier, at least one operation and maintenance platform, and at least one configuration set, including: The BNS identifier is used as the root node, at least one operation and maintenance platform is used as the intermediate child node, and at least one instance configuration included in each of the at least one configuration set is used as the leaf node. A configuration state graph is constructed based on the root node, at least one intermediate child node, multiple leaf nodes, and a preset instance configuration sorting.

[0008] In one optional embodiment, configuration checks are performed on the target service based on a configuration state graph and a preset set of standard configuration check rules, including: Based on the instance configuration sorting and the standard configuration check rule sorting of the standard configuration check rule set, the standard configuration check rules are determined for the multiple instance configurations included in the configuration state graph. Configuration checks are performed on multiple instance configurations based on the configuration constraints corresponding to multiple standard configuration check rules, and the instance check results of each instance configuration are used as the service check results of the target service.

[0009] In one optional embodiment, configuration checks are performed on the configurations of multiple instances based on configuration constraints corresponding to multiple standard configuration check rules, including: For multiple instance configurations, perform the following operations respectively: From multiple configuration constraints, determine the first configuration constraint corresponding to the first instance configuration; wherein, the first instance configuration is any one of the multiple instance configurations; When the first instance configuration meets the first configuration constraints, the first instance configuration is marked as a compliant configuration, and an instance check result for the first instance configuration is generated based on the compliance information of the first instance configuration. When the first instance configuration does not meet the first configuration constraints, the first instance configuration is marked as non-compliant, and an instance check result of the first instance configuration is generated based on the non-compliant information of the first instance configuration.

[0010] In an optional embodiment, after performing configuration checks on the configurations of multiple instances based on the configuration constraints corresponding to multiple standard configuration check rules, the method further includes: From multiple instance inspection results, obtain at least one instance inspection result that indicates the instance configuration is non-compliant; For at least one instance check result, perform the following operations respectively: Based on the second instance inspection results corresponding to the second instance configuration, a non-compliance root cause analysis is performed on the second instance configuration to obtain the fundamental non-compliance reasons and potential non-compliance reasons of the second instance configuration; wherein, the second instance inspection result is any one of at least one instance inspection result; A configuration modification strategy for the second instance configuration is generated based on the fundamental non-compliance reasons and potential non-compliance reasons. The second instance configuration is then modified based on the configuration modification strategy to obtain the modified second instance configuration. Based on the second configuration constraints corresponding to the second instance configuration, a performance test is performed on the modified second instance configuration to obtain the performance test results; wherein, the performance test results indicate whether the modified second instance configuration meets the second configuration constraints.

[0011] In an optional embodiment, the method further includes: If the performance test results indicate that the modified second instance configuration does not meet the second configuration constraints, a configuration modification request is sent to the terminal device so that the terminal device can display the instance modification interface to the operation and maintenance personnel; the instance modification interface is used to display at least the modified second instance configuration and its corresponding performance test results.

[0012] Secondly, embodiments of this application also provide a configuration checking device based on BNS, the method comprising: The first acquisition module is used to obtain the BNS identifier set by BNS for the target service in response to a configuration check request for the target service. The second acquisition module is used to acquire at least one configuration set of at least one service instance from the operation and maintenance platform associated with at least one service instance of the target service based on the BNS identifier; wherein each configuration set includes: instance configuration of at least one service instance on the corresponding operation and maintenance platform; The graph construction module is used to construct a configuration status graph based on BNS identifiers, at least one operation and maintenance platform, and at least one configuration set. The configuration check module is used to perform configuration checks on the target service based on the configuration status graph and a set of preset standard configuration check rules. The set of standard configuration check rules includes standard configuration check rules set separately for various instance configurations.

[0013] In an optional embodiment, when obtaining at least one configuration set of at least one service instance from the operation and maintenance platform associated with at least one service instance of the target service based on the BNS identifier, the second obtaining module is specifically used for: Based on the BNS identifier, determine the instance configuration mapping corresponding to at least one service instance; Obtain configuration data corresponding to at least one instance configuration mapping from the operation and maintenance data of at least one operation and maintenance platform; Perform data cleaning and standardization on at least one configuration data set to obtain at least one configuration set.

[0014] In one optional embodiment, when constructing a configuration status graph based on BNS identifiers, at least one operation and maintenance platform, and at least one configuration set, the graph construction module is specifically used for: The BNS identifier is used as the root node, at least one operation and maintenance platform is used as the intermediate child node, and at least one instance configuration included in each of the at least one configuration set is used as the leaf node. A configuration state graph is constructed based on the root node, at least one intermediate child node, multiple leaf nodes, and a preset instance configuration sorting.

[0015] In an optional embodiment, when performing configuration checks on the target service based on the configuration state graph and a preset set of standard configuration check rules, the configuration check module is specifically used for: Based on the instance configuration sorting and the standard configuration check rule sorting of the standard configuration check rule set, the standard configuration check rules are determined for the multiple instance configurations included in the configuration state graph. Configuration checks are performed on multiple instance configurations based on the configuration constraints corresponding to multiple standard configuration check rules, and the instance check results of each instance configuration are used as the service check results of the target service.

[0016] In an optional embodiment, when performing configuration checks on multiple instance configurations based on configuration constraints corresponding to multiple standard configuration check rules, the configuration check module is specifically used for: For multiple instance configurations, perform the following operations respectively: From multiple configuration constraints, determine the first configuration constraint corresponding to the first instance configuration; wherein, the first instance configuration is any one of the multiple instance configurations; When the first instance configuration meets the first configuration constraints, the first instance configuration is marked as a compliant configuration, and an instance check result for the first instance configuration is generated based on the compliance information of the first instance configuration. When the first instance configuration does not meet the first configuration constraints, the first instance configuration is marked as non-compliant, and an instance check result of the first instance configuration is generated based on the non-compliant information of the first instance configuration.

[0017] In an optional embodiment, after performing configuration checks on multiple instance configurations based on configuration constraints corresponding to multiple standard configuration check rules, the configuration check module is further configured to: From multiple instance inspection results, obtain at least one instance inspection result that indicates the instance configuration is non-compliant; For at least one instance check result, perform the following operations respectively: Based on the second instance inspection results corresponding to the second instance configuration, a non-compliance root cause analysis is performed on the second instance configuration to obtain the fundamental non-compliance reasons and potential non-compliance reasons of the second instance configuration; wherein, the second instance inspection result is any one of at least one instance inspection result; A configuration modification strategy for the second instance configuration is generated based on the fundamental non-compliance reasons and potential non-compliance reasons. The second instance configuration is then modified based on the configuration modification strategy to obtain the modified second instance configuration. Based on the second configuration constraints corresponding to the second instance configuration, a performance test is performed on the modified second instance configuration to obtain the performance test results; wherein, the performance test results indicate whether the modified second instance configuration meets the second configuration constraints.

[0018] In an optional embodiment, the configuration check module is further configured to: If the performance test results indicate that the modified second instance configuration does not meet the second configuration constraints, a configuration modification request is sent to the terminal device so that the terminal device can display the instance modification interface to the operation and maintenance personnel; the instance modification interface is used to display at least the modified second instance configuration and its corresponding performance test results.

[0019] Thirdly, embodiments of this application provide an electronic device, including: processor; Stored program memory, The program includes instructions that, when executed by the processor, cause the processor to perform the BNS-based configuration check method as described in the first aspect.

[0020] Fourthly, embodiments of this application provide a non-transitory computer-readable storage medium storing computer instructions, wherein the computer instructions are used to cause a computer to perform the BNS-based configuration check method as described in the first aspect.

[0021] Fifthly, this application provides a computer program product that, when invoked by a computer, causes the computer to perform the BNS-based configuration check method steps as described in the first aspect.

[0022] The beneficial effects of this application are as follows: In the BNS-based configuration inspection method provided in this application embodiment, based on the BNS identifier set for the target service, at least one configuration set of at least one service instance can be quickly obtained from the operation and maintenance platform associated with at least one service instance of the target service. Furthermore, through a configuration state graph constructed based on the BNS identifier, at least one operation and maintenance platform, and at least one configuration set, as well as a preset set of standard configuration inspection rules, configuration inspection of multiple instance configurations in the configuration state graph can be accurately performed. Thus, through automated inspection based on BNS, manual intervention is reduced, thereby improving the efficiency and accuracy of configuration inspection while lowering operation and maintenance costs.

[0023] Furthermore, other features and advantages of this application will be set forth in the following description and will be apparent in part from the description, or may be learned by practicing the application. The objectives and other advantages of this application may be realized and obtained by means of the structures particularly pointed out in the written description, claims, and drawings. Attached Figure Description

[0024] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described herein are used to provide a further understanding of this application, constitute a part of this application, and do not constitute an improper limitation of this application. In the accompanying drawings: Figure 1 This is a schematic diagram of an optional system architecture applicable to the embodiments of this application.

[0025] Figure 2 This is a schematic diagram illustrating the implementation process of a configuration checking method based on BNS provided in an embodiment of this application.

[0026] Figure 3 This is a logical diagram illustrating an embodiment of the present application for obtaining a configuration set.

[0027] Figure 4 This is a schematic diagram of a specific scenario for a configuration state map provided in an embodiment of this application.

[0028] Figure 5 This is a schematic diagram illustrating the implementation process of an instance configuration check method provided in this application embodiment.

[0029] Figure 6This is a logical diagram illustrating another method for determining the data adjustment result of the type to be queried, as provided in an embodiment of this application.

[0030] Figure 7 This is a schematic diagram of a configuration checking device based on BNS provided in an embodiment of this application.

[0031] Figure 8 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0032] Embodiments of this application will now be described in more detail with reference to the accompanying drawings. While some embodiments of this application are shown in the drawings, it should be understood that this application can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of this application. It should be understood that the drawings and embodiments of this application are for illustrative purposes only and are not intended to limit the scope of protection of this application.

[0033] It should be understood that the steps described in the method embodiments of this application may be performed in different orders and / or in parallel. Furthermore, the method embodiments may include additional steps and / or omit the steps shown. The scope of this application is not limited in this respect.

[0034] The term "comprising" and its variations as used herein are open-ended, meaning "including but not limited to". The term "based on" means "at least partially based on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Definitions of other terms will be given in the following description. It should be noted that the concepts of "first", "second", etc., mentioned in this application are used only to distinguish different devices, modules, or units, and are not intended to limit the order of functions performed by these devices, modules, or units or their interdependencies.

[0035] It should be noted that the terms "a" and "a plurality of" used in this application are illustrative rather than restrictive, and those skilled in the art should understand that, unless otherwise expressly indicated in the context, they should be understood as "one or more".

[0036] The names of the messages or information exchanged between multiple devices in the embodiments of this application are for illustrative purposes only and are not intended to limit the scope of these messages or information.

[0037] The following explanations of some terms used in the embodiments of this application are provided to facilitate understanding by those skilled in the art.

[0038] (1) BNS: Similar to the Domain Name System (DNS), BNS translates domain names into Internet Protocol (IP) addresses, making it easier for users to access Internet services. BNS provides a mapping from service names to service instances. It can retrieve a list of information about the instances running under a service based on a name, including hostname, IP address, port, running status, tag, etc.

[0039] (2) Checklist: refers to a static document developed by operations and maintenance personnel to guide the service launch or handover acceptance. It lists dozens of configuration specifications that the service must meet in terms of monitoring, logging, deployment, etc.

[0040] (3) Configuration Status Graph: Taking the BNS representation of the target service as the root node, it automatically associates and integrates fragmented configuration information from different operation and maintenance platforms to form a unified view of the current full-dimensional configuration status of the target service.

[0041] (4) Noah system: a service management and monitoring platform that can be used to manage service registration and discovery, health checks, configuration management, monitoring indicator reporting and alarm policy settings.

[0042] (5) Tag: refers to the metadata tag attached to the service instance, which is used to identify the instance's deployment environment version, data center, business attributes and other information. It is the key to realizing service classification, traffic scheduling and differentiated configuration management.

[0043] Based on the above explanations of terms and related terminology, the design concept of the embodiments of this application will be briefly introduced below: In existing configuration checking methods, operations and maintenance personnel typically rely on a static checklist, manually logging into multiple independent operations and maintenance platforms to query and compare each configuration set for the service instance of the target service. However, for specific configurations, customized check scripts can be used to perform configuration checks.

[0044] However, the configuration checking methods described above are extremely inefficient due to the time-consuming nature of manual checks. Furthermore, since checking the configuration of a target service requires manually verifying multiple configurations on the checklist item by item, manual operation is prone to fatigue, making it easy to miss or misidentify configurations. In addition, semi-automated (or fragmented) checks based on check scripts can only cover partial checks and require maintenance personnel to maintain the check scripts, resulting in high maintenance costs. Therefore, how to improve the efficiency and accuracy of configuration checks while reducing maintenance costs is a pressing issue that needs to be addressed.

[0045] In view of this, in order to solve or improve the above problems, this application provides a configuration inspection method based on BNS, which specifically includes: in response to a configuration inspection request for a target service, obtaining a BNS identifier set by BNS for the target service; then, based on the BNS identifier, obtaining at least one configuration set of at least one service instance from an operation and maintenance platform associated with at least one service instance of the target service; wherein each configuration set may include: instance configurations of at least one service instance on the corresponding operation and maintenance platform; further, constructing a configuration state graph based on the BNS identifier, at least one operation and maintenance platform, and at least one configuration set; finally, performing configuration inspection on the target service based on the configuration state graph and a preset set of standard configuration inspection rules; wherein the set of standard configuration inspection rules may include: standard configuration inspection rules set separately for various instance configurations. Therefore, based on the BNS identifier set by BNS for the target service, at least one configuration set of at least one service instance can be quickly obtained from an operation and maintenance platform associated with at least one service instance of the target service; and through the configuration state graph constructed based on the BNS identifier, at least one operation and maintenance platform, and at least one configuration set, and the preset set of standard configuration inspection rules, configuration inspection of multiple instance configurations in the configuration state graph can be accurately performed. In this way, automated detection based on BNS reduces human intervention, thereby improving the efficiency and accuracy of configuration checks while reducing operation and maintenance costs.

[0046] In particular, the preferred embodiments of this application will be described below with reference to the accompanying drawings. It should be understood that the preferred embodiments described herein are for illustration and explanation only and are not intended to limit this application. Furthermore, the embodiments of this application and the features in the embodiments can be combined with each other unless otherwise specified.

[0047] See Figure 1The diagram illustrates an optional system architecture applicable to an embodiment of this application. This system architecture may include: terminal devices (101a, 101b) and server 102. The terminal devices (101a, 101b) and server 102 can interact via a communication network. The communication network may employ wireless communication or wired communication methods. For example, the terminal devices (101a, 101b) can access the network and communicate with server 102 via cellular mobile communication technology. The aforementioned cellular mobile communication technology may include, for example, 5th generation mobile networks (5G) technology or next-generation mobile communication technology. Optionally, the terminal devices (101a, 101b) can access the network and communicate with server 102 via short-range wireless communication. The aforementioned short-range wireless communication method may include, for example, wireless fidelity (Wi-Fi) technology.

[0048] This application embodiment does not impose any limitation on the number of communication devices involved in the above system architecture. For example, the above system architecture may include more terminal devices, or fewer terminal devices, or other network devices. Figure 1 As shown, only terminal devices (101a, 101b) and server 102 are described as examples. The following is a brief introduction to each of the above communication devices and their respective functions.

[0049] A terminal device (101a, 101b) is a device that can provide voice and / or data connectivity to a user, and may be a device that supports wired and / or wireless connections.

[0050] For example, terminal devices (101a, 101b) may include, but are not limited to: mobile phones, tablets, laptops, handheld computers, mobile internet devices (MID), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminal devices in industrial control, wireless terminal devices in autonomous driving, wireless terminal devices in smart grids, wireless terminal devices in transportation safety, wireless terminal devices in smart cities, or wireless terminal devices in smart homes, etc.

[0051] In addition, the terminal devices (101a, 101b) can have related clients installed. These clients can be software, such as applications (APPs), browsers, short video software, web pages, mini programs, etc.

[0052] It should be noted that the terminal devices (101a, 101b) in this application embodiment can enable the client related to the BNS-based configuration check to send a configuration check request for the target service to the server 102 so as to perform subsequent method steps such as instance configuration check for at least one service instance of the target service.

[0053] Server 102 can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDN), and big data and artificial intelligence platforms.

[0054] It is worth mentioning that, in this embodiment of the application, server 102 can be used to respond to a configuration check request for a target service, obtain the BNS identifier set by BNS for the target service; then, based on the BNS identifier, obtain at least one configuration set of at least one service instance from the operation and maintenance platform associated with at least one service instance of the target service; wherein, each configuration set includes: instance configurations of at least one service instance on the corresponding operation and maintenance platform; further, based on the BNS identifier, at least one operation and maintenance platform and at least one configuration set, construct a configuration state graph; finally, perform configuration checks on the target service based on the configuration state graph and a preset set of standard configuration check rules; wherein, the set of standard configuration check rules includes: standard configuration check rules set separately for various instance configurations.

[0055] The following describes the BNS-based configuration checking method provided by the exemplary embodiments of this application in conjunction with the above-described system architecture and with reference to the accompanying drawings. It should be noted that the above-described system architecture is only shown for the purpose of understanding the spirit and principles of this application, and the embodiments of this application are not limited in any way in this respect.

[0056] See Figure 2 The diagram shown illustrates the implementation flow of a configuration check method based on BNS provided in this application. Taking a server as an example, the specific implementation flow of this method is as follows: S201: In response to a configuration check request for the target service, obtain the BNS identifier set by BNS for the target service.

[0057] The BNS identifier can be used to obtain the instance configuration of all service instances of the target service.

[0058] S202: Based on the BNS identifier, obtain at least one configuration set of at least one service instance from the operation and maintenance platform associated with at least one service instance of the target service.

[0059] For example, the operation and maintenance platform associated with at least one service instance of the target service may include, but is not limited to, any one or a combination of a monitoring platform (e.g., a Noah monitoring center for monitoring and alarm configuration), a deployment platform (e.g., a Noah service management platform for managing service instances and deployment information), and a resource management platform (e.g., a cloud management platform for managing infrastructure resources). This application embodiment does not specifically limit this. It is understood that instance configurations can be set for each service instance on each operation and maintenance platform.

[0060] Each configuration set may include: instance configurations for at least one service instance on its corresponding operations and maintenance platform. It should be noted that while the target service instance typically runs on the same operations and maintenance platform, other operations and maintenance platforms will still configure the target service instance to ensure its smooth operation.

[0061] Assume the target service has four service instances (e.g., Ser.instance.A, Ser.instance.B, Ser.instance.C, and Ser.instance.D), and the operation and maintenance platforms associated with these four service instances are a monitoring platform, a deployment platform, and a resource management platform. Then, based on the BNS identifier, the server can obtain three configuration sets for the four service instances from the monitoring platform, the deployment platform, and the resource management platform: Config.Set.a for the monitoring platform, Config.Set.b for the deployment platform, and Config.Set.c for the resource management platform.

[0062] Specifically, after receiving the service BNS identifier, the server's built-in intelligent scheduler will, based on predefined collection adapters, initiate precise queries synchronously or asynchronously to various independent operation and maintenance data sources (such as monitoring platforms, deployment platforms, and resource management platforms). Through this process, the server can efficiently retrieve full-dimensional instance configuration data, including monitoring metric thresholds, log collection paths, service instance lists, resource tags, deployment versions, capacity specifications, and more.

[0063] In one alternative implementation, see [link to relevant documentation]. Figure 3As shown, when executing step S202, the server can determine the instance configuration mapping (e.g., F.1 ~ FN) corresponding to at least one service instance (e.g., Ser.inst.1 ~ Ser.inst.N) based on the BNS identifier; then, it obtains the configuration data (e.g., Inst.Data.1 ~ Inst.Data.N) corresponding to at least one instance configuration mapping from the operation and maintenance data of at least one operation and maintenance platform; finally, it performs data cleaning and (format) standardization processing on at least one configuration data to obtain at least one configuration set (e.g., Config.Set.1 ~ Config.Set.N).

[0064] Therefore, it can be seen that all instance configurations (i.e., at least one set of configurations) related to the target service can be quickly obtained through BNS identifiers. Furthermore, by cleaning and standardizing the operation and maintenance data of different operation and maintenance platforms, the data volume can be reduced while eliminating the format differences of instance configurations of different operation and maintenance platforms, such as eliminating naming ambiguity.

[0065] S203: Construct a configuration status graph based on BNS identifiers, at least one operation and maintenance platform, and at least one configuration set.

[0066] In one alternative implementation, see [link to relevant documentation]. Figure 4 As shown, when executing step S203, the server can use the BNS identifier as the root node, at least one operation and maintenance platform as an intermediate child node (i.e., one operation and maintenance platform corresponds to one intermediate child node), and at least one instance configuration included in each of the at least one configuration set as leaf nodes, thereby constructing a configuration state graph based on the root node, at least one intermediate child node (i.e., intermediate child node 1 ~ intermediate child node n), multiple leaf nodes (e.g., intermediate child node 1 corresponds to leaf node 1.1 ~ leaf node 1.m1, intermediate child node n corresponds to leaf node n.1 ~ leaf node n.mn), and a preset instance configuration sorting.

[0067] Optionally, the aforementioned preset instance configuration sorting may include a predetermined sorting of instance configurations under different operation and maintenance platforms. Taking the example of a target service having four service instances (Ser.instance.A, Ser.instance.B, Ser.instance.C, and Ser.instance.D), if the instance configuration sorting of the aforementioned four service instances on the monitoring platform is 1, 20, 17, and 35 respectively, then the instance order of the aforementioned four service instances under the intermediate sub-node of the monitoring platform is: Ser.instance.A, Ser.instance.C, Ser.instance.B, and Ser.instance.D. It should be noted that the instance configuration sorting of the same service instance may be the same or different on different operation and maintenance platforms.

[0068] Of course, the order of instance configurations for any two service instances on different operation and maintenance platforms can be the same or different. For example, service instance 1 may have a higher instance configuration order on operation and maintenance platform 1 than service instance 2 on operation and maintenance platform 1, and service instance 1 may have a higher instance configuration order on operation and maintenance platform 2 than service instance 2 on operation and maintenance platform 2. Alternatively, service instance 1 may have a higher instance configuration order on operation and maintenance platform 1 than service instance 2 on operation and maintenance platform 1, while service instance 1 may have a lower instance configuration order on operation and maintenance platform 2.

[0069] Based on the methods described in steps S202-S203 above, after obtaining the raw data (i.e., operation and maintenance data), it is not simply piled up, but a key data fusion and knowledge construction process is executed. First, data from different sources is cleaned and standardized in format to eliminate naming ambiguity and format differences. Then, using the input BNS identifier as the unique root node and logical anchor point, and utilizing instance configurations such as service instance ID, host IP, and resource ID as intrinsic association keys, the cleaned data fragments are automatically and intelligently connected and integrated to generate a configuration state graph of the target service. It should be understood that the configuration state graph is a tree-like or graph-like structured data model dynamically generated in memory, which can clearly show the topological and state relationships between service instances and all their configuration attributes and associated resources.

[0070] Furthermore, the configuration status graph is a dynamic and queryable digital panoramic view of service configurations. It completely changes the inefficient way that traditional operations and maintenance personnel need to manually switch and piece together information between multiple operations and maintenance platforms. It transforms the originally isolated configuration information into a knowledge graph with inherent connections that machines can directly understand and process. Moreover, as an authoritative and real-time updated "data fact", it is seamlessly transmitted to the downstream rule engine, ensuring the integrity, accuracy and consistency of the information on which automated verification is based, and realizing a fundamental transformation from "manual verification" to "intelligent acceptance".

[0071] S204: Perform configuration checks on the target service based on the configuration state graph and a set of preset standard configuration check rules.

[0072] The standard configuration check rule set can include standard configuration check rules set separately for various instance configurations. For example, the standard configuration check rule set can include: a first standard configuration check rule, a second standard configuration check rule, and a third standard configuration check rule. The first standard configuration check rule is used to check monitoring and alarm configurations, the second standard configuration check rule is used to check log path specifications, and the third standard configuration check rule is used to check hierarchical release settings.

[0073] In one alternative implementation, when performing step S201, refer to... Figure 5 As shown, after the server constructs the configuration state graph, it can perform the following instance configuration checks on at least one service instance in accordance with the preset standard configuration check rules: S501: Based on instance configuration sorting and standard configuration check rule sorting of the standard configuration check rule set, determine the standard configuration check rules set separately for multiple instance configurations included in the configuration state graph.

[0074] It should be noted that the order of each standard configuration check rule in the standard configuration check rule sorting can be determined by a weighted sum of the instance configurations on each operation and maintenance platform.

[0075] Optionally, the weighting factors for different operation and maintenance platforms can be the same or different. The weighting factor of an operation and maintenance platform can be determined based on its contribution to the operation of the service instance. For example, if the first instance configuration is ranked 5th on the first operation and maintenance platform, 4th on the second operation and maintenance platform, and 8th on the third operation and maintenance platform, and the weighting factors of the three operation and maintenance platforms are 0.4, 0.2, and 0.4 respectively, then the order of the standard configuration check rules corresponding to the second instance configuration is 0.4×5 + 0.2×4 + 0.4×8 = 6.

[0076] In addition, if the order of the standard configuration check rules determined by the weighted summation of the instance configuration is not an integer, the order of the standard configuration check rules corresponding to the instance configuration can be determined in various ways, such as taking values ​​up, taking values ​​down, or rounding, to ensure that the order of the standard configuration check rules corresponding to the instance configuration is an integer.

[0077] In this way, by sorting according to instance configuration and standard configuration check rules, the position of the standard configuration check rules corresponding to multiple instance configurations in the standard configuration check rule set can be quickly located, which can improve the matching speed of standard configuration check rules and thus improve the efficiency of configuration checks on target services.

[0078] Furthermore, the standard configuration check rule set, as a flexibly configurable and extensible rule base, defines in a structured manner the various specifications and standards that service instance configurations must meet, such as the completeness of monitoring and alarm policies, the compliance of log file paths, and the correctness of resource tag formats. Thus, after receiving the configuration status graph, the engine automatically retrieves all check rules applicable to the target service from the standard configuration check rule set and drives the process of verifying the configurations of each instance of the target service according to a predetermined strategy (e.g., parallel or sequential).

[0079] S502: Based on the configuration constraints corresponding to multiple standard configuration check rules, perform configuration checks on multiple instance configurations, and use the instance check results of each instance configuration as the service check result of the target service.

[0080] In one alternative implementation, after determining the standard configuration check rules corresponding to the multiple instance configurations included in the configuration state graph, the server checks any one instance configuration among the multiple instance configurations, such as the first instance configuration, for example, see [link to relevant documentation]. Figure 6 As shown, the following operations can be performed: determine the first configuration constraint corresponding to the first instance configuration from multiple configuration constraints; then, when the first instance configuration meets the first configuration constraint, mark the first instance configuration as a compliant configuration, and generate an instance check result for the first instance configuration based on the compliance information of the first instance configuration; and when the first instance configuration does not meet the first configuration constraint, mark the first instance configuration as a non-compliant configuration, and generate an instance check result for the first instance configuration based on the non-compliant information of the first instance configuration.

[0081] The first configuration constraint is the expected standard set for the first instance configuration. For example, the first configuration constraint can take the form of a threshold range, a regular expression pattern, or a list of required fields. Of course, the first configuration constraint can also perform more complex logical operations and state inferences on the first instance configuration, but this embodiment does not limit this.

[0082] Based on the instance configuration check methods described in steps S501-S502 above, the instance configurations of interest to the rules are accurately located and extracted from the configuration status graph, such as real-time data like specific alarm parameters or tag key-value pairs. Subsequently, the server compares the real-time data with the expected standards defined in the standard configuration check rules, or performs more complex logical operations and status inferences. The entire process is fully automated and requires no manual intervention. Finally, a clear judgment of "compliant" or "non-compliant" is output for each instance configuration, and specific compliance or non-compliance information is captured.

[0083] Furthermore, after verifying the configurations of multiple instances, the server can systematically summarize and integrate the inspection results. For example, it can generate a structured and highly readable inspection result report (i.e., the service inspection results of the target service). This report clearly lists the items, descriptions, and results of each inspection (e.g., compliant / non-compliant (or pass / fail)) and specific details of failed items (e.g., the difference between actual and expected configuration values). This inspection result report accurately identifies all deviations between instance configurations and standard specifications, providing direct and objective evidence for subsequent problem analysis and handling. It is a key link in achieving a closed loop from "problem discovery" to "guided repair."

[0084] In one optional implementation, after the server performs configuration checks on multiple instance configurations based on the configuration constraints corresponding to multiple standard configuration check rules, it can further obtain at least one instance check result from the multiple instance check results that indicates the instance configuration is non-compliant. For any one of these at least one instance check results, such as the check result corresponding to the second instance configuration (i.e., the second instance configuration check result), the following operations can be performed: A root cause analysis of the non-compliance of the second instance configuration is conducted based on the second instance check result to obtain the fundamental non-compliance reasons and potential non-compliance reasons. Next, a configuration modification strategy for the second instance configuration is generated based on the fundamental and potential non-compliance reasons, and the second instance configuration is modified according to the configuration modification strategy to obtain the modified second instance configuration. Finally, a performance test is performed on the modified second instance configuration based on the second configuration constraints corresponding to the second instance configuration to obtain the performance test results. The aforementioned performance test results can characterize whether the modified second instance configuration meets the second configuration constraints.

[0085] In this way, the server can not only parse and classify the inspection result reports, but also perform logical diagnosis on all inspection items (i.e., service instances) marked as "failed" or "non-compliant". Combining the standard configuration inspection rule set and historical problem analysis, it analyzes the root cause and potential impact of each configuration problem, and automatically generates specific, step-by-step repair guidelines or configuration modification examples, i.e., configuration modification strategies. For example, for the non-compliant instance configuration of "Central Processing Unit (CPU) utilization alarm not configured", it not only points out the missing information, but also suggests specific monitoring indicators, recommended thresholds, and configuration operation paths, making the repair suggestions directly actionable.

[0086] If the modified second instance configuration still does not meet the second configuration constraints, further adjustments or modifications can be made to the modified second instance configuration. Therefore, in one optional implementation, when the performance test results indicate that the modified second instance configuration does not meet the second configuration constraints, the server sends a configuration modification request to the terminal device, so that the terminal device can display the instance modification interface to the operations and maintenance personnel. The aforementioned instance modification interface can at least be used to display the modified second instance configuration and its corresponding performance test results. In this way, instance configurations that fail verification or generate disputes can be escalated to operations and maintenance personnel (e.g., site reliability engineers, SREs) for arbitration according to a preset process. Every step of the process, including status changes, operation records, and final conclusions, is fully preserved, forming a traceable closed loop from problem discovery, push notifications, repair to verification, achieving standardized, transparent, and efficient management of operations and maintenance acceptance work. Furthermore, instance configurations that pass verification can be synchronized to the relevant operations and maintenance platform.

[0087] Based on the above methods, the problems found during inspections can be intelligently attributed, specific repair suggestions can be generated, and the responsible persons can be automatically associated, tracking work orders can be created, and repair tasks can be pushed, until automatic verification is triggered, forming a complete closed loop from "discovering problems" to "solving problems", eliminating the pain points of manual tracking being prone to loss and difficult to hold accountable.

[0088] In summary, in the BNS-based configuration checking method provided in this application embodiment, in response to a configuration checking request for a target service, the BNS identifier set by the BNS for the target service is obtained; then, based on the BNS identifier, at least one configuration set of at least one service instance is obtained from the operation and maintenance platform associated with at least one service instance of the target service; wherein, each configuration set includes: instance configurations of at least one service instance on the corresponding operation and maintenance platform; further, a configuration state graph is constructed based on the BNS identifier, at least one operation and maintenance platform, and at least one configuration set; finally, the configuration of the target service is checked based on the configuration state graph and a preset set of standard configuration checking rules; wherein, the set of standard configuration checking rules includes: standard configuration checking rules set separately for various instance configurations.

[0089] This approach, by generating a comprehensive and structured configuration state graph, completely transforms the inefficient traditional method of manually piecing together information across platforms. Furthermore, based on the configuration state graph and a pre-defined set of standard configuration check rules, it performs full-scale automatic comparison and diagnosis. This not only efficiently checks the configurations of all service instances of the target service but also understands the logical relationships between instance configurations, achieving in-depth analysis beyond simple compliance checks. Therefore, it improves the efficiency and accuracy of configuration checks while reducing operational costs.

[0090] Furthermore, based on the same technical concept, embodiments of this application also provide a BNS-based configuration checking device, which is used to implement the above-described method flow of embodiments of this application. For example, see [link to relevant documentation]. Figure 7 As shown, the BNS-based configuration checking device 700 may include: a first acquisition module 701, a second acquisition module 702, a map construction module 703, and a configuration checking module 704, wherein: The first acquisition module 701 is used to obtain the BNS identifier set by BNS for the target service in response to a configuration check request for the target service. The second acquisition module 702 is used to acquire at least one configuration set of at least one service instance from the operation and maintenance platform associated with at least one service instance of the target service based on the BNS identifier; wherein each configuration set includes: instance configuration of at least one service instance on the corresponding operation and maintenance platform; The graph construction module 703 is used to construct a configuration status graph based on BNS identifiers, at least one operation and maintenance platform, and at least one configuration set. The configuration check module 704 is used to perform configuration checks on the target service based on the configuration status graph and a preset set of standard configuration check rules; wherein, the set of standard configuration check rules includes: standard configuration check rules set separately for various instance configurations.

[0091] In an optional embodiment, when obtaining at least one configuration set of at least one service instance from the operation and maintenance platform associated with at least one service instance of the target service based on the BNS identifier, the second acquisition module 702 is specifically used for: Based on the BNS identifier, determine the instance configuration mapping corresponding to at least one service instance; Obtain configuration data corresponding to at least one instance configuration mapping from the operation and maintenance data of at least one operation and maintenance platform; Perform data cleaning and standardization on at least one configuration data set to obtain at least one configuration set.

[0092] In an optional embodiment, when constructing a configuration status graph based on BNS identifiers, at least one operation and maintenance platform, and at least one configuration set, the graph construction module 703 is specifically used for: The BNS identifier is used as the root node, at least one operation and maintenance platform is used as the intermediate child node, and at least one instance configuration included in each of the at least one configuration set is used as the leaf node. A configuration state graph is constructed based on the root node, at least one intermediate child node, multiple leaf nodes, and a preset instance configuration sorting.

[0093] In an optional embodiment, when performing configuration checks on the target service based on the configuration state graph and a preset set of standard configuration check rules, the configuration check module 704 is specifically used for: Based on the instance configuration sorting and the standard configuration check rule sorting of the standard configuration check rule set, the standard configuration check rules are determined for the multiple instance configurations included in the configuration state graph. Configuration checks are performed on multiple instance configurations based on the configuration constraints corresponding to multiple standard configuration check rules, and the instance check results of each instance configuration are used as the service check results of the target service.

[0094] In an optional embodiment, when performing configuration checks on multiple instance configurations based on configuration constraints corresponding to multiple standard configuration check rules, the configuration check module 704 is specifically used for: For multiple instance configurations, perform the following operations respectively: From multiple configuration constraints, determine the first configuration constraint corresponding to the first instance configuration; wherein, the first instance configuration is any one of the multiple instance configurations; When the first instance configuration meets the first configuration constraints, the first instance configuration is marked as a compliant configuration, and an instance check result for the first instance configuration is generated based on the compliance information of the first instance configuration. When the first instance configuration does not meet the first configuration constraints, the first instance configuration is marked as non-compliant, and an instance check result of the first instance configuration is generated based on the non-compliant information of the first instance configuration.

[0095] In an optional embodiment, after performing configuration checks on multiple instance configurations based on configuration constraints corresponding to multiple standard configuration check rules, the configuration check module 704 is further configured to: From multiple instance inspection results, obtain at least one instance inspection result that indicates the instance configuration is non-compliant; For at least one instance check result, perform the following operations respectively: Based on the second instance inspection results corresponding to the second instance configuration, a non-compliance root cause analysis is performed on the second instance configuration to obtain the fundamental non-compliance reasons and potential non-compliance reasons of the second instance configuration; wherein, the second instance inspection result is any one of at least one instance inspection result; A configuration modification strategy for the second instance configuration is generated based on the fundamental non-compliance reasons and potential non-compliance reasons. The second instance configuration is then modified based on the configuration modification strategy to obtain the modified second instance configuration. Based on the second configuration constraints corresponding to the second instance configuration, a performance test is performed on the modified second instance configuration to obtain the performance test results; wherein, the performance test results indicate whether the modified second instance configuration meets the second configuration constraints.

[0096] In an optional embodiment, the configuration check module 704 is further configured to: If the performance test results indicate that the modified second instance configuration does not meet the second configuration constraints, a configuration modification request is sent to the terminal device so that the terminal device can display the instance modification interface to the operation and maintenance personnel; the instance modification interface is used to display at least the modified second instance configuration and its corresponding performance test results.

[0097] Based on the description of the method and apparatus embodiments above, an exemplary embodiment of the present invention also provides an electronic device, including: at least one processor; and a memory communicatively connected to the at least one processor. The memory stores a computer program executable by the at least one processor, which, when executed by the at least one processor, causes the electronic device to perform the method according to an embodiment of the present invention.

[0098] This application also provides a non-transitory computer-readable storage medium storing a computer program, wherein the computer program, when executed by a computer's processor, is used to cause the computer to perform a method according to an embodiment of this application.

[0099] This application also provides a computer program product, including a computer program, wherein the computer program, when executed by a computer's processor, is used to cause the computer to perform a method according to an embodiment of this application.

[0100] See Figure 8 The diagram shown below illustrates the structure of an electronic device 800 that can serve as a server or client in this application, and is an example of a hardware device that can be applied to various aspects of this application. The electronic device is intended to represent various forms of digital electronic computer devices, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the application described and / or claimed herein.

[0101] like Figure 8 As shown, the electronic device 800 includes a computing unit 801, which can perform various appropriate actions and processes based on a computer program stored in a read-only memory (ROM) 802 or a computer program loaded from a storage unit 808 into a random access memory (RAM) 803. The RAM 803 may also store various programs and data required for the operation of the device 800. The computing unit 801, ROM 802, and RAM 803 are interconnected via a bus 804. An input / output (I / O) interface 805 is also connected to the bus 804.

[0102] Multiple components in electronic device 800 are connected to I / O interface 805, including: input unit 806, output unit 807, storage unit 808, and communication unit 809. Input unit 806 can be any type of device capable of inputting information to electronic device 800. Input unit 806 can receive input digital or character information and generate key signal inputs related to user settings and / or function control of electronic device. Output unit 807 can be any type of device capable of presenting information and may include, but is not limited to, a display, speaker, video / audio output terminal, vibrator, and / or printer. Storage unit 808 may include, but is not limited to, disks and optical discs. Communication unit 809 allows electronic device 800 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks, and may include, but is not limited to, modems, network cards, infrared communication devices, wireless communication transceivers and / or chipsets, such as Bluetooth devices, WiFi devices, worldwide interoperability for microwave access (WiMax) devices, cellular communication devices, and / or the like.

[0103] The computing unit 801 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of the computing unit 801 include, but are not limited to, CPUs, graphics processing units (GPUs), various artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, digital signal processors (DSPs), and any suitable processors, controllers, microcontrollers, etc. The computing unit 801 performs the various methods and processes described above.

[0104] For example, in some embodiments, the BNS-based configuration checking method described above can be implemented as a computer software program tangibly contained in a machine-readable medium, such as storage unit 808. In some embodiments, part or all of the computer program can be loaded and / or installed on electronic device 800 via ROM 802 and / or communication unit 809. In some embodiments, computing unit 801 can be configured to perform the BNS-based configuration checking method described above by any other suitable means (e.g., by means of firmware).

[0105] The program code used to implement the methods of this application may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing device, such that when executed by the processor or controller, the functions / operations specified in the flowcharts and / or block diagrams are implemented. The program code may be executed entirely on a machine, partially on a machine, as a standalone software package partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0106] In the context of this application, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, RAM, ROM, erasable programmable read-only memory (EPROM) or flash memory, optical fibers, compact disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0107] As used in this application, the terms "machine-readable medium" and "computer-readable medium" refer to any computer program product, device, and / or apparatus (e.g., disk, optical disk, memory, programmable logic device, PLD) used to provide machine instructions and / or data to a programmable processor, including machine-readable media that receive machine instructions as machine-readable signals. The term "machine-readable signal" refers to any signal used to provide machine instructions and / or data to a programmable processor.

[0108] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device for displaying information to the user (e.g., a cathode ray tube (CRT) or liquid crystal display (LCD) monitor); and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the computer. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0109] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or computing systems that include middleware components (e.g., application servers), or computing systems that include frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), and the Internet.

[0110] Computer systems can include clients and servers. Clients and servers are generally located far apart and typically interact through communication networks. Client-server relationships are created by computer programs running on the respective computers and having a client-server relationship with each other.

[0111] Furthermore, it should be understood that the above-disclosed embodiments are merely preferred embodiments of this application and should not be construed as limiting the scope of the invention. Therefore, any equivalent variations made in accordance with the claims of this invention are still within the scope of this application.

Claims

1. A configuration checking method based on Baidu Name Service (BNS), characterized in that, include: In response to a configuration check request for a target service, obtain the BNS identifier set by BNS for the target service; Based on the BNS identifier, at least one configuration set of the at least one service instance is obtained from the operation and maintenance platform associated with at least one service instance of the target service; wherein, each configuration set includes: the instance configuration of the at least one service instance on the corresponding operation and maintenance platform; Based on the BNS identifier, at least one operation and maintenance platform, and at least one configuration set, a configuration status graph is constructed. The target service is configured based on the configuration status graph and a set of preset standard configuration check rules; wherein, the set of standard configuration check rules includes standard configuration check rules set separately for various instance configurations.

2. The method as described in claim 1, characterized in that, The step of obtaining at least one configuration set of the at least one service instance from the operation and maintenance platform associated with at least one service instance of the target service based on the BNS identifier includes: Based on the BNS identifier, determine the instance configuration mapping corresponding to each of the at least one service instance; From the operation and maintenance data of each of the at least one operation and maintenance platform, obtain the configuration data corresponding to at least one instance configuration mapping respectively; At least one set of configuration data is cleaned and standardized to obtain the at least one set of configuration data.

3. The method as described in claim 1, characterized in that, The construction of a configuration state graph based on the BNS identifier, at least one operation and maintenance platform, and at least one configuration set includes: The BNS identifier is used as the root node, the at least one operation and maintenance platform is used as the intermediate child node, and the at least one instance configuration included in each of the at least one configuration set is used as the leaf node. The configuration state graph is constructed based on the root node, at least one intermediate child node, multiple leaf nodes, and a preset instance configuration sort.

4. The method as described in claim 3, characterized in that, The configuration check of the target service based on the configuration state graph and a preset set of standard configuration check rules includes: Based on the instance configuration sorting and the standard configuration check rule sorting of the standard configuration check rule set, standard configuration check rules are determined for each of the multiple instance configurations included in the configuration state graph. Configuration checks are performed on the configurations of the multiple instances based on the configuration constraints corresponding to the multiple standard configuration check rules, and the instance check results of the multiple instance configurations are used as the service check results of the target service.

5. The method as described in claim 4, characterized in that, The configuration check of the multiple instance configurations based on the configuration constraints corresponding to multiple standard configuration check rules includes: For each of the aforementioned instance configurations, perform the following operations: From the plurality of configuration constraints, a first configuration constraint corresponding to the first instance configuration is determined; wherein, the first instance configuration is any one of the plurality of instance configurations; When the first instance configuration meets the first configuration constraints, the first instance configuration is marked as a compliant configuration, and an instance check result of the first instance configuration is generated based on the compliance information of the first instance configuration. If the first instance configuration does not meet the first configuration constraints, the first instance configuration is marked as non-compliant, and an instance check result of the first instance configuration is generated based on the non-compliant information of the first instance configuration.

6. The method as described in claim 5, characterized in that, After performing configuration checks on the configurations of the multiple instance instances based on the configuration constraints corresponding to the multiple standard configuration check rules, the process further includes: From multiple instance inspection results, obtain at least one instance inspection result that indicates the instance configuration is non-compliant; For each of the at least one instance inspection results, perform the following operations respectively: Based on the second instance inspection results corresponding to the second instance configuration, a non-compliance root cause analysis is performed on the second instance configuration to obtain the fundamental non-compliance reasons and potential non-compliance reasons of the second instance configuration; wherein, the second instance inspection result is any one of the at least one instance inspection results; A configuration modification strategy for the second instance configuration is generated based on the fundamental non-compliance reasons and the potential non-compliance reasons, and the second instance configuration is modified based on the configuration modification strategy to obtain the modified second instance configuration; Based on the second configuration constraints corresponding to the second instance configuration, a performance test is performed on the modified second instance configuration to obtain a performance test result; wherein, the performance test result indicates whether the modified second instance configuration satisfies the second configuration constraints.

7. The method as described in claim 6, characterized in that, The method further includes: When the performance test results indicate that the modified second instance configuration does not meet the second configuration constraints, a configuration modification request is sent to the terminal device so that the terminal device can display the instance modification interface to the operation and maintenance personnel; the instance modification interface is at least used to display the modified second instance configuration and its corresponding performance test results.

8. A configuration checking device based on BNS, characterized in that, include: The first acquisition module is used to acquire the BNS identifier set by BNS for the target service in response to a configuration check request for the target service. The second acquisition module is used to acquire at least one configuration set of the at least one service instance from the operation and maintenance platform associated with at least one service instance of the target service based on the BNS identifier; wherein each configuration set includes: the instance configuration of the at least one service instance on the corresponding operation and maintenance platform; The graph construction module is used to construct a configuration status graph based on the BNS identifier, at least one operation and maintenance platform, and at least one configuration set; The configuration check module is used to perform configuration checks on the target service based on the configuration status graph and a preset set of standard configuration check rules; wherein, the set of standard configuration check rules includes: standard configuration check rules set separately for various instance configurations.

9. An electronic device, characterized in that, include: processor; A memory storing a program; wherein the program includes instructions that, when executed by the processor, cause the processor to perform the method as described in any one of claims 1-7.

10. A non-transitory computer-readable storage medium storing computer instructions, wherein, The computer instructions are used to cause the computer to perform the method as described in any one of claims 1-7.

Images