Call chain processing method, device and medium for business scenarios

Abstract

The present disclosure provides a call chain processing method, device and medium for business scenarios, including: displaying a business scenario call chain query interface, including a first control for inputting identification information of a business scenario to be queried, a second control for inputting processing time of a business scenario, a third control for inputting business information and a fourth control for triggering a query; in response to a first interactive operation oriented to the fourth control, displaying a business call chain of a target business scenario according to relevant information of the input target business scenario; in response to a second interactive operation oriented to a target business call chain in a business call chain, displaying at least one system-level call chain of the target business call chain. Through the present disclosure, a business call chain under a business scenario and a system-level call chain under the business call chain can be determined, and the business call chain and the system-level call chain can be integrated to display the call chain information of the business scenario in a more unified and complete manner.

Description

Technical Field

[0001] The present disclosure relates to the field of cloud network services, and in particular to a call chain processing method, device and medium for business scenarios. Background Art

[0002] As the scale of cloud network services gradually expands, more and more users use terminal devices to handle services. However, as the scale of services gradually expands and the types of services continue to increase, the call chain of business scenarios has also become increasingly complex.

[0003] The existing call chain acquisition method can determine a single system-level call chain. The system and the call chain are composed of multiple backend services in series. However, this method cannot determine the business-level call chain including the frontend service. Summary of the invention

[0004] The present disclosure provides a call chain processing method, device and medium for business scenarios, so as to determine the business-level call chain including the front-end service while determining the system-level call chain.

[0005] In a first aspect, the present disclosure provides a call chain processing method for business scenarios, including:

[0006] Displaying a business scenario call chain query interface, the business scenario call chain query interface includes a first control for inputting identification information of a business scenario to be queried, a second control for inputting processing time of the business scenario, a third control for inputting business information, and a fourth control for triggering a query;

[0007] In response to the first interactive operation directed to the fourth control, displaying a business call chain of the target business scenario according to the input relevant information of the target business scenario, where the relevant information includes at least one of identification information, processing time, and business information;

[0008] In response to a second interactive operation directed to a target business call chain in the business call chain, at least one system-level call chain of the target business call chain is displayed.

[0009] In one possible implementation, based on the relevant information of the target business scenario that has been input, a business call chain of the target business scenario is displayed, including: obtaining a call log of the service bus; performing data correlation analysis on the call log based on the relevant information of the target business scenario that has been input to obtain a business call chain of the target business scenario; and displaying the business call chain of the target business scenario.

[0010] In one possible implementation, based on the relevant information of the target business scenario that has been input, data correlation analysis is performed on the call log to obtain a business call chain of the target business scenario, including: based on the relevant information of the target business scenario that has been input, data correlation analysis is performed on the call log of the service bus to obtain multiple capability families of the target business scenario, and the call logs of the capability family that contain the same business information are sorted by time, with the business call chain as the key of the key-value pair, and the request message, response message and related dependency information as the value of the key-value pair.

[0011] In one possible implementation, in response to a second interactive operation oriented toward a target business call chain in a business call chain, at least one system-level call chain of the target business call chain is displayed, including: in response to the second interactive operation oriented toward a target business call chain in a business call chain, basic information of the target business call chain is displayed, the basic information including a request message, a response message and a tracking sequence number of the system-level call chain; in response to a third interactive operation oriented toward the tracking sequence number, at least one system-level call chain of the target business call chain is displayed.

[0012] In a possible implementation, in response to a third interactive operation for tracking serial numbers, at least one system-level call chain of the target business call chain is displayed, including: in response to the third interactive operation for tracking serial numbers, based on the tracking serial number, obtaining at least one system-level call chain of the target business call chain, the at least one system-level call chain of the target business call chain is obtained by concatenating the system-level logs of each link corresponding to the tracking serial number according to the Agent, and storing them in a database; displaying at least one system-level call chain of the target business call chain.

[0013] In a possible implementation, the method further includes: determining an execution state of the target business call chain according to the basic information; and determining that a failure occurs in the target business call chain in response to an abnormal execution state of the target business call chain.

[0014] A possible implementation also includes: after determining that a fault occurs in the target business call chain, determining at least one system-level call chain of the target business call chain according to the tracking sequence number of the target business call chain; and determining the fault location based on the system-level call chain.

[0015] In a second aspect, the present disclosure provides a call chain processing device for business scenarios, including:

[0016] A first display module, used to display a business scenario call chain query interface, wherein the business scenario call chain query interface includes a first control for inputting identification information of a business scenario to be queried, a second control for inputting processing time of the business scenario, a third control for inputting business information, and a fourth control for triggering a query;

[0017] A second display module, configured to respond to the first interactive operation directed to the fourth control and display a business call chain of the target business scenario according to the input relevant information of the target business scenario, wherein the relevant information includes at least one of identification information, processing time and business information;

[0018] The third display module is used to display at least one system-level call chain of the target business call chain in response to a second interactive operation directed to the target business call chain in the business call chain.

[0019] In one possible implementation, the second display module is specifically used to: obtain the call log of the service bus; perform data correlation analysis on the call log based on the relevant information of the target business scenario that has been input to obtain the business call chain of the target business scenario; and display the business call chain of the target business scenario.

[0020] In one possible implementation, an analysis module is further included, which is used to perform data correlation analysis on the call log of the service bus based on the relevant information of the target business scenario that has been input, to obtain multiple capability families of the target business scenario, and the capability families contain call logs with the same business information sorted by time, with the business call chain as the key of the key-value pair, and the request message, response message and related dependency information as the value of the key-value pair.

[0021] In one possible implementation, the third display module is specifically used to: in response to a second interactive operation oriented to a target business call chain in a business call chain, display basic information of the target business call chain, the basic information including a request message, a response message and a tracking serial number of a system-level call chain; in response to a third interactive operation oriented to a tracking serial number, display at least one system-level call chain of the target business call chain.

[0022] In a possible implementation, the third display module is specifically used for: in response to a third interactive operation oriented to the tracking serial number, obtaining at least one system-level call chain of the target business call chain based on the tracking serial number, wherein the at least one system-level call chain of the target business call chain is obtained by concatenating the system-level logs of each link corresponding to the tracking serial number according to the Agent and storing them in a database; and displaying at least one system-level call chain of the target business call chain.

[0023] In a possible implementation, it further includes a determination module, which is used to determine the execution state of the target business call chain according to the basic information; in response to the execution state of the target business call chain being abnormal, determine that the target business call chain has a fault.

[0024] In a possible implementation, the determination module is also used to: after determining that a fault occurs in the target business call chain, determine at least one system-level call chain of the target business call chain according to the tracking sequence number of the target business call chain; and determine the fault location based on the system-level call chain.

[0025] In a third aspect, the present disclosure provides an electronic device, including:

[0026] Memory and processor;

[0027] The memory is used to store program instructions;

[0028] The processor is used to call the program instructions in the memory to execute the call chain processing method oriented to the business scenario of the first aspect.

[0029] In a fourth aspect, the present invention discloses a computer-readable storage medium, in which computer program instructions are stored. When the computer program instructions are executed, the call chain processing method for business scenarios of the first aspect is implemented.

[0030] In a fifth aspect, the present disclosure provides a computer program product, including a computer program, which, when executed by a processor, implements the business scenario-oriented call chain processing method of the first aspect.

[0031] The present disclosure provides a call chain processing method, device and medium for business scenarios, including: displaying a business scenario call chain query interface, the business scenario call chain query interface includes a first control for inputting identification information of the business scenario to be queried, a second control for inputting the processing time of the business scenario, a third control for inputting business information and a fourth control for triggering the query; in response to a first interactive operation oriented to the fourth control, displaying the business call chain of the target business scenario according to the relevant information of the input target business scenario, the relevant information includes at least one of identification information, processing time and business information; in response to a second interactive operation oriented to the target business call chain in the business call chain, displaying at least one system-level call chain of the target business call chain. Through the present disclosure, a business call chain under a business scenario and at least one system-level call chain under the business call chain can be determined, and the business call chain and the system-level call chain can be integrated, so that the call chain information of the business scenario can be displayed more uniformly and completely. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0033] Figure 1 A system-level call chain architecture diagram based on Dapper provided for the present disclosure;

[0034] Figure 2 An application scenario diagram provided for an embodiment of the present disclosure;

[0035] Figure 3-a A flowchart of a call chain processing method for a business scenario provided by an embodiment of the present disclosure;

[0036] Figure 3-b A schematic diagram of an interface provided by an embodiment of the present disclosure;

[0037] Figure 4 Basic information of the front-end service provided by an embodiment of the present disclosure;

[0038] Figure 5 A schematic diagram of a system-level call chain provided in an embodiment of the present disclosure;

[0039] Figure 6 A logical diagram of a call chain processing system for a business scenario provided by an embodiment of the present disclosure;

[0040] Figure 7 A business structure diagram provided for an embodiment of the present disclosure;

[0041] Figure 8 A schematic diagram of the structure of a call chain processing system for a business scenario of an embodiment of the present disclosure;

[0042] Fig. 9 A schematic diagram of the structure of a call chain processing device for business scenarios provided by an embodiment of the present disclosure;

[0043] Fig.10 A schematic diagram of the structure of an electronic device provided in one embodiment of the present disclosure. DETAILED DESCRIPTION

[0044] In order to make the purpose, technical solution and advantages of the embodiments of the present disclosure clearer, the technical solution in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the drawings in the embodiments of the present disclosure. Obviously, the described embodiments are part of the embodiments of the present disclosure, not all of the embodiments. Based on the embodiments in the present disclosure, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present disclosure.

[0045] At present, Dapper (an object mapper) can be used to realize the connection between various called services in a distributed system. Among them, through a unique trace identity (TraceId), various services involved in a call are connected into a link, and can be displayed through the front-end display layer. Figure 1 As shown, Figure 1 A system-level call chain architecture diagram based on Dapper provided for the present invention.

[0046] However, the inventors found in their research that Figure 1 For example, Dapper can only determine the system-level call chain consisting of backend service 1, backend service 2, backend service 3, and backend service 4 under frontend service 1. If frontend service 2 exists, Dapper cannot determine the business-level call chain that connects frontend service 1 and frontend service 2 in series. Since a business scenario requires the cooperation of several frontend services to be implemented, Dapper cannot uniformly determine the connection of several frontend services.

[0047] Therefore, based on this problem, the present disclosure proposes a call chain processing method, device and medium for business scenarios, which combines the business-level call chain and the system-level call chain to uniformly display the call chain information including the front-end service and back-end service of the business scenario.

[0048] Figure 2 is an application scenario diagram of an embodiment of the present disclosure, Figure 2 In the embodiment, an electronic device 201 and a server 202 are included, and the electronic device 201 exchanges information with the server 202. The determination of the front-end service and the back-end service of the business scenario, and the construction of the business call chain and the system-level call chain can be executed on the server 202, and the display end of the electronic device 201 can be used to trigger the query of the business call chain and the system-level call chain, and display them on the interactive interface.

[0049] The electronic device 201 and the server 202 may exchange information via a wired manner or wirelessly. Figure 2 The application scenario may also include a data storage device, and the electronic device 201 may be any one of a computer, a mobile phone or a tablet, which is not limited in the present disclosure.

[0050] Next, a call chain processing method, device and medium for business scenarios are introduced through specific embodiments.

[0051] Figure 3-a A flowchart of a call chain processing method for a business scenario provided by an embodiment of the present disclosure.

[0052] like Figure 3-a As shown, the method includes:

[0053] S301. Display a business scenario call chain query interface, which includes a first control for inputting identification information of a business scenario to be queried, a second control for inputting processing time of the business scenario, a third control for inputting business information, and a fourth control for triggering a query.

[0054] The business scenario call chain query interface can be displayed by any electronic device with a display function, and the electronic device can be a mobile phone, a computer or other electronic device with a display.

[0055] The identification information of the business scenario can reflect the specific type of the business scenario, for example, the business scenario can be a user submitting an order, a user changing their own information, or a user consulting business information, etc. The business information can be a serial number, which can include the time of the business scenario handling, the content of the business scenario, and the priority of the business scenario, etc.

[0056] For example, Figure 3-b This is a schematic diagram of an interface provided by an embodiment of the present disclosure. Figure 3-b As shown, the first control 301 corresponds to an input box for identification information of the business scenario, the second control 302 corresponds to an input box for processing time of the business scenario, the third control 303 corresponds to inputting business scenario information, and the fourth control 304 is used to trigger a query. In this example, the identification information of the business scenario is an order submission scenario, the processing time of the business scenario is 2021-10-14, and the business information is 2110140950976819. After triggering the query of the fourth control 304, the business call chain will be displayed. The business call chain contains 3 front-end services. This disclosure does not limit the specific content of the business call chain. In the front-end service: "User" corresponds to obtaining users, "Order" corresponds to user requests, and "Payment" corresponds to payments.

[0057] Should Figure 3-b In the figure, the first control 301, the second control 302, the third control 303 and the fourth control 304 are displayed in the first area of ​​the business scenario call chain query interface, and the business call chain is displayed in the second area of ​​the business scenario call chain query interface, but this layout format is only an example and does not constitute a limitation to the present disclosure.

[0058] S302. In response to the first interactive operation directed to the fourth control, a business call chain of the target business scenario is displayed according to the input relevant information of the target business scenario, where the relevant information includes at least one of identification information, processing time, and business information.

[0059] The business call chain is used to connect the front-end services corresponding to the business scenarios in series and display them uniformly on the interactive interface. The front-end services included in the business call chain can be obtaining user identity, modifying user passwords, user order requests, user order modification requests, user order cancellation, and user payment, etc.

[0060] S303: In response to a second interactive operation directed to a target business call chain in the business call chain, display at least one system-level call chain of the target business call chain.

[0061] It should be noted that, in any embodiment of the present disclosure, the first interactive operation and / or the second interactive operation may be clicking the screen, touching the screen, clicking the mouse pointer, or triggering the interaction through sound, etc., which is not limited by the present disclosure.

[0062] The business call chain contains at least one front-end service. Since each front-end service will also call at least one back-end service, each front-end service contained in the target business call chain corresponds to a system-level call chain.

[0063] For example, the system-level call chain can be determined by tracking sequence numbers of Dapper and the front-end service.

[0064] In addition, the business call chain and the system-level call chain can be displayed in the interactive interface at the same time, or can be displayed in the interactive interface step by step, that is, after operating the business call chain, the corresponding system-level call chain is displayed, which is not limited in the present disclosure.

[0065] In an embodiment of the present disclosure, a call chain processing method for business scenarios is provided, the method comprising: displaying a business scenario call chain query interface, the business scenario call chain query interface comprising a first control for inputting identification information of the business scenario to be queried, a second control for inputting the processing time of the business scenario, a third control for inputting business information, and a fourth control for triggering the query; in response to a first interactive operation oriented to the fourth control, displaying the business call chain of the target business scenario according to the relevant information of the input target business scenario, the relevant information comprising at least one of identification information, processing time, and business information; in response to a second interactive operation oriented to the target business call chain in the business call chain, displaying at least one system-level call chain of the target business call chain. Through the present disclosure, a business call chain under a business scenario and a system-level call chain under the business call chain can be determined, and the business call chain and the system-level call chain can be integrated to display the call chain information of the business scenario in a more unified and complete manner.

[0066] In some embodiments, displaying at least one system-level call chain of a business call chain may include: in response to a second interactive operation directed to a target business call chain in the business call chain, displaying basic information of the target business call chain, the basic information including a request message, a response message and a tracking sequence number of the system-level call chain; in response to a third interactive operation directed to the tracking sequence number, displaying at least one system-level call chain of the target business call chain.

[0067] For example, this embodiment divides the system-level call chain and the service call chain into two steps, that is, based on the service call chain, the system-level call chain is determined through interactive operations. Figure 4 Basic information of the front-end service provided by an embodiment of the present disclosure. Figure 4 As shown, Figure 4 In the business call chain, after selecting "User" to obtain the user front-end service, the request message, response message and tracking sequence number of the user front-end service will be displayed. Specifically, it can be found that the user's name is Zhang San, the response message of the front-end service shows that the execution is successful, and the tracking sequence number of the user front-end service is 0af51f3516342229279986067db2a5.

[0068] In this embodiment, by selecting (interactive operation) the front-end service on the business call chain, the tracking sequence number of each front-end service can be determined, and an entry can be provided for viewing the system-level call chain.

[0069] Based on the above embodiments, further determining the system-level call chain may include: in response to a third interactive operation oriented to the tracking sequence number, based on the tracking sequence number, obtaining at least one system-level call chain of the target business call chain, wherein the at least one system-level call chain of the target business call chain is obtained by concatenating the system-level logs of each link corresponding to the tracking sequence number according to the Agent, and storing them in a database; and displaying at least one system-level call chain of the target business call chain.

[0070] Figure 5 A schematic diagram of a system-level call chain provided by an embodiment of the present disclosure. Figure 5 As shown, for Figure 4The front-end service with the tracking serial number 0af51f3516342229279986067db2a5 can determine the system-level call chain under the front-end service after the third interactive operation. The third interactive operation can be the same as the first interactive operation or the second interactive operation, or it can be different. In the system-level call chain, the front-end service "getUser" includes two back-end services "getName" and "getAge". "getAge" calls the "logging" log service, and "getName" accesses the "Redis" memory library once. The call chain is implemented through "Pinpoint".

[0071] based on Figure 3-a , Figure 3-b to Figure 5 , the business call chain and the system-level call chain can be combined and displayed to the outside in a hierarchical manner. First, the front-end services included in a business scenario can be clearly queried, and the front-end services are connected in series by the business call chain; second, in the business call chain, the back-end services of each front-end service can be further determined, and the back-end services are connected in series by the system-level call chain.

[0072] In addition, since the business data is stored in the log, it is impossible to intuitively determine the front-end service based on the business scenario. Therefore, before displaying the above-mentioned business call chain and system-level call chain, it is necessary to first determine the front-end services included in the business scenario, and then display them in the form of a business call chain. In some embodiments, based on the relevant information of the target business scenario that has been input, the business call chain of the target business scenario is displayed, including: obtaining the call log of the service bus; performing data correlation analysis on the call log based on the relevant information of the target business scenario that has been input to obtain the business call chain of the target business scenario; and displaying the business call chain of the target business scenario.

[0073] The call log recorded by the service bus generally includes the processing time of the business scenario, the service address (also called the service URL), the request message, the response message, the service execution time, the tracking sequence number, etc. Based on the input business scenario information, the business call chain of the business scenario is determined in the call log of the service bus.

[0074] Furthermore, the call log of the service bus can be introduced through Table 1. In Table 1, ID represents a digital serial number, Req_time represents the processing time of the business scenario, Service_ucl represents the service URL, Req_info represents the request message, Rsp_info represents the response message, Proc_time represents the service execution time (or response time), and TraceId represents the trace sequence number.

[0075] Table 1

[0076]

[0077]

[0078] In addition, Table 2 further describes the fields in Table 1 in detail. Table 2 is as follows:

[0079] Table 2

[0080] Field Name Field Type Field Description ID bigint Digital serial number Req_time datetime Processing time of business scenarios Service_url string Service URL Req_info string Request message Rsp_info string Response message Proc_time int Processing time (in milliseconds) TraceId string Tracking serial number

[0081] In an achievable implementation, the above-mentioned data correlation analysis is performed on the call log according to the relevant information of the target business scenario that has been input to obtain the business call chain of the target business scenario, which may include: according to the relevant information of the target business scenario that has been input, data correlation analysis is performed on the call log of the service bus to obtain multiple capability families of the target business scenario, and the call logs of the capability family containing the same business information are sorted by time, with the business call chain as the key of the key-value pair, and the request message, response message and related dependency information as the value of the key-value pair.

[0082] For example, data relevance can be to query the relevant front-end services from the call log in the service bus according to the business scenario information. After the front-end service is determined, the front-end service corresponds to the capability family one by one. Specifically, by analyzing the call log of the service bus within a unit time (generally, set to 10 minutes), the call logs containing the same business value are gathered together. Sort by time, with the service URL as the key, and the request, response log and other dependent information as the value, to form a preliminary capability family. It can be seen from Tables 1 and 2 that one service URL corresponds to one front-end service, so the business call chain composed of the front-end services can also be used as a key. In addition, since there is 2110140950976819 in the above three logs. When the business scenario information is also 2110140950976819, the above three service URLs can be matched, that is, three front-end services, and each front-end service corresponds to a capability family. The capability family can be stored in the business scenario configuration library. The data model of the capability family in the business scenario configuration library is the data model of the business scenario. The data model of the capability family can be reflected by Table 3 and Table 4:

[0083] Table 3

[0084]

[0085] Table 4

[0086]

[0087]

[0088] In summary, the above method can be used to determine the front-end service and then determine the business call chain.

[0089] Optionally, after the business call chain and the system-level call chain are uniformly displayed to the outside, the call chain processing method for business scenarios disclosed herein may also include: determining the execution status of the target business call chain based on basic information; in response to an abnormal execution status of the target business call chain, determining that a fault has occurred in the target business call chain.

[0090] Because in the process of handling business, a business scenario often completes a complete business scenario by calling multiple front-end services. When an error occurs at the user level, the user can only provide user-level error information, because the user level is mainly business information (such as order number, business number, and other uncertain information), and the business information cannot be actually associated with the system-level call chain, and it is impossible to clarify which front-end service or back-end service the error message belongs to. Secondly, the call chain implemented based on Dapper can only realize the system-level call chain information of one of the front-end services based on TraceId. However, in actual applications, a business scenario involves multiple front-end services, and each front-end service corresponds to multiple system-level call chains. Therefore, when a problem occurs at a node in the business scenario, it is often difficult to determine the specific location of the fault source due to the lack of connection between the front-end services. The present disclosure can be based on Figure 4 In the business call chain, based on the response message of each front-end service, the execution status of the front-end service is determined, and then it is determined whether each front-end service has a fault.

[0091] Furthermore, after determining that a target business call chain fails, at least one system-level call chain of the target business call chain is determined based on the tracking sequence number of the target business call chain; and based on the system-level call chain, the fault location is determined.

[0092] After the specific front-end service with a fault is determined, the back-end service corresponding to the front-end service can be determined through the third interactive operation, and displayed in series through the system-level service call chain. Figure 5 For example, in Figure 5 Determine the specific location of the fault source in the back-end business.

[0093] In the disclosed embodiment, by means of the integration of the business-level call chain and the system-level call chain, the front-end services are also connected in series, so the location of a failure in a certain business scenario can be quickly determined.

[0094] In addition, based on the above-mentioned call chain processing method for business scenarios, the present disclosure may also provide a call chain processing system for business scenarios. Figure 6 This is a logical diagram of a call chain processing system for a business scenario provided by an embodiment of the present disclosure. Figure 6As shown, the call chain processing system of the business scenario can connect the front-end services of the service bus layer in series to build a business call chain. In addition, for each front-end service in the business call chain, the system-level call chain of each front-end service can be determined. For example, the system-level call chain of front-end service 1 includes back-end service 1, back-end service 2, back-end service 3, and back-end service 4; front-end service 2 includes back-end service 5 and back-end service 6. Connecting front-end services in series can effectively solve problems that Dapper cannot solve.

[0095] In addition, you can Figure 7 The following describes the business structure of an embodiment of the present disclosure. Figure 7 As shown, the user layer can be an application or web platform installed on the user's device, etc.; the API layer is the enterprise-level service bus layer, which includes multiple front-end services, and the business layer includes multiple business centers, such as user center, order center, and product center, etc., and each business center can call multiple back-end services.

[0096] Based on the above business structure, through microservices, the business layer can be split into multiple business centers. The user layer can be a mobile APP or a PC web system. The front-end service will be registered to the enterprise service bus. The communication protocol is usually http / https+json and http / https+xml. In general, the back-end service calls within the business center are often directly called through the distributed service framework protocol (RPC method). Based on this business structure, Figure 8 A schematic diagram showing the structure of a call chain processing system for a business scenario of an embodiment of the present disclosure is shown. Figure 8 The call chain processing system of the business scenario may include a business scenario call chain console module, a log collection and storage module, a business scenario discovery module, and a system-level call chain module. Among them, the log collection and storage module can be used to collect and organize the call logs of the service bus. Among them, the call logs of the service bus can be divided into two parts: the service bus log and the business center log. The service bus log mainly records the execution logs of each service of the service bus itself and the logs of calling the services of the subordinate centers; the business center log mainly records the execution logs of each service of the business center itself and the logs of calling its downstream services. The logs recorded by the service bus generally include the processing time of the business scenario, service URL, request message, response message, service execution time, tracking sequence number, etc. The log collection and storage module collects and aggregates the logs into the data warehouse in real time. The present disclosure adopts the Flume log collection system, the Kafka message system, and the Flink distributed data flow engine, and the data warehouse adopts the ElasticSearch distributed engine. The Flink distributed data flow engine can automatically extract the business fields of the request message and the response message and put them into the data warehouse.

[0097] In addition, the request message and response message may be in JSON or XML format, and the business fields therein are uniformly converted into an array of "field name_field value", which is subsequently used as the data source of the business scenario discovery module.

[0098] The business scenario discovery module is used to determine at least one front-end service of the business scenario based on real-time analysis of data relevance. The method is the same as described above and will not be repeated here.

[0099] The business scenario call chain console module can include two modules: the business scenario management module and the business scenario call chain query and display module. Among them, the business scenario management module is used to manage the front-end service and the back-end service. For example, managers and other relevant personnel can conduct targeted manual intervention and modification; the business scenario call chain query and display module is used to query from the data warehouse based on three query conditions, namely, the business scenario identifier, the processing time of the business scenario, and the business field information, to obtain the front-end service corresponding to the service URL, and display it on the interactive interface through the business call chain.

[0100] The system-level call chain module is used to determine the system-level call chain of each front-end service according to the tracking serial number of each front-end service, and display it on the interactive interface.

[0101] Figures 4 to 8 The embodiments of the present invention may be used in combination with each other or used independently, and the present disclosure is not limited thereto.

[0102] Next, through Fig. 9 The call chain processing device 900 for business scenarios disclosed in the present invention includes:

[0103] A first display module 901 is used to display a business scenario call chain query interface, which includes a first control for inputting identification information of a business scenario to be queried, a second control for inputting processing time of the business scenario, a third control for inputting business information, and a fourth control for triggering a query;

[0104] A second display module 902 is used to respond to the first interactive operation oriented to the fourth control and display the business call chain of the target business scenario according to the input relevant information of the target business scenario, where the relevant information includes at least one of identification information, processing time and business information;

[0105] The third display module 903 is used to display at least one system-level call chain of the target business call chain in response to the second interactive operation oriented to the target business call chain in the business call chain.

[0106] In one possible implementation, the second display module 902 is specifically used to: obtain the call log of the service bus; perform data correlation analysis on the call log based on the relevant information of the target business scenario that has been input to obtain the business call chain of the target business scenario; and display the business call chain of the target business scenario.

[0107] In one possible implementation, a business scenario discovery module (not shown) is further included, which is used to perform data correlation analysis on the call log of the service bus based on the relevant information of the target business scenario that has been input, to obtain multiple capability families of the target business scenario, and the capability families contain call logs with the same business information sorted by time, with the business call chain as the key of the key-value pair, and the request message, response message and related dependency information as the value of the key-value pair.

[0108] In one possible implementation, the third display module 903 is specifically used to: in response to a second interactive operation oriented to a target business call chain in a business call chain, display basic information of the target business call chain, the basic information including a request message, a response message and a tracking serial number of a system-level call chain; in response to a third interactive operation oriented to a tracking serial number, display at least one system-level call chain of the target business call chain.

[0109] In a possible implementation, the third display module 903 is specifically used for: in response to the third interactive operation for the tracking serial number, based on the tracking serial number, obtaining at least one system-level call chain of the target business call chain, wherein the at least one system-level call chain of the target business call chain is obtained by concatenating the system-level logs of each link corresponding to the tracking serial number according to the Agent and storing them in a database; and displaying at least one system-level call chain of the target business call chain.

[0110] In a possible implementation, a determination module (not shown) is further included, which is used to determine the execution status of the target business call chain based on the basic information; in response to the execution status of the target business call chain being abnormal, determine that the target business call chain has a fault.

[0111] In a possible implementation, the determination module is also used to: after determining that a fault occurs in the target business call chain, determine at least one system-level call chain of the target business call chain according to the tracking sequence number of the target business call chain; and determine the fault location based on the system-level call chain.

[0112] It is supplemented that the first display module 901, the second display module 902 and the third display module 903 can be understood as a further division of the functions of the business scenario call chain query and display module, and the functional implementation of the business scenario call chain query and display module is realized by combining the business scenario management module, the log collection and storage module, the business scenario discovery module and the system-level call chain module. For example, when the second display module 902 displays the business call chain of the target business scenario, the call log of the service bus is obtained through the log collection and storage module; and the business scenario discovery module performs data correlation analysis on the call log according to the relevant information of the target business scenario input in the first area, and obtains the business call chain of the target business scenario. For another example, when the third display module 903 obtains at least one system-level call chain of the target business call chain, at least one system-level call chain of the target business call chain is obtained by the system-level call chain module according to the Agent to connect the system-level logs of each link corresponding to the tracking sequence number and store them in the database.

[0113] The device provided in the embodiments of the present disclosure may be used to execute the method of the embodiments described above, and its implementation principle and technical effect are similar and will not be described in detail here.

[0114] It should be noted that it should be understood that the division of the various modules of the above device is only a division of logical functions. In actual implementation, they can be fully or partially integrated into one physical entity, or they can be physically separated. And these modules can all be implemented in the form of software called by processing elements; they can also be all implemented in the form of hardware; some modules can also be implemented in the form of software called by processing elements, and some modules can be implemented in the form of hardware. For example, the processing module can be a separately established processing element, or it can be integrated in a chip of the above device. In addition, it can also be stored in the memory of the above device in the form of program code, and called and executed by a processing element of the above device. The implementation of other modules is similar. In addition, these modules can be fully or partially integrated together, or they can be implemented independently. The processing element described here can be an integrated circuit with signal processing capabilities. In the implementation process, each step of the above method or each module above can be completed by an integrated logic circuit of hardware in the processor element or instructions in the form of software.

[0115] For example, the above modules may be one or more integrated circuits configured to implement the above methods, such as one or more application specific integrated circuits (ASIC), or one or more microprocessors (digital signal processors, DSP), or one or more field programmable gate arrays (FPGA), etc. For another example, when a module above is implemented in the form of a processing element scheduling program code, the processing element may be a general-purpose processor, such as a central processing unit (CPU) or other processor that can call program code. For another example, these modules may be integrated together and implemented in the form of a system-on-a-chip (SOC).

[0116] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented by software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present disclosure is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid state disk (SSD)), etc.

[0117] Fig.10 A schematic diagram of the structure of an electronic device provided by an embodiment of the present disclosure. For example, the electronic device may be provided as a computer. Fig.10, the electronic device 1000 includes a processing component 1001, which further includes one or more processors, a memory resource represented by a memory 1002 for storing instructions executable by the processing component 1001, such as an application, and a display 1003. The application stored in the memory 1002 may include one or more modules each corresponding to a set of instructions. In addition, the processing component 1001 is configured to execute instructions, in conjunction with the display 1003 to perform any of the above method embodiments.

[0118] The electronic device 1000 may further include a power supply component 1004 configured to perform power management of the electronic device 1000, a wired or wireless network interface 1005 configured to connect the electronic device 1000 to a network, and an input / output (I / O) interface 1006. The electronic device 1000 may operate based on an operating system stored in the memory 1002, such as Windows Server™, Mac OS X™, Unix™, Linux™, FreeBSD™ or the like.

[0119] The present disclosure also provides a computer-readable storage medium, in which computer-executable instructions are stored. When a processor executes the computer-executable instructions, the call chain processing method for the business scenario described above is implemented.

[0120] The present disclosure also provides a computer program product, including a computer program, which, when executed by a processor, implements the above-mentioned call chain processing method for business scenarios.

[0121] The computer-readable storage medium mentioned above can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk. The readable storage medium can be any available medium that can be accessed by a general or special-purpose computer.

[0122] An exemplary readable storage medium is coupled to a processor so that the processor can read information from the readable storage medium and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can be located in an application specific integrated circuit (Application Specific Integrated Circuits, referred to as: ASIC). Of course, the processor and the readable storage medium can also exist as discrete components in a call chain processing device for business scenarios.

[0123] Those skilled in the art can understand that all or part of the steps of implementing the above-mentioned method embodiments can be completed by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, the steps of the above-mentioned method embodiments are executed; and the aforementioned storage medium includes: ROM, RAM, disk or optical disk and other media that can store program codes.

[0124] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present disclosure, rather than to limit them. Although the present disclosure 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 replace some or all of the technical features therein by equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present disclosure.

Claims

1. A call chain processing method for business scenarios, characterized in that: include: Displaying a business scenario call chain query interface, the business scenario call chain query interface comprising a first control for inputting identification information of a business scenario to be queried, a second control for inputting processing time of the business scenario, a third control for inputting business information, and a fourth control for triggering a query; In response to the first interactive operation directed to the fourth control, displaying a business call chain of the target business scenario according to the input relevant information of the target business scenario, where the relevant information includes at least one of identification information, processing time, and business information; In response to a second interactive operation directed to a target business call chain in the business call chain, displaying at least one system-level call chain of the target business call chain; The step of displaying the business call chain of the target business scenario according to the inputted relevant information of the target business scenario includes: Obtain a call log of the service bus; the service bus is an enterprise-level service bus; the call log includes the processing time of the business scenario, service address, request message, response message, service execution time, and tracking sequence number; According to the input relevant information of the target business scenario, the call log is analyzed for data relevance to obtain a business call chain of the target business scenario; the business call chain includes at least one front-end service, and the front-end service is registered with the enterprise service bus; Display the business call chain of the target business scenario.

2. The call chain processing method for business scenarios according to claim 1 is characterized in that: The step of performing data correlation analysis on the call log according to the input relevant information of the target business scenario to obtain the business call chain of the target business scenario includes: According to the relevant information of the target business scenario that has been input, data correlation analysis is performed on the call log of the service bus to obtain multiple capability families of the target business scenario. The capability family contains call logs with the same business information sorted by time, with the business call chain as the key of the key-value pair, and the request message, response message and related dependency information as the value of the key-value pair.

3. The call chain processing method for business scenarios according to claim 1 or 2, characterized in that: The step of displaying at least one system-level call chain of the target business call chain in response to the second interactive operation directed to the target business call chain in the business call chain includes: In response to a second interactive operation directed to a target business call chain in the business call chain, basic information of the target business call chain is displayed, wherein the basic information includes a request message, a response message, and a tracking sequence number of the system-level call chain; In response to a third interactive operation directed to the tracking sequence number, at least one system-level call chain of the target business call chain is displayed.

4. The call chain processing method for business scenarios according to claim 3 is characterized in that: The step of displaying at least one system-level call chain of the target business call chain in response to the third interactive operation oriented to the tracking sequence number includes: In response to the third interactive operation for the tracking sequence number, based on the tracking sequence number, at least one system-level call chain of the target business call chain is obtained, wherein the at least one system-level call chain of the target business call chain is obtained by concatenating system-level logs of various links corresponding to the tracking sequence number according to the Agent, and storing the concatenated system-level logs in a database; At least one system-level call chain of the target business call chain is displayed.

5. The call chain processing method for business scenarios according to claim 3 is characterized in that: Also includes: Determining the execution status of the target service call chain according to the basic information; In response to the execution state of the target service call chain being abnormal, it is determined that a fault occurs in the target service call chain.

6. The call chain processing method for business scenarios according to claim 5 is characterized in that: Also includes: After determining that the target service call chain fails, determining at least one system-level call chain of the target service call chain according to the tracking sequence number of the target service call chain; Based on the system-level call chain, a fault location is determined.

7. A call chain processing device for business scenarios, characterized in that: include: A first display module, used to display a business scenario call chain query interface, wherein the business scenario call chain query interface includes a first control for inputting identification information of a business scenario to be queried, a second control for inputting processing time of the business scenario, a third control for inputting business information, and a fourth control for triggering a query; A second display module, configured to respond to the first interactive operation directed to the fourth control and display a business call chain of the target business scenario according to the input relevant information of the target business scenario, wherein the relevant information includes at least one of identification information, processing time and business information; A third display module, configured to display at least one system-level call chain of the target business call chain in response to a second interactive operation directed to the target business call chain in the business call chain; The second display module is specifically used to: obtain a call log of a service bus; the service bus is an enterprise-level service bus; the call log contains the processing time of the business scenario, the service address, the request message, the response message, the service execution time, and the tracking sequence number; according to the relevant information of the input target business scenario, perform data correlation analysis on the call log to obtain a business call chain of the target business scenario; the business call chain contains at least one front-end service, and the front-end service is registered with the enterprise-level service bus; Displays the business call chain of the target business scenario.

8. An electronic device, characterized in that: include: Memory and processing; wherein: The memory is used to store program instructions; The processor is used to call program instructions in the memory to execute the call chain processing method for business scenarios according to any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that: Computer program instructions are stored in the computer-readable storage medium. When the computer program instructions are executed, the call chain processing method for business scenarios according to any one of claims 1 to 6 is implemented.

Images