Link radiography method and system of micro-service system

By generating link contrast images to display the global link information of the microservice system, the problem of long-term failure location of microservice system is solved, and a rapid understanding of the mutual influence of microservices is achieved, and maintenance efficiency is improved.

CN119007947APending Publication Date: 2024-11-22SHENZHEN YISHIHUOLALA TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411099323.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-12
Publication Date
2024-11-22

AI Technical Summary

Technical Problem

When a microservice system fails, it is necessary to analyze the code of multiple microservice modules to locate the source of the failure, which makes the maintenance process long and it is difficult to quickly understand the mutual influence between each microservice.

Method used

Provide a link contrast method for microservice systems, which can obtain system operation data, process global link information, generate link contrast images, display the relationship and performance indicators between microservices, assist in quickly locate the source of failures, and improve maintenance. efficiency.

Benefits of technology

Through the visual display of link contrast images, relevant personnel can quickly understand the mutual influence between each microservice module in the microservice system, significantly improving maintenance efficiency and reducing the need to consult code.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119007947A_ABST
    Figure CN119007947A_ABST
Patent Text Reader

Abstract

The invention discloses a link radiography method and system for a micro-service system. The method comprises the steps of obtaining system operation data generated during operation of the micro-service system; processing the system operation data to obtain global link information of the micro-service system, the global link information including information related to a micro-service link operated in the micro-service system; and displaying a link contrast image according to the global link information, wherein the link contrast image is used for representing the micro-service link.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of microservice technology, and in particular to a link imaging method and system for a microservice system. Background Art

[0002] Microservice architecture has been widely used in many fields such as Internet logistics and online shopping. A system based on microservice architecture, that is, a microservice system, is composed of several microservice modules with different functions. Multiple microservice modules cooperate with each other to achieve specific functions, such as user registration, creation of logistics orders, and coordination of carrier vehicles in the Internet logistics system.

[0003] This characteristic of the microservice system has created certain obstacles to system maintenance. When a function of the system fails, technicians often need to analyze the code of multiple microservice modules to determine the mutual influence between the microservice modules, so as to locate the source of the failure. This process is often time-consuming. Summary of the invention

[0004] To this end, this application discloses the following technical solutions:

[0005] The first aspect of the present application provides a link imaging method for a microservice system, comprising:

[0006] Obtain system operation data generated when the microservice system is running;

[0007] Processing the system operation data to obtain global link information of the microservice system, wherein the global link information includes information related to microservice links running in the microservice system;

[0008] A link imaging image is displayed according to the global link information, wherein the link imaging image is used to characterize the microservice link, and the microservice link includes an association relationship between each microservice in the microservice system.

[0009] Optionally, also include:

[0010] When a change in the microservice link is detected according to the global link information, the microservice link before the change and the microservice link after the change are displayed in different display modes in the link angiography image.

[0011] Optionally, also include:

[0012] In response to a fault prompt message of the microservice system, analyzing a target microservice that is a source of the fault according to the global link information;

[0013] The target microservice is displayed in the link angiography image in a first display mode, the first display mode is different from a second display mode, and the second display mode is a display mode of a non-target microservice.

[0014] Optionally, the global link information includes the running status of multiple microservices in the microservice link, the calling relationship between microservices and the performance indicators of the microservices;

[0015] The link angiography image includes:

[0016] A microservice icon corresponding to the plurality of microservices in the microservice link, wherein an icon attribute of the microservice icon is used to indicate a running state of the corresponding microservice;

[0017] A connection line connecting two microservice icons, wherein the connection line corresponds to the call relationship;

[0018] Performance indicator information associated with the microservice icon, the performance indicator information is used to indicate a performance indicator of the corresponding microservice.

[0019] Optionally, the performance indicator information includes a performance indicator curve graph, and the performance indicator curve graph includes performance indicators of corresponding microservices at different times.

[0020] Optionally, obtaining the system operation data generated when the microservice system is running includes at least one of the following:

[0021] Monitor the message queues of each microservice in the microservice system, and obtain the microservice messages in the message queues as system operation data;

[0022] Receiving system operation data uploaded by the input terminal according to user operation instructions;

[0023] The operation logs of each microservice in the microservice system are collected as system operation data.

[0024] Optionally, also include:

[0025] Preprocessing the system operation data to obtain preprocessed system operation data, wherein the preprocessing includes at least one of data cleaning and data conversion;

[0026] The processing of the system operation data to obtain global link information of the microservice system includes:

[0027] The preprocessed system operation data is processed to obtain global link information of the microservice system.

[0028] Optionally, also include:

[0029] Performing traffic simulation processing on the microservice link according to the global link information;

[0030] The simulation result corresponding to the traffic simulation process is displayed in the link imaging image.

[0031] Optionally, also include:

[0032] In response to a request from a communication client, the link contrast image is sent to the communication client.

[0033] A second aspect of the present application provides a link imaging system for a microservice system, comprising:

[0034] The collection module is used to obtain the system operation data generated when the microservice system is running;

[0035] Imaging module for:

[0036] Processing the system operation data to obtain global link information of the microservice system, wherein the global link information includes information related to microservice links running in the microservice system;

[0037] A link imaging image is displayed according to the global link information, wherein the link imaging image is used to characterize the microservice link, and the microservice link includes an association relationship between each microservice in the microservice system.

[0038] The beneficial effects of this solution are:

[0039] Based on the global link information of the microservice system, the association relationship between each microservice in the microservice system is visualized in the form of link imaging images, so as to assist relevant personnel to quickly and conveniently understand the mutual influence between each microservice module in the microservice system without consulting the code, thereby achieving the effect of improving the maintenance efficiency of the microservice system. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the related technologies, the drawings required for use in the embodiments or the related technical descriptions are briefly introduced below. Obviously, the drawings described below are merely embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying any creative work.

[0041] Figure 1 It is a flow chart of a link imaging method of a microservice system provided in an embodiment of the present application;

[0042] Figure 2 is a schematic diagram of a link angiography image provided in an embodiment of the present application;

[0043] Figure 3 It is a schematic diagram of a link imaging system of a microservice system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0044] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0045] This application embodiment provides a link imaging method for a microservice system, see Figure 1 , the method may include the following steps.

[0046] S101, obtaining system operation data generated when the microservice system is running.

[0047] The imaging method of this embodiment can be executed by a link imaging system running on a server.

[0048] In step S101, the link imaging system can capture the system operation data generated by the microservice system in real time in a variety of ways. This embodiment does not limit the source of the system operation data.

[0049] As some examples, the system operation data may include at least one of microservice messages of each microservice module (hereinafter referred to as microservice), manually entered data uploaded by an input terminal, and operation logs of microservices.

[0050] Correspondingly, in step S101, the link imaging system may obtain system operation data in at least one of the following capture modes:

[0051] Capture method 1: monitor the message queues of each microservice in the microservice system and obtain the microservice messages in the message queue as system operation data;

[0052] Capture method 2, receiving system operation data uploaded by the input terminal according to user operation instructions;

[0053] Capture method three: collect the operation logs of each microservice in the microservice system as system operation data.

[0054] In capture method one, the link imaging system can call the message queue interface of each microservice, and monitor the message queue of each microservice in real time through the message queue interface. When a new microservice message is detected in the message queue, the microservice message is copied to the link imaging system. The copied microservice message is equivalent to the system operation data.

[0055] The microservices in the microservice system interact with each other by transmitting microservice messages, and each microservice generally has a receiving message queue for receiving microservice messages and a sending message queue for sending microservice messages. The former is used to store microservice messages received by the microservice but not yet processed, and the latter is used to store microservice messages generated by the microservice that need to be sent to other microservices. The link imaging system can monitor the receiving message queue and the sending message queue respectively, and capture the microservice messages in the two queues as system operation data.

[0056] In the second capture method, the operation and maintenance personnel of the microservice system can operate the input terminal and manually enter the system operation data on the input terminal. Then, the input terminal responds to the upload operation instruction and uploads the system operation data manually entered by the operation and maintenance personnel to the link imaging system.

[0057] In capture method three, the link imaging system can periodically access the operation logs of each microservice in the microservice system. Each time it accesses, it copies the newly added log data in the operation log from the current time to the time of the previous access to the link imaging system, and uses the copied log data as the system operation data.

[0058] S102, processing the system operation data to obtain global link information of the microservice system, where the global link information includes information related to the microservice links running in the microservice system.

[0059] In some optional embodiments, the link imaging system may perform the following steps before performing S102:

[0060] Preprocessing the system operation data to obtain preprocessed system operation data, wherein the preprocessing includes at least one of data cleaning and data conversion;

[0061] Correspondingly, S102 may be replaced by: processing the preprocessed system operation data to obtain global link information of the microservice system.

[0062] That is, before processing to obtain the global link information, the link imaging system may perform data cleaning on the system operation data, may perform data conversion on the system operation data, or may perform data cleaning and data conversion on the system operation data.

[0063] Data cleaning of system operation data refers to identifying abnormal data in the system operation data and deleting these abnormal data. The way to identify abnormal data can be to determine whether the value of each data is within its corresponding reasonable value range. If it is within this range, it is determined that the data is normal data and retained. If it is not within this range, it is identified as abnormal data and deleted.

[0064] Data conversion of system operation data refers to converting the system operation data from the current data format into a specific target data format. The target data format is not limited. As an example, the target data format may be a table data format. Correspondingly, when performing data conversion, the link imaging system may parse the field values ​​corresponding to each field in the table from the system operation data, and fill the field values ​​into the corresponding fields of the table. The filled table is the system operation data converted into a table format.

[0065] The advantage of preprocessing the system operation data before processing it is that, on the one hand, data cleaning can delete abnormal data to avoid the global link information obtained from processing containing erroneous information, thereby ensuring the correctness of the link angiography images displayed subsequently; on the other hand, system operation data from various sources and formats can be converted into a unified target data format through data conversion, which is conducive to improving the execution efficiency of the subsequent steps of obtaining global link information and link angiography images.

[0066] In this embodiment, the global link information may include the following information:

[0067] The running status of multiple microservices in the microservice chain, the calling relationship between microservices, and the performance indicators of microservices.

[0068] In this embodiment, the microservice link can correspond to the functions implemented by the microservice system. Taking the Internet logistics system as an example, multiple microservices that implement the user registration function constitute a user registration microservice link, multiple microservices that implement the logistics order creation function constitute a creation order microservice link, and multiple microservices that implement the coordination of carrier vehicles constitute a capacity coordination microservice link.

[0069] When the system operation data includes microservice messages, the link imaging system can process the microservice messages as follows to obtain the above global link information:

[0070] First, the link mapping system parses the microservice message to determine the microservice that sends the microservice message and the microservice that receives the microservice message, thereby determining which two microservices belong to the same microservice link;

[0071] by Figure 2 (1) is an example. After parsing a microservice message received by microservice 2, the link imaging system finds that the message is sent by microservice 1 to microservice 2, so it is determined that microservice 1 and microservice 2 belong to the same microservice link. Similarly, after parsing a microservice message received by microservice 3, it can be determined that microservice 2 and microservice 3 belong to the same microservice link, thereby determining that microservices 1, 2 and 3 belong to the same microservice link.

[0072] Then, the link imaging system analyzes the content of the microservice message and determines the call relationship between the sender and the receiver based on the content. For example, if the content of the microservice message is that the sender requires the receiver to feedback specific data, then the call relationship can be determined as the sender calling the receiver; if the content of the microservice message is that the sender responds to the receiver's request and feedbacks specific data to the receiver, then the call relationship can be determined as the receiver calling the sender;

[0073] by Figure 2 (1) is an example. Assuming that after parsing the microservice message sent by microservice 1 to microservice 2, it is found that the content of the message is microservice 1 requesting microservice 2 to feedback specific data, then it can be determined that the calling relationship between the two is microservice 1 calling microservice 2;

[0074] Finally, the link imaging system counts the number and type of microservice messages sent and received by a microservice within a period of time to obtain the performance indicators of the microservice. Performance indicators include but are not limited to flow indicators, processing efficiency indicators, etc. For example, the number of microservice messages sent by the microservice in a unit time is counted to obtain the flow indicator of the microservice, and the amount of valid data output by the microservice in a unit time is counted to obtain the processing efficiency indicator of the microservice.

[0075] When the system operation data includes manually entered data uploaded by the input terminal, the manually entered data generally directly includes the above global link information. For example, the manually entered data may include that microservice link A includes microservice 7 and microservice 8, wherein microservice 7 calls microservice 8, the current flow of microservice 7 is XX, and the current flow of microservice 8 is YY.

[0076] Correspondingly, the link imaging system can directly extract global link information from manually entered data.

[0077] When the system operation data includes the operation logs of microservices, the link imaging system can process the operation logs as follows to obtain the above global link information:

[0078] The operation log of a microservice can record the message sending, message receiving, data processing and other behaviors performed by the microservice in the past period of time;

[0079] The link imaging system analyzes the message receiving and sending behaviors of microservices in the operation logs, and determines which microservices belong to the same microservice link based on these behaviors, as well as the call relationships between microservices on the same microservice link;

[0080] Exemplarily, analyzing the running log of microservice 5 reveals the following message receiving and sending behaviors:

[0081] Microservice 5 sends some data to be processed to Microservice 6, and receives the processing results fed back by Microservice 6;

[0082] Microservice 5 receives some data sent by microservice 4, processes the data and feeds the processing results back to microservice 4;

[0083] Through the above behaviors recorded in the running log, the link imaging system can determine that microservices 4, 5, and 6 belong to the same microservice link, and the calling relationship is that microservice 4 calls microservice 5, and microservice 5 calls microservice 6;

[0084] Then, the link imaging system can analyze the number of times the microservice performs data processing and the amount of data processed in the operation log, as well as the number of times the microservice performs message sending and the number of messages sent in the operation log. Based on the analysis results, the number of messages sent by the microservice per unit time and the amount of data processed can be determined, thereby obtaining performance indicators such as the traffic and processing efficiency of the microservice.

[0085] S103, displaying a link imaging image according to the global link information, where the link imaging image is used to represent the microservice link, and the microservice link includes the association relationship between each microservice in the microservice system.

[0086] After obtaining the global link information, the link imaging system can generate a link imaging image of the microservice system according to the global link information, and then display the link imaging image on the web control center of the link imaging system.

[0087] Based on the global link information obtained in S102, the generated link angiography image may include the following contents:

[0088] A microservice icon corresponding to multiple microservices in a microservice link, wherein the icon attribute of the microservice icon is used to indicate the running status of the corresponding microservice;

[0089] A line connecting two microservice icons, corresponding to the call relationship;

[0090] The performance indicator information associated with the microservice icon is used to indicate the performance indicator of the corresponding microservice.

[0091] The microservice icon may include only a specific graphic or a graphic plus text. Figure 2 The link imaging image shown in (1) is an example. The microservice icon may include a graphic plus text. The text may be the name of the corresponding microservice, for example Figure 2 In (1), microservice 1 plus the upper rectangular frame constitutes the icon of microservice 1, and microservice 2 plus the upper circle constitutes the icon of microservice 2.

[0092] The link imaging image can indicate the running status of the corresponding microservice through different icon attributes, for example, different icon shapes can be used to indicate the load status of the corresponding microservice, and different icon colors can be used to indicate whether the corresponding microservice is in a fault state.

[0093] The running status of a microservice can be determined by the link imaging system based on the global link information. For example, the link imaging system obtains one or more performance indicators of a microservice from the global link information. If these performance indicators are in a higher range, it is determined that the microservice is in a heavily loaded state. If these performance indicators are in a lower range, it is determined that the microservice is in a lightly loaded state. If these performance indicators are significantly lower than normal values, such as traffic or processing efficiency approaching 0, it is determined that the microservice is in a faulty state.

[0094] by Figure 2 (1) is an example. The link imaging system can use a rectangular box as the microservice icon of microservice 1 in the link imaging system, indicating that the current load of microservice 1 is relatively light and less data needs to be processed, and use a circle as the microservice icon of microservice 2, indicating that the current load of microservice 2 is relatively heavy and more data needs to be processed.

[0095] The connection line between microservices is used to indicate that the two connected microservices belong to the same microservice link, and on the other hand, it is used to indicate the calling relationship between the two connected microservices. Figure 2 (1) is an example. The connection line may have an arrow, and the direction of the arrow represents the call relationship. For example, based on Figure 2 As can be seen from the arrows of the connecting line in (1), microservices 1, 2, and 3 belong to the same microservice link, where microservice 1 calls microservice 2, and microservice 2 calls microservice 3.

[0096] The performance indicator information may be in various forms. As an example, the performance indicator information may be a table showing various performance indicators of the corresponding microservice over the past period of time; as an example, the performance indicator information may include the values ​​of the current performance indicators of one or more corresponding microservices; as another example, the performance indicator information may include a performance indicator curve graph including the performance indicators of the corresponding microservice at different times.

[0097] by Figure 2 (1) is an example. The performance indicator information of microservice 1 may include Figure 2 The performance indicator curve chart on the left side of microservice 1 in (1) can show the change trend of the traffic of microservice 1 over time in the past period of time.

[0098] The beneficial effect of this embodiment is that, based on the global link information of the microservice system, the association relationship between each microservice in the microservice system is visualized in the form of link imaging images, thereby assisting relevant personnel to quickly and conveniently understand the mutual influence between each microservice module in the microservice system without consulting the code, thereby achieving the effect of improving the maintenance efficiency of the microservice system.

[0099] In some optional embodiments, the link imaging system may further perform the following steps:

[0100] When a change in a microservice link is detected according to the global link information, the microservice link before the change and the microservice link after the change are displayed in different display modes in the link contrast image.

[0101] The link imaging system can periodically capture the system operation data of the microservice system in real time, for example, capturing the system operation data every 10 minutes. After capturing new system operation data each time, the link imaging system obtains new global link information based on processing the new system operation data, and then compares the new global link information with the global link information obtained last time. If the two are consistent, the link imaging system may not update the link imaging image. If the two are inconsistent, the link imaging system updates the link imaging image according to the newly obtained global link information.

[0102] Among them, if the running status of the microservice changes between the new global link information and the previous global link information, the link imaging system can directly update the icon attributes of the corresponding microservice icon in the link imaging image, and represent the latest status of the microservice through the changed icon attributes.

[0103] by Figure 2 (1) is an example. Assuming that microservice 1 is under heavy load in the new global link information, the link imaging system can Figure 2 In (1), the icon of microservice 1 changes from a rectangle to a circle to indicate that microservice 1 is currently under heavy load.

[0104] If the performance indicator of the microservice changes between the new global link information and the previous global link information, the link imaging system can directly update the corresponding performance indicator information in the link imaging image to represent the new performance indicator after the change.

[0105] For example, before the change, the traffic of microservice 1 was 10 megabits per second (MB / s), and in the new global link information, the traffic of microservice 1 becomes 20 megabits per second (MB / s). The link imaging system can directly change the performance indicator information representing the traffic in the link imaging image from 10 megabits per second (MB / s) to 20 megabits per second (MB / s).

[0106] If the connection relationship and / or call relationship between microservices changes between the new global link information and the previous global link information, the link imaging system can update the link imaging image so that the microservice link before the change (that is, the microservice link corresponding to the previous global link information) and the microservice link after the change (that is, the microservice link corresponding to the new global link information) are displayed in the link imaging image, as well as the microservice link before the change and the microservice link after the change.

[0107] Still Figure 2 For example, Figure 2 (1) is the link angiography image before updating, Figure 2 (2) is the link angiography image after the change, Figure 2 In (1), the microservice links indicated by the previous global link information are microservice 1, microservice 2 and microservice 3, and the calling relationship is as follows Figure 2 shown in (1); Figure 2 (2) indicates that in the updated link imaging image, based on the new global link information, the above-mentioned microservice links are changed to microservice 1, microservice 7 and microservice 3, so the link imaging system displays the links of microservice 1, microservice 2 and microservice 3, as well as microservice 1, microservice 7 and microservice 3 in the updated link imaging image, the former is represented by a dotted line and the latter is represented by a solid line, thereby indicating that the microservice link is changed from the original 1-2-3 to 1-7-3.

[0108] In some optional embodiments, the link imaging system of this embodiment may further perform the following steps:

[0109] In response to a fault prompt message of the microservice system, a target microservice that is the source of the fault is analyzed based on global link information;

[0110] The target microservice is displayed in a first display mode in the link angiography image. The first display mode is different from the second display mode. The second display mode is a display mode of the non-target microservice.

[0111] The microservice system can output a fault prompt message to the link imaging system when it detects that any function is not executed normally.

[0112] For example, taking the Internet logistics system as an example, assuming that a new user fails to register or an old user fails to log in, the microservice system can determine that the user registration and login functions are abnormal, and output a fault prompt message to the link imaging system; assuming that the carrier driver fails to accept an order, the microservice system can determine that the function of coordinating the carrier vehicle is abnormal, and output a fault prompt message to the link imaging system.

[0113] The fault prompt message may indicate a faulty function, for example, it may indicate a fault in the current user registration and login function, or a fault in the function of coordinating transport vehicles.

[0114] After receiving the fault prompt message, the link imaging system first locates the microservice link used to implement the function based on the faulty function indicated by the fault prompt message, and then detects which microservices in the microservice link are in a faulty state in the link imaging image.

[0115] After identifying multiple microservices in a faulty state on the corresponding microservice link, the link imaging system can determine the target microservice that is the source of the fault based on the call relationship indicated in the link imaging image.

[0116] The target microservice may be determined by, for each microservice in a fault state, determining whether the microservice calls other microservices on the link, and determining whether other microservices called by the microservice are in a fault state;

[0117] If a microservice is in a faulty state and does not call other microservices on the same link, it can be determined that this microservice belongs to the target microservice;

[0118] If a microservice is in a faulty state and calls other microservices on the same link, but the other called microservices are not in a faulty state, it can be determined that this microservice belongs to the target microservice;

[0119] If a microservice is in a faulty state and calls other microservices on the same link, and the other called microservices are also in a faulty state, it can be determined that this microservice does not belong to the target microservice.

[0120] As an example, assuming that microservice A is in a faulty state and does not call other microservices on the same link, it can be determined that microservice A belongs to the target microservice;

[0121] Assume that microservice B is in a faulty state and calls another microservice C on the same link, but the called microservice C is not in a faulty state, it can be determined that microservice B belongs to the target microservice;

[0122] Assuming that microservice D is in a faulty state and calls other microservice E on the same link, and the called microservice E is also in a faulty state, it can be determined that microservice D does not belong to the target microservice.

[0123] After determining the target microservice, the link imaging system may display the target microservice in a first display mode in the link imaging image, where the first display mode is different from a second display mode, and the second display mode is a display mode of a non-target microservice.

[0124] That is, the link imaging system can display the icons of the target microservice and the icons of the non-target microservices in different display modes in the link imaging image, so that relevant users can quickly find the target microservice and perform targeted maintenance.

[0125] Exemplarily, the link imaging system may display the icon of the target microservice in a flashing manner and the icon of the non-target microservice in a static manner in the link imaging system; or the link imaging system may display the icon of the target microservice in red and the icon of the non-target microservice in green in the link imaging system.

[0126] Optionally, the link imaging system may also display connection lines between multiple microservices in a faulty state in a link imaging image using a first display mode, thereby displaying a fault propagation path.

[0127] Optionally, the link imaging system can also send a fault alarm message to the terminal device of the relevant maintenance personnel. The fault alarm message can describe the fault propagation path and the target microservice so that the relevant maintenance personnel can handle the fault in time.

[0128] In some optional embodiments, the link imaging system may further perform the following steps:

[0129] Perform traffic simulation on microservice links based on global link information;

[0130] The simulation results corresponding to the traffic simulation processing are displayed in the link imaging image.

[0131] The traffic simulation process is as follows:

[0132] The link imaging system can select a microservice link that needs to be simulated for traffic from multiple microservice links displayed in the link imaging image according to the user's operation instructions, and then generate a certain number of multiple simulated business requests for each microservice included in the microservice link and send them to the microservice, and detect the performance indicators of the microservice within a period of time after sending these simulated business requests, and display the detected performance indicators as simulation results on the link imaging image.

[0133] By performing traffic simulation processing, relevant users can understand the carrying capacity of each microservice on the specified microservice link to facilitate the maintenance and upgrade of the microservice.

[0134] In some optional embodiments, the link imaging system may also send the link imaging image to the communication client in response to a request of the communication client.

[0135] In this embodiment, relevant maintenance personnel can remotely access the link imaging system on the communication client and send a request to the link imaging system to browse the current link imaging image. The link imaging system responds to the request and sends the current link imaging image to the communication client, so that relevant maintenance personnel can remotely browse the link imaging image.

[0136] The present application also provides a link imaging system for a microservice system. Figure 3 , the system may include:

[0137] The collection module 301 is used to obtain the system operation data generated when the microservice system is running;

[0138] The imaging module 302 is used for:

[0139] Processing the system operation data to obtain global link information of the microservice system, where the global link information includes information related to the microservice links running in the microservice system;

[0140] A link imaging image is displayed according to the global link information. The link imaging image is used to characterize the microservice link. The microservice link includes the association relationship between each microservice in the microservice system.

[0141] In this embodiment, the imaging module 302 may include an initialization module, a frame analysis module, an overlapping image analyzer and an end rendering analyzer.

[0142] Among them, the initialization module can perform initialization operations when the link imaging system is started, such as clearing cached data, restoring various parameters to default values, etc.

[0143] The frame parsing module can be used to parse global link information and generate graphic elements such as icons, connection lines, performance indicator information, etc. that represent microservices in link imaging images.

[0144] The overlay resolver can overlay the graphic elements output by the frame analysis module onto an image to obtain a link angiography image.

[0145] The end rendering parser is used to render the link contrast image output by the overlap parser to the web control center.

[0146] Optionally, the imaging module 302 is further used for:

[0147] When a change in a microservice link is detected according to the global link information, the microservice link before the change and the microservice link after the change are displayed in different display modes in the link contrast image.

[0148] Optionally, the imaging module 302 is further used for:

[0149] In response to a fault prompt message of the microservice system, a target microservice that is the source of the fault is analyzed based on global link information;

[0150] The target microservice is displayed in a first display mode in the link angiography image. The first display mode is different from the second display mode. The second display mode is a display mode of the non-target microservice.

[0151] Optionally, the global link information includes the running status of multiple microservices in the microservice link, the calling relationship between microservices, and the performance indicators of the microservices;

[0152] Link angiography images include:

[0153] A microservice icon corresponding to multiple microservices in a microservice link, wherein the icon attribute of the microservice icon is used to indicate the running status of the corresponding microservice;

[0154] A line connecting two microservice icons, corresponding to the call relationship;

[0155] The performance indicator information associated with the microservice icon is used to indicate the performance indicator of the corresponding microservice.

[0156] Optionally, the performance indicator information includes a performance indicator curve graph, and the performance indicator curve graph includes performance indicators of corresponding microservices at different times.

[0157] Optionally, the imaging module 302 is further used for:

[0158] Preprocessing the system operation data to obtain preprocessed system operation data, wherein the preprocessing includes at least one of data cleaning and data conversion;

[0159] When the imaging module 302 processes the system operation data and obtains the global link information of the microservice system, it can be used to:

[0160] The preprocessed system operation data is processed to obtain the global link information of the microservice system.

[0161] Optional, such as Figure 3 As shown, the system also includes a traffic simulation module for:

[0162] Perform traffic simulation on microservice links based on global link information;

[0163] The simulation results corresponding to the traffic simulation processing are displayed in the link imaging image.

[0164] Optional, such as Figure 3 As shown, the system may include a notification service for:

[0165] In response to a request from the communication client, the link contrast image is sent to the communication client.

[0166] Optionally, the system can also provide an external application program interface (such as Trace OpenAPI and MicroOpenAPI), and the application can call the system of this embodiment through the API to obtain the global link information and / or link imaging images generated by the system of this embodiment, or can remotely access the link imaging system of this embodiment through the API.

[0167] Optionally, the link imaging system of this embodiment can also store the generated global link information and link imaging images in a database, and provide a basic command and query service (basic command and query service) based on the database. Relevant users can access the basic command and query service through the operation and maintenance client provided by the web control center, thereby querying the specified global link information and link imaging images.

[0168] The working principle of the link imaging system of the microservice system provided in this embodiment can refer to the relevant steps of the link imaging method of the microservice system provided in any embodiment of the present application, and will not be repeated here.

[0169] It should be noted that the various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the various embodiments can be referenced to each other.

[0170] For the convenience of description, the above system or system is described by dividing the functions into various modules or units. Of course, when implementing the present application, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0171] It can be known from the description of the above implementation methods that those skilled in the art can clearly understand that the present application can be implemented by means of software plus a necessary general hardware platform. Based on such an understanding, the technical solution of the present application can be essentially or partly contributed to the relevant technology in the form of a software product, which can be stored in a storage medium such as ROM / RAM, a disk, an optical disk, etc., including several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in the various embodiments of the present application or certain parts of the embodiments.

[0172] Finally, it should be noted that, in this article, relational terms such as first, second, third and fourth are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the statement "comprise a ..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.

[0173] The above is only a preferred implementation of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A link imaging method for a microservice system, characterized in that: include: Obtain system operation data generated when the microservice system is running; Processing the system operation data to obtain global link information of the microservice system, wherein the global link information includes information related to microservice links running in the microservice system; A link imaging image is displayed according to the global link information, wherein the link imaging image is used to characterize the microservice link, and the microservice link includes an association relationship between each microservice in the microservice system.

2. The method according to claim 1, characterized in that Also includes: When a change in the microservice link is detected according to the global link information, the microservice link before the change and the microservice link after the change are displayed in different display modes in the link angiography image.

3. The method according to claim 1, characterized in that Also includes: In response to a fault prompt message of the microservice system, analyzing a target microservice that is a source of the fault according to the global link information; The target microservice is displayed in the link angiography image in a first display mode, the first display mode is different from a second display mode, and the second display mode is a display mode of a non-target microservice.

4. The method according to claim 1, characterized in that: The global link information includes the operating status of multiple microservices in the microservice link, the calling relationship between microservices and the performance indicators of microservices; The link angiography image includes: A microservice icon corresponding to the plurality of microservices in the microservice link, wherein an icon attribute of the microservice icon is used to indicate a running state of the corresponding microservice; A connection line connecting two microservice icons, wherein the connection line corresponds to the call relationship; Performance indicator information associated with the microservice icon, the performance indicator information is used to indicate a performance indicator of the corresponding microservice.

5. The method according to claim 4, characterized in that The performance indicator information includes a performance indicator curve graph, and the performance indicator curve graph includes performance indicators of corresponding microservices at different times.

6. The method according to claim 1, characterized in that The obtaining of system operation data generated when the microservice system is running includes at least one of the following: Monitor the message queues of each microservice in the microservice system, and obtain the microservice messages in the message queues as system operation data; Receiving system operation data uploaded by the input terminal according to user operation instructions; The operation logs of each microservice in the microservice system are collected as system operation data.

7. The method according to claim 1, characterized in that Also includes: Preprocessing the system operation data to obtain preprocessed system operation data, wherein the preprocessing includes at least one of data cleaning and data conversion; The processing of the system operation data to obtain global link information of the microservice system includes: The preprocessed system operation data is processed to obtain global link information of the microservice system.

8. The method according to claim 1, characterized in that Also includes: Performing traffic simulation processing on the microservice link according to the global link information; The simulation result corresponding to the traffic simulation process is displayed in the link imaging image.

9. The method according to claim 1, characterized in that: Also includes: In response to a request from a communication client, the link contrast image is sent to the communication client.

10. A link imaging system for a microservice system, characterized in that: include: The collection module is used to obtain the system operation data generated when the microservice system is running; Imaging module for: Processing the system operation data to obtain global link information of the microservice system, wherein the global link information includes information related to microservice links running in the microservice system; A link imaging image is displayed according to the global link information, wherein the link imaging image is used to characterize the microservice link, and the microservice link includes an association relationship between each microservice in the microservice system.