Automatic detection methods, devices, storage media, and equipment for microservice configuration conflicts

By analyzing the microservice configuration network using a breadth-first search algorithm and quantized rules, and combining topology dependency knowledge graphs and time-series logs, the problem of missed and false detections of cross-service configuration linkage conflicts in existing technologies is solved. This achieves efficient and accurate configuration conflict detection and risk tracing, ensuring the safe and stable operation of the microservice cluster.

CN123074931APending Publication Date: 2026-11-10FOSHAN GUOXIN TECHNOLOGY IND CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611156374.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-07-31
Publication Date
2026-11-10

AI Technical Summary

Technical Problem

Existing microservice configuration detection technologies struggle to accurately capture cross-service configuration conflicts, resulting in missed and false detections. Furthermore, they cannot achieve risk tracing and source localization, leading to low efficiency and poor targeting in configuration conflict detection, which fails to meet the security management needs of large-scale microservice clusters.

Method used

The algorithm employs breadth-first search and quantitative rule analysis to analyze cross-service associated configuration networks, calculates comprehensive conflict scores, and combines topology dependency knowledge graphs and time-series logs to achieve global risk quantification and classification and refined conflict detection, generating structured detection results.

Benefits of technology

It improves the comprehensiveness, accuracy and efficiency of microservice configuration conflict detection, ensures the safe and stable operation of cluster configuration, and can fully identify various configuration anomalies and generate detailed conflict information.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123074931A_ABST
    Figure CN123074931A_ABST
Patent Text Reader

Abstract

This invention relates to the field of microservice configuration detection technology, and particularly to a method, apparatus, storage medium, and device for automatic microservice configuration conflict detection. It analyzes cross-service associated configuration networks based on a preset breadth-first search algorithm and preset quantification rules to obtain a comprehensive conflict score; it performs conflict detection on the cross-service associated configuration networks based on the comprehensive conflict score and preset conflict judgment conditions to obtain multiple conflict occurrence times; and it generates microservice configuration conflict detection results based on the comprehensive conflict score and each configuration conflict information. By using breadth-first search to traverse cross-service configuration networks and quantify and classify risks, and combining topology detection and time-series log correlation to trace the causal links of configuration changes, it relies on algorithms to complete refined conflict verification, which can identify hidden cross-service configuration anomalies and improve the accuracy of microservice configuration conflict detection and system operational stability.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of microservice configuration detection technology, and in particular to a method, apparatus, storage medium and device for automatic detection of microservice configuration conflicts. Background Technology

[0002] With the widespread adoption of cloud-native and microservice architectures, the number of microservices, the scale of configuration items, and service dependencies within clusters are growing exponentially, making cross-service configuration linkage scenarios increasingly complex. Most existing microservice configuration conflict detection technologies employ static, single-point comparison methods, performing compliance checks only on a single service configuration. They lack the ability to analyze the overall cross-service topology. Furthermore, existing detection methods struggle to accurately capture implicit temporal linkage conflicts such as incompatible upstream and downstream parameters, overlapping routes, and resource contention, resulting in widespread missed and false detections. Moreover, existing technologies cannot achieve a combination of risk temporal tracing and localization, leading to low conflict resolution efficiency and poor targeting, failing to meet the practical needs of large-scale microservice cluster configuration security management and proactive fault avoidance. Summary of the Invention

[0003] In order to overcome the shortcomings of the prior art, the purpose of this invention is to provide a method, apparatus, storage medium and device for automatic detection of microservice configuration conflicts.

[0004] The automatic microservice configuration conflict detection method includes: obtaining the cross-service related configuration network from the configuration center, and analyzing the cross-service related configuration network according to a preset breadth-first search algorithm and preset quantization rules to obtain a comprehensive conflict score; performing conflict detection on the cross-service related configuration network according to the comprehensive conflict score and preset conflict judgment conditions to obtain multiple conflict occurrence times; obtaining the location target event, parent event identifier, and configuration time sequence log; performing conflict detection on the configuration time sequence log according to the location target event, parent event identifier, preset conflict detection algorithm, and each conflict occurrence time to obtain multiple configuration conflict information; and generating a microservice configuration conflict detection result based on the comprehensive conflict score and each configuration conflict information.

[0005] Furthermore, the step of analyzing the cross-service associated configuration network according to a preset breadth-first search algorithm and preset quantization rules to obtain a comprehensive conflict score includes: analyzing the cross-service associated configuration network according to the breadth-first search algorithm to obtain a set of microservice nodes; obtaining the node business priority of each microservice node in the set of microservice nodes to obtain a set of node business priorities; obtaining the number of affected instances of each microservice node in the set of microservice nodes to obtain a total number of instances; and quantifying and scoring the set of node business priorities and the total number of instances according to the quantization rules to obtain a comprehensive conflict score.

[0006] Furthermore, the step of performing conflict detection on the cross-service associated configuration network based on the comprehensive conflict score and preset conflict determination conditions to obtain multiple conflict occurrence times includes: determining whether the comprehensive conflict score is greater than a preset conflict score threshold; if the comprehensive conflict score is greater than the conflict score threshold, then analyzing the cross-service associated configuration network according to a preset breadth-first search algorithm to obtain the call relationship characteristics between nodes; constructing a microservice topology dependency knowledge graph based on a preset set of node business priorities, a set of microservice nodes, and the call relationship characteristics between nodes; and performing node detection on the microservice topology dependency knowledge graph according to a preset traversal analysis method and conflict determination conditions to obtain multiple conflict occurrence times.

[0007] Furthermore, the step of performing conflict detection on the configuration timing log based on the location target event, parent event identifier, preset conflict detection algorithm, and the time of each conflict occurrence to obtain multiple configuration conflict information includes: analyzing the configuration timing log based on a preset vector clock offset determination algorithm, a preset timing detection window, the location target event, and the parent event identifier to obtain multiple change events; and performing conflict detection on each change event based on the conflict detection algorithm and the time of each conflict occurrence to obtain multiple configuration conflict information.

[0008] Furthermore, the step of analyzing the configuration timing log based on a preset vector clock partial order determination algorithm, a preset timing detection window, a location target event, and a parent event identifier to obtain multiple change events includes: analyzing the configuration timing log based on the vector clock partial order determination algorithm, a parent event identifier, and a location target event to obtain a configuration change chain; and performing source tracing analysis on the configuration change chain based on the timing detection window and a preset basic backtracking duration to obtain multiple change events.

[0009] Furthermore, the conflict detection is performed on each change event according to the conflict detection algorithm and the time of each conflict occurrence to obtain multiple configuration conflict information, including: collecting all existing configuration data and service operation related data in the configuration center; constructing a baseline snapshot based on the all existing configuration data and service operation related data; and performing conflict detection on the baseline snapshot and each change event according to the conflict detection algorithm and the time of each conflict occurrence to obtain multiple configuration conflict information.

[0010] Furthermore, the step of generating microservice configuration conflict detection results based on the comprehensive conflict score and each configuration conflict information includes: classifying each configuration conflict information into categories according to a preset conflict classification rule base to obtain configuration coverage conflict categories, port routing conflict categories, and resource overrun conflict categories; and generating microservice configuration conflict detection results based on the comprehensive conflict score, configuration coverage conflict categories, port routing conflict categories, and resource overrun conflict categories.

[0011] Furthermore, the microservice configuration conflict automatic detection device includes: an analysis module, used to acquire the cross-service related configuration network of the configuration center, and analyze the cross-service related configuration network according to a preset breadth-first search algorithm and preset quantization rules to obtain a comprehensive conflict score; a first detection module, used to perform conflict detection on the cross-service related configuration network according to the comprehensive conflict score and preset conflict judgment conditions to obtain multiple conflict occurrence times; a data acquisition module, used to acquire the location target event, parent event identifier, and configuration time sequence log; a second conflict detection module, used to perform conflict detection on the configuration time sequence log according to the location target event, parent event identifier, preset conflict detection algorithm, and each conflict occurrence time to obtain multiple configuration conflict information; and a result generation module, used to generate microservice configuration conflict detection results according to the comprehensive conflict score and each configuration conflict information.

[0012] Furthermore, a microservice configuration conflict automatic detection device includes: a memory and at least one processor, wherein the memory stores instructions; at least one processor invokes the instructions in the memory to cause the microservice configuration conflict automatic detection device to perform the steps of the microservice configuration conflict automatic detection method as described in any one of the above descriptions.

[0013] In this invention, the technical solution traverses the cross-service associated configuration network using a breadth-first search algorithm, calculates a comprehensive conflict score by combining business priority and instance scale as dual-dimensional quantitative rules, and achieves global quantitative classification of configuration conflict risk. It completes topology layer risk detection through multi-dimensional conflict judgment conditions, estimates the time of conflict occurrence, and constructs a correlation mapping relationship between topology risk and time-series logs. This solution integrates the location of target events, parent event identifiers, and configuration time-series logs to sort out the causal chain of configuration changes, completes refined conflict verification based on conflict detection algorithms, comprehensively identifies various configuration anomalies, and generates structured conflict information. Finally, it integrates the global risk score and detailed conflict data to generate detection results, taking into account both overall risk rating and single-point fault location. This effectively solves the problems of missing time-series tracing and missed detection of implicit cross-service conflicts in traditional configuration detection methods, improving the comprehensiveness, accuracy, and efficiency of distributed microservice configuration conflict detection, and ensuring the safe and stable operation of cluster configuration. Attached Figure Description

[0014] The above and / or additional aspects and advantages of the present invention will become apparent and readily understood from the description of the embodiments taken in conjunction with the following drawings, in which: Figure 1 A flowchart of the microservice configuration conflict automatic detection method provided in this embodiment of the invention; Figure 2 This is a schematic diagram of the structure of the microservice configuration conflict automatic detection device provided in an embodiment of the present invention; Figure 3 This is a schematic diagram of the structure of the microservice configuration conflict automatic detection device provided in an embodiment of the present invention. Detailed Implementation

[0015] The terms "first," "second," "third," "fourth," etc. (if present) in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" or "having" and any variations thereof are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0016] For ease of understanding, the specific process of the embodiments of the present invention is described below. Please refer to [link / reference]. Figure 1 One embodiment of the microservice configuration conflict automatic detection method in this invention includes: 101. Obtain the cross-service associated configuration network of the configuration center, and analyze the cross-service associated configuration network according to the preset breadth-first search algorithm and preset quantification rules to obtain a comprehensive conflict score; In this embodiment, the cross-service associated configuration network integrates all microservice nodes, configuration sharing relationships, and service call dependency links, fully presenting the configuration linkage relationships within the cluster. A breadth-first search algorithm is used to traverse the network topology layer by layer, completely collecting information on all associated microservice nodes, avoiding the shortcomings of depth-first traversal, which is prone to missing branch links and getting stuck in local loops. Pre-defined quantitative rules integrate two types of evaluation indicators: node business priority weight and affected instance scale. Weighted calculations are performed based on the node data collected during the traversal to quantitatively assess the overall conflict risk level of the configuration network and output a comprehensive conflict score. The comprehensive conflict score can intuitively represent the degree of harm and scope of impact of potential conflicts, serving as a quantitative benchmark for subsequent graded detection. 102. Based on the comprehensive conflict score and the preset conflict judgment conditions, perform conflict detection on the cross-service associated configuration network to obtain multiple conflict occurrence times; In this embodiment, the comprehensive conflict score reflects the global risk level of the configured network. The preset conflict judgment conditions include multi-dimensional verification criteria such as configuration mutual exclusion, resource exclusivity, routing compatibility, and upstream and downstream parameter transmission constraints. The comprehensive conflict score is compared with the risk threshold to achieve risk classification. Full-domain detection is carried out along the service-dependent links for high-risk areas to identify service links with potential linkage conflicts. The potential time interval corresponding to each risk link is calculated by combining the configuration change timing constraints, and multiple conflict occurrence times are summarized. The conflict occurrence time is used as the timing tracing anchor point to establish the correlation between topology risks and timing logs. 103. Obtain the location target event, parent event identifier, and configuration timing log; In this embodiment, the target event is identified as an abnormal configuration event locked by the operations and maintenance personnel, which serves as the starting point for tracing the source. The parent event identifier records the predecessor and successor relationships between configuration change events. The configuration time-series log continuously records all configuration distribution, modification, and activation operations of the microservice. The system synchronously collects the above three types of data, providing complete original materials for distinguishing the causal relationship of events and conducting time-series conflict tracing in a distributed scenario, thus eliminating the problem of a broken tracing chain caused by a single data source. 104. Based on the location target event, parent event identifier, preset conflict detection algorithm, and the time of each conflict occurrence, perform conflict detection on the configuration time sequence log to obtain multiple configuration conflict information; In this embodiment, the target event is used as the source tracing anchor. The causal chain of configuration changes is sorted out by combining the parent event identifier, and the effective retrieval interval is locked based on the time of each conflict. The conflict detection algorithm is used to compare the change events in the chain with the cluster operation baseline at the corresponding time item by item to identify anomalies such as configuration overlay, port preemption, resource overrun, and route overlap. Once a configuration change that violates the operation constraints is detected, the conflict location, associated microservice, conflict type, conflict occurrence time and other elements are recorded and multiple configuration conflict information are generated. The configuration conflict information carries a detailed list of anomalies and provides structured data for the final result encapsulation. 105. Generate microservice configuration conflict detection results based on the overall conflict score and various configuration conflict information; In this embodiment, the comprehensive conflict score provides a global risk quantification rating, and each configuration conflict information carries detailed anomaly data for each conflict. The system structurally integrates global risk indicators and detailed conflict information, associating multiple dimensions such as risk level, conflict type, involved services, and occurrence sequence, and uniformly encapsulates them to form microservice configuration conflict detection results. The detection results take into account both overall risk assessment and single-point conflict details, making it easier for operation and maintenance personnel to grasp the overall risk level, locate various configuration anomalies, and support subsequent fault classification, configuration rectification, and change rollback operations. In this embodiment, a breadth-first search algorithm is used to traverse the cross-service associated configuration network. A comprehensive conflict score is calculated using dual-dimensional quantitative rules based on business priority and instance size, achieving global quantitative classification of configuration conflict risks. Topology-level risk detection is completed through multi-dimensional conflict judgment conditions, the timing of conflict occurrence is estimated, and a mapping relationship between topology risks and time-series logs is constructed. This solution integrates the location of target events, parent event identifiers, and configuration time-series logs to trace the causal chain of configuration changes. Fine-grained conflict verification is performed using conflict detection algorithms, comprehensively identifying various configuration anomalies and generating structured conflict information. Finally, the global risk score and detailed conflict data are merged to generate detection results, balancing overall risk rating and single-point fault location. This effectively solves the problems of missing time-series tracing and missed detection of implicit cross-service conflicts in traditional configuration detection methods, improving the comprehensiveness, accuracy, and efficiency of distributed microservice configuration conflict detection, and ensuring the safe and stable operation of cluster configuration.

[0017] The second embodiment of the microservice configuration conflict automatic detection method in this invention includes: 201. Analyze the cross-service associated configuration network using the breadth-first search algorithm to obtain the set of microservice nodes; In this embodiment, the cross-service associated configuration network is composed of various microservices within the configuration center, inter-service dependencies, and configuration reference links. A breadth-first search algorithm is used to traverse the topology network layer by layer from the starting node, expanding the search along configuration associations and call dependency links to avoid the local loop omission problem that is prone to occur in depth-first traversal. During the traversal, all independent microservice entity nodes in the network are identified, duplicate nodes and invalid dummy nodes are removed, and a complete set of microservice nodes is formed. This set of microservice nodes completely covers all service objects that may be affected by configuration changes, providing a basic topology data source for subsequent extraction of business priorities and statistics on the scale of affected instances. 202. Obtain the node business priority of each microservice node in the microservice node set to obtain the node business priority set; In this embodiment, microservice nodes are pre-configured with corresponding node business priorities. The node business priorities are set according to the importance of the services they carry. Core link transaction services and basic middleware services correspond to high priorities, while auxiliary statistics and offline task services correspond to lower priorities. The set of microservice nodes is traversed, and the predefined node business priority parameters of each microservice node are read one by one. All priority parameters are collected to form a node business priority set. The node business priority set quantifies the importance level of each service in the business link and is used for subsequent conflict risk weighting calculation to realize a differentiated evaluation logic with higher service conflict risk weight. 203. Obtain the number of affected instances for each microservice node in the microservice node set to get the total number of instances; In this embodiment, the number of affected instances represents the scale of microservice deployment instances that may experience operational anomalies after a configuration conflict occurs. The set of microservice nodes is traversed, and the number of currently running instances in the cluster for each microservice node is queried. The total number of affected instances for all nodes is summed to obtain the total number of instances. The total number of instances measures the scope of the impact of the configuration conflict from the perspective of deployment scale. The larger the total number of instances, the more running instances will be affected once the conflict is triggered, and the wider the scope of the fault propagation. The total number of instances is used as a key scale factor for quantitative scoring, forming a two-way evaluation dimension with business priority. 204. Quantify and score the node business priority set and the total number of instances according to the quantification rules to obtain a comprehensive conflict score; In this embodiment, the preset quantification rules incorporate a weighted calculation model, and simultaneously integrate the dimensions of business importance and cluster deployment scale for comprehensive evaluation. The calculation logic of the quantification rules is as follows: based on the set of node business priorities, different microservices are assigned corresponding weight coefficients, and the impact range of the fault represented by the total number of instances is used for weighted calculation, and a unified comprehensive conflict score is output. The comprehensive conflict score can intuitively quantify the overall risk level of potential conflicts in the current cross-service configuration network. The higher the score, the greater the possibility and severity of business failures caused by potential conflicts. The comprehensive conflict score serves as a preliminary coarse judgment indicator, used to trigger subsequent topology map construction and conflict moment retrieval processes. In this embodiment, a breadth-first search algorithm is used to traverse the cross-service associated configuration network, comprehensively and without omission screening all associated microservice nodes, ensuring the integrity and accuracy of the topology data source. This solution also introduces node business priority and the number of affected instances as evaluation indicators. It differentiates the risk weights of core services and ordinary services based on business importance, achieving differentiated risk assessment, and quantifies the spread of conflict failures by counting the total number of instances, constructing a multi-dimensional and comprehensive risk assessment system. The quantitative rules of the built-in weighted calculation model fuse the two indicators to calculate a comprehensive conflict score, which can objectively and accurately quantify the potential risk level of cross-service configuration conflicts, solving the problem of ambiguous risk classification. Simultaneously, the comprehensive conflict score serves as a preliminary coarse judgment basis, providing precise triggering conditions for subsequent topology map construction and conflict moment retrieval, improving the hierarchy and rationality of microservice configuration conflict detection.

[0018] The third embodiment of the microservice configuration conflict automatic detection method in this invention includes: 301. Determine whether the overall conflict score is greater than the preset conflict score threshold; In this embodiment, the comprehensive conflict score integrates the microservice business priority and the scale of affected instances to quantitatively characterize the overall risk level of potential conflicts in cross-service associated configuration networks. A preset conflict score threshold serves as a risk grading boundary to distinguish between low-risk scenarios that do not require deep retrieval and high-risk scenarios that require refined detection. The calculated comprehensive conflict score is compared with the conflict score threshold to achieve pre-risk grading and screening. If the comprehensive conflict score does not exceed the conflict score threshold, it is determined that the potential conflict hazard of the current configuration network is low, and the subsequent detection process can be directly simplified. If it exceeds the conflict score threshold, the complete topology parsing process is initiated to achieve on-demand triggering of deep detection and avoid meaningless computational consumption in low-risk scenarios. 302. If the overall conflict score is greater than the conflict score threshold, the cross-service associated configuration network will be analyzed according to the preset breadth-first search algorithm to obtain the call relationship characteristics between nodes. In this embodiment, the cross-service associated configuration network carries the microservice nodes, configuration reference links, and service interaction logic. A breadth-first search algorithm is used to traverse the network topology layer by layer from the starting node, searching along configuration dependencies and service call links layer by layer, avoiding the defects of depth-first traversal that are prone to missing branch links and getting trapped in local loops. During the traversal, direct calls, indirect dependencies, and configuration sharing associations between services are identified, and information such as call direction, association tightness, and bidirectional interaction attributes are extracted and summarized to form the call relationship features between nodes. The call relationship features between nodes fully characterize the linkage logic between microservices, providing related elements for building a topology dependency knowledge graph. 303. A microservice topology dependency knowledge graph is constructed based on the preset set of node business priorities, the set of microservice nodes, and the characteristics of inter-node call relationships; In this embodiment, each microservice entity within the microservice node set is used as a node entity in the microservice topology dependency knowledge graph. Dependency association edges between entities are generated based on the call relationship features between nodes. The business importance level in the node business priority set is used as attribute information and bound to the corresponding graph node to complete the node weight labeling. The node entities, association edges, and attribute parameters are structurally encapsulated to build the microservice topology dependency knowledge graph. This microservice topology dependency knowledge graph models discrete microservice nodes, dependencies, and business weights in a unified way, intuitively presenting the full picture of cross-service configuration associations, and providing a standardized graph carrier for subsequent full-link traversal and risk node retrieval. 304. Perform node detection on the microservice topology dependency knowledge graph according to the preset traversal analysis method and conflict determination conditions to obtain multiple conflict occurrence times; In this embodiment, the preset conflict determination condition is a multi-dimensional constraint verification criterion set for cross-service dependency links, integrating mutual exclusion constraints of configuration parameters, exclusive resource constraints, uniqueness constraints of routing rules, and compatibility constraints of upstream and downstream parameter transmission; it is used to identify potential abnormal risks in service linkage scenarios: when the upstream microservice configuration is modified, it causes downstream dependent service port preemption, resource quota out-of-bounds, unexpected overwriting of configuration items with the same name, overlapping gateway routes, and incompatibility of upstream and downstream parameters, then it is determined that the dependency link has potential conflict risks; relying on the preset traversal analysis method, it performs a full domain traversal along the service dependency links within the microservice topology dependency knowledge graph node by node and link by link; during the traversal, it verifies the configuration dependency logic and parameter transmission relationship within the link in combination with the preset conflict determination condition, and identifies service links with linkage conflict risks; when a dependency link with potential conflict is detected, the time node corresponding to the potential conflict is calculated in combination with the configuration change timing constraints, the time information corresponding to all risk links is summarized, and multiple conflict occurrence times are output; the conflict occurrence time is used as the timing anchor point for subsequent configuration timing log tracing and refined conflict verification, realizing the transition from the topology risk pre-determination position to the specific time interval; In this embodiment, risk classification screening is first carried out using a comprehensive conflict score and a preset conflict score threshold. Deep topology analysis is initiated only for high-risk scenarios, effectively reducing invalid computations in low-risk scenarios and saving cluster computing resources. Breadth-first search is used to traverse the cross-service associated configuration network to fully extract the call relationship features between nodes. A microservice topology dependency knowledge graph is constructed by integrating microservice nodes and business priorities to achieve structured global modeling of discrete configuration dependency relationships. Based on multi-dimensional conflict judgment conditions, link traversal detection is carried out within the microservice topology dependency knowledge graph to predict upstream and downstream linkage anomalies and estimate the time of conflict occurrence. This solution can identify cross-service implicit temporal conflicts from the perspective of global dependency links, lock potential conflict temporal intervals in advance, provide reliable temporal anchors for subsequent configuration temporal log tracing and fine-grained conflict verification, improve the pre-emptive perception capability of distributed microservice configuration conflicts, and reduce the probability of business failures caused by configuration changes.

[0019] The fourth embodiment of the microservice configuration conflict automatic detection method in this invention includes: 401. Analyze the configuration timing log based on the preset vector clock off-order determination algorithm, preset timing detection window, location target event and parent event identifier to obtain multiple change events; In this embodiment, configuration time-series logs in a distributed microservice scenario suffer from issues such as event concurrency and physical time sequence disorder, making it difficult to directly identify causal relationships between changes. A preset vector clock partial order determination algorithm relies on the vector clock information attached to events and the parent event identifier to trace predecessor dependencies and determine the causal partial order between the target event and other log events. Using the target event as the source anchor, log entries with temporal causal relationships are selected to form a configuration change chain. Then, a time-series detection window is used to define the effective retrieval interval, and a preset backtracking range is used to filter invalid historical records exceeding the time limit. The effective log entries within the chain are structured and parsed to extract key information such as the change subject, configuration items, and effective time, outputting multiple change events. Irrelevant and redundant logs are stripped from the change events, providing a concise and ordered analysis object for subsequent conflict detection. 402. Based on the conflict detection algorithm and the time of each conflict occurrence, perform conflict detection on each change event to obtain multiple configuration conflict information; In this embodiment, the time of each conflict occurrence is used as a time-series anchor point to determine the cluster operating baseline corresponding to the conflict verification. A conflict detection algorithm is used to analyze the configuration modification content carried by each change event. This conflict detection algorithm integrates multi-dimensional operating constraint rules, comparing the configuration parameters, routing rules, and resource thresholds in the change event with the cluster baseline information at the corresponding time item by item, identifying various abnormal conflicts such as configuration overlay, port preemption, overlapping routing rules, and resource quota exceeding limits. When a configuration change that violates the cluster operating constraints is detected, key information such as conflict location, associated microservice node, conflict type, and conflict occurrence time is collected simultaneously, and multiple configuration conflict information are summarized. The configuration conflict information completely records all the core elements of the conflict, providing complete original material for subsequent conflict classification, risk rating, and generation of the final detection results. In this embodiment, by introducing a vector clock partial order determination algorithm to process microservice configuration time-series logs, the problems of concurrent configuration events, disordered timing, and difficulty in distinguishing causal relationships in distributed scenarios can be effectively solved, thus clarifying the complete configuration change chain. At the same time, invalid log data is filtered through time-series detection windows and backtracking range constraints, simplifying valid change events, reducing subsequent detection computing power overhead, and ensuring the efficiency of source tracing analysis. This solution relies on time-series anchors combined with conflict detection algorithms and integrates multi-dimensional cluster operation constraint rules to perform differential verification on each change event. It can identify various implicit cross-service conflicts such as configuration overlay, port preemption, route overlap, and resource overrun. This solution takes into account both time-series causal relationships and real cluster operation constraints, and can completely capture time-linked configuration anomalies, outputting structured conflict information with complete elements, improving the comprehensiveness and timeliness of microservice configuration conflict detection, and realizing refined management of configuration change risks.

[0020] The fifth embodiment of the microservice configuration conflict automatic detection method in this invention includes: 501. Analyze the configuration timing log based on the vector clock partial order determination algorithm, parent event identifier, and location target event to obtain the configuration change chain; In this embodiment, the configuration sequence log continuously records all configuration distribution, modification, and activation actions of the microservice. In a distributed scenario, configuration changes suffer from concurrency and out-of-order arrival issues, making it difficult to directly distinguish the causal relationship between events. The vector clock partial order determination algorithm is a logical clock algorithm suitable for distributed systems. It relies on the vector clock vector attached to each event to record the version update status of each participating node. By comparing the partial order between vectors, it determines the causal relationship between events, distinguishing between causal events with sequential dependencies and concurrent events that do not affect each other. This algorithm can rely on the vector clock information carried by each event, combined with the parent event identifier to trace the predecessor relationship of the event, and determine the causal partial order between the target event and other configuration change events. Using the target event as the tracing anchor, it uses the parent event identifier to progressively associate configuration log entries with temporal causality, eliminating isolated change records without causal relationships, and sorting out a complete event sequence with sequential dependencies, forming a configuration change chain. The configuration change chain clearly restores a series of continuous configuration modification behaviors before and after the target event is triggered, eliminating the tracing bias caused by the disordered timing of distributed logs, and providing an orderly tracing carrier of configuration sequence for subsequent change event extraction. Logs continuously record all configuration distribution, modification, and activation actions of microservices. In distributed scenarios, configuration changes can lead to concurrency and out-of-order arrival issues, making it difficult to directly distinguish the causal relationship between events. The vector clock partial order determination algorithm is a logical clock algorithm suitable for distributed systems. It does not rely on a globally unified physical clock. It uses the vector clock vector attached to each event to record the version update status of each participating node. By comparing the partial order of vectors, it determines the causal relationship between events, distinguishing between causal events with sequential dependencies and concurrent events that do not affect each other. This algorithm can rely on the vector clock information carried by each event and combine it with the parent event identifier to trace the predecessor relationship of the event and determine the causal partial order between the target event and other configuration change events. Using the target event as the tracing anchor, it uses the parent event identifier to link configuration log entries with temporal causality layer by layer upwards, eliminating isolated change records without causal relationship, and sorting out a complete event sequence with sequential dependencies to form a configuration change chain. The configuration change chain clearly restores a series of continuous configuration modification behaviors before and after the target event is triggered, eliminating the tracing bias caused by the disorder of the timing of distributed logs, and providing an orderly tracing carrier for subsequent change event extraction. 502. Perform source tracing analysis on the configuration change chain based on the timing detection window and the preset basic backtracking duration to obtain multiple change events; In this embodiment, the timing detection window defines the effective time interval for a single tracing process, and the preset basic backtracking duration sets the maximum time boundary for reverse retrieval, preventing unlimited traversal of massive timing logs from causing computational consumption and retrieval timeouts. Reverse tracing retrieval is carried out along the configuration change chain, with the location of the target event as the retrieval endpoint. Simultaneously constrained by the dual boundaries of the timing detection window and the basic backtracking duration, configuration operation records within the effective time range within the chain are filtered, and invalid historical changes exceeding the time limit are discarded. The filtered and retained log entries are structured and parsed to extract key information such as associated microservices, configuration item content, change time, and effective conditions, and are organized to generate multiple standardized change events. The change events serve as the basic analysis unit for snapshot comparison and conflict verification, ensuring that subsequent conflict detection can lock configuration change behaviors within the effective time range. In this embodiment, a vector clock partial order determination algorithm is introduced to process microservice configuration time-series logs. This eliminates the need to rely on a globally unified physical clock in the distributed system and can determine the causal partial order relationship of each configuration change event. By anchoring and locating the target event and combining it with the parent event identifier, the complete configuration change chain is sorted out, isolated invalid change records are eliminated, and the true configuration modification time sequence and dependencies are fully restored. At the same time, dual time boundary constraints are set by setting a time-series detection window and a basic backtracking duration to limit the effective scope of source tracing and avoid computational redundancy and retrieval timeout issues caused by indiscriminately traversing massive logs. This solution can efficiently filter and structure the output of valid change events, providing an accurate and orderly time-series data source for subsequent microservice configuration conflict snapshot comparison and conflict detection, thereby improving the source tracing accuracy and detection reliability of implicit time-series configuration conflicts in distributed scenarios.

[0021] The sixth embodiment of the automatic microservice configuration conflict detection method in this invention includes: 601. Collect all existing configuration data and service operation-related data from the configuration center; In this embodiment, the full set of existing configuration data includes static configuration information such as persistent configuration items, parameter values, configuration scope, and bound service identifiers for each microservice; service operation-related data covers dynamic operation parameters such as service instance deployment information, port usage information, resource quotas, routing mapping relationships, and service dependency links; the system synchronously pulls the above two types of data from the configuration center, service registry, and operation monitoring component, removes invalid and expired abandoned configuration entries and offline invalid instance information, and completes data cleaning and unified formatting; integrating static configuration information and dynamic operation information provides a complete data source for building a benchmark snapshot that can truly reflect the cluster's operating status; 602. A baseline snapshot is constructed based on the full set of existing configuration data and service operation-related data; In this embodiment, the baseline snapshot is used to record the complete configuration and operating status of the microservice cluster at a certain time segment, serving as a reference standard for comparison before and after configuration changes. The principle of constructing the baseline snapshot is to use a specified logical time as the segment boundary, integrate static configuration information and dynamic operating information to complete global state modeling, breaking the limitation of only collecting configuration parameters separately. Based on the cleaned full-volume existing configuration data and service operation-related data, structured encapsulation is performed to bind each microservice configuration parameter, port allocation, resource quota, and routing rule to the corresponding running instance, forming a unified snapshot view that links static configuration and operating status. This baseline snapshot can objectively restore the true operating baseline of the cluster before the change, avoiding the misjudgment problem caused by relying solely on isolated configuration file comparison and ignoring the actual operating status, and providing a unified reference benchmark for subsequent conflict comparison. 603. Based on the conflict detection algorithm and the time of each conflict occurrence, perform conflict detection on the baseline snapshot and each change event to obtain multiple configuration conflict information; In this embodiment, the time of each conflict occurrence is used as the time determination node. A baseline snapshot at the corresponding time is retrieved, and a conflict detection algorithm is used to compare and verify the modified configuration parameters, routing rules, and resource thresholds in each change event with the baseline data in the baseline snapshot item by item. This conflict detection algorithm is a configuration consistency constraint verification algorithm for microservice clusters. It uses a time-series snapshot as the comparison baseline and integrates multi-dimensional verification rules for configuration uniqueness constraints, resource exclusivity constraints, routing mutual exclusion constraints, and resource capacity threshold constraints. It performs structured differential parsing on the parameter differences before and after the configuration change, and can identify compliance conflicts such as single-service configuration overlay, cross-service resource contention, overlapping routing rules, and resource threshold exceeding limits. This conflict detection algorithm has the ability to perceive business constraints and verify the global state of the cluster. It can identify abnormal situations such as parameter overlay, port contention, resource quota exceeding limits, and overlapping routing rules caused by change events. Once a configuration change that violates the operating constraints is detected, the conflict location, involved microservices, conflict type, and conflict occurrence time are recorded, and multiple configuration conflict information are generated. The configuration conflict information carries fine-grained conflict details, supporting subsequent conflict classification and risk result summary output. In this embodiment, the time-series baseline snapshot corresponding to each conflict occurrence time is used as the verification baseline. Structured differential verification is carried out by combining multiple constraint rules such as configuration uniqueness, resource exclusivity, route mutual exclusion, and capacity threshold. This algorithm has the ability to perceive the global state of the cluster and can identify multiple types of implicit configuration conflicts such as configuration overlay, port preemption, route overlap, and resource overrun. This solution can locate the conflict location, associated service, conflict type, and occurrence time, and output refined and structured configuration conflict information. It provides detailed and reliable data support for subsequent conflict classification and risk result generation, improves the comprehensiveness and professionalism of configuration conflict detection in microservice distributed scenarios, and ensures the stability and security of cluster configuration operation.

[0022] The seventh embodiment of the automatic microservice configuration conflict detection method in this invention includes: 701. Classify each configuration conflict information according to the preset conflict classification rule base to obtain configuration coverage conflict category, port routing conflict category, and resource overrun conflict category; In this embodiment, a pre-defined conflict classification rule base contains feature judgment standards, conflict cause rules, and type matching templates for various configuration conflicts, used to classify and identify all configuration conflict information. The classification judgment logic distinguishes conflicts based on their generation mechanism and abnormal manifestation: configuration overlay conflicts correspond to conflict features such as multiple versions of configuration overlay and abnormal replacement of configuration key values ​​leading to abnormal service parameters; port routing conflicts correspond to network scheduling abnormal features such as service port occupancy conflicts, duplicate gateway routing rules, and path interception conflicts; resource overload conflicts correspond to resource overload features such as configuration resource thresholds exceeding the cluster carrying capacity limit, concurrent capacity exceeding the limit, and memory thread quota exceeding the limit. By matching and comparing each configuration conflict information with the pre-defined templates in the conflict classification rule base one by one, the conflict type is classified, resulting in configuration overlay conflict categories, port routing conflict categories, and resource overload conflict categories, thus achieving structured sorting of messy conflict data. 702. Generate microservice configuration conflict detection results based on the comprehensive conflict score, configuration coverage conflict category, port routing conflict category, and resource overrun conflict category; In this embodiment, the comprehensive conflict score carries the risk quantification level of the overall configuration conflict, which can intuitively reflect the overall fault severity and impact range of the current cross-service configuration network. Each conflict category corresponds to detailed anomaly information, involved service nodes, conflict occurrence time, and anomaly details for different conflicts. The system integrates and summarizes the quantitative risk indicators with the multi-dimensional conflict classification results in a structured manner. By associating the comprehensive risk rating with the details of multiple conflict types, it encapsulates and forms a complete and multi-dimensional microservice configuration conflict detection result, providing operation and maintenance personnel with integrated detection output content of conflict type, conflict scope, and risk level, supporting subsequent fault classification, problem rectification, and configuration rollback operations. In this embodiment, relying on a conflict classification rule base with built-in judgment criteria and matching templates, configuration conflict information is automatically classified according to the conflict formation mechanism, distinguishing between configuration coverage, port routing, and resource overrun conflicts. This standardizes and structures the original conflict data, facilitating the identification of the root causes of different conflicts. The solution further integrates a comprehensive conflict score characterizing the scale and severity of the fault's impact, as well as detailed information on various conflicts, to generate microservice configuration conflict detection results. It also provides risk quantification ratings and classification conflict details. This solution combines risk rating with conflict type identification, allowing operations and maintenance personnel to quickly distinguish the severity and urgency of faults based on the output, and carry out targeted handling work such as configuration correction, resource expansion, and routing adjustment. This effectively reduces the difficulty of locating configuration faults in distributed microservice clusters and improves the closed-loop risk management capability of the entire configuration change process.

[0023] The above describes the automatic microservice configuration conflict detection method in the embodiments of the present invention. The following describes the automatic microservice configuration conflict detection device in the embodiments of the present invention. Please refer to [link / reference]. Figure 2 One embodiment of the microservice configuration conflict automatic detection device in this invention includes: Analysis module 1 is used to obtain the cross-service associated configuration network of the configuration center, and analyze the cross-service associated configuration network according to the preset breadth-first search algorithm and preset quantification rules to obtain a comprehensive conflict score. The first detection module 2 is used to perform conflict detection on the cross-service associated configuration network based on the comprehensive conflict score and preset conflict judgment conditions, so as to obtain multiple conflict occurrence times; Data acquisition module 3 is used to acquire the location target event, parent event identifier, and configuration time sequence log; The second conflict detection module 4 is used to perform conflict detection on the configuration time sequence log based on the location target event, parent event identifier, preset conflict detection algorithm and the time of each conflict occurrence, so as to obtain multiple configuration conflict information. Result generation module 5 is used to generate microservice configuration conflict detection results based on the comprehensive conflict score and various configuration conflict information. In this embodiment, a breadth-first search algorithm is used to traverse the cross-service associated configuration network. A comprehensive conflict score is calculated using dual-dimensional quantitative rules based on business priority and instance size, achieving global quantitative classification of configuration conflict risks. Topology-level risk detection is completed through multi-dimensional conflict judgment conditions, the timing of conflict occurrence is estimated, and a mapping relationship between topology risks and time-series logs is constructed. This solution integrates the location of target events, parent event identifiers, and configuration time-series logs to trace the causal chain of configuration changes. Fine-grained conflict verification is performed using conflict detection algorithms, comprehensively identifying various configuration anomalies and generating structured conflict information. Finally, the global risk score and detailed conflict data are merged to generate detection results, balancing overall risk rating and single-point fault location. This effectively solves the problems of missing time-series tracing and missed detection of implicit cross-service conflicts in traditional configuration detection methods, improving the comprehensiveness, accuracy, and efficiency of distributed microservice configuration conflict detection, and ensuring the safe and stable operation of cluster configuration.

[0024] Figure 3 This is a schematic diagram of the structure of an automatic microservice configuration conflict detection device 900 provided in an embodiment of the present invention. The automatic microservice configuration conflict detection device 900 can vary significantly due to different configurations or performance characteristics. It may include one or more central processing units (CPUs) 910 (e.g., one or more processors) and a memory 920, and one or more storage media 930 (e.g., one or more mass storage devices) for storing application programs 933 or data 932. The memory 920 and storage media 930 can be temporary or persistent storage. The program stored in the storage media 930 may include one or more modules (not shown in the diagram), each module may include a series of instruction operations on the automatic microservice configuration conflict detection device 900. Furthermore, the processor 910 may be configured to communicate with the storage media 930 and execute a series of instruction operations on the storage media 930 on the automatic microservice configuration conflict detection device 900 to implement the steps of the automatic microservice configuration conflict detection method provided in the above-described method embodiments.

[0025] The microservice configuration conflict automatic detection device 900 may also include one or more power supplies 940, one or more wired or wireless network interfaces 950, one or more input / output interfaces 960, and / or one or more operating systems 931, such as Windows Server, MacOSX, Unix, Linux, FreeBSD, etc. Those skilled in the art will understand that... Figure 3 The illustrated structure of the microservice configuration conflict automatic detection device does not constitute a limitation on the microservice configuration conflict automatic detection device, and may include more or fewer components than illustrated, or combine certain components, or have different component arrangements.

[0026] The present invention also provides a computer-readable storage medium, which can be a non-volatile computer-readable storage medium or a volatile computer-readable storage medium, wherein the computer-readable storage medium stores instructions that, when executed on a computer, cause the computer to perform the steps of the microservice configuration conflict automatic detection method.

[0027] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working process of the system, device, or unit described above can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0028] Finally, it should be noted that the above descriptions are merely preferred embodiments of the present invention and are not intended to limit the present invention. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art can still modify the technical solutions described in the foregoing embodiments or make equivalent substitutions for some of the technical features. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

Claims

1. A method for automatic detection of microservice configuration conflicts, characterized in that, include: Obtain the cross-service associated configuration network from the configuration center, and analyze the cross-service associated configuration network according to the preset breadth-first search algorithm and preset quantification rules to obtain a comprehensive conflict score; Based on the comprehensive conflict score and preset conflict determination conditions, conflict detection is performed on the cross-service associated configuration network to obtain multiple conflict occurrence times; Obtain the location target event, parent event identifier, and configuration timing log; The configuration time-series log is used to detect conflicts based on the target event, parent event identifier, preset conflict detection algorithm, and the time of each conflict occurrence to obtain multiple configuration conflict information. Microservice configuration conflict detection results are generated based on the overall conflict score and various configuration conflict information.

2. The microservice configuration conflict automatic detection method as described in claim 1, characterized in that, The analysis of the cross-service associated configuration network based on a preset breadth-first search algorithm and preset quantization rules to obtain a comprehensive conflict score includes: The cross-service associated configuration network is analyzed using a breadth-first search algorithm to obtain the set of microservice nodes; Obtain the node business priority of each microservice node in the microservice node set to obtain the node business priority set; Obtain the number of affected instances for each microservice node in the microservice node set to get the total number of instances; The node business priority set and the total number of instances are quantitatively scored according to the quantification rules to obtain a comprehensive conflict score.

3. The microservice configuration conflict automatic detection method as described in claim 2, characterized in that, The process involves performing conflict detection on the cross-service associated configuration network based on a comprehensive conflict score and preset conflict determination criteria to obtain multiple conflict occurrence times, including: Determine whether the overall conflict score is greater than the preset conflict score threshold; If the overall conflict score is greater than the conflict score threshold, the cross-service associated configuration network will be analyzed according to the preset breadth-first search algorithm to obtain the call relationship characteristics between nodes. A microservice topology dependency knowledge graph is constructed based on the preset set of node business priorities, the set of microservice nodes, and the characteristics of inter-node call relationships. Based on the preset traversal analysis method and conflict determination conditions, node detection is performed on the microservice topology dependency knowledge graph to obtain multiple conflict occurrence times.

4. The microservice configuration conflict automatic detection method as described in claim 1, characterized in that, The configuration time-series log is used to perform conflict detection based on the location target event, parent event identifier, preset conflict detection algorithm, and the time of each conflict occurrence to obtain multiple configuration conflict information, including: The configuration timing log is analyzed based on the preset vector clock off-order determination algorithm, the preset timing detection window, the location target event and the parent event identifier to obtain multiple change events; Conflict detection is performed on each change event based on the conflict detection algorithm and the time of each conflict occurrence to obtain multiple configuration conflict information.

5. The microservice configuration conflict automatic detection method as described in claim 4, characterized in that, The configuration timing log is analyzed based on a preset vector clock off-order determination algorithm, a preset timing detection window, the location target event, and the parent event identifier to obtain multiple change events, including: The configuration timing log is analyzed based on the vector clock partial order determination algorithm, parent event identifier, and location target event to obtain the configuration change chain; The configuration change chain is traced and analyzed based on the timing detection window and the preset basic backtracking duration to obtain multiple change events.

6. The microservice configuration conflict automatic detection method as described in claim 4, characterized in that, The conflict detection algorithm and the time of each conflict occurrence are used to perform conflict detection on each change event to obtain multiple configuration conflict information, including: Collect all existing configuration data and service operation-related data from the configuration center; A baseline snapshot is constructed based on the full set of existing configuration data and service operation-related data. Based on the conflict detection algorithm and the time of each conflict occurrence, conflict detection is performed on the baseline snapshot and each change event to obtain multiple configuration conflict information.

7. The microservice configuration conflict automatic detection method as described in claim 1, characterized in that, The process of generating microservice configuration conflict detection results based on the comprehensive conflict score and various configuration conflict information includes: The configuration conflict information is categorized according to the preset conflict classification rule base to obtain configuration overlay conflict category, port routing conflict category, and resource overrun conflict category; Microservice configuration conflict detection results are generated based on the overall conflict score, configuration coverage conflict category, port routing conflict category, and resource overrun conflict category.

8. A microservice configuration conflict automatic detection device, characterized in that, include: The analysis module is used to obtain the cross-service related configuration network of the configuration center, and analyze the cross-service related configuration network according to the preset breadth-first search algorithm and preset quantification rules to obtain a comprehensive conflict score. The first detection module is used to perform conflict detection on the cross-service associated configuration network based on the comprehensive conflict score and preset conflict judgment conditions, so as to obtain multiple conflict occurrence times; The data acquisition module is used to acquire the location target event, parent event identifier, and configuration time sequence log; The second conflict detection module is used to perform conflict detection on the configuration time sequence log based on the location target event, parent event identifier, preset conflict detection algorithm and the time of each conflict occurrence, so as to obtain multiple configuration conflict information. The results generation module is used to generate microservice configuration conflict detection results based on the comprehensive conflict score and various configuration conflict information.

9. A microservice configuration conflict automatic detection device, characterized in that, The microservice configuration conflict automatic detection device includes: a memory and at least one processor, wherein the memory stores instructions; At least one of the processors invokes the instructions in the memory to cause the microservice configuration conflict auto-detection device to perform the steps of the microservice configuration conflict auto-detection method as described in any one of claims 1-7.

10. A computer-readable storage medium storing instructions thereon, characterized in that, When the instructions are executed by the processor, they implement the steps of the microservice configuration conflict automatic detection method as described in any one of claims 1-7.