CN111913789A - Program tracking method, device and medium supporting micro-service architecture - Google Patents
Program tracking method, device and medium supporting micro-service architecture Download PDFInfo
- Publication number
- CN111913789A CN111913789A CN202010604143.9A CN202010604143A CN111913789A CN 111913789 A CN111913789 A CN 111913789A CN 202010604143 A CN202010604143 A CN 202010604143A CN 111913789 A CN111913789 A CN 111913789A
- Authority
- CN
- China
- Prior art keywords
- program
- program tracking
- micro service
- service node
- tracking
- 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
- 238000000034 method Methods 0.000 title claims abstract description 61
- 230000006870 function Effects 0.000 description 18
- 238000012545 processing Methods 0.000 description 11
- 230000008569 process Effects 0.000 description 10
- 238000010586 diagram Methods 0.000 description 9
- 238000004590 computer program Methods 0.000 description 7
- 235000014510 cooky Nutrition 0.000 description 6
- 230000004044 response Effects 0.000 description 6
- 238000005516 engineering process Methods 0.000 description 4
- 230000009286 beneficial effect Effects 0.000 description 2
- 230000004069 differentiation Effects 0.000 description 2
- 230000007613 environmental effect Effects 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000001960 triggered effect Effects 0.000 description 2
- 235000008694 Humulus lupulus Nutrition 0.000 description 1
- 230000006978 adaptation Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 239000000284 extract Substances 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 239000002699 waste material Substances 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
- G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
- G06F9/4881—Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues
-
- 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/3636—Software debugging by tracing the execution of the program
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application discloses a program tracking method, a device and a medium for supporting a micro-service architecture. The method comprises the following steps: the method comprises the steps that a first micro service node obtains a pre-configured program tracking parameter; generating program tracking data of the first micro service node according to the program tracking parameters; and if the first micro service node calls the second micro service node, indicating the second micro service node to continue program tracking so as to generate program tracking data of the second micro service node. According to the method and the system, the program tracking can be carried out on the currently working micro service nodes, and if the micro service nodes are called, the called micro service nodes can be indicated by the currently working micro service nodes to continue the program tracking, so that program tracking data of which the continuity and integrity meet requirements on the whole calling link can be recorded, and the problem of the service function is conveniently located.
Description
Technical Field
The present application relates to the field of internet technologies, and in particular, to a program tracking method, device, and medium supporting a micro service architecture.
Background
Under the micro-service architecture, each micro-service node may be deployed at different network locations, and a complete service function request often spans multiple different components on multiple micro-service nodes. In traditional operation and maintenance and development, the running condition of the application is determined by looking at the running log of the application.
However, in the micro service architecture mode, because the number of micro service nodes is large, the way of checking the operation log to determine the operation state of the micro service node is not suitable any more, and when the service function has a problem, it is difficult to locate the micro service node having the problem through the log.
Disclosure of Invention
The embodiment of the application provides a program tracking method, device and medium supporting a micro-service architecture, which are used for solving the following technical problems in the prior art: in the micro-service architecture mode, the micro-service nodes with problems are difficult to locate by checking the running logs.
The embodiment of the application adopts the following technical scheme:
a program tracking method supporting micro service architecture comprises the following steps:
the method comprises the steps that a first micro service node obtains a pre-configured program tracking parameter;
generating program tracking data of the first micro service node according to the program tracking parameters;
and if the first micro service node calls a second micro service node, indicating the second micro service node to continue program tracking so as to generate program tracking data of the second micro service node.
Optionally, the method further comprises:
and sending the program tracking data of the first micro service node to a preset program tracking center so that the program tracking center can collect the program tracking data of the first micro service node and the program tracking data of the second micro service node.
Optionally, the method further comprises:
and generating a component calling relation tree in the nodes of the first micro service node and the second micro service node and among the nodes according to the program tracking data of the first micro service node and the program tracking data of the second micro service node.
Optionally, the obtaining, by the first microserver node, the preconfigured program tracking parameters includes:
receiving a user request;
and responding to the user request, and acquiring the program tracking parameters configured for the user corresponding to the user request from the program tracking parameters configured for different users in advance.
Optionally, before generating the program trace data of the first micro service node, the method further includes:
acquiring a specific identifier carried by the user request and used for indicating whether to perform program tracking;
determining that the particular identifier indicates that program tracking is to be performed.
Optionally, generating program trace data of the first microserver node according to the program trace parameter includes:
generating a first program tracking context according to the program tracking parameters;
and generating program tracking data of the first micro service node according to the first program tracking context.
Optionally, instructing the second microserver node to continue program tracing includes:
generating a second program tracking context according to the first program tracking context;
and instructing the second micro service node to continue program tracking according to the second program tracking context, wherein the second program tracking context is used for associating the program tracking data of the first micro service node with the program tracking data of the second micro service node.
Optionally, the first program tracking context and the second program tracking context include at least one of the following identifiers: the first tracking identifier is used for marking program tracking data belonging to the same component calling relationship tree; and the second tracking identifier is used for marking the program tracking data generated corresponding to the last call.
A program tracking device supporting a micro-service architecture, which is loaded with a first micro-service node, the device comprising:
at least one processor; and the number of the first and second groups,
a memory communicatively coupled to the at least one processor; wherein,
the memory stores instructions executable by the at least one processor to enable the at least one processor to:
the first micro service node acquires a pre-configured program tracking parameter;
generating program tracking data of the first micro service node according to the program tracking parameters;
and if the first micro service node calls a second micro service node, indicating the second micro service node to continue program tracking so as to generate program tracking data of the second micro service node.
A program tracking medium supporting a microservice architecture, the medium comprising a non-volatile computer storage medium storing computer-executable instructions for application to a first microservice node, the computer-executable instructions configured to:
the first micro service node acquires a pre-configured program tracking parameter;
generating program tracking data of the first micro service node according to the program tracking parameters;
and if the first micro service node calls a second micro service node, indicating the second micro service node to continue program tracking so as to generate program tracking data of the second micro service node.
The embodiment of the application adopts at least one technical scheme which can achieve the following beneficial effects: the method can not only perform program tracking on the currently working micro service nodes, but also instruct the called micro service nodes to continue program tracking by the currently working micro service nodes if the calling among the micro service nodes occurs, so that program tracking data with continuity and integrity meeting requirements on the whole calling link can be recorded, and the service function problem can be conveniently positioned.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:
FIG. 1 is a flowchart illustrating a program tracing method supporting a micro service architecture according to some embodiments of the present application;
fig. 2 is a detailed flowchart of the method of fig. 1 in an application scenario provided by some embodiments of the present application;
fig. 3 is a schematic view of an interaction flow between multiple subjects involved in the method of fig. 1 in an application scenario provided by some embodiments of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions of the present application will be described in detail and completely with reference to the following specific embodiments of the present application and the accompanying drawings. It should be apparent that the described embodiments are only some of the embodiments of the present application, and not all of the embodiments. 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 application.
Fig. 1 is a flowchart illustrating a program tracking method supporting a micro service architecture according to some embodiments of the present application. The main execution unit of the process is a micro service node, and for convenience of description, the micro service node is referred to as a first micro service node, and some other micro service node except the first micro service node is referred to as a second micro service node. The first micro service node and the second micro service node may be located in the same device or in different devices.
The method of fig. 1 comprises the steps of:
s100: the first micro service node acquires a pre-configured program tracking parameter.
In some embodiments of the present application, the program trace parameter is a set of parameters describing a trace range of the program, and includes information such as a program trace user, a trace duration, a component that enables trace, a granularity at which each component records trace information, and the like.
In some embodiments of the present application, the program tracking parameters may be configured according to differentiation for different users, so that it is convenient to meet the differentiation requirements of different users; further, for the same user, the program tracking parameters used each time the program tracking is performed for the user may also be differentiated; the program tracking parameters to be used may be configured autonomously by the user.
S102: and generating program tracking data of the first micro service node according to the program tracking parameters.
In some embodiments of the present application, a specific program running on the first micro service node may be tracked according to the program tracking parameter, for example, for a program running in response to a user request, a call between components in the first micro service node due to the running of the program may be tracked.
S104: and if the first micro service node calls a second micro service node, indicating the second micro service node to continue program tracking so as to generate program tracking data of the second micro service node.
In some embodiments of the present application, the business process may be performed across different microservice nodes, and accordingly, program tracing needs to be performed on these microservice nodes to obtain more complete program tracing data. Based on this, the micro service node as the caller indicates that the second micro service node as the callee only needs to perform program tracking, and the indication carries corresponding associated data, so as to subsequently summarize program tracking data respectively generated by each micro service node participating in the current service processing process.
By the method of fig. 1, program tracking can be performed on the currently working microservice node, and if calling between microservice nodes occurs, the currently working microservice node can indicate the called microservice node to continue program tracking, so that program tracking data with continuity and integrity meeting requirements on the whole calling link can be recorded, and service function problems can be conveniently located.
The present application also provides some more specific embodiments of the method of fig. 1 and an extended method, as described further below.
In some embodiments of the present application, an additional module, called a program tracking center, is preset, and the program tracking center may be disposed on a separate server or may be disposed on the same device as some micro service nodes. The program tracking center can be communicated with a plurality of micro service nodes and is used for summarizing the program tracking data of the micro service nodes, so that the workload of the micro service nodes is reduced, and the program tracking data is better utilized. Based on this, the program tracking center can collect the program tracking data of the first micro service node and the program tracking data of the second micro service node, and can analyze and process the collected program tracking data so as to locate the service function problem.
Of course, the program tracking center may also provide more common services, for example, store the pre-configured program tracking parameters and provide a corresponding access interface, so that when the micro service node needs to be used, the program tracking parameters may be obtained from the program tracking center through the access interface.
In some embodiments of the present application, a service processing procedure is often triggered by a user request, and a corresponding program tracking procedure may also be triggered by the user request, so that it is convenient to determine a certain range of program tracking data based on an operation feedback of a user, and further efficiently locate a service function problem. Based on this, assuming that a user request sent by a user first reaches the first micro service node, the first micro service node receives the user request, and triggers a corresponding service program to provide service in response to the user request, obtains a program tracking parameter configured for the user corresponding to the user request from program tracking parameters configured for different users in advance, and further tracks a program (for example, the service program) designated by the user according to the program tracking parameter.
Further, in practical applications, if program tracing is performed for all user requests or all user requests of a certain user, a large amount of processing resources are consumed, and a large amount of program trace data is generated, which occupies a large amount of storage space. In order to reduce unnecessary waste, program tracking can be performed more specifically, whether program tracking is to be performed according to a user request is specified by a user or automatically specified by a preset rule, a specific identifier is assumed to be specified and carried in the user request, after the first micro service node receives the user request, whether the specific identifier carried in the user request indicates that program tracking is to be performed is judged, if yes, program tracking is performed, and otherwise, program tracking is not performed.
In practical application, Cookie is a file which is already applied and popularized and can be associated with user identity, the technology is mature, and the specific identification can be represented in a Cookie form, so that the Cookie-based electronic tag has the advantages of good compatibility and universality, low implementation cost and high reliability.
In some embodiments of the present application, for a first micro service node, a first program trace context is generated according to a program trace parameter, and program trace data of the first micro service node is generated according to the first program trace context. The program tracking parameters are general parameters which are globally applicable to the current tracking, and when each specific micro service node performs tracking, environment parameters suitable for the current micro service node need to be generated so as to better guide program tracking at the current micro service node, and the environment parameters are called program tracking contexts. Based on the program tracing data, for the first micro service node, a first program tracing context is generated according to the program tracing parameters, and program tracing data of the first micro service node is generated according to the first program tracing context. When the cross-node is called, the first micro service node can also generate a cross-node tracking context according to the first program tracking context, which is called a second program tracking context, record the environmental parameters related to environmental switching, and further instruct the second micro service node to continue program tracking according to the second program tracking context; certainly, if there is a need (for example, the second microservice node is very reliable and does not have a service function problem basically), the cross-node tracking context may also indicate that the second microservice node does not continue to perform program tracking, which is helpful to reduce the total amount of program tracking data and improve the problem location efficiency. The second program trace context can be used to correlate program trace data of the first micro service node with program trace data of the second micro service node, facilitating subsequent summarization of the program trace data.
The second micro service node can generate the program tracking context of the node according to the second program tracking context, and the program tracking context is used for guiding program tracking of the node.
In some embodiments of the present application, the first program tracking context, the second program tracking context, includes at least one of the following: the first tracking identifier is used for marking program tracking data belonging to the same component calling relationship tree; and the second tracking identifier is used for marking the program tracking data generated corresponding to the last call. The first trace identifier includes, for example, a trace ID and a trace data ID, and the second trace identifier includes, for example, a parent trace data ID, which will be described in detail later for ease of understanding. The first program trace context includes, for example, a trace ID, a trace data ID, and the second program trace context includes, for example, a trace ID, a parent trace data ID.
In some embodiments of the present application, a component call relation tree is mentioned in the foregoing, where the component call relation tree shows a call relation between components (e.g., methods, HTTP request processing, database access, etc.) in and/or between microservice nodes, and the tree structure representation has advantages of concise information, good intuition, and is clear for information such as the number of hops passed by the caller, the callee, and the call link. After the program tracking data is summarized, a complete component call relation tree can be extracted so as to efficiently locate the business function problem.
The program trace data records the call relationships described above. Program trace data is a data set having a structure, which contains, for example, a trace ID, a parent trace ID, a start time, an end time, a user, a component name, whether a component call was successful, exception information, and the like; and may also contain information for each component with the adaptation to that component, such as URL, Method, heads for HTTP components, DBTYPE, SQL, PARAMS for database components, etc. Program trace data is created at the beginning of each component call, basic information such as start time, component information, current user, etc. is recorded, other supplementary data is recorded during component operation, and the result of the component call is recorded after the component operation is finished, so that the recorded information constitutes program trace data.
In some embodiments of the application, after the program tracking center collects the program tracking data, a component calling relationship tree may be constructed according to the tracking ID and the tracking data ID, receiving incomplete program tracking data is further supported, and an existing component calling relationship tree is updated according to newly added program tracking data. In order to facilitate the use of service personnel, the program tracking center can provide a corresponding query interface for querying all or a designated part of the component call relationship tree and corresponding program tracking data, and if necessary, under the condition of associating log data in advance, corresponding log data can be obtained according to the component call relationship tree or the program tracking data index, so that the service function problem can be positioned efficiently.
According to the above description, some embodiments of the present application provide a detailed flow chart of the method of fig. 1 in an application scenario, as illustrated in fig. 2. Under the application scene, a program tracking center is preset.
The process in fig. 2 comprises the following steps:
configuring program tracking parameters by a user, and storing the configured program tracking parameters in a program tracking center;
the method comprises the steps that a first micro service node receives a user request of a user, obtains a program tracking parameter corresponding to the user from a program tracking center, and further generates a first program tracking context;
when the components in the first micro service node are called, generating program tracking data according to the first program tracking context, and sending the program tracking data to a program tracking center;
if the first micro service node calls a second micro service node, creating a second program tracking context and sending the second program tracking context to the second micro service node;
the second micro service node generates a program tracking context suitable for the second micro service node according to the second program tracking context, similar to the processing of the first micro service node, and when the components in the second micro service node are called, generates program tracking data according to the program tracking context suitable for the second micro service node, and sends the program tracking data to the program tracking center, and the second micro service node can also further call other micro service nodes.
More intuitively, some embodiments of the present application further provide a schematic diagram of an interaction flow between a plurality of subjects involved in the method of fig. 1 in an application scenario, as shown in fig. 3. The multiple principals include a browser, two microservices nodes (node a, node B), and a program tracking center.
A user a performs service function operation on a browser, the browser sends a user request in response to the user operation to call a node A to complete a certain service function, and supposing that SQL call occurs in the node A in the service processing process corresponding to the user request, the node A also calls a certain function of a node B, the browser and the node A communicate with each other by adopting an HTTP protocol, and the node A and the node B also communicate with each other by adopting the HTTP protocol.
Program tracking parameters are preconfigured. For example, a user a configures a tracking time for itself for 10 minutes, according to the configuration, the system automatically stops program tracking after 10 minutes, and automatically stores the configuration in a program tracking center, so that a user request sent by the user a can automatically carry a Cookie with a specific identifier within the program tracking time, and the value taking indicates that program tracking is to be performed, if the Cookie is 1.
After a user a initiates a user request to a node a, because the user request includes a Cookie, trace is 1, the node a obtains program tracking parameters of the user a from a program tracking center and generates a program tracking context corresponding to the user request, such as { "enabled": true, "traceId": ti01 and "span ID": null }, where the parameters indicate that the request starts program tracking, and the tracking ID of the request is ti01, and program tracking data does not exist currently.
In response to a user request from user a, node a generates a trace 1, which is:
meaning that the trace data does not have a parent trace data ID (because the trace data is the first piece), the trace data ID is 1, the type is an HTTP request, the method of the HTTP request is GET, the timestamp of the receipt of the request is 1591856949939, the end time of the request is null (because the request has not ended), the response code of the request is null (because the request has not ended), and the trace data ID in the program trace context becomes 1 after the trace data is created.
As mentioned previously, a SQL call is made in node A. Before the SQL call, a trace 2 is generated, which is:
the parent trace ID in the trace data is 1 (because the HTTP request is not completed when the trace data is created, the trace data generated by the HTTP request is the parent of the trace data), the type is SQL call, the used SQL statement is select from table, the start timestamp is 1591856949959, and the end timestamp is null (because the SQL call is not completed). After this trace data is created, the trace data ID in the program trace context becomes 2.
After the SQL call is completed, the end time in the trace data is supplemented, and then the trace data called by the SQL is:
at this point the trace data is complete, it is sent to the program trace center, and the trace data ID in the program trace context is set to 1.
As mentioned above, node a may also invoke a function in node B, and when the program tracking context corresponding to the request in node a is { "enabled": true, "traceId": ti01 "," spanId ": 1}, node a converts it into a program tracking context across nodes and appends it to the request invoking node B in various ways according to the request type, for example, in a Header manner for HTTP requests, such as: the meaning of the Trace-Header: ti01:1:1 indicates that the current tracking ID is ti01, the tracking data ID is 1, and the tracking state of the current request is on.
After receiving the request, the node B extracts the program tracking context across the nodes from the request, and creates the program tracking context of the node B according to the program tracking context, such as { "enabled": true, "traceId": ti01 "," spanId ": 1 }. Since the current tracking state is on, the node B will generate a tracking data 3 for the received HTTP request, such as:
after generation, the trace data ID in the program trace context associated with the request in node B is changed to 3. After the request is completed, the incomplete information will be supplemented, and finally the complete form of the trace data is:
the trace data is sent to the program tracking center and the program tracking context is automatically destroyed.
After the node A receives the response information of the node B and the function processing is completed, the node A returns the request result, and when the request is completed, the incomplete tracking data 1 is supplemented, and the final result is
The trace data is sent to the program tracking center and the program tracking context is automatically destroyed.
After receiving a series of trace data, the program tracking center will construct the component call relation tree of the trace by itself, such as:
based on the same idea, some embodiments of the present application further provide devices and media corresponding to the above system.
Some embodiments of the present application provide a program tracking device supporting a micro service architecture, which is loaded with a first micro service node, and the device includes:
at least one processor; and the number of the first and second groups,
a memory communicatively coupled to the at least one processor; wherein,
the memory stores instructions executable by the at least one processor to enable the at least one processor to:
the first micro service node acquires a pre-configured program tracking parameter;
generating program tracking data of the first micro service node according to the program tracking parameters;
and if the first micro service node calls a second micro service node, indicating the second micro service node to continue program tracking so as to generate program tracking data of the second micro service node.
Some embodiments of the present application provide a program tracking medium supporting a microservice architecture, the medium comprising a non-volatile computer storage medium storing computer-executable instructions for application to a first microservice node, the computer-executable instructions configured to:
the first micro service node acquires a pre-configured program tracking parameter;
generating program tracking data of the first micro service node according to the program tracking parameters;
and if the first micro service node calls a second micro service node, indicating the second micro service node to continue program tracking so as to generate program tracking data of the second micro service node.
The embodiments in the present application are described in a progressive manner, and the same and similar parts among the embodiments can be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the device and media embodiments, the description is relatively simple as it is substantially similar to the method embodiments, and reference may be made to some descriptions of the method embodiments for relevant points.
The device, the medium and the method provided by the embodiment of the application are corresponding, so that the device and the medium also have similar beneficial technical effects as the corresponding method.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a system, apparatus, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.
Claims (10)
1. A program tracing method for supporting a micro-service architecture, comprising:
the method comprises the steps that a first micro service node obtains a pre-configured program tracking parameter;
generating program tracking data of the first micro service node according to the program tracking parameters;
and if the first micro service node calls a second micro service node, indicating the second micro service node to continue program tracking so as to generate program tracking data of the second micro service node.
2. The method of claim 1, wherein the method further comprises:
and sending the program tracking data of the first micro service node to a preset program tracking center so that the program tracking center can collect the program tracking data of the first micro service node and the program tracking data of the second micro service node.
3. The method of claim 1, wherein the method further comprises:
and generating a component calling relation tree in the nodes of the first micro service node and the second micro service node and among the nodes according to the program tracking data of the first micro service node and the program tracking data of the second micro service node.
4. The method of claim 1, wherein the first microservice node obtaining preconfigured program trace parameters, comprises:
receiving a user request;
and responding to the user request, and acquiring the program tracking parameters configured for the user corresponding to the user request from the program tracking parameters configured for different users in advance.
5. The method of claim 4, wherein prior to generating program trace data for the first microservice node, the method further comprises:
acquiring a specific identifier carried by the user request and used for indicating whether to perform program tracking;
determining that the particular identifier indicates that program tracking is to be performed.
6. The method of claim 1, wherein generating program trace data for the first microservice node based on the program trace parameters comprises:
generating a first program tracking context according to the program tracking parameters;
and generating program tracking data of the first micro service node according to the first program tracking context.
7. The method of claim 6, wherein instructing the second microservice node to continue program tracking comprises:
generating a second program tracking context according to the first program tracking context;
and instructing the second micro service node to continue program tracking according to the second program tracking context, wherein the second program tracking context is used for associating the program tracking data of the first micro service node with the program tracking data of the second micro service node.
8. The method of claim 7, wherein the first program trace context, the second program trace context, comprise at least one of the following: the first tracking identifier is used for marking program tracking data belonging to the same component calling relationship tree; and the second tracking identifier is used for marking the program tracking data generated corresponding to the last call.
9. A program tracking device supporting a microservice architecture, the device having a first microservice node installed thereon, the device comprising:
at least one processor; and the number of the first and second groups,
a memory communicatively coupled to the at least one processor; wherein,
the memory stores instructions executable by the at least one processor to enable the at least one processor to:
the first micro service node acquires a pre-configured program tracking parameter;
generating program tracking data of the first micro service node according to the program tracking parameters;
and if the first micro service node calls a second micro service node, indicating the second micro service node to continue program tracking so as to generate program tracking data of the second micro service node.
10. A program tracking medium supporting a microservice architecture, storing computer-executable instructions, for application to a first microservice node, the computer-executable instructions configured to:
the first micro service node acquires a pre-configured program tracking parameter;
generating program tracking data of the first micro service node according to the program tracking parameters;
and if the first micro service node calls a second micro service node, indicating the second micro service node to continue program tracking so as to generate program tracking data of the second micro service node.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010604143.9A CN111913789A (en) | 2020-06-29 | 2020-06-29 | Program tracking method, device and medium supporting micro-service architecture |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010604143.9A CN111913789A (en) | 2020-06-29 | 2020-06-29 | Program tracking method, device and medium supporting micro-service architecture |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111913789A true CN111913789A (en) | 2020-11-10 |
Family
ID=73226695
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010604143.9A Pending CN111913789A (en) | 2020-06-29 | 2020-06-29 | Program tracking method, device and medium supporting micro-service architecture |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111913789A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2022111154A1 (en) * | 2020-11-30 | 2022-06-02 | International Business Machines Corporation | Proactive anomaly detection |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20180113790A1 (en) * | 2016-10-20 | 2018-04-26 | Cisco Technology, Inc. | Agentless distributed monitoring of microservices through a virtual switch |
| CN109921927A (en) * | 2019-02-20 | 2019-06-21 | 苏州人之众信息技术有限公司 | Real-time calling D-chain trace method based on micro services |
| CN109992465A (en) * | 2017-12-29 | 2019-07-09 | 中国电信股份有限公司 | Service tracks method, apparatus and computer readable storage medium |
| CN110069358A (en) * | 2019-04-18 | 2019-07-30 | 彩讯科技股份有限公司 | Call chain trace analysis method, apparatus, electronic equipment and storage medium |
| CN110445643A (en) * | 2019-07-25 | 2019-11-12 | 泰康保险集团股份有限公司 | Asynchronous micro services call link tracking, device, medium and electronic equipment |
| CN110730246A (en) * | 2019-10-23 | 2020-01-24 | 家乡互动(厦门)网络科技有限公司 | Distributed link tracking method under micro-service architecture |
| CN111078504A (en) * | 2019-12-25 | 2020-04-28 | 深圳前海环融联易信息科技服务有限公司 | Distributed call chain tracking method and device, computer equipment and storage medium |
| CN111277643A (en) * | 2020-01-18 | 2020-06-12 | 深圳市麦谷科技有限公司 | HTTP link tracking recording method and system |
-
2020
- 2020-06-29 CN CN202010604143.9A patent/CN111913789A/en active Pending
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20180113790A1 (en) * | 2016-10-20 | 2018-04-26 | Cisco Technology, Inc. | Agentless distributed monitoring of microservices through a virtual switch |
| CN109992465A (en) * | 2017-12-29 | 2019-07-09 | 中国电信股份有限公司 | Service tracks method, apparatus and computer readable storage medium |
| CN109921927A (en) * | 2019-02-20 | 2019-06-21 | 苏州人之众信息技术有限公司 | Real-time calling D-chain trace method based on micro services |
| CN110069358A (en) * | 2019-04-18 | 2019-07-30 | 彩讯科技股份有限公司 | Call chain trace analysis method, apparatus, electronic equipment and storage medium |
| CN110445643A (en) * | 2019-07-25 | 2019-11-12 | 泰康保险集团股份有限公司 | Asynchronous micro services call link tracking, device, medium and electronic equipment |
| CN110730246A (en) * | 2019-10-23 | 2020-01-24 | 家乡互动(厦门)网络科技有限公司 | Distributed link tracking method under micro-service architecture |
| CN111078504A (en) * | 2019-12-25 | 2020-04-28 | 深圳前海环融联易信息科技服务有限公司 | Distributed call chain tracking method and device, computer equipment and storage medium |
| CN111277643A (en) * | 2020-01-18 | 2020-06-12 | 深圳市麦谷科技有限公司 | HTTP link tracking recording method and system |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2022111154A1 (en) * | 2020-11-30 | 2022-06-02 | International Business Machines Corporation | Proactive anomaly detection |
| GB2617003A (en) * | 2020-11-30 | 2023-09-27 | Ibm | Proactive anomaly detection |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112910945B (en) | Request link tracking method and service request processing method | |
| CN112035317B (en) | Micro-service link monitoring method, device, equipment and medium | |
| CN111078504A (en) | Distributed call chain tracking method and device, computer equipment and storage medium | |
| CN106375458B (en) | Service calling system, method and device | |
| CN113032419B (en) | Multi-source data aggregation search method, device, equipment and storage medium | |
| CN108462598B (en) | Log generation method, log analysis method and device | |
| CN106411970B (en) | A kind of fault handling method based on service call, device and system | |
| CN111459760B (en) | Micro-service monitoring method and device and computer storage medium | |
| CN111355802B (en) | Information pushing method and device | |
| CN114745295A (en) | Data acquisition method, device, equipment and readable storage medium | |
| CN114153806A (en) | File storage method, device, equipment and storage medium | |
| CN103685354A (en) | Method and device for testing based on RMI protocol | |
| CN105099769A (en) | Method, device and system for processing abnormal operations of service platform | |
| CN105141653A (en) | Method, equipment and system for data interaction of service platform | |
| CN113127335B (en) | System testing method and device | |
| CN113596078A (en) | Service problem positioning method and device | |
| CN113987401A (en) | Recording method and device of network general log, storage medium and processor | |
| CN111913789A (en) | Program tracking method, device and medium supporting micro-service architecture | |
| CN116974948B (en) | Service system testing method, system, equipment and medium | |
| CN112579877B (en) | Control method, device, storage medium and equipment of information source system | |
| CN110543401B (en) | Hierarchical application topology generation method, hierarchical application topology generation system and hierarchical application topology cluster | |
| CN114895852A (en) | Data processing method, system, device, storage medium and electronic equipment | |
| CN112769928B (en) | Information interaction method and device based on service scene | |
| CN108810299B (en) | Information analysis method, medium and equipment | |
| CN114629788B (en) | Configuration information updating method, system, storage medium and electronic device |
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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20201110 |