Service calling relation display method and device, equipment and medium

Abstract

The invention relates to the technical field of micro-services and the field of financial science and technology, and provides a service calling relation display method and device, equipment and a medium, and the method comprises the steps: obtaining a service calling relation chain of a business system, the service calling relation chain being used for describing a target service having a calling relation in the business system; obtaining log attribute information of an operation log of the target service; obtaining full-link calling index information of the service calling relation chain; and according to the log attribute information and the full-link calling index information, visually displaying the service calling relation chain in a three-dimensional space in a graphic form. According to the invention, the calling relationship between services in the business system can be visually displayed, so that the operation and maintenance personnel can be assisted to quickly position the fault reason of the business system, and the fault positioning efficiency of the business system is improved.

Description

Technical Field

[0001] The present invention relates to the fields of microservice technology and financial technology, and in particular to a service call relationship display method, a service call relationship display device, an electronic device, and a computer-readable storage medium. Background Art

[0002] In the digital age, microservices architecture has become widespread. An increasing number of business systems, such as insurance, banking, and e-commerce, are adopting it. The core of microservices architecture is the decomposition of large business systems into multiple small, autonomous services. For example, an e-commerce system can be divided into user services, product services, order services, payment services, and logistics services. Each service focuses on a single business function, such as a product service responsible for managing and displaying product information.

[0003] In the continuous iteration and update process of the business system, it includes more and more services. Due to the diversity and dynamic nature of services in the microservice architecture, the calling relationship between services will change frequently. When a service in the business system fails, it often affects other related services, making it difficult for operation and maintenance personnel to quickly locate the cause of the business system failure. Summary of the Invention

[0004] The embodiments of the present invention provide a service call relationship display method, a service call relationship display device, an electronic device and a computer-readable storage medium, which can intuitively display the call relationship between services in a business system, assist operation and maintenance personnel in quickly locating the cause of business system failures, and improve the fault location efficiency of the business system.

[0005] In a first aspect, a method for displaying a service call relationship is provided, comprising: Obtaining a service call relationship chain of a business system, wherein the service call relationship chain is used to describe a target service having a call relationship in the business system; Obtaining log attribute information of the operation log of the target service; Obtaining full-link call indicator information of the service call relationship chain; Based on the log attribute information and the full-link call indicator information, the service call relationship chain is visualized in the form of a graph in three-dimensional space.

[0006] In a second aspect, a service call relationship display device is provided, comprising: A relationship acquisition module is used to acquire a service call relationship chain of a business system, wherein the service call relationship chain is used to describe a target service with a call relationship in the business system; An attribute acquisition module, configured to acquire log attribute information of the operation log of the target service; An indicator acquisition module is used to obtain the full-link call indicator information of the service call relationship chain; A graphic display module is used to visualize the service call relationship chain in the form of a graphic in three-dimensional space based on the log attribute information and the full-link call indicator information.

[0007] In a third aspect, a computer device is provided, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the steps in the above-mentioned service call relationship display method are implemented.

[0008] In a fourth aspect, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps in the above-mentioned service call relationship display method are implemented.

[0009] In the solution implemented by the above-mentioned service call relationship display method, device, equipment and medium, the service call relationship chain of the business system is obtained, which is used to describe the target service with a call relationship in the business system; the log attribute information of the operation log of the target service is obtained; the full-link call indicator information of the service call relationship chain is obtained; and based on the log attribute information and the full-link call indicator information, the service call relationship chain is visualized in the form of a graphic in three-dimensional space. In this way, the call relationship between services in the business system can be visualized and intuitively displayed, thereby assisting operation and maintenance personnel to quickly locate the cause of the business system failure and improve the fault location efficiency of the business system. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments of the present invention. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0011] Figure 1 This is a schematic diagram of an application environment of a service call relationship display method according to an embodiment of the present invention; Figure 2 1 is a flow chart of a method for displaying service call relationships in one embodiment of the present invention; Figure 3 This is an example diagram of maintaining a service call relationship chain in a graph structure in one embodiment of the present invention; Figure 4 This is an example diagram of visually displaying a service call relationship chain A and a service call relationship chain B in three-dimensional space in one embodiment of the present invention; Figure 5This is an example diagram showing an information analysis interface corresponding to a service call relationship chain B in three-dimensional space in one embodiment of the present invention; Figure 6 This is a schematic diagram of the structure of a service call relationship display device in one embodiment of the present invention; Figure 7 is a structural diagram of a computer device in one embodiment of the present invention; Figure 8 FIG. 2 is another structural diagram of a computer device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0012] The following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of them. All other embodiments derived by persons of ordinary skill in the art based on the embodiments of the present invention without inventive effort shall fall within the scope of protection of the present invention.

[0013] The service call relationship display method provided by the embodiment of the present invention can be applied as follows: Figure 1 In the application environment shown, a client communicates with a server via a network. The server can receive a link display request from a user (e.g., a business system operator) through the client and obtain the service call relationship chain of the business system indicated by the link display request. The service call relationship chain describes the target services in the business system that have a call relationship, as well as the call relationship links between the target services. The server can also obtain log attribute information from the target service's operation logs and full-link call metric information for the service call relationship chain. Based on the full-link call metric information and the log attribute information corresponding to the target service, the server can visualize the service call relationship chain in three-dimensional space as a graph. The visualization data is then returned to the client, allowing the client to also visualize the service call relationship chain in three-dimensional space locally. The server can be a standalone server or a server cluster consisting of multiple servers. A client, also known as a user end, is a program that corresponds to a server and provides local services to clients. The client can be installed on, but is not limited to, various computers, laptops, smartphones, tablets, and portable wearable devices.

[0014] See also Figure 2 As shown, Figure 2 A flow chart of a method for displaying service call relationships provided by an embodiment of the present invention includes the following steps: S110: Obtain a service call relationship chain of the business system. The service call relationship chain is used to describe target services that have a call relationship in the business system.

[0015] Business systems are business systems that adopt microservice architecture, such as insurance systems, banking systems, e-commerce systems, etc. that adopt microservice architecture.

[0016] Business requests are generated within the context of business activities and represent specific business actions that users or external systems expect a business system to perform. For example, in an e-commerce system, a user placing an order for a product is a business request; a merchant listing a product is also a business request; in a banking system, a customer-initiated transfer is also a business request, and so on.

[0017] The trace identifier (TraceID) is a unique identifier used to identify the process of a complete business operation (a complete business operation is divided into multiple independent sub-operations and executed by services related to the business system). It is generated when a business request is initiated and then passed between the various target services in the entire call chain.

[0018] In an embodiment of the present application, in response to a link display request, the operation log generated in the business system indicated by the link display request can be obtained, and a call relationship analysis can be performed based on the obtained operation log to determine the call relationship between services in the business system, and then based on the tracking identifier of the business request and the call relationship between services, the service call relationship chain corresponding to different business requests in the business system can be obtained. For a business request, the service call relationship chain of the business request describes the complete call link between the target services involved in the business request, as well as the call time of the target service. Among them, the link display request can be generated by the client in response to the user operation and sent to the server, or it can be automatically triggered by the internal cycle of the server. For example, the server automatically obtains the service call relationship chain in the business system every 10 seconds for subsequent visual display.

[0019] For example, taking the e-commerce system as an example, the operation log generated by a service is obtained as follows: [2025-04-17 14:30:05.234] [INFO][TraceID:78ab12cd34ef56gh] [SpanID:1a2b3c4d5e6f7g8h] [caller:front-end-service] [callee:user-service][Operation:verifyLogin] -Request:{ "username":"emma_smith", "password":"********" } -Response:{ "status":"success", "user_id":56789, "message":"Userloggedinsuccessfully" } - Duration: 200ms The above operation log shows that at 2:30:05:234 PM on April 17, 2025, the front-end service initiated a call to the user service. The user service executed the sub-operation (verifyLogin) with the SpanID "1a2b3c4d5e6f7g8h" in response to the call: the login verification operation. This operation took 200 milliseconds to execute. The call request included the username "emma_smith" and password "********." The user service successfully verified the login information and returned a success status (success). It also provided the user ID "56789" and confirmed that the user had successfully logged in. The above call was initiated by the front-end service in response to the business request with the TraceID "78ab12cd34ef56gh." Accordingly, all operation logs with TraceID "78ab12cd34ef56gh" can be obtained. Based on the calling relationships between services recorded in these operation logs, the complete service calling relationship chain of the business system's overall response to the business request with TraceID "78ab12cd34ef56gh" and the execution of business operations can be obtained.

[0020] It should be noted that the embodiment of the present application does not limit the form of the service call relationship chain obtained. For example, it can be in the form of a graph structure, for example, see Figure 3 As shown in the figure, a service call relationship chain is obtained and represented as a directed graph. The service call relationship chain involves four services of a business system: Service A, Service B, Service C, and Service D. Service B calls Service A, Service C calls Service B, and Service D calls Service C. Service A, Service B, Service C, and Service D are the target services of the service call relationship chain.

[0021] S120: Obtain log attribute information of the operation log of the target service in the service call relationship chain.

[0022] As described above, after obtaining the service call relationship chains corresponding to different business requests within the business system, the log attribute information of the operation logs of the target services involved in the service call relationship chain is further obtained for each service call relationship chain. For example, if a service call relationship chain obtained for a certain business system involves five different services within the service system, the log attribute information of the operation logs recorded by each of the five target services during the call process corresponding to the service call relationship chain is obtained.

[0023] The acquired log attribute information may include the log recording time of the operation log, the log recording time, etc.

[0024] S130: Obtain full-link call indicator information of the service call relationship chain.

[0025] For a service call relationship chain, the full-link call indicator information of the service call relationship chain is used to describe the overall call indicator of the service call relationship chain. For example, the full-link call indicator information may include the link integrity, link resource consumption, etc. of the service call relationship chain.

[0026] For example, when obtaining the link integrity of a service call relationship chain, the actual service call relationship chain obtained can be compared with the standardized service call relationship chain of its corresponding business request to obtain a matching score between the service call relationship chain and the standardized service call relationship chain as the link integrity of the service call relationship chain.

[0027] For example, when obtaining the link resource consumption of a service call relationship chain, resource consumption-related data such as processor consumption, memory consumption, and network consumption during the duration of the service call relationship chain can be obtained from the resource monitoring system, and the average processor consumption, average memory consumption, and average network consumption during the duration can be calculated as the link resource consumption of the service call relationship chain.

[0028] S140: Based on the log attribute information and the full-link call indicator information, the service call relationship chain is visualized in the form of a graph in three-dimensional space.

[0029] As mentioned above, after obtaining the service call relationship chain of the business system, as well as the full-link call indicator information of the service call relationship chain and the log attribute information of the operation log of the target service in the service call relationship chain, for a service call relationship chain, further according to the configured visualization strategy, based on the log attribute information and full-link call indicator information corresponding to the service call relationship chain, the service call relationship chain is visualized in the form of a graphic in three-dimensional space.

[0030] Optionally, in one embodiment, the three-dimensional space includes a service identity dimension, a time dimension, and a call indicator dimension. The log attribute information includes the log recording time of the operation log. Based on the log attribute information and the full-link call indicator information, the service call relationship chain is visualized in the three-dimensional space in the form of a graph, including: Determine the service identity dimension coordinates and call time coordinates of the corresponding target service, as well as the call indicator dimension coordinates of the corresponding full-link call indicator information; Drawing a first graphic representing the target service in a three-dimensional space according to the call indicator dimension coordinate, the service identity dimension coordinate, and the call time coordinate, and drawing a connecting line representing the call relationship between the target services between the first graphics; A recording time coordinate corresponding to the log recording time is determined, and a second graphic representing the operation log is drawn on a connecting line corresponding to the operation log according to the recording time coordinate.

[0031] In an embodiment of the present application, the three-dimensional space used to visually display the service call relationship chain includes a service identity dimension, a time dimension, and a call indicator dimension. Among them, the two-dimensional space defined by the service identity dimension and the time dimension can realize the basic visual display of the service call relationship chain. Adding a call indicator dimension on this basis can enrich the information of the visual display, and at the same time enable different service call relationship chains to be visually displayed in the same three-dimensional space.

[0032] For a service call relationship chain obtained, the coordinates of the service identity dimension corresponding to the identity of the target service in the service call relationship chain are determined based on the service call relationship chain, and are recorded as service identity dimension coordinates. The service identity dimension coordinates are used to distinguish different target services. The method for determining the service identity dimension coordinates is not specifically limited here. The service identity dimension coordinates corresponding to different target services are different, and the service identity dimension coordinates corresponding to the same target service are the same. The method for determining the service identity dimension coordinates can be configured according to actual needs. For example, if two service call relationship chains are obtained, and service A exists in both service call relationship chains, then the service identity dimension coordinates determined for service A are the same for both service call relationship chains. For any of the two service call relationship chains, the service identity dimension coordinates determined for the other target services are different from the service identity dimension coordinates of service A. In addition, based on the call time of the target service described by the service call relationship chain, the coordinates of the time dimension corresponding to the target service in the service call relationship chain are determined, and are recorded as call time coordinates. Furthermore, the coordinates of the call indicator dimension corresponding to the full-link indicator information of the service call relationship chain are also determined, and are recorded as call indicator dimension indicators.

[0033] For a target service in a service call relationship chain, a drawing style for a graphic representing the target service is further determined (this can be either default or dynamically configured). A graphic representing the target service is drawn according to the determined drawing style at a three-dimensional spatial location determined by the target service's service identity dimension coordinates, call time coordinates, and the determined call indicator dimension indicators of the service call relationship chain. This graphic is recorded as a first graphic. In this way, first graphics representing different target services in a service call relationship chain are drawn in three-dimensional space. Based on the drawn first graphics, connecting lines are further drawn between the first graphics corresponding to target services with a call relationship.

[0034] Furthermore, for the target service's operation log, the recording time coordinate corresponding to the time the operation log was recorded is determined, as well as a drawing style for the graphic representing the operation log (which can be configured by default or dynamically). A graphic representing the operation log is drawn at the three-dimensional spatial location determined by the recording time coordinate corresponding to the operation log and the connecting line corresponding to the target service to which the operation log belongs. This is referred to as a second graphic. In this way, a second graphic representing a different operation log of the target service can be drawn in three-dimensional space.

[0035] At this point, the drawn first graphics, the connecting lines between the first graphics, and the second graphics located on the connecting lines, that is, a service call relationship chain is visualized in the form of graphics in three-dimensional space. For example, see Figure 4 The figure shows an example visualization of service call relationship chain A and service call relationship chain B. The three-dimensional space is represented by an XYZ coordinate system, with the X-axis corresponding to the time dimension of the three-dimensional space, the Y-axis corresponding to the service identity dimension of the three-dimensional space, and the Z-axis corresponding to the call indicator dimension of the three-dimensional space. It can be seen that service call relationship chain A and service call relationship chain B are visualized in the same three-dimensional space, and the call relationship links of service call relationship chain A and service call relationship chain B are intuitively displayed.

[0036] Optionally, in one embodiment, drawing a first graphic representing the target service in a three-dimensional space according to the call indicator dimension coordinate, the service identity dimension coordinate, and the call time coordinate includes: Determining a drawing position of a first graphic representing a target service according to the call indicator dimension coordinate, the service identity dimension coordinate, and the call time coordinate; Acquiring first local call indicator information of the target service, and determining a drawing style of a first graphic representing the target service based on the first local call indicator information; The first graphic representing the target service is drawn in the three-dimensional space according to the drawing position and drawing style of the first graphic representing the target service.

[0037] Unlike full-link call metrics, which describe the call metrics for the entire service call chain, local call metrics describe the call metrics associated with a single target service. For example, local call metrics may include the target service's cumulative call count, cumulative error count (the cumulative number of call errors), call frequency, and error rate (the ratio of cumulative error count to cumulative call count). It should be noted that the first local call metrics information and the second local call metrics information described below are used only to distinguish between different local call metrics information and do not specifically refer to them as specific local call metrics information.

[0038] The drawing style of the first graphic includes but is not limited to at least one of the shape, size, color, and color depth of the first graphic.

[0039] In an embodiment of the present application, the drawing style of the first graphic representing the target service is dynamically determined. Among them, for a target service in a service call relationship chain, on the one hand, the call indicator dimension coordinates corresponding to the service call relationship chain, and the three-dimensional space position determined by the service identity dimension coordinates and the call time coordinates corresponding to the target service are determined as the drawing position of the first graphic representing the target service. On the other hand, the first local call indicator information of the target service is obtained, and according to the correspondence between the configured first local call indicator information and the drawing style, the drawing style corresponding to the first local call indicator information of the target service is determined as the drawing style of the first graphic representing the target service. In this way, after determining the drawing position and drawing style of the first graphic representing the target service, the first graphic representing the target service can be drawn in three-dimensional space according to the drawing position and drawing style of the first graphic representing the target service.

[0040] For example, a blue sphere with a first preset radius is used by default to represent the target service. However, the color of the blue sphere is dynamically determined based on the first local call indicator information of the target service. For example, if the first local call indicator information is the cumulative number of calls, the greater the cumulative number of calls to a target service, the darker the blue sphere representing the target service, and the smaller the cumulative number of calls, the lighter the blue sphere representing the target service. In this way, for a target service, the color of the blue sphere representing the target service can be used to intuitively determine whether the target service is a frequently called service.

[0041] Optionally, in one embodiment, drawing a connection line between the first graphics to represent the calling relationship between the target services includes: Obtaining second local call indicator information of the target service, and determining a drawing style of a connection line representing a call relationship between the target services based on the second local call indicator information; According to the drawing style of the connection line representing the calling relationship between the target services, a connection line representing the calling relationship between the target services is drawn between the first graphics.

[0042] The drawing style of the connecting line includes but is not limited to at least one of the line type, thickness, and color of the connecting line.

[0043] In an embodiment of the present application, the drawing style of the connection line representing the call relationship between target services is dynamically determined. For a target service, the second local call indicator information of the target service is obtained, and according to the correspondence between the configured second local call indicator information and the drawing style, the drawing style corresponding to the second local call indicator information of the target service is determined as the drawing style of the connection line representing the call relationship between the target service and other target services that call the target service. In this way, after determining the drawing style of the connection line representing the call relationship between the target service and other target services that call the target service, the connection line representing the call relationship between the target service and other target services that call the target service can be drawn between the first graphic representing the target service and the first graphic representing other target services that call the target service according to the drawing style.

[0044] For example, by default, a solid line of a specified thickness is used to represent the call relationship between target services. However, the color of this solid line is dynamically determined based on the target service's second-part call indicator information. For example, if the second-part call indicator information is the cumulative number of errors, the greater the cumulative number of errors for a target service, the closer the color of the connecting line representing the target service's call relationship is to yellow, and the smaller the cumulative number of errors, the closer the color of the connecting line representing the target service's call relationship is to black. In this way, for a target service, the color of the connecting line representing the target service's call relationship can be used to intuitively understand whether the target service frequently experiences call errors.

[0045] Optionally, in one embodiment, drawing a second graphic representing the operation log on a connecting line corresponding to the operation log according to the recording time coordinate includes: Determining a drawing position of a second graphic representing the operation log on its corresponding connecting line according to the recording time coordinate; Obtaining an operation execution time of an operation corresponding to the operation log, and determining a drawing style of a second graphic representing the operation log according to the operation execution time; The second graphic representing the operation log is drawn on the connection line corresponding to the operation log according to the drawing position and drawing style of the second graphic representing the operation log.

[0046] In an embodiment of the present application, the drawing style of the second graphic representing the operation log of the target service is dynamically determined. Among them, for an operation log of a target service, on the one hand, the recording time coordinates of the operation log and the three-dimensional space position determined by the connecting line corresponding to the target service to which the operation log belongs are determined as the drawing position of the second graphic representing the operation log. On the other hand, the operation execution time of the operation to which the operation log belongs is obtained, and according to the correspondence between the configured operation execution time and the drawing style, the drawing style corresponding to the operation execution time of the operation to which the operation log belongs is determined as the drawing style of the second graphic representing the operation log. In this way, after determining the drawing position and drawing style of the second graphic representing the operation log, the second graphic representing the operation log can be drawn in three-dimensional space according to the drawing position and drawing style of the second graphic representing the operation log, and the second graphic of the operation log will be drawn on the connecting line corresponding to the target service to which the operation log belongs.

[0047] For example, by default, a red sphere with a second preset radius (the second preset radius is smaller than the first preset radius) is used to represent the operation log. However, the color of the red sphere is dynamically determined based on the execution time of the operation to which the operation log belongs. The longer the execution time of the operation in the operation log, the darker the red sphere representing the operation log, and the lighter the red sphere representing the operation log when the execution time of the operation log is shorter. In this way, the lighter the red sphere representing the operation log, the more intuitive it is about the execution time of the operation in the operation log.

[0048] Optionally, in one embodiment, after visually displaying the service call relationship chain in a three-dimensional space in the form of a graph based on the log attribute information and the full-link call indicator information, the method further includes: In response to the selection operation of the service call relationship chain in the three-dimensional space, an information analysis interface is displayed in the three-dimensional space, which includes at least one of the first local call indicator information, second local call indicator information, full-link call indicator information and link analysis results corresponding to the selected service call relationship chain.

[0049] The link analysis result is obtained by performing a link analysis based on at least one of the first local call indicator information, the second local call indicator information, and the full-link call indicator information in accordance with the configured link analysis strategy. For example, for a service call relationship chain, the first local call indicator information, the second local call indicator information, and the full-link call indicator information corresponding to the service call relationship chain can be input into a pre-trained link analysis model, and a link analysis is performed using the link analysis model to obtain a link analysis result describing whether resources need to be expanded for the target service of the service call relationship chain.

[0050] For example, please refer to Figure 5 When the user operates the cursor to select a graphic of a service call relationship chain, an information analysis interface is displayed in the form of a floating window in three-dimensional space.

[0051] Optionally, in one embodiment, after visually displaying the service call relationship chain in a three-dimensional space in the form of a graph based on the log attribute information and the full-link call indicator information, the method further includes: An input view adjustment operation is received, and a display view of a graphic displaying a service call relationship chain is adjusted according to the view adjustment operation, where the view adjustment operation includes at least one of rotation, scaling, and translation.

[0052] The present embodiment further provides the ability for users to adjust the display view of the service call relationship chain in three-dimensional space, allowing users to adjust the display view of the service call relationship chain in three-dimensional space according to their actual needs. For example, a three-dimensional graphics development library such as Three.js or Unity can be used to implement a visual interactive interface, thereby enabling view adjustment operations such as rotation, scaling, and translation of the displayed service call relationship chain graphic through the visual interactive interface.

[0053] Optionally, in one embodiment, after visually displaying the service call relationship chain in a three-dimensional space in the form of a graph based on the log attribute information and the full-link call indicator information, the method further includes: Receiving input link filtering conditions and determining a target service call relationship chain that matches the link filtering conditions; A graphic that highlights the target service call relationship chain in three-dimensional space.

[0054] In an embodiment of the present application, a link screening interface may be provided, the link screening interface including a screening condition input interface, so that input link screening conditions are received through the screening condition input interface of the link screening interface. The screening conditions include, but are not limited to, at least one of a service identifier, a call time, full-link call indicator information (such as link integrity, link resource consumption, etc.), and local call indicator information (such as cumulative number of calls, cumulative number of errors, call frequency, error rate, etc.).

[0055] After receiving the input link filtering conditions, the service call relationship chain that matches the link filtering conditions is determined and recorded as the target service call relationship chain. According to the configured highlighting strategy, the target service call relationship chain graphic is highlighted in three-dimensional space. The configuration of the highlighting strategy is not specifically limited here. For example, the highlighting strategy can be: highlight the target service call relationship chain graphic.

[0056] As can be seen from the above, the service call relationship display solution provided by the present invention obtains the service call relationship chain of the business system, which is used to describe the target service with a call relationship in the business system; obtains the log attribute information of the operation log of the target service; obtains the full-link call indicator information of the service call relationship chain; and visualizes the service call relationship chain in the form of a graphic in three-dimensional space based on the log attribute information and the full-link call indicator information. In this way, the call relationship between services in the business system can be visualized and intuitively displayed, thereby assisting operation and maintenance personnel to quickly locate the cause of the business system failure and improve the fault location efficiency of the business system.

[0057] In one embodiment, a service call relationship display device is provided, which corresponds to the service call relationship display method in the above embodiment. Figure 6 As shown, the service call relationship display device includes a relationship acquisition module 210, an attribute acquisition module 220, an indicator acquisition module 230 and a graphic display module 240. The functional modules are described in detail as follows: The relationship acquisition module 210 is used to acquire the service call relationship chain of the business system. The service call relationship chain is used to describe the target service with a call relationship in the business system; The attribute acquisition module 220 is used to obtain log attribute information of the operation log of the target service; The indicator acquisition module 230 is used to obtain the full-link call indicator information of the service call relationship chain; The graphic display module 240 is used to visualize the service call relationship chain in the form of a graphic in three-dimensional space based on log attribute information and full-link call indicator information.

[0058] Optionally, in one embodiment, the three-dimensional space includes a service identity dimension, a time dimension, and a call index dimension, and the log attribute information includes the log recording time of the operation log. The graphic display module 240 is used to determine the service identity dimension coordinates and the call time coordinates of the corresponding target service, as well as the call index dimension coordinates of the corresponding full-link call index information; according to the call index dimension coordinates, the service identity dimension coordinates, and the call time coordinates, a first graphic representing the target service is drawn in the three-dimensional space, and a connecting line representing the call relationship between the target services is drawn between the first graphics; the recording time coordinates corresponding to the log recording time are determined, and according to the recording time coordinates, a second graphic representing the operation log is drawn on the connecting line corresponding to the operation log.

[0059] Optionally, in one embodiment, the graphic display module 240 is used to determine the drawing position of the first graphic representing the target service based on the call indicator dimension coordinates, the service identity dimension coordinates, and the call time coordinates; obtain the first local call indicator information of the target service, and determine the drawing style of the first graphic representing the target service based on the first local call indicator information; and draw the first graphic representing the target service in three-dimensional space according to the drawing position and drawing style of the first graphic representing the target service.

[0060] Optionally, in one embodiment, the graphic display module 240 is used to obtain the second local call indicator information of the target service, and determine the drawing style of the connection line representing the call relationship between the target services based on the second local call indicator information; according to the drawing style of the connection line representing the call relationship between the target services, the connection line representing the call relationship between the target services is drawn between the first graphics.

[0061] Optionally, in one embodiment, the graphic display module 240 is used to determine the drawing position of the second graphic representing the operation log on its corresponding connecting line based on the recording time coordinate; obtain the operation execution time of the operation corresponding to the operation log, and determine the drawing style of the second graphic representing the operation log based on the operation execution time; draw the second graphic representing the operation log on the connecting line corresponding to the operation log according to the drawing position and drawing style of the second graphic representing the operation log.

[0062] Optionally, in one embodiment, the graphic display module 240 is further used to receive an input view adjustment operation, and adjust the display view of the graphic displaying the service call relationship chain according to the view adjustment operation, where the view adjustment operation includes at least one of rotation, scaling, and translation.

[0063] Optionally, in one embodiment, the graphic display module 240 is further configured to receive input link filtering conditions, determine a target service call relationship chain matching the link filtering conditions, and highlight a graphic of the target service call relationship chain in three-dimensional space.

[0064] For the specific definition of the service call relationship display device, please refer to the definition of the service call relationship display method above, and will not be repeated here. The various modules in the above-mentioned service call relationship display device can be implemented in whole or in part by software, hardware, or a combination thereof. The above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules.

[0065] In one embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as follows: Figure 7As shown. The computer device includes a processor, a memory, a network interface and a database connected via a system bus. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile and / or volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and computer program in the non-volatile storage medium. The network interface of the computer device is used to communicate with an external client via a network connection. When the computer program is executed by the processor, the steps of the service call relationship display method in the above embodiment are implemented.

[0066] In one embodiment, a computer device is provided. The computer device may be a client, and its internal structure diagram may be as follows: Figure 8 As shown. The computer device includes a processor, memory, network interface, display screen, and input device connected via a system bus. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and computer program in the non-volatile storage medium. The network interface of the computer device is used to communicate with an external server via a network connection. When the computer program is executed by the processor, the steps of the service call relationship display method in the above embodiment are implemented.

[0067] In one embodiment, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the steps of the service call relationship display method in the above embodiment are implemented, such as: Obtain the service call relationship chain of the business system. The service call relationship chain is used to describe the target service with a call relationship in the business system; Get the log attribute information of the target service's operation log; Obtain the full-link call indicator information of the service call relationship chain; Based on the log attribute information and full-link call indicator information, the service call relationship chain is visualized in the form of a graph in three-dimensional space.

[0068] In one embodiment, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores a computer program. When the computer program is executed by a processor, the steps of the service call relationship display method in the above embodiment are implemented, such as: Obtain the service call relationship chain of the business system. The service call relationship chain is used to describe the target service with a call relationship in the business system; Get the log attribute information of the target service's operation log; Obtain the full-link call indicator information of the service call relationship chain; Based on the log attribute information and full-link call indicator information, the service call relationship chain is visualized in the form of a graph in three-dimensional space.

[0069] It should be noted that the above functions or steps that can be implemented by the computer-readable storage medium or computer device can be found in the relevant descriptions of the server side and the client side in the aforementioned method embodiment. To avoid repetition, they will not be described one by one here.

[0070] Those skilled in the art will understand that all or part of the processes in the above-mentioned embodiments can be implemented by instructing the relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application may include non-volatile and / or volatile memory. Non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory may include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in many forms such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), Rambus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

[0071] Those skilled in the art will clearly understand that for the sake of convenience and brevity of description, only the division of the above-mentioned functional units and modules is used as an example. In actual applications, the above-mentioned functions can be distributed and completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above.

[0072] The embodiments described above are only used to illustrate the technical solutions of the present invention, rather than to limit the same. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the various embodiments of the present invention, and should all be included in the scope of protection of the present invention.

[0073] It should be noted that the non-Company's software tools or components appearing in the embodiments of the present invention are merely examples and do not represent actual use.

Claims

1. A method for displaying service call relationships, characterized in that: include: Obtaining a service call relationship chain of a business system, wherein the service call relationship chain is used to describe a target service having a call relationship in the business system; Obtaining log attribute information of the operation log of the target service; Obtaining full-link call indicator information of the service call relationship chain; Based on the log attribute information and the full-link call indicator information, the service call relationship chain is visualized in the form of a graph in three-dimensional space.

2. The service call relationship display method according to claim 1, characterized in that: The three-dimensional space includes a service identity dimension, a time dimension, and a call indicator dimension. The log attribute information includes the log recording time of the operation log. The service call relationship chain is visualized in the three-dimensional space in the form of a graph based on the log attribute information and the full-link call indicator information, including: Determine the service identity dimension coordinates and call time coordinates corresponding to the target service, and determine the call indicator dimension coordinates corresponding to the full-link call indicator information; Drawing a first graphic representing the target service in the three-dimensional space according to the call indicator dimension coordinate, the service identity dimension coordinate, and the call time coordinate, and drawing a connecting line representing the call relationship between the target services between the first graphics; A recording time coordinate corresponding to the log recording time is determined, and a second graphic representing the operation log is drawn on a connecting line corresponding to the operation log according to the recording time coordinate.

3. The service call relationship display method according to claim 2, characterized in that: Drawing a first graphic representing the target service in the three-dimensional space according to the call indicator dimension coordinate, the service identity dimension coordinate, and the call time coordinate includes: Determining a drawing position of a first graphic representing the target service according to the call indicator dimension coordinate, the service identity dimension coordinate, and the call time coordinate; Acquiring first local call indicator information of the target service, and determining a drawing style of a first graphic representing the target service based on the first local call indicator information; A first graphic representing the target service is drawn in the three-dimensional space according to a drawing position and a drawing style of the first graphic representing the target service.

4. The service call relationship display method according to claim 2, characterized in that: Drawing a connection line between the first graphics to represent the calling relationship between the target services includes: Acquiring second local call indicator information of the target service, and determining a drawing style of a connection line representing a call relationship between the target services based on the second local call indicator information; According to the drawing style of the connection line representing the calling relationship between the target services, a connection line representing the calling relationship between the target services is drawn between the first graphics.

5. The service call relationship display method according to claim 2, characterized in that: Drawing a second graphic representing the operation log on a connecting line corresponding to the operation log according to the recording time coordinate includes: determining, based on the recording time coordinates, a drawing position of a second graphic representing the operation log on its corresponding connecting line; Obtaining an operation execution time of the operation corresponding to the operation log, and determining a drawing style of a second graphic representing the operation log according to the operation execution time; The second graphic representing the operation log is drawn on the connection line corresponding to the operation log according to the drawing position and drawing style of the second graphic representing the operation log.

6. The service call relationship display method according to any one of claims 1 to 5, characterized in that: After visually displaying the service call relationship chain in a three-dimensional space in the form of a graph based on the log attribute information and the full-link call indicator information, the method further includes: An input view adjustment operation is received, and a display view of a graphic displaying the service call relationship chain is adjusted according to the view adjustment operation, wherein the view adjustment operation includes at least one of rotation, scaling, and translation.

7. The service call relationship display method according to any one of claims 1 to 5, characterized in that: After visually displaying the service call relationship chain in a three-dimensional space in the form of a graph based on the log attribute information and the full-link call indicator information, the method further includes: Receiving input link screening conditions, and determining a target service call relationship chain that matches the link screening conditions; A graphic of the target service call relationship chain is highlighted in the three-dimensional space.

8. A service call relationship display device, characterized in that: include: A relationship acquisition module is used to acquire a service call relationship chain of a business system, wherein the service call relationship chain is used to describe a target service with a call relationship in the business system; An attribute acquisition module, configured to acquire log attribute information of the operation log of the target service; An indicator acquisition module is used to obtain the full-link call indicator information of the service call relationship chain; A graphic display module is used to visualize the service call relationship chain in the form of a graphic in three-dimensional space based on the log attribute information and the full-link call indicator information.

9. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the computer program, the service call relationship display method according to any one of claims 1 to 7 is implemented.

10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the service call relationship display method according to any one of claims 1 to 7 is implemented.

Images