Transaction landing point query method and device, equipment and medium

Abstract

This disclosure provides a method for querying transaction endpoints, applicable to the field of big data technology. The method includes: obtaining the first business primary key information of the transaction to be queried and information about the first business transaction scenario to which it belongs; obtaining the application link configured for the first business transaction scenario to obtain a first application link; determining the transaction identifier information used to identify the transaction to be queried in any first application within the first application link; and determining the endpoint server executing the transaction to be queried by retrieving the transaction identifier information from the logs of S servers in the first application. This disclosure also provides a transaction endpoint query device, equipment, storage medium, and program product.

Description

Technical Field

[0001] This disclosure relates to the field of big data technology, and more specifically to a method, apparatus, device, medium, and program product for querying transaction endpoints. Background Technology

[0002] Enterprises are undergoing rapid digital transformation, leading to a surge of technical upgrades aimed at improving system responsiveness, mitigating operational risks, and facilitating seamless integration with external systems. These upgrades have increased the number of servers and application instances required for various applications, particularly in long-chain business scenarios where the number of path branches has multiplied. Addressing issues arising during these upgrades and evaluating their effectiveness necessitates in-depth analysis at the application, server, and even log layers. All of this analysis must be grounded in precise execution path monitoring.

[0003] In realizing the concept disclosed herein, the inventors discovered at least the following problems in the prior art: Currently, when monitoring transaction paths, either staff members manually traverse and search to determine the path, or specific query tools are developed for certain applications to locate the path, which is inefficient and difficult to apply universally. Summary of the Invention

[0004] In view of the above problems, this disclosure provides a universal and automated method, apparatus, device, medium and program product for querying transaction endpoints.

[0005] A first aspect of this disclosure provides a method for querying transaction endpoints. The method includes: obtaining first business primary key information of a transaction to be queried and information about a first business transaction scenario to which it belongs; obtaining an application link configured for the first business transaction scenario to obtain a first application link; wherein the application link is a process connected by each of N applications as processing nodes, where N is an integer greater than or equal to 2; determining transaction identifier information used to identify the transaction to be queried in any first application within the first application link; and determining the endpoint server executing the transaction to be queried by retrieving the transaction identifier information from the logs of S servers in the first application, where S is an integer greater than or equal to 2. Specifically, determining the transaction identifier information used to identify the transaction to be queried in any first application within the first application link includes: when the first application is the first application in the first application link, determining the transaction identifier information as the first business primary key information; and when the first application is an application other than the first application, determining the transaction identifier information according to the transaction information transfer method between the first application and its upstream application in the first application link.

[0006] According to embodiments of this disclosure, the transaction information transfer method includes: the first application and its upstream application both using the same business primary key information to identify the same transaction; or the upstream application of the first application generates event information after processing a transaction and transmits the event information to the first application, wherein the first application uses the event information to identify the transaction transferred from its upstream application.

[0007] According to an embodiment of this disclosure, the method further includes: configuring the transaction information transfer method between each of the R applications and other applications, wherein the R applications include all applications in the first application link.

[0008] According to an embodiment of this disclosure, the method further includes: configuring M application links corresponding to M business transaction scenarios, wherein M is an integer greater than or equal to 1, and the M business transaction scenarios include the first business transaction scenario.

[0009] According to an embodiment of this disclosure, determining the landing server for executing the queried transaction by retrieving the transaction identifier information from the logs of the S servers of the first application includes: performing log retrieval on each of the S servers; and after retrieving the target log containing the transaction identifier information, using the server where the target log is located as the landing server.

[0010] According to an embodiment of this disclosure, the step of performing log retrieval server by server in the S servers includes: in each server, retrieving logs generated within a predetermined time period prior to the completion time of the transaction to be queried.

[0011] According to embodiments of this disclosure, after using the server where the target log is located as the landing server, the method further includes: downloading the target log; and / or correspondingly outputting information of the first application and information of the landing server.

[0012] According to embodiments of this disclosure, the method further includes setting a tag for the server of each of the R applications, wherein the tag is identification information tagged in natural language, and wherein the R applications include all applications in the first application chain. The corresponding output of the information of the first application and the landing server includes: correspondingly outputting the name of the first application and the tag of the landing server.

[0013] According to an embodiment of this disclosure, the step of outputting the information of the first application and the information of the landing server further includes: displaying the information of each application in the first application link and the information of the corresponding landing server in pairs, according to the order of the applications in the first application link.

[0014] According to an embodiment of this disclosure, obtaining the first business primary key information includes: in response to the initiation of the transaction to be queried, obtaining the first business primary key information.

[0015] A second aspect of this disclosure provides a transaction endpoint query device. The device includes a transaction module, a transaction chain module, a determination module, and a query module. The transaction module is used to obtain first business primary key information of the transaction to be queried and information about the first business transaction scenario to which it belongs. The transaction chain module is used to obtain an application chain configured for the first business transaction scenario to obtain a first application chain; wherein the application chain is a process connected by each application in N applications as a processing node, where N is an integer greater than or equal to 2. The determination module is used to determine transaction identifier information used to identify the transaction to be queried in any first application in the first application chain. The query module is used to determine the endpoint server executing the transaction to be queried by retrieving the transaction identifier information from the logs of S servers in the first application, where S is an integer greater than or equal to 2. Specifically, the determination module is used to determine the transaction identifier information as the first business primary key information when the first application is the first application in the first application chain; and when the first application is an application other than the first application, to determine the transaction identifier information according to the transaction information transfer method between the first application and its upstream application in the first application chain.

[0016] According to embodiments of this disclosure, the apparatus further includes a first configuration module. The first configuration module is used to configure the transaction information transfer method between each of the R applications and other applications, wherein the R applications include all applications in the first application chain.

[0017] According to embodiments of this disclosure, the apparatus further includes a second configuration module. The second configuration module is used to configure M application links corresponding to M business transaction scenarios, where M is an integer greater than or equal to 1, and the M business transaction scenarios include the first business transaction scenario.

[0018] According to embodiments of this disclosure, the apparatus further includes an output module. The output module is used to output information of the first application and information of the landing server.

[0019] According to embodiments of this disclosure, the apparatus further includes a tagging module. The tagging module is used to assign a tag to the server of each of the R applications, wherein the tag is identification information tagged in natural language, and wherein the R applications include all applications in the first application chain. Correspondingly, the output module is specifically used to output the name of the first application and the tag of the landing server.

[0020] A third aspect of this disclosure provides an electronic device. The electronic device includes one or more processors and one or more memories. The one or more memories are used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors perform the methods described above.

[0021] A fourth aspect of this disclosure also provides a computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, cause the processor to perform the methods described above.

[0022] A fifth aspect of this disclosure also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described method. Attached Figure Description

[0023] The foregoing contents, as well as other objects, features, and advantages of this disclosure, will become clearer from the following description of embodiments with reference to the accompanying drawings, in which:

[0024] Figure 1 The illustration shows an application scenario of the transaction endpoint query method, apparatus, device, medium, and program product according to embodiments of the present disclosure;

[0025] Figure 2 A flowchart illustrating a transaction location query method according to an embodiment of the present disclosure is shown schematically.

[0026] Figure 3 This illustration schematically shows a flowchart of determining the landing server through log retrieval in a transaction landing point query method according to an embodiment of the present disclosure;

[0027] Figure 4 The illustration schematically shows an architecture diagram of an application chain according to an embodiment of the present disclosure;

[0028] Figure 5 This illustration schematically shows the flow of a transaction location query method according to an embodiment of the present disclosure;

[0029] Figure 6 This illustration schematically shows a transaction location query method flow according to another embodiment of the present disclosure;

[0030] Figure 7 A flowchart illustrating a transaction location query method according to another embodiment of the present disclosure is shown schematically;

[0031] Figure 8 This schematic diagram illustrates a structural block diagram of a transaction location query device according to an embodiment of the present disclosure;

[0032] Figure 9 This illustration schematically shows the workflow of a transaction location query device according to an embodiment of the present disclosure during a testing process; and

[0033] Figure 10 A block diagram schematically illustrates an electronic device suitable for implementing the transaction landing point query method according to embodiments of the present disclosure. Detailed Implementation

[0034] The embodiments of the present disclosure will now be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the disclosure. In the following detailed description, numerous specific details are set forth to provide a thorough understanding of the embodiments of the present disclosure for ease of explanation. However, it will be apparent that one or more embodiments may be practiced without these specific details. Furthermore, descriptions of well-known structures and techniques are omitted in the following description to avoid unnecessarily obscuring the concepts of the present disclosure.

[0035] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit this disclosure. The terms “comprising,” “including,” etc., as used herein indicate the presence of the stated features, steps, operations, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, or components.

[0036] All terms used herein (including technical and scientific terms) have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein are to be interpreted in a manner consistent with the context of this specification, and not in an idealized or overly rigid way.

[0037] When using expressions such as "at least one of A, B and C", they should generally be interpreted in accordance with the meaning that is commonly understood by those skilled in the art (e.g., "a system having at least one of A, B and C" should include, but is not limited to, a system having A alone, a system having B alone, a system having C alone, a system having A and B, a system having A and C, a system having B and C, and / or a system having A, B and C, etc.).

[0038] In this article, an "application chain" refers to a process formed by connecting N applications, each of which acts as a processing node, where N is an integer greater than or equal to 2. The N applications in an application chain are all the applications used to implement transactions in the corresponding business transaction scenario. The connection relationship between these N applications can be serial or parallel. In a serial connection, there is a calling and being called relationship between two applications. That is, when executing a transaction, the upstream application calls the immediately following downstream application.

[0039] In this article, "landing point" refers to the server that executes a transaction in each application, also known as the "landing point server".

[0040] The various embodiments of this disclosure provide a universal and automated method, apparatus, device, medium, and program product for querying transaction landing points by analyzing, refining, and abstracting the transaction path monitoring achieved through manual retrieval.

[0041] Specifically, the transaction endpoint query method implemented according to this disclosure can be achieved through the following operations. First, obtain the first business primary key information of the transaction to be queried and the information of the first business transaction scenario to which it belongs. Then, obtain the application link configured for the first business transaction scenario to obtain the first application link. Next, determine the transaction identifier information used to identify the transaction to be queried in any first application in the first application link, wherein when the first application is the first application in the first application link, the transaction identifier information is determined to be the first business primary key information, and when the first application is an application other than the first application, the transaction identifier information is determined according to the transaction information transfer method between the first application and its upstream application in the first application link. Afterwards, by retrieving the transaction identifier information from the logs of S servers of the first application, the endpoint server executing the transaction to be queried is determined, where S is an integer greater than or equal to 2.

[0042] According to embodiments of this disclosure, user operations can be used to configure business transaction scenarios and corresponding application links. Based on this, the location and query of the endpoint server for any transaction within that business transaction scenario under any application can be achieved. This allows for independent use across industries, business transaction scenarios, transactions, and applications, decoupling the query of transaction endpoints from these elements. It does not need to serve a specific industry or business transaction scenario; instead, the binding relationship can be configured according to analysis and monitoring needs, thus realizing a general solution framework for querying transaction endpoints.

[0043] Figure 1The illustration schematically depicts an application scenario of a transaction endpoint query method, apparatus, device, medium, and program product according to embodiments of this disclosure. It should be noted that... Figure 1 The examples shown are merely examples of system architectures that can be applied to the embodiments of this disclosure, in order to help those skilled in the art understand the technical content of this disclosure, but do not mean that the embodiments of this disclosure cannot be used in other devices, systems, environments or scenarios.

[0044] like Figure 1 As shown, application scenario 100 according to this embodiment may include at least one terminal device (three are shown in the figure: terminal devices 101, 102, and 103), network 104, server 105, network 106, and clusters 107 and 108. Network 104 is used to provide a communication link between terminal devices 101, 102, and 103 and server 105. Network 106 is used to provide a communication link between server 105 and clusters 107 and 108. Networks 104 and 106 may include various connection types, such as wired or wireless communication links or fiber optic cables, etc.

[0045] Terminal devices 101, 102, and 103 can be various electronic devices with displays and web browsing capabilities, including but not limited to smartphones, tablets, laptops, and desktop computers. Various communication client applications can be installed on terminal devices 101, 102, and 103, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, and social media platforms (for example only).

[0046] Server 105 could be a server that provides various services, such as a website's backend management server (for example only).

[0047] Clusters 107 and 108 are server clusters running different applications. For example, cluster 107 is a server cluster running application A, and the diagram shows an example with 4 servers. Cluster 108 is a server cluster running application B, and the diagram shows an example with 4 servers.

[0048] Users can use terminal devices 101, 102, and 103 to interact with server 105 via network 104 to receive or send messages, etc.

[0049] For example, a user initiates a transaction to server 105 using a client application on terminal devices 101, 102, and 103. Upon receiving the transaction request, server 105 can forward it to the corresponding application for execution based on the business transaction application scenario to which the transaction belongs. Suppose that the transaction in this business transaction scenario requires completion by both application A and application B, where application A is an upstream application of application B. Server 105 can forward the transaction request to a server (e.g., A1) in cluster 107 running application A for processing. After server A1 completes its processing, it calls a server (e.g., B2) in cluster 108 running application B for further processing. Once server B2 in cluster 108 has completed its processing, it can return the result to server 105, which then returns the final result to terminal devices 101, 102, and 103. In this scenario, the application chain of the business transaction scenario to which the user-initiated transaction belongs is application A -> application B, and the execution path information of the transaction is "application A, server A1" -> "application B, server B1".

[0050] In some embodiments, networks 104 and 106 can communicate. In other embodiments, networks 104 and 106 may be the same network or partially overlapping networks. Accordingly, terminal devices 101, 102, and 103 can also connect to clusters 107 and 108 through networks 104 and 106. Thus, users can also use terminal devices 101, 102, and 103 to initiate related transactions to clusters 107 and / or 108. When a transaction requires the joint completion of application A and application B, and application A is an upstream application of application B, users can also send a transaction request to cluster 107 through terminal devices 101, 102, and 103. This transaction request may reach server A1 in cluster 107. After server A1 in cluster 107 completes its processing, it calls server B2 in cluster 108. After server B2 in cluster 108 completes its processing, it feeds back the processing result to terminal devices 101, 102, and 103.

[0051] It is understood that the example above, in which only two applications are serially connected in the application link, is merely exemplary, and this disclosure does not limit the number of applications in the application link or the serial-parallel relationship.

[0052] It should be noted that the transaction endpoint query method provided in this embodiment can generally be executed by server 105. For example, server 105 can query the endpoint servers in various applications (e.g., application A and / or application B) for the transaction to be queried, which is determined based on the user's operations on terminal devices 101, 102, and 103, thereby generating execution path information for the transaction to be queried. Accordingly, the transaction endpoint query device, equipment, medium, and program product provided in this embodiment can also be located in server 105. Of course, in other embodiments, the transaction endpoint query method provided in this embodiment can also be executed by cluster 107 or cluster 108. Accordingly, the transaction endpoint query device provided in this embodiment can also be located in cluster 107 or cluster 108.

[0053] It should be understood that Figure 1 The number of terminal devices, networks, servers, and clusters shown is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, servers, and clusters can be included.

[0054] The following will be based on Figure 1 The described application scenarios, through Figures 2-7 The transaction location query method of this disclosure embodiment will be described in detail, wherein the method of this disclosure embodiment is executed by server 105 as an example.

[0055] Figure 2 A flowchart illustrating a transaction location query method according to an embodiment of the present disclosure is shown schematically.

[0056] like Figure 2 As shown, the transaction landing point query method according to this embodiment may include operations S210 to S240.

[0057] In operation S210, obtain the primary key information of the first business transaction to be queried and the information of the first business transaction scenario to which it belongs.

[0058] This primary key information is the unique identifier of the transaction to be queried. For example, the order number in an order payment transaction or the delivery tracking number in a logistics delivery transaction.

[0059] In one embodiment, the first business primary key information and the information of the first business transaction scenario to which it belongs can be input by the user through operations on terminal devices 101, 102, and 103. For example, when testers want to monitor the gray-scale operation status of a product, the IPv4 / IPv6 switchover, or the switching effect between a mainframe and an open platform, a corresponding front-end page can be developed. Then, testers can open the front-end page on terminal devices 101, 102, and 103, select the transaction scenario information to which the transaction to be queried belongs, and input the first business primary key information.

[0060] In one embodiment, server 105 may automatically obtain the first business primary key information and the information of the first business transaction scenario. For example, a script can be configured to allow server 105 to periodically or conditionally obtain the business primary key information of all transactions under a certain business transaction scenario within a certain period, thereby allowing each transaction under that business transaction scenario within that period to be queried. When obtaining the business primary key information, server 105 can extract the business primary key information from the processing results information fed back to terminal devices 101, 102, and 103.

[0061] According to one embodiment of this disclosure, first business primary key information can be obtained in response to the initiation of a transaction to be queried. For example, when a user initiates a transaction to be queried through terminal devices 101, 102, and 103, server 105 processes the received transaction request and obtains the business primary key information of the transaction while forwarding the transaction request to the cluster of the corresponding application. In this way, the business primary key information of the transaction to be queried can be obtained automatically.

[0062] In operation S220, the application link configured for the first business transaction scenario is obtained, resulting in the first application link. The application link is a process formed by connecting each of N applications as a processing node, where N is an integer greater than or equal to 2.

[0063] The application chain configured for each business transaction scenario in this disclosure is an execution flow composed of applications used to implement transactions in that business transaction scenario.

[0064] In addition to the switching and calling relationships between application packages, the application chain can also include detailed information such as server information under each application (e.g., server IP, server username, server password and / or server identifier) ​​and log information in each server (e.g., log path, log file type).

[0065] In operation S230, determine the transaction identification information used to identify the transaction to be queried in any of the first applications in the first application link.

[0066] When the first application is the first application in the first application chain, the transaction identifier information is determined to be the first business primary key information.

[0067] When the first application is an application other than the first application, the transaction identification information is determined according to the transaction information transfer method between the first application and its upstream application in the first application link.

[0068] There are generally two ways to transfer transaction information between applications: First, adjacent upstream and downstream applications use the same business primary key information to identify the same transaction (hereinafter referred to as "the first transfer method"); Second, after processing a transaction, the upstream application generates event information (for example, by recording it through a specific field) and passes the event information to the downstream application, so that the downstream application can use the event information to identify the transaction transferred from its upstream application (hereinafter referred to as "the second transfer method").

[0069] When a first application transfers transaction information with its upstream application using the first transfer method, the transaction identifier information of the transaction to be queried in the first application is the business primary key information of that transaction in its upstream application. For example, when the upstream application of the first application is the first application in the first application chain, the transaction identifier information in that first application is the first business primary key information. As another example, if the upstream application of the first application is an application in the middle of the first application chain, and the transaction information transfer methods between multiple applications preceding the first application in the first application chain are all the first transfer method, the transaction identifier information in that first application is still the first business primary key information. However, if the transaction information transfer methods between multiple applications preceding the first application in the first application chain include the second transfer method, then it is necessary to query the business primary key information of the transaction to be queried in the upstream application of the first application. The queried business primary key information may not be the same as the first business primary key information.

[0070] When the first application and its upstream application transfer transaction information using the second transfer method, it is necessary to query the event information from the log record of the transaction to be queried in the upstream application of the first application, so as to use it as the transaction identifier information of the transaction to be queried in the first application.

[0071] In operation S240, the server that executes the transaction to be queried is determined by retrieving transaction identification information from the logs of S servers in the first application, where S is an integer greater than or equal to 2.

[0072] In the transaction landing point query method of the embodiments of this disclosure, users can selectively query landing point servers in any one or more applications in the first application chain according to their needs. For example, only one or some applications may be subject to gray-scale operation. In this case, only the application subject to gray-scale operation can be used as the first application to query the landing point servers therein.

[0073] Alternatively, according to other embodiments of this disclosure, the landing server of each application can be queried in the order of all applications in the first application link. That is, all applications in the first application link are retrieved and queried sequentially as the first application. In this way, the execution path information of the transaction to be queried can be obtained. In this manner, based on the user's pre-configured business transaction scenario and its application link, transaction identification information can be retrieved in different application servers, realizing complete detection of the execution path of the transaction in the business transaction scenario and improving the efficiency of monitoring the execution path of long-link transactions.

[0074] Figure 3 The flowchart illustrating the process of determining the landing server by log retrieval in the transaction landing query method according to an embodiment of the present disclosure is shown. Figure 4 The illustration shows a schematic diagram of the application chain architecture according to an embodiment of the present disclosure.

[0075] like Figure 3 As shown, the process of determining the landing server in operation S240 according to this embodiment may include operations S301 to S303. The following is in conjunction with... Figure 4 The following example illustrates this.

[0076] First, in operation S301, logs are retrieved one by one from the S servers.

[0077] refer to Figure 4 Assume the application path for the transaction to be queried is application A -> application B. To determine the landing server in application A, logs can be retrieved one by one from the four servers A1, A2, A3, and A4 of application A. Similarly, to determine the landing server in application B, logs can be retrieved one by one from the four servers B1, B2, B3, and B4 of application B.

[0078] Considering that an application may be used in multiple business transaction scenarios and a large number of transactions may occur at the same time, when performing log retrieval on each server, logs generated within a predetermined time period (e.g., 1 hour) prior to the completion time of the transaction to be queried can be retrieved. This avoids both vulnerability logs and the retrieval of massive amounts of logs.

[0079] Then, in operation S302, after retrieving the target log containing transaction identifier information, the server where the target log is located is used as the destination server.

[0080] In one embodiment, once transaction identifier information is retrieved, the search can be stopped and the current application can be exited. For example, in Figure 4 In the example, log retrieval can be performed first on the server of application A. Once the transaction identifier information is retrieved, the process can exit application A and proceed to the four servers of application B to retrieve logs one by one. In this way, transaction identifier information can be retrieved on different application servers according to the priority of the application call relationship in the first application chain, realizing complete monitoring and tracking of the execution path of the transaction to be queried.

[0081] In some embodiments, target logs can be downloaded before exiting the current application for later querying, thus broadening the scope of personalized query applications.

[0082] Next, in operation S303, the information of the first application and the landing server are output. For example, application A - server A1.

[0083] In some implementations, the server of each of the R applications can be pre-labeled, where the label is information used for identification in natural language, and the R applications include all applications in the first application chain.

[0084] Typically, servers are identified by serial numbers or similar encodings, and the identification methods may differ between different types or manufacturers of servers. Using serial numbers and similar identifiers is insufficient for purely IT-savvy users such as testers and maintenance personnel to effectively distinguish servers. Therefore, in some embodiments of this disclosure, servers can be explicitly distinguished by assigning tags in natural language to them. In this way, during operation S303, the name of the first application and the tag of the landing server can be output, allowing testers, maintenance personnel, and other users to quickly and clearly locate the landing server from among the multiple servers of each application.

[0085] In other implementations, when a landing server has been identified for each application in the first application chain, the information of each application in the first application chain and its corresponding landing server can be displayed in pairs, according to the order of the applications in the first application chain. This allows for the display of the complete execution path information of the transaction to be queried, achieving complete monitoring of the execution path of the transaction.

[0086] When determining the landing server for each application in the first application chain, the log retrieval process can be divided into the application layer, server layer, and log layer. The application layer retrieval order is based on the order of the applications in the application chain; the server layer retrieval order is based on the order of the server tags maintained by the operator under each application; after entering the log layer, the log can be retrieved sequentially from front to back according to the order of the log lines printed.

[0087] Figure 5 The flowchart of a transaction location query method according to an embodiment of the present disclosure is illustrated. Figure 5 The business transaction scenario shown involves two applications: Application A and Application B, with each application deployed on four servers. For details, please refer to [reference needed]. Figure 4 The illustration. In Figure 5 In this scenario, application A and application B can connect serially and transfer information according to the first transfer method described above, meaning that both application A and application B use the same business primary key information to identify the same transaction. It should be noted that the following... Figure 5 The description of the process shown is merely an exemplary embodiment of the transaction landing point query method of this disclosure and does not constitute a limitation of this disclosure.

[0088] like Figure 5 As shown, the specific implementation of this transaction landing point query method may include steps S51 to S58.

[0089] S51: Users (e.g., testers, maintenance personnel, supervisors, etc.) add business transaction scenario names to the front-end pages of terminal devices 101, 102, and 103.

[0090] S52: Users maintain detailed information about applications A and B under the business transaction scenario name, such as application name, server IP, server username, server password, log path, log file, and server identifier.

[0091] S53: The user initiates a transaction under the business transaction scenario name and records the business primary key information.

[0092] S54: Users select the business transaction scenario name and enter the business primary key information on the front-end page of terminal devices 101, 102, and 103.

[0093] S55: Server 105 automatically connects to server A1 and queries the logs within one hour from the time the transaction was completed (the time can be preset in the system) based on the log path and file name, avoiding the need to query massive amounts of logs.

[0094] S56: Match the user-entered business primary key information sequentially according to the log printing order. Once a match is found, automatically download the log file on server A1 and exit server A1 to perform the same logical search on server B1. If no business primary key information is found on server A1, automatically exit server A1 and enter server A2 to perform the same logical search, repeating this process until the business primary key information is found on all four servers of application A, then exit application A. Then, proceed to application B to perform the same logical search.

[0095] S57: The information of the two servers (i.e., the landing servers) containing business primary key information in the retrieved logs are precisely matched with the server tags that the user has maintained in advance. After a successful match, the search results are output to the front-end pages of terminal devices 101, 102, and 103 in the form of "Application A - Server Tag; Application B - Server Tag" for display.

[0096] S58: Users can download the logs containing the business primary key information (i.e., the target logs) from the system for personalized retrieval for other purposes.

[0097] If there is a need to retrieve the server landing point of other transactions under the same business transaction scenario, simply execute S53-S58.

[0098] Figure 6 The flowchart of a transaction location query method according to another embodiment of the present disclosure is illustrated schematically. Figure 6 The business transaction scenario shown involves two applications: Application A and Application B, with each application deployed on four servers. For details, please refer to [reference needed]. Figure 4 The illustration. In Figure 6 In this scenario, application A and application B can be connected serially and transfer information according to the second transfer method described above. That is, after application A completes its processing, it generates an event message (e.g., an event number), and then transmits this event number along with the intermediate processing result of the transaction to application B. It should be noted that the following... Figure 6 The process description shown is only an exemplary embodiment of the transaction landing point query method of this disclosure and does not constitute a limitation of this disclosure.

[0099] like Figure 6 As shown, the specific implementation of this transaction landing point query method may include steps S61 to S610.

[0100] S61: Users (e.g., testers, maintenance personnel, supervisors, etc.) add the name of the business transaction scenario in the front-end page of terminal devices 101, 102, and 103.

[0101] S62: Under the name of this business transaction scenario, the user adds detailed information for application A and application B, such as application name, server IP, server username, server password, log path, log file, server tag, etc. The user must also maintain the transaction information transfer method for application A and application B under this business transaction scenario.

[0102] Taking order payment as an example, a transaction can flow through two applications sequentially (e.g., an online payment application and a personal e-banking application). Assuming application A is the online payment application and application B is the personal e-banking application, when implementing an order payment transaction, application A needs to call application B.

[0103] When querying transaction endpoints, for the same payment transaction, log retrieval in application B requires first retrieving the transaction's "event number" from application A's logs. Conversely, retrieval of logs in application A can rely on the user-recorded order number (i.e., business primary key information). Therefore, the field name (e.g., serialno) and inter-application call flag (sign) for the "event number" used for transaction information transfer between application A and application B can be pre-maintained in the details of both applications A and B for subsequent correlation retrieval.

[0104] S63: When a user initiates a business transaction in this scenario, the business primary key information is recorded.

[0105] S64: Users select the business transaction scenario name and enter the business primary key information on the front-end page of terminal devices 101, 102, and 103.

[0106] S65: Server 105 automatically connects to Server A1 and queries the logs within one hour from the time the transaction was completed (the time can be preset in the system) based on the log path and file name, avoiding the need to query massive amounts of logs.

[0107] S66: Match the user-entered business primary key information sequentially according to the log printing order (e.g., starting from the latest printed log and proceeding backwards). Once the business primary key information is successfully matched, the system will precisely search for the "call flag (sign)" of application A calling application B, starting from the log line containing the business primary key information. After matching the call flag (sign), the system will automatically retrieve the event number field serialno from the log line containing the call flag (sign) and record the value of this field to obtain the event number. If no business primary key information is matched in A1, the system will automatically exit server A1 and search other servers in application A sequentially until the business primary key information is retrieved and the event number is obtained. Finally, the system will automatically download the log file on that server.

[0108] S67: Server 105 automatically connects to B1 and queries the logs within one hour from the time the transaction was completed (the time can be preset in the system) based on the log path and file name.

[0109] S68: Match the serialno field values ​​sequentially according to the log printing order. Once a match is found, the corresponding log file on that server will be automatically downloaded. If no match is found, search servers B2, B3, and B4 in sequence until a match is found.

[0110] S69: The information of the two servers (i.e., the landing servers) containing business primary key information in the retrieved logs are precisely matched with the server tags that the user has maintained in advance. After a successful match, the search results are output to the front-end pages of terminal devices 101, 102, and 103 in the form of "Application A - Server Tag; Application B - Server Tag" for display.

[0111] S610: Users can download target logs from the system for personalized searches for other purposes.

[0112] If there is a need to retrieve server landing points in the same business transaction scenario in the future, simply execute S63-S610.

[0113] Understandable. Figure 5 and Figure 6 The two application scenarios shown can be complementary, representing two typical methods in the transaction landing point query scenario, and can be extended in multiple applications.

[0114] When applications A and B, which constitute an upstream and downstream relationship, each have four servers connected to them, given the uncertainty of the transaction's landing point, it's not difficult to deduce 16 possible landing point scenarios through permutations and combinations. When applications A and B are involved in canary releases (e.g., two servers in applications A and / or B are canary servers, and the other two are not), manually locating the landing server requires repeated traversal, potentially requiring 16 repetitive queries in extreme cases. However, using the transaction landing point query method of this disclosure, regardless of whether applications A and B transfer via the first or second method, only the business transaction scenario information, the corresponding application link, and the transfer method between upstream and downstream applications need to be maintained once at the front end. After inputting the business primary key information and selecting the name of the business transaction scenario, automatic matching and retrieval can be performed, eliminating the repetitive manual query costs for testers. The effectiveness is evident.

[0115] Figure 7 A flowchart illustrating a transaction location query method according to another embodiment of the present disclosure is shown.

[0116] like Figure 7 As shown, the transaction landing point query method according to this embodiment may include operation S711 and / or operation S712 before operation S210 to operation S240.

[0117] When operating S711, configure M application links corresponding to M business transaction scenarios, where M is an integer greater than or equal to 1, and the M business transaction scenarios include the first business transaction scenario.

[0118] In operation S712, the transaction information transfer method between each of the R applications and other applications is configured, where the R applications include all applications in the first application link.

[0119] In one embodiment, as described above Figure 5 and Figure 6 This illustration shows that when performing a query, you can configure the application chain for the corresponding business transaction scenario and the method for transferring transaction information between various applications within that application chain. Subsequently, if there are transactions under the same business transaction scenario, they can be directly reused.

[0120] In other implementations, various business transaction scenarios provided by organizations (e.g., enterprises or departments) can be collected, and corresponding application links can be pre-configured. Additionally, various applications maintained within the organization can be collected, and transaction information transfer methods between each application and other applications can be set based on the calling or being called relationships between each application and other applications. This approach allows for one-time maintenance followed by long-term repetition, and facilitates automated querying of the entire transaction endpoint process. It also enables flexible customization and rapid deployment of application links according to business needs, decoupling the query of transaction endpoints from specific business transaction scenarios and applications.

[0121] As can be seen, the transaction endpoint query method of this disclosure has a wide range of applications and is easy to promote. It can be widely used in testing business systems, monitoring server status, and analyzing cluster problems. For example, in daily online payment business testing, after completing a payment transaction, testers need to pay attention to whether the server through which the transaction flows is running a grayscale version or a non-grayscale version, or which specific server the transaction flows through, so that they can log in to the server to obtain logs to analyze problems.

[0122] Based on the transaction endpoint query methods of the above embodiments, this disclosure also provides a transaction endpoint query device. The following will be combined with... Figure 8 and Figure 9 The device is described in detail.

[0123] Figure 8 A schematic block diagram of a transaction location query device 800 according to an embodiment of the present disclosure is shown.

[0124] like Figure 8 As shown, according to embodiments of this disclosure, the device 800 may include a transaction module 810, a transaction chain module 820, a determination module 830, and a query module 840. According to other embodiments of this disclosure, the device 800 may further include at least one of a first configuration module 850, a second configuration module 860, a tag module 870, or an output module 880. The device 800 can be used to implement [see...]. Figures 2-7 The described method for querying transaction landing points.

[0125] Specifically, the transaction module 810 is used to obtain the first business primary key information of the transaction to be queried and the information of the first business transaction scenario to which it belongs. In one embodiment, the transaction module 810 performs the operation S210 described above.

[0126] The transaction chain module 820 is used to obtain the application chain configured for the first business transaction scenario, thus obtaining the first application chain. The application chain is a process formed by connecting each of N applications as a processing node, where N is an integer greater than or equal to 2. The transaction chain module 820 can sort out the applications called and their calling relationships under the first business transaction scenario, construct the application chain, and realize the permutation and combination of applications under the first business transaction scenario. In one embodiment, the transaction chain module 820 can execute the operation S220 described above.

[0127] The determining module 830 is used to determine the transaction identifier information used to identify the transaction to be queried in any of the first applications in the first application chain. Specifically, when the first application is the first application in the first application chain, the transaction identifier information is determined to be the first business primary key information; and when the first application is an application other than the first application, the transaction identifier information is determined according to the transaction information transfer method between the first application and its upstream application in the first application chain. In one embodiment, the determining module 830 can perform the operation S230 described above.

[0128] The query module 840 is used to determine the landing server of the transaction to be queried by retrieving transaction identification information from the logs of S servers in the first application, where S is an integer greater than or equal to 2. In one embodiment, the query module 840 can perform the operation S240 described above.

[0129] The query module 840 can perform precise retrieval in the logs of multiple servers of the first application based on the primary key information of the first business.

[0130] The first configuration module 850 is used to configure the transaction information transfer method between each of the R applications and other applications, wherein the R applications include all applications in the first application link. In one embodiment, the first configuration module 850 can perform the operation S712 described above.

[0131] The second configuration module 860 is used to configure M application links corresponding to M business transaction scenarios, where M is an integer greater than or equal to 1, and the M business transaction scenarios include the first business transaction scenario. In one embodiment, the second configuration module 860 can execute the operation S711 described above.

[0132] The tagging module 870 is used to set tags for the servers of each of the R applications. The tags are identification information tagged in natural language. The R applications include all applications in the first application chain. The tagging module 870 tags the application server information, transforming implicit information into explicit information. Correspondingly, the output module 880 can output the name of the first application and the tag of the landing server. Thus, by using server information tagging, users can quickly and clearly locate the execution path of a transaction.

[0133] The output module 880 is used to output information about the first application and the landing server.

[0134] Figure 9 This schematically illustrates the workflow of a transaction endpoint query device 800 according to an embodiment of the present disclosure during a testing process, wherein... Figure 9 The illustration is merely exemplary and does not constitute a limitation on device 800.

[0135] like Figure 9 As shown, the operational workflow of each module in the transaction landing point query device 800 during the testing process can include steps 1) to 7).

[0136] Step 1), the user initiates a business transaction through interaction with the transaction module 810.

[0137] Step 2), after the business transaction is processed by each application server, business primary key information is generated;

[0138] Step 3) Based on user operation, input business primary key information in query module 840 for retrieval and matching;

[0139] Step 4), the query module 840 receives the application link and transaction information transfer method pre-configured in the transaction chain module 820 (through the first configuration module 850 and the second configuration module 860), and performs the query according to the information; wherein, the function of receiving query clues in the query module 840 in step 4) is basically the same as the function of the determination module 830.

[0140] Step 5) The query module 840 interacts with the servers under each application, including connecting, extracting logs, retrieving primary key information, and transmitting server information back.

[0141] Step 6) The query module 840 maps the server information returned to the record to the preset server tags in the tag module 870.

[0142] Step 7), the output module 880 outputs the application name and the corresponding label of the landing server to the user.

[0143] According to embodiments of this disclosure, any and multiple modules selected from transaction module 810, transaction chain module 820, determination module 830, query module 840, first configuration module 850, second configuration module 860, tag module 870, or output module 880 can be combined into one module, or any one of these modules can be split into multiple modules. Alternatively, at least some of the functions of one or more of these modules can be combined with at least some of the functions of other modules and implemented in one module. According to embodiments of this disclosure, at least one of the transaction module 810, transaction chain module 820, determination module 830, query module 840, first configuration module 850, second configuration module 860, tag module 870, or output module 880 can be at least partially implemented as hardware circuitry, such as a field-programmable gate array (FPGA), programmable logic array (PLA), system-on-a-chip, system-on-a-substrate, system-on-package, application-specific integrated circuit (ASIC), or any other reasonable means of integrating or packaging circuitry, or implemented in software, hardware, or firmware, or in any suitable combination of any of these three implementation methods. Alternatively, at least one of the transaction module 810, transaction chain module 820, determination module 830, query module 840, first configuration module 850, second configuration module 860, tag module 870, or output module 880 can be at least partially implemented as a computer program module, which, when run, can perform corresponding functions.

[0144] Figure 10 A block diagram schematically illustrates an electronic device suitable for implementing the transaction landing point query method according to embodiments of the present disclosure.

[0145] like Figure 10 As shown, an electronic device 1000 according to an embodiment of the present disclosure includes a processor 1001, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1002 or a program loaded from a storage portion 1008 into a random access memory (RAM) 1003. The processor 1001 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or an associated chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 1001 may also include onboard memory for caching purposes. The processor 1001 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.

[0146] RAM 1003 stores various programs and data required for the operation of electronic device 1000. Processor 1001, ROM 1002, and RAM 1003 are interconnected via bus 1004. Processor 1001 performs various operations of the method flow according to embodiments of the present disclosure by executing programs in ROM 1002 and / or RAM 1003. It should be noted that programs may also be stored in one or more memories other than ROM 1002 and RAM 1003. Processor 1001 may also perform various operations of the method flow according to embodiments of the present disclosure by executing programs stored in one or more memories.

[0147] According to embodiments of this disclosure, the electronic device 1000 may further include an input / output (I / O) interface 1005, which is also connected to a bus 1004. The electronic device 1000 may also include one or more of the following components connected to the I / O interface 1005: an input section 1006 including a keyboard, mouse, etc.; an output section 1007 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 1008 including a hard disk, etc.; and a communication section 1009 including a network interface card such as a LAN card, modem, etc. The communication section 1009 performs communication processing via a network such as the Internet. A drive 1010 is also connected to the I / O interface 1005 as needed. A removable medium 1011, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on the drive 1010 as needed so that computer programs read from it can be installed into the storage section 1008 as needed.

[0148] This disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or it may exist independently and not assembled into the device / apparatus / system. The computer-readable storage medium carries one or more programs that, when executed, implement the method according to the embodiments of this disclosure.

[0149] According to embodiments of this disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, such as including, but not limited to: portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this disclosure, the computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. For example, according to embodiments of this disclosure, the computer-readable storage medium may include ROM 1002 and / or RAM 1003 and / or one or more memories other than ROM 1002 and RAM 1003 described above.

[0150] Embodiments of this disclosure also include a computer program product comprising a computer program containing program code for performing the methods shown in the flowchart. When the computer program product is run on a computer system, the program code is used to cause the computer system to implement the methods provided in the embodiments of this disclosure.

[0151] When the computer program is executed by the processor 1001, it performs the functions defined in the system / apparatus of this disclosure embodiments. According to embodiments of this disclosure, the systems, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0152] In one embodiment, the computer program may rely on a tangible storage medium such as an optical storage device or a magnetic storage device. In another embodiment, the computer program may also be transmitted and distributed in the form of signals over a network medium, and may be downloaded and installed via the communication section 1009, and / or installed from a removable medium 1011. The program code contained in the computer program can be transmitted using any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination thereof.

[0153] In such an embodiment, the computer program can be downloaded and installed from a network via communication section 1009, and / or installed from removable medium 1011. When the computer program is executed by processor 1001, it performs the functions defined in the system of this disclosure embodiment. According to embodiments of this disclosure, the systems, devices, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0154] According to embodiments of this disclosure, program code for executing the computer programs provided in embodiments of this disclosure can be written in any combination of one or more programming languages. Specifically, these computational programs can be implemented using high-level procedural and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, languages ​​such as Java, C++, Python, "C", or similar programming languages. The program code can execute entirely on a user's computing device, partially on a user's device, partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0155] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0156] Those skilled in the art will understand that the features described in the various embodiments and / or claims of this disclosure can be combined or combined in various ways, even if such combinations or combinations are not explicitly described in this disclosure. In particular, the features described in the various embodiments and / or claims of this disclosure can be combined or combined in various ways without departing from the spirit and teachings of this disclosure. All such combinations and / or combinations fall within the scope of this disclosure.

[0157] The embodiments of this disclosure have been described above. However, these embodiments are for illustrative purposes only and are not intended to limit the scope of this disclosure. Although various embodiments have been described above, this does not mean that the measures in the various embodiments cannot be used advantageously in combination. The scope of this disclosure is defined by the appended claims and their equivalents. Various substitutions and modifications can be made by those skilled in the art without departing from the scope of this disclosure, and all such substitutions and modifications should fall within the scope of this disclosure.

Claims

1. A method for querying transaction landing points, comprising: Obtain the primary key information of the first business transaction to be queried and the information of the first business transaction scenario to which it belongs; Obtain the application link configured for the first business transaction scenario to obtain the first application link; wherein, the application link is a process connected by each application in N applications as a processing node, where N is an integer greater than or equal to 2; wherein, each application in the application link is run by a server cluster consisting of multiple servers; Determine the transaction identifier information used to identify the transaction to be queried in any of the first applications in the first application chain, including: When the first application is the first application in the first application chain, the transaction identifier information is determined to be the first business primary key information; and When the first application is an application other than the first application, the transaction identification information is determined according to the transaction information transfer method between the first application and its upstream application in the first application link; By retrieving the transaction identifier information from the logs of S servers in the first application, the landing server executing the transaction to be queried is determined, where S is an integer greater than or equal to 2; The transaction information transfer methods include: The first application and its upstream application both use the same business primary key information to identify the same transaction, or After processing a transaction, the upstream application of the first application generates event information and transmits the event information to the first application. The first application uses the event information to identify transactions transferred from its upstream application. The first application identifies a transaction transferred from its upstream application using the event information by: querying the information of the transaction to be executed from the logs of the server cluster of the upstream application of the first application based on the transaction identifier information used to identify the transaction to be executed in the upstream application, and obtaining the event information therefrom.

2. The method according to claim 1, wherein, The method further includes: Configure the transaction information transfer method between each of the R applications and other applications, wherein the R applications include all applications in the first application link.

3. The method according to claim 1, wherein, The method further includes: Configure M application links corresponding to M business transaction scenarios, where M is an integer greater than or equal to 1, and the M business transaction scenarios include the first business transaction scenario.

4. The method according to claim 1, wherein, The step of determining the landing server that executed the queried transaction by retrieving the transaction identifier information from the logs of the S servers of the first application includes: Log retrieval is performed on each of the S servers; and After retrieving the target log containing the transaction identifier information, the server where the target log is located is used as the landing server.

5. The method according to claim 4, wherein, The step of performing log retrieval server by server among the S servers includes: In each server, logs generated within a predetermined time period prior to the completion time of the transaction to be queried are retrieved.

6. The method according to claim 4, wherein, After using the server where the target log is located as the destination server, the method further includes: Download the target log; and / or The information of the first application and the information of the landing point server are output accordingly.

7. The method according to claim 6, wherein, The method further includes: setting a label for the server of each of the R applications, wherein the label is identification information marked in natural language, and wherein the R applications include all applications in the first application chain; The corresponding output of the information of the first application and the landing server includes: the corresponding output of the name of the first application and the label of the landing server.

8. The method according to claim 6 or 7, wherein, The corresponding output of the information of the first application and the information of the landing server also includes: According to the order of the applications in the first application link, the information of each application in the first application link and the information of the corresponding landing server are displayed in pairs.

9. A transaction location query device, comprising: The transaction module is used to obtain the primary key information of the first business of the transaction to be queried and the information of the first business transaction scenario to which it belongs; The transaction chain module is used to obtain the application chain configured for the first business transaction scenario to obtain the first application chain; wherein, the application chain is a process formed by connecting each application in N applications as a processing node, where N is an integer greater than or equal to 2; wherein, each application in the application chain is run by a server cluster composed of multiple servers. The determining module is configured to determine transaction identifier information used to identify the transaction to be queried in any of the first applications in the first application chain, including: When the first application is the first application in the first application chain, the transaction identifier information is determined to be the first business primary key information; and When the first application is an application other than the first application, the transaction identification information is determined according to the transaction information transfer method between the first application and its upstream application in the first application link; The query module is used to determine the landing server that executed the transaction to be queried by retrieving the transaction identification information from the logs of S servers in the first application, where S is an integer greater than or equal to 2. The transaction information transfer methods include: The first application and its upstream application both use the same business primary key information to identify the same transaction, or After processing a transaction, the upstream application of the first application generates event information and transmits the event information to the first application. The first application uses the event information to identify transactions transferred from its upstream application. The determining module is further configured to: when the first application identifies a transaction transferred from its upstream application using the event information, query the information of the transaction to be executed from the logs of the server cluster of the upstream application of the first application based on the transaction identifier information used to identify the transaction to be executed in the upstream application, and obtain the event information therefrom.

10. The apparatus according to claim 9, wherein, The device further includes: The first configuration module is used to configure the transaction information transfer method between each of the R applications and other applications, wherein the R applications include all applications in the first application link.

11. The apparatus according to claim 9, wherein, The device further includes: The second configuration module is used to configure M application links corresponding to M business transaction scenarios, where M is an integer greater than or equal to 1, and the M business transaction scenarios include the first business transaction scenario.

12. An electronic device, comprising: One or more processors; One or more memories for storing one or more programs. Wherein, when the one or more programs are executed by the one or more processors, the one or more processors perform the method according to any one of claims 1 to 8.

13. A computer-readable storage medium having stored thereon executable instructions that, when executed by a processor, cause the processor to perform the method according to any one of claims 1 to 8.

14. A computer program product comprising a computer program that, when executed by a processor, implements the method according to any one of claims 1 to 8.

Images