CN114168421A - Customized code compatibility analysis system and method based on micro-service call chain - Google Patents
Customized code compatibility analysis system and method based on micro-service call chain Download PDFInfo
- Publication number
- CN114168421A CN114168421A CN202111502755.8A CN202111502755A CN114168421A CN 114168421 A CN114168421 A CN 114168421A CN 202111502755 A CN202111502755 A CN 202111502755A CN 114168421 A CN114168421 A CN 114168421A
- Authority
- CN
- China
- Prior art keywords
- call
- calling
- call chain
- chain
- information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/362—Software debugging
- G06F11/3628—Software debugging of optimised code
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3089—Monitoring arrangements determined by the means or processing involved in sensing the monitored data, e.g. interfaces, connectors, sensors, probes, agents
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The system and the method for analyzing the compatibility of customized codes based on a micro-service call chain generate a unique tracking identifier at a unified gateway through a distributed link identifier generator; the probe unit injects a call chain acquisition logic entry into the target method in a class loading stage; the data acquisition reporting client collects and reports the information of the calling nodes and the calling relationship; the call chain information collection service unit collects and cleans call chain data and restores the call chain; the call chain information application unit is used for performing customized code compatibility analysis, providing call retrieval and visualization, and generating a compatibility check list on a research and development management platform. The method is characterized in that a probe is used for non-intruding into a business system, and calling node and calling relation information are collected; analyzing and identifying a calling link containing a calling node by restoring the calling link, and persisting the calling link; the invention can quickly position the compatible code range caused by the standard API change, so that developers can accurately position and quickly solve the problem.
Description
Technical Field
The invention relates to a customer code compatibility analysis system and method based on a micro service call chain, belonging to the technical field of data processing.
Background
With the continuous upgrade of the industrial internet and the increasingly mature technical field of SaaS (Software-as-a-service), more and more enterprise information systems adopt the SaaS mode. Although the standard requirements of certain customers are met by adopting the SaaS mode, the personalized requirements of different customers are different, and in order to solve the customization problem, SaaS manufacturers at home and abroad such as Jintie, Youyou, Sales force and the like generally adopt a micro-service-based technical architecture to construct a personalized configuration platform.
At present, each SaaS manufacturer can generally realize the personalized requirements of customers through the following technical means:
the method comprises the steps that (I) an aPaaS platform for constructing a service model dynamically generates an interface layout and a field component based on model metadata configuration, and a uniform API (application programming interface) at the back end realizes data persistence logic.
And (II) introducing a business rule engine, and defining business logic rules in advance through a graphical configuration or script form. And presetting a buried point in the standard product code, and executing the service logic according to the service configuration rule when the program runs.
And (III) standard code personalization, wherein the customization logic is realized by embedding personalized hard codes in the standard product codes. And dynamically judging the tenant code during the operation, and calling the corresponding customized code segment.
Some companies also adopt an independent micro-service mode for tenants, and the private cloud-like mode isolates the mutual influence of the standard API and the personalized logic to a certain extent, but wastes cloud resources and brings more difficulty to development and deployment.
Although the above-mentioned several personalization solutions address the customization requirements to some extent, they also create quality risks for the product at the back. When the product standard API changes (for example, the interface name or the parameter changes), the personalized code of the client has inevitable compatibility problems due to the limitations of various technical solutions. If the rule engine often adopts weak type script technology, the API change error is often discovered only when the rule engine is actually operated. While the hard coding method can find type errors during compiling, the change of internal logic cannot be sensed, and the problem of logic compatibility can be found only during running. For a huge SaaS cloud system, personalized codes of customers are dispersed in a plurality of micro-service internal code structures, and the change of one interface can cause chain reaction of a plurality of micro-services. The hidden danger is difficult to be clearly checked in the early development stage, huge work is brought to daily code inspection, and the hidden danger is often covered by a large number of baseline tests in the later stage.
Disclosure of Invention
Therefore, the invention provides a customized code compatibility analysis system and method based on a micro service call chain, which can quickly position the compatibility code range caused by standard API change, so that developers can accurately position and quickly solve the problem.
In order to achieve the above purpose, the invention provides the following technical scheme: the customized code compatibility analysis system based on the micro service call chain comprises:
a distributed link identification generator for generating a unique tracking identification at a unified gateway;
the probe unit injects a calling chain acquisition logic entrance into the target method in a class loading stage;
the data acquisition reporting client is used for collecting and reporting calling node and calling relation information;
the call chain information collection service unit is used for collecting and cleaning call chain data and restoring a call chain;
and the call chain information application unit is used for performing customized code compatibility analysis, providing call retrieval and visualization, and generating a compatibility check list on a research and development management platform.
As a preferred scheme of the customer code compatibility analysis system based on the micro service call chain, the distributed link identification generator transmits the unique tracking identification between different micro services and different threads of the same process by calling a chain track.
The data collection reporting client asynchronously reports the collected calling node and calling relation information to the calling chain information collection service unit through the message unit.
The preferable scheme of the customer code compatibility analysis system based on the micro service call chain further comprises a relational database, wherein the call chain information collection service unit persists the restored call chain information into the relational database, and provides data support for compatibility analysis through the relational database.
The system is used as a preferred scheme of a customer code compatibility analysis system based on a micro service call chain, and further comprises a KV memory database, wherein the KV memory database is used for verifying the call chain information by the data acquisition reporting client and the call chain information collection service unit.
The invention also provides a customer code compatibility analysis method based on the micro service call chain, and the customer code compatibility analysis system based on the micro service call chain comprises basic data preparation, call data acquisition, call data processing and compatibility analysis.
As a preferred scheme of the customized code compatibility analysis method based on the micro service call chain, the basic data preparation comprises the following steps:
(11) when a user request reaches a business service, a distributed link unique tracking identifier is obtained or generated;
(12) and acquiring the current tenant information, service information, version information and menu information requested by the user.
As a preferred scheme of the customized code compatibility analysis method based on the micro service call chain, the call data collection comprises the following steps:
(21) recording the class name and target method information being executed, wherein one target method is recorded as a calling node;
(22) describing a calling node and a called node through a calling pair according to an original calling tree;
(23) judging whether the call chain is processed or not, if so, discarding the call chain, and if not, reporting the call chain information to a call chain information collection service unit;
(24) and asynchronously reporting the call chain to the call chain information collection service unit.
As a preferred scheme of the customized code compatibility analysis method based on the micro service call chain, the call data processing comprises the following steps:
(31) judging whether the call chain is processed or not, if so, discarding the call chain, and if not, processing the call chain;
(32) restoring the original calling tree according to a calling pair consisting of the calling node and the called node;
(33) persisting the processed call chain information;
(34) identifying that the call chain has been processed.
As a preferred scheme of the customized code compatibility analysis method based on the micro service call chain, the compatibility analysis comprises the following steps:
(41) inquiring all calling chains containing the calling nodes according to the class names and the target method names of the calling nodes;
(42) and marking a requirement mark on the calling node according to the class name and the target method name of the calling node, and generating a compatibility checking list of the requirement mark.
The invention has the following advantages: generating a unique tracking identifier at the unified gateway through a distributed link identifier generator; the probe unit injects a call chain acquisition logic entry into the target method in a class loading stage; the data acquisition reporting client collects and reports the information of the calling nodes and the calling relationship; the call chain information collection service unit collects and cleans call chain data and restores the call chain; the call chain information application unit is used for performing customized code compatibility analysis, providing call retrieval and visualization, and generating a compatibility check list on a research and development management platform. The method is characterized in that a probe is used for non-intruding into a business system, and calling node and calling relation information are collected; analyzing and identifying the calling link containing the calling node by restoring the calling link, persisting the calling link, and accumulating and perfecting the relational database; on the basis of a relational database, a method for realizing a retrieval standard is developed to obtain a related calling link, and the related calling link can be flexibly displayed; a compatibility check list can be generated, and a basis is provided for testing compatibility and on-line memo verification; the invention solves the technical problem that the customized logic cannot sense the change of the standard logic after the SaaS platform is customized, thereby causing abnormal business logic, and can quickly position the compatible code range (including a function menu of a client, a micro-service code distribution list and the like) caused by the change of the standard API, so that developers can accurately position and quickly solve the problem, and the quality of iterative research and development of products is greatly improved.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below. It should be apparent that the drawings in the following description are merely exemplary, and that other embodiments can be derived from the drawings provided by those of ordinary skill in the art without inventive effort.
The structures, ratios, sizes, and the like shown in the present specification are only used for matching with the contents disclosed in the specification, so that those skilled in the art can understand and read the present invention, and do not limit the conditions for implementing the present invention, so that the present invention has no technical significance, and any structural modifications, changes in the ratio relationship, or adjustments of the sizes, without affecting the functions and purposes of the present invention, should still fall within the scope of the present invention.
FIG. 1 is a schematic diagram of a system for analyzing compatibility of customized code based on a micro service call chain according to an embodiment of the present invention;
FIG. 2 is a schematic diagram illustrating call chain information persistence in a method for analyzing compatibility of customized code based on micro service call chains according to an embodiment of the present invention;
FIG. 3 is a schematic diagram illustrating a description of a call pair in a method for analyzing compatibility of customized code based on a microservice call chain according to an embodiment of the present invention;
fig. 4 is a schematic diagram illustrating call tree restoration in the method for analyzing compatibility of customized code based on micro service call chains according to the embodiment of the present invention.
Detailed Description
The present invention is described in terms of particular embodiments, other advantages and features of the invention will become apparent to those skilled in the art from the following disclosure, and it is to be understood that the described embodiments are merely exemplary of the invention and that it is not intended to limit the invention to the particular embodiments disclosed. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Example 1
Referring to fig. 1, embodiment 1 of the present invention provides a system for analyzing customized code compatibility based on a microservice call chain, including:
the distributed link identification generator 1 is used for generating a unique tracking identification at the unified gateway;
the probe unit 2 injects a calling chain acquisition logic entry into the target method in the class loading stage;
the data acquisition reporting client 3 is used for collecting and reporting the information of the calling nodes and the calling relation;
the call chain information collection service unit 4 is used for collecting and cleaning call chain data and restoring a call chain;
the call chain information application unit 5 is used for performing customized code compatibility analysis, providing call retrieval and visualization, and generating a compatibility check list on a research and development management platform.
In this embodiment, the distributed link identifier generator 1 transfers unique tracking identifiers between different microservices and between different threads of the same process by calling a chain track.
Specifically, the distributed link identifier generator 1 generates a unique tracking identifier (TraceID) at the unified gateway, and reliably transfers the unique tracking identifier between different micro services and between different threads of the same process along the micro service calling chain track, wherein the unique tracking identifier can be called at one time in the micro service system.
Specifically, the complete micro service system includes a plurality of micro service units, and the micro service subsystems are mutually called, so that a call chain is formed. The call chain may document the components that the client request goes through from being issued to being responded to, the microservice, the total duration of the request, and the duration of each component.
Specifically, the link trace framework for tracing the calling process of the micro service is Zipkin, Pinpoint, Sky Walking, CAT.
Zipkin is a calling chain analysis tool of a Twitter open source, is widely used based on spring closed slot, and is characterized by light weight and simple use and deployment.
The Pinpoint is based on the call chain analysis of byte code injection and an application monitoring analysis tool, supports various plug-ins, and has powerful UI function and no code invasion at an access end.
Skywalk is native open-source calling chain analysis based on bytecode injection, applies a monitoring analysis tool, supports various plug-ins, has strong UI function, has no code intrusion at an access end, and is added with an Apache incubator.
CAT is a series of monitoring platform tools of call chain analysis, application monitoring analysis, log collection, monitoring alarm and the like based on coding and configuration of public comment open sources.
Specifically, Java provides a bytecode that depends on Java agent technology and modifies a target method, and non-invasive embedding is achieved. The collector using the Java agent mode is a probe. When the application program is started, the Java agent is used, or an attach (pid) mode is used during running, the probe package can be led into the application program, and implantation of the buried point is completed.
The probe unit 2 can be upgraded nonintrusively by heat. The user does not need to understand the principles of the depth and can use the complete monitoring service. At the present stage, a plurality of open source monitoring products already provide rich java probe libraries as monitoring service providers, and development cost is further reduced.
In this embodiment, the data collection and report client 3 further includes a message unit 6, and asynchronously reports the collected call node and call relationship information to the call chain information collection service unit 4 through the message unit 6.
In particular, the messaging unit 6 is integrated with a messaging system, which may be an open source messaging system such as an ActiveMQ. The ActivateMQ is an open-source message system provided by Apache, is completely realized by adopting Java, and can well support J2EE to provide JMS specification.
The JMS is a group of Java application program interfaces, provides a series of services such as creation, sending, receiving, reading and the like of messages, is an API irrelevant to manufacturers, and can well communicate with message components of different manufacturers. The message types supported by JMS include simple text, serializable objects, key-value pairs, byte streams, and payload-less messages, among others. The sending of the message is asynchronous, and after the sender of the message sends the message, the receiver of the message does not need to wait for the immediate response, so that the efficiency of the distributed system cooperation is improved.
In this embodiment, the system further includes a relational database 7, and the call chain information collection service unit 4 persists the restored call chain information in the relational database 7, and provides data support for compatibility analysis through the relational database 7.
In particular, the relational database 7 employs a relational model to organize data, storing data in rows and columns for easy understanding by a user. The relational model can be understood as a two-dimensional table model, and a relational database is a data organization composed of two-dimensional tables and relations between the two-dimensional tables.
Referring to fig. 2, call chain information data persistence is to convert a data model in memory into a storage model and to convert a storage model into a data model in memory. The data model may be any data structure or object model and the storage model may be a relational model, XML, binary stream, etc.
In this embodiment, the system further includes a KV memory database 8, where the KV memory database 8 is used for reporting the data acquisition to the client and verifying the call chain information by the call chain information collection service unit.
Specifically, the KV memory database 8 is used for collecting the data acquisition reporting client 3 and verifying the duplication of the call chain information by the data acquisition reporting client 3, so as to prevent repeated collection and processing.
The KV memory database 8 is a Key-value database, is a database for storing data by Key value pairs, and like a map in java, the whole database can be understood as a large map, and each Key corresponds to a unique value. The KV memory database 8 has the advantages of high query speed, large data storage amount and high concurrency support, and is very suitable for query through a main key.
In summary, the present invention generates a unique tracking identifier at the unified gateway through the distributed link identifier generator; the probe unit injects a call chain acquisition logic entry into the target method in a class loading stage; the data acquisition reporting client collects and reports the information of the calling nodes and the calling relationship; the call chain information collection service unit collects and cleans call chain data and restores the call chain; the call chain information application unit is used for performing customized code compatibility analysis, providing call retrieval and visualization, and generating a compatibility check list on a research and development management platform. The method is characterized in that a probe is used for non-intruding into a business system, and calling node and calling relation information are collected; analyzing and identifying the calling link containing the calling node by restoring the calling link, persisting the calling link, and accumulating and perfecting the relational database; on the basis of a relational database, a method for realizing retrieval standard is developed to obtain a related call link, and the related call link can be flexibly displayed according to the dimensions of tenants and menus; a compatibility check list can be generated, and a basis is provided for testing compatibility and on-line memo verification; the invention solves the technical problem that the customized logic cannot sense the change of the standard logic after the SaaS platform is customized, thereby causing abnormal business logic, and can quickly position the compatible code range (including a function menu of a client, a micro-service code distribution list and the like) caused by the change of the standard API, so that developers can accurately position and quickly solve the problem, and the quality of iterative research and development of products is greatly improved.
Example 2
Referring to fig. 3 and fig. 4, embodiment 2 of the present invention further provides a method for analyzing compatibility of a customized code based on a micro service call chain, where the system for analyzing compatibility of a customized code based on a micro service call chain in embodiment 1 or any possible implementation manner thereof includes basic data preparation, call data collection, call data processing, and compatibility analysis.
Specifically, the basic data preparation includes:
(11) when a user request reaches a business service, a distributed link unique tracking identifier is obtained or generated;
(12) and acquiring the current tenant information, service information, version information and menu information requested by the user.
Specifically, the invoking data collection includes:
(21) recording the class name and target method information being executed, wherein one target method is recorded as a calling node;
(22) describing a calling node and a called node through a calling pair according to an original calling tree;
(23) judging whether the call chain is processed or not, if so, discarding the call chain, and if not, reporting the call chain information to a call chain information collection service unit;
(24) and asynchronously reporting the call chain to the call chain information collection service unit.
Specifically, the invoking data processing includes:
(31) judging whether the call chain is processed or not, if so, discarding the call chain, and if not, processing the call chain;
(32) restoring the original calling tree according to a calling pair consisting of the calling node and the called node;
(33) persisting the processed call chain information;
(34) identifying that the call chain has been processed.
Specifically, the compatibility analysis includes:
(41) inquiring all calling chains containing the calling nodes according to the class names and the target method names of the calling nodes; customized nodes affected upstream and downstream after standard node modification can be analyzed.
(42) And marking a requirement mark on the calling node according to the class name and the target method name of the calling node, generating a compatibility check list of the requirement mark, and providing a basis for testing the affected customized node.
It should be noted that the foregoing method for analyzing compatibility of a customized code based on a micro service call chain depends on the system for analyzing compatibility of a customized code based on a micro service call chain in embodiment 1, and specific implementation details are the same as those in embodiment 1, and are not described herein again.
Example 3
Embodiment 3 of the present invention provides a non-transitory computer-readable storage medium, where a program code of a microservice call chain-based customization code compatibility analysis method is stored in the computer-readable storage medium, where the program code includes instructions for executing the microservice call chain-based customization code compatibility analysis method of embodiment 2 or any possible implementation manner of the microservice call chain-based customization code compatibility analysis method.
The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.
Example 4
An embodiment 4 of the present invention provides an electronic device, including: a memory and a processor;
the processor and the memory are communicated with each other through a bus; the memory stores program instructions executable by the processor to invoke the method for customized code compatibility analysis based on a chain of microservice invocation of embodiment 2 or any possible implementation thereof.
Specifically, the processor may be implemented by hardware or software, and when implemented by hardware, the processor may be a logic circuit, an integrated circuit, or the like; when implemented in software, the processor may be a general-purpose processor implemented by reading software code stored in a memory, which may be integrated in the processor, located external to the processor, or stand-alone.
In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the invention to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website site, computer, server, or data center to another website site, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.).
It will be apparent to those skilled in the art that the modules or steps of the present invention described above may be implemented by a general purpose computing device, they may be centralized on a single computing device or distributed across a network of multiple computing devices, and alternatively, they may be implemented by program code executable by a computing device, such that they may be stored in a storage device and executed by a computing device, and in some cases, the steps shown or described may be performed in an order different than that described herein, or they may be separately fabricated into individual integrated circuit modules, or multiple ones of them may be fabricated into a single integrated circuit module. Thus, the present invention is not limited to any specific combination of hardware and software.
Although the invention has been described in detail above with reference to a general description and specific examples, it will be apparent to one skilled in the art that modifications or improvements may be made thereto based on the invention. Accordingly, such modifications and improvements are intended to be within the scope of the invention as claimed.
Claims (10)
1. The customized code compatibility analysis system based on the micro service call chain is characterized by comprising the following components:
a distributed link identification generator for generating a unique tracking identification at a unified gateway;
the probe unit injects a calling chain acquisition logic entrance into the target method in a class loading stage;
the data acquisition reporting client is used for collecting and reporting calling node and calling relation information;
the call chain information collection service unit is used for collecting and cleaning call chain data and restoring a call chain;
and the call chain information application unit is used for performing customized code compatibility analysis, providing call retrieval and visualization, and generating a compatibility check list on a research and development management platform.
2. The microservice call chain-based customized code compatibility analysis system of claim 1, wherein the distributed link identifier generator passes the unique tracking identifier between different microservices, between different threads of the same process, through a call chain trace.
3. The microservice call-chain-based customized code compatibility analysis system according to claim 1, further comprising a message unit, wherein the data collection reporting client asynchronously reports the collected call node and call relation information to the call-chain information collection service unit through the message unit.
4. The microservice call-chain based customized code compatibility analysis system of claim 1, further comprising a relational database into which the call-chain information collection service persists restored call-chain information, through which data support is provided for compatibility analysis.
5. The microservice-call-chain-based customized code compatibility analysis system according to claim 1, further comprising a KV memory database, wherein the KV memory database is used for the data acquisition reporting client and the call-chain information collection service unit to check and duplicate call-chain information.
6. The customer code compatibility analysis method based on the micro service call chain adopts the customer code compatibility analysis system based on the micro service call chain of any one of claims 1 to 5, and is characterized by comprising basic data preparation, call data acquisition, call data processing and compatibility analysis.
7. The method of claim 6, wherein the base data preparation comprises:
(11) when a user request reaches a business service, a distributed link unique tracking identifier is obtained or generated;
(12) and acquiring the current tenant information, service information, version information and menu information requested by the user.
8. The microservice call chain-based customized code compatibility analysis method of claim 7, wherein the call data collection comprises:
(21) recording the class name and target method information being executed, wherein one target method is recorded as a calling node;
(22) describing a calling node and a called node through a calling pair according to an original calling tree;
(23) judging whether the call chain is processed or not, if so, discarding the call chain, and if not, reporting the call chain information to a call chain information collection service unit;
(24) and asynchronously reporting the call chain to the call chain information collection service unit.
9. The microservice call chain-based customized code compatibility analysis method of claim 8, wherein the call data processing comprises:
(31) judging whether the call chain is processed or not, if so, discarding the call chain, and if not, processing the call chain;
(32) restoring the original calling tree according to a calling pair consisting of the calling node and the called node;
(33) persisting the processed call chain information;
(34) identifying that the call chain has been processed.
10. The method of claim 9, wherein the compatibility analysis comprises:
(41) inquiring all calling chains containing the calling nodes according to the class names and the target method names of the calling nodes;
(42) and marking a requirement mark on the calling node according to the class name and the target method name of the calling node, and generating a compatibility checking list of the requirement mark.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111502755.8A CN114168421A (en) | 2021-12-09 | 2021-12-09 | Customized code compatibility analysis system and method based on micro-service call chain |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111502755.8A CN114168421A (en) | 2021-12-09 | 2021-12-09 | Customized code compatibility analysis system and method based on micro-service call chain |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114168421A true CN114168421A (en) | 2022-03-11 |
Family
ID=80485231
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111502755.8A Pending CN114168421A (en) | 2021-12-09 | 2021-12-09 | Customized code compatibility analysis system and method based on micro-service call chain |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114168421A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114679487A (en) * | 2022-03-25 | 2022-06-28 | 度小满科技(北京)有限公司 | Link processing method, device, storage medium and processor |
| CN115277475A (en) * | 2022-07-05 | 2022-11-01 | 浪潮云信息技术股份公司 | Method and system for realizing link tracking by API gateway |
| CN116016262A (en) * | 2022-12-28 | 2023-04-25 | 天翼云科技有限公司 | Method and device for detecting call chain consistency in real time based on union |
-
2021
- 2021-12-09 CN CN202111502755.8A patent/CN114168421A/en active Pending
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114679487A (en) * | 2022-03-25 | 2022-06-28 | 度小满科技(北京)有限公司 | Link processing method, device, storage medium and processor |
| CN114679487B (en) * | 2022-03-25 | 2023-12-22 | 度小满科技(北京)有限公司 | Link processing method, device, storage medium and processor |
| CN115277475A (en) * | 2022-07-05 | 2022-11-01 | 浪潮云信息技术股份公司 | Method and system for realizing link tracking by API gateway |
| CN116016262A (en) * | 2022-12-28 | 2023-04-25 | 天翼云科技有限公司 | Method and device for detecting call chain consistency in real time based on union |
| CN116016262B (en) * | 2022-12-28 | 2024-05-24 | 天翼云科技有限公司 | Method and device for detecting call chain consistency in real time based on union |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108415832B (en) | Interface automation test method, device, equipment and storage medium | |
| US8584112B2 (en) | Open application lifecycle management framework | |
| CN114168421A (en) | Customized code compatibility analysis system and method based on micro-service call chain | |
| Zhou et al. | API deprecation: a retrospective analysis and detection method for code examples on the web | |
| US8468391B2 (en) | Utilizing log event ontology to deliver user role specific solutions for problem determination | |
| US11023306B2 (en) | Implementing a post error analysis system that includes log creation facilities associated with instances of software applications | |
| US9697104B2 (en) | End-to end tracing and logging | |
| CN108845940B (en) | Enterprise-level information system automatic function testing method and system | |
| US20210326197A1 (en) | System And Method For Automatically Identifying And Resolving Computing Errors | |
| WO2014031618A2 (en) | Data relationships storage platform | |
| EP1810131A2 (en) | Services oriented architecture for data integration services | |
| CN113326247B (en) | Cloud data migration method and device and electronic equipment | |
| CN110851471A (en) | Distributed log data processing method, device and system | |
| Amalfitano et al. | The DynaRIA tool for the comprehension of Ajax web applications by dynamic analysis | |
| CN117370203B (en) | Automatic test method, system, electronic equipment and storage medium | |
| CN112527619A (en) | Analysis link calling method and system based on directed acyclic graph structure | |
| CN115185797A (en) | Method and system for testing visual algorithm model, electronic equipment and storage medium | |
| CN112445691B (en) | Non-invasive intelligent contract performance detection method and device | |
| CN116841900A (en) | Interface document, test case generation method, test case generation device, computer equipment and storage medium | |
| Konur | Towards Light‐Weight Probabilistic Model Checking | |
| CN116010244A (en) | Automatic test method, device, electronic equipment and storage medium | |
| CN115509913A (en) | Software automation test method, device, machine readable medium and equipment | |
| CN113419738A (en) | Interface document generation method and device and interface management equipment | |
| CN113032254A (en) | Evaluation method and device for test coverage condition | |
| Mengistu | Distributed Microservice Tracing Systems: Open-source tracing implementation for distributed Microservices build in Spring framework |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |