Monitoring Method, Device, Equipment and Storage Medium for Business Transactions

Abstract

The present application provides a method, device, equipment and storage medium for monitoring business transactions. The method includes: generating at least one buried point event under the business application according to the buried point configuration file of each business application for the target business transaction; generating a transaction monitoring event under each business application according to the combined configuration of each buried point event under different set abstract monitoring logics; and deploying the transaction monitoring event under each business application into the business application to monitor the execution status of the target business transaction on each business application. By combining and configuring the buried point events under each business application through different set abstract monitoring logics, the present application can achieve the monitoring of the execution status of business transactions on each business application, filter redundant data in the process of business transaction execution from the source, greatly reduce the workload of code writing in the early stage of business transaction monitoring, and improve the application scalability of business transaction monitoring.

Description

Technical Field

[0001] The embodiments of the present application relate to the technical field of data processing, and particularly to a method, device, equipment and storage medium for monitoring business transactions. Background Art

[0002] With the rapid development of Internet technology, various business transactions initiated by users usually need to pass through multiple related business application systems, such as back-end transaction systems and front-end user systems, etc. Therefore, in order to test the execution correctness of each business transaction, it is necessary to monitor various types of transaction process data generated under this business transaction, such as global transaction numbers, transaction information, user information, etc., on each business application system that this business transaction passes through, so as to judge whether this business transaction is executed correctly.

[0003] Currently, in order to avoid the problems of data redundancy and manual supplementation of non-log data when monitoring corresponding business transactions by capturing various transaction logs of business transactions, usually, implementation codes specifically for business transaction monitoring are written for the specific implementation classes, method parameters and return contents of key information within the business application systems that business transactions pass through, and then probe technology is used to monitor the execution process data of this business transaction under this specific implementation class, method parameters and return contents.

[0004] However, due to the huge business application systems, for the execution correctness test of each business transaction, it is necessary to monitor business transactions for each implementation class, method parameters and return contents within various different business applications. Therefore, it is necessary to write separate code implementations for business transaction data monitoring for each implementation class, method parameters and return contents within each business application, which increases the code writing workload in the early stage of business transaction monitoring and reduces the application scalability of business transaction monitoring. Summary of the Invention

[0005] The present application provides a method, device, equipment and storage medium for monitoring business transactions. By combining and configuring the buried point events under each business application through different preset abstract monitoring logics, the monitoring of the execution status of business transactions on each business application is realized, greatly reducing the code writing workload in the early stage of business transaction monitoring and improving the application scalability of business transaction monitoring.

[0006] In a first aspect, the embodiments of the present application provide a method for monitoring business transactions, and the method includes:

[0007] Generating at least one buried point event under the business application according to the buried point configuration file of each business application for the target business transaction;

[0008] Generate transaction monitoring events for each business application according to the combined configuration of each of the buried point events under different preset abstract monitoring logics;

[0009] Deploy the transaction monitoring events for each business application into the business application to monitor the execution status of the target business transaction on each of the business applications.

[0010] Further, the generating transaction monitoring events for each business application according to the combined configuration of each of the buried point events under different preset abstract monitoring logics includes:

[0011] In response to the combined configuration operation of each of the buried point events in the constructed monitoring configuration page, perform configuration conversion of each of the buried point events under different abstract monitoring logics;

[0012] In response to the configuration completion operation in the monitoring configuration page, generate transaction monitoring events for each business application according to the business application where the converted buried point events are located;

[0013] Wherein, two or more abstract monitoring logics are set in the monitoring configuration page.

[0014] Further, the performing configuration conversion of each of the buried point events under different abstract monitoring logics in response to the combined configuration operation of each of the buried point events in the constructed monitoring configuration page includes:

[0015] In response to the triggering operation of any abstract monitoring logic in the monitoring configuration page, display the monitoring execution template set under the abstract monitoring logic;

[0016] In response to the event selection operation in the monitoring configuration page, perform configuration conversion on the selected target buried point event according to the monitoring execution template.

[0017] Further, the monitoring the execution status of the target business transaction on each of the business applications includes:

[0018] During the execution of the target business transaction on each business application, dynamically display the execution status of the target business transaction at each of the buried point positions according to the buried point positions pointed to by the transaction monitoring events under the business application.

[0019] Further, the abstract monitoring logic is at least divided into three types: basic monitoring category, conditional monitoring category, and judgment monitoring category.

[0020] Further, after monitoring the execution status of the target business transaction on each of the business applications, it further includes:

[0021] Generate an execution test report for the target business transaction according to the execution status of the buried point events in the determined monitoring category configured according to the associations among the business applications.

[0022] In a second aspect, an embodiment of the present application provides a monitoring device for business transactions. The device includes:

[0023] A buried point generation module, configured to generate at least one buried point event under the business application according to the buried point configuration file of each business application for the target business transaction;

[0024] A buried point configuration module, configured to generate a transaction monitoring event for each business application according to the combined configuration of the buried point events under different set abstract monitoring logics;

[0025] A transaction monitoring module, configured to deploy the transaction monitoring event for each business application into the business application to monitor the execution status of the target business transaction on each business application.

[0026] In a third aspect, an embodiment of the present application provides an electronic device, which includes:

[0027] A processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the monitoring method for business transactions provided in the first aspect of the present application.

[0028] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium for storing a computer program, and the computer program enables a computer to execute the monitoring method for business transactions provided in the first aspect of the present application.

[0029] In a fifth aspect, an embodiment of the present application provides a computer program product, including a computer program / instructions, characterized in that when the computer program / instructions are executed by a processor, the monitoring method for business transactions provided in the first aspect of the present application is implemented.

[0030] A method, device, equipment and storage medium for monitoring business transactions provided by an embodiment of the present application generate at least one buried point event under each business application according to the buried point configuration file of each business application for the target business transaction, and then generate a transaction monitoring event under each business application according to the combined configuration executed on each buried point event by using different abstract monitoring logics. Furthermore, the transaction monitoring events under each business application are deployed into the business application to monitor the execution status of the target business transaction on each business application. Thus, by combining and configuring the buried point events under each business application through the set different abstract monitoring logics, the monitoring of the execution status of business transactions on each business application can be realized, redundant data in the process of business transaction execution can be filtered from the source, and there is no need to write separate monitoring codes for each implementation class, method parameter and return content that need to be monitored in each business application, greatly reducing the workload of code writing in the early stage of business transaction monitoring and improving the application scalability of business transaction monitoring. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following will briefly introduce the drawings required for the description of the embodiments. Obviously, the following drawings are only some embodiments of the present invention, and those of ordinary skill in the art can obtain other drawings without creative efforts based on these drawings.

[0032] Figure 1 It is a flowchart of a method for monitoring a business transaction shown in an embodiment of the present application;

[0033] Figure 2 It is a schematic diagram of the principle of the monitoring process of the business transaction shown in an embodiment of the present application;

[0034] Figure 3 It is a schematic diagram of the set abstract monitoring logics shown in an embodiment of the present application;

[0035] Figure 4 It is a schematic diagram of the principle of configuring each buried point event with different abstract monitoring logics in the monitoring configuration page shown in an embodiment of the present application;

[0036] Figure 5 It is a flowchart of another method for monitoring a business transaction shown in an embodiment of the present application;

[0037] Figure 6 It is a schematic block diagram of a device for monitoring a business transaction shown in an embodiment of the present application;

[0038] Figure 7 It is a schematic block diagram of the electronic device provided by an embodiment of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0039] The following will clearly and completely describe the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, rather than all the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention.

[0040] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and do not necessarily need to be used to describe a specific order or sequence. It should be understood that such data can be interchanged under appropriate circumstances so that the embodiments of the present invention described here can be implemented in an order different from those illustrated or described here. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product or server including a series of steps or units does not necessarily have to be limited to those steps or units clearly listed, but may include other steps or units not clearly listed or inherent to these processes, methods, products or devices.

[0041] In view of the problem that when monitoring business transactions executed within each business application in the prior art, it is necessary to write separate monitoring codes for each implementation class, method parameters, and return content that need to be monitored within each business application, resulting in a huge amount of code writing work in the early stage of business transaction monitoring, the embodiments of the present application design a business transaction monitoring method that is common among various business applications. By abstractly analyzing various monitoring functions existing when business transactions are executed on each business application, a variety of different abstract monitoring logics are preset, so as to further combine and configure and optimize the buried point events under each business application through different abstract monitoring logics, and the execution status monitoring of business transactions on each business application can be realized, filtering redundant data in the process of business transaction execution from the source, greatly reducing the amount of code writing work in the early stage of business transaction monitoring, and improving the application scalability of business transaction monitoring.

[0042] Figure 1 It is a flowchart of a method for monitoring a business transaction shown in the embodiments of the present application. Refer to Figure 1 , and the method may specifically include the following steps:

[0043] S110, generate at least one buried point event under the business application according to the buried point configuration file of each business application for the target business transaction.

[0044] Among them, the target business transaction in this application is a business transaction that is initiated when a certain business is executed and passes through multiple business applications. At this time, when testing the execution status of the target business transaction, it is necessary to listen for various transaction status data generated by the target business transaction on each business application that the target business transaction passes through. However, considering that the transaction scenarios of the target business transaction on different business applications are different, the transaction data listened on different business applications is also different. Therefore, this application can perform data burying points on each business application so as to only listen for the transaction execution status at the data burying point position on each business application.

[0045] As an optional implementation solution in the embodiment of this application, according to the actual listening requirements for the target business transaction on each business application, a corresponding data burying point configuration file will be generated for each business application in advance. The data burying point configuration file of each business application records the data burying point positions where the target business application needs to perform data listening when executing on this business application, such as listening to a certain method in the execution code of the business application, etc.

[0046] Optionally, when listening to the execution status of the target business transaction on each business application, first obtain the data burying point configuration file generated in advance for each business application for this target business transaction. Then, as Figure 2 shown, parse the data burying point configuration file of each business application, and the data burying point positions where each business application needs to listen for this target business transaction can be obtained. Furthermore, a corresponding data burying point event can be generated according to the data burying point definition under each data burying point position. Thus, for each business application, at least one data burying point event under this business application will be obtained.

[0047] Among them, the data burying point event under each business application is used to implement the basic listening function of this business application for this data burying point definition.

[0048] It should be noted that the data burying point configuration file of each business application can be described by code content.

[0049] S120, generate the transaction listening event under each business application according to the combined configuration of each data burying point event under different set abstract listening logics.

[0050] Considering that the buried point events under each business application are mainly used to implement the basic monitoring function of the buried point definition in the business application, during the entire execution process of the target business transaction on the business application, there may be personalized monitoring requirements for a certain buried point event, such as specific positions or specific conditions, or personalized monitoring requirements for the specific order or comparison between multiple buried point events. As a result, the various buried point events generated according to the buried point configuration file cannot implement such personalized monitoring functions. Therefore, it is necessary to further optimize and configure the monitoring functions of each buried point event according to the personalized monitoring requirements of the target business request.

[0051] In this application, in order to ensure the further convenient configuration of each buried point event in each business application, the actual monitoring logics that meet various monitoring requirements when the target business transaction is executed on each business application will be abstractly analyzed, so as to preset a variety of different abstract monitoring logics for various different monitoring functions within the business application, so that each abstract monitoring logic can respectively execute the abstract implementation under different monitoring functions.

[0052] It should be noted that as Figure 3 shown, each abstract monitoring logic in this application can be represented by a function module with the corresponding monitoring function of the abstract monitoring logic.

[0053] After obtaining each buried point event under each business application, the actual monitoring requirements of each buried point event under each business application and whether there are associated monitoring requirements between each buried point event can be analyzed, so as to judge whether each buried point event needs to perform the optimized configuration under the corresponding abstract monitoring logic. Then, according to the actual monitoring requirements of each buried point event, the different abstract monitoring logics that have been set can be used to further perform single buried point optimization configuration and multiple buried point combination configuration for each buried point event, so as to generate transaction monitoring events under each business application according to the business application to which the buried point events belong after further configuration, so as to ensure the realization of the true monitoring function of the target business request under each business application.

[0054] It should be understood that the combined configuration of each buried point event using different abstract monitoring logics can be the further combined configuration of each buried point event under the same business application, or the further combined configuration of each buried point event under different business applications.

[0055] Exemplarily, when listening to the key content of a certain log output method (such as log.info(), log.out(), etc.) in a business application, since this log output method is a global general method and will be called at many positions when executing a target business transaction in the business application, for the buried point event of this log output method, an abstract hierarchical listening logic or conditional filtering logic can be adopted to further optimize and configure this buried point event, and further determine the actual listening content of this log output method.

[0056] In addition, each abstract listening logic set in this application is at least divided into three types: basic listening category, conditional listening category, and judgment listening category. As Figure 3 shown, the basic listening category can include abstract listening logics represented by a general listening module (common) and a mirror listening module (image). The conditional listening category can include abstract listening logics represented by an interval listening module (interval), an internal listening module (inner), a conditional filtering listening module (filter), a hierarchical listening module (hierarchy), and a call order listening module (order). The judgment listening category can include abstract listening logics represented by a sequence listening module (sequence), a statistical listening module (statistic), and a comparison listening module (compare).

[0057] S130, Deploy the transaction listening events under each business application into this business application to monitor the execution status of the target business transaction on each business application.

[0058] After generating the transaction listening events under each business application, the JAVA probe technology can be used to deploy the transaction listening events under each business application into this business application, so that when executing the target business transaction on each business application, the deployed transaction listening events on this business application can be called to capture the transaction execution data of the target business transaction on this business application, thereby monitoring the execution status of the target business transaction on each business application.

[0059] Exemplarily, since the transaction listening events under each business application are obtained by further combining and configuring the buried point events under this business application, the transaction listening events under each business application will also point to the buried point positions that need to be listened to within this business application. Therefore, to monitor the execution status of the target business transaction on each business application, specifically, it can be: during the process of executing the target business transaction on each business application, according to the buried point positions pointed to by the transaction listening events under this business application, dynamically display the execution status of the target business transaction at each buried point position.

[0060] That is to say, in the process of executing the target business transaction on each business application, first, it analyzes each buried point location that needs to execute the monitoring function pointed to by the transaction monitoring event under the business application, so as to capture the transaction data executed by the target business transaction at each buried point location within the business application, and generate the corresponding execution status at each buried point location for dynamic display, improving the intuitiveness of business transaction monitoring.

[0061] In addition, since each abstract monitoring logic set in this application is at least divided into three types: basic monitoring category, conditional monitoring category, and judgment monitoring category. Therefore, when combining and configuring each buried point event, it is also possible to pre-configure various judgment rules among the buried point events of each business application in advance by using the abstract monitoring logic under the judgment monitoring category. For example, use the abstract monitoring logic represented by the sequence monitoring module to further configure the execution order of the buried point events in different business applications, and use the abstract monitoring logic represented by the statistic monitoring module to further configure the transaction data statistics rules of the buried point events in different business applications, etc.

[0062] Therefore, after monitoring the execution status of the target business transaction on each business application, it will also generate an execution test report of the target business transaction according to the execution status of the buried point events under the judgment monitoring category configured in association among the business applications. That is, obtain the execution status of the buried point events under the judgment monitoring category configured in association among the business applications, and analyze the execution status of each buried point event according to the judgment rules configured for the buried point events configured in association among the business applications by using the abstract monitoring logic under the judgment monitoring category, so as to generate an execution test report of the target business transaction.

[0063] At this time, using the abstract monitoring logic under the judgment monitoring category to further combine and configure various judgment rules for the buried point events of each business application in advance, so that after monitoring the execution status of the target business transaction on each of the business applications, it can directly analyze the overall execution situation of the target business transaction among each business application according to the various abstract monitoring logics under the judgment monitoring category combined and configured in advance, so as to automatically complete the test of the execution correctness of the target business transaction among each business application, without the need for testers to manually input the corresponding judgment rules on the retrieval and analysis page to test the execution situation of the target business transaction after extracting the transaction execution data of the target business transaction on each business application, thereby improving the test efficiency of the execution of the target business transaction.

[0064] The technical solution provided by the embodiments of this application generates at least one buried point event under each business application according to the buried point configuration file of each business application facing the target business transaction. Then, according to the combined configuration of different abstract listening logics for each buried point event, a transaction listening event under each business application is generated. Furthermore, the transaction listening event under each business application is deployed into the business application to monitor the execution status of the target business transaction on each business application. Thus, by combining and configuring the buried point events under each business application through different set abstract listening logics, the monitoring of the execution status of business transactions on each business application can be realized, redundant data in the process of business transaction execution can be filtered from the source, and there is no need to separately write individual listening codes for each implementation class, method parameter, and return content that need to be monitored within each business application, greatly reducing the workload of code writing in the early stage of business transaction monitoring and improving the application scalability of business transaction monitoring.

[0065] As an alternative implementation solution in the embodiments of this application, when combining and configuring each buried point event under each business application with different abstract listening logics according to the actual listening requirements of each buried point event, in order to ensure the further convenient configuration of each buried point event, this application will pre-build a listening configuration page, which will display two or more set abstract listening logics, and display each buried point event under each business application in partitions according to each business application.

[0066] Among them, as Figure 4 shown, for the display of each abstract listening logic, the abstract listening logics under each listening category can be respectively displayed under the three listening categories of the pre-divided basic listening category, conditional listening category, and judgment listening category, so that when combining and configuring each buried point event with a certain abstract listening logic later, the abstract listening logic can be quickly found under the listening category to which it belongs by analyzing the listening category to which the abstract listening logic belongs.

[0067] In the following embodiments of this application, the specific process of combining and configuring each buried point event under each business application with different abstract listening logics in the pre-built listening configuration page will be explained in detail.

[0068] Figure 5 It is a flowchart of another method for monitoring business transactions shown in the embodiments of this application. As Figure 5 shown, the method can specifically include the following steps:

[0069] S510, generate at least one buried point event under the business application according to the buried point configuration file of each business application facing the target business transaction.

[0070] S520 performs configuration conversion on each buried point event under different abstract listening logics in response to the combined configuration operations of each buried point event in the constructed listening configuration page.

[0071] Optionally, after generating each buried point event under each business application according to the buried point configuration file of the business application, since the generated buried point events at this time can only execute the basic listening functions defined in the buried point configuration file, that is, execute the listening functions of the abstract listening logic under the basic listening category. Therefore, as Figure 4 shown, for each business application in the constructed listening configuration page, each buried point event under the business application is displayed in a partitioned manner. At the same time, in the listening configuration page, each abstract listening logic belonging to the listening category is respectively displayed under each listening category, and the abstract listening functions executed by each abstract listening logic have been set.

[0072] Specifically, for various actual listening requirements that need to be further configured among the buried point events under each business application, any corresponding abstract listening logic can be triggered in the listening configuration page. At this time, after detecting the triggering operation of a certain abstract listening logic, the information that needs to be optimized and configured for the abstract listening function set by the abstract listening logic will be displayed in the listening configuration page, so as to determine a specific buried point event that needs to configure the abstract listening logic from the buried point events under each business application by dragging or clicking. The determined specific buried point events can be buried point events under the same business application or buried point events under different business applications to achieve combined configuration among buried point events under different business applications. Then, according to the configuration information of the abstract listening function set under the triggered abstract listening logic, further optimization configuration is performed on the determined specific buried point events. By using the same method as above, further combined configuration under different abstract listening logics can be performed on the buried point events under each business application, so as to achieve configuration conversion of each buried point event under different abstract listening logics, making the buried point positions where each buried point event definition needs to execute the listening function more accurate.

[0073] Exemplarily, the present application can set a corresponding listening execution template for each abstract listening logic to uniformly display the information that needs to be optimized and configured for the abstract listening function set by the abstract listening logic. Therefore, the configuration conversion of each buried point event under different abstract listening logics can be mainly divided into: in response to the triggering operation of any abstract listening logic in the listening configuration page, displaying the listening execution template set under the abstract listening logic; in response to the event selection operation in the listening configuration page, performing configuration conversion on the selected target buried point event according to the listening execution template.

[0074] That is to say, for various actual monitoring requirements that need to be further configured between each buried point event, when any corresponding abstract monitoring logic is triggered in the monitoring configuration page, in response to the trigger operation of any abstract monitoring logic in the monitoring configuration page, first, a monitoring execution template set under the abstract monitoring logic will be displayed in the monitoring configuration page, and various information and monitoring configuration logics that need to be optimized and configured for the abstract monitoring functions it has will be set in the monitoring execution template.

[0075] As Figure 4 shown, taking the abstract monitoring logic represented by the interval monitoring module (interval) as an example, the monitoring execution template will display the starting point of the global serial number (Start), transaction log 1 (INNER1) to transaction log n (INNERn), and the end point of the global serial number (End) that need to be configured.

[0076] Then, in a drag-and-drop or point-and-click manner, from each buried point event under each business application displayed in the monitoring configuration page, for each configuration information set in the monitoring execution template, select the appropriate target buried point event, and input the configuration parameters of each selected target buried point event according to the specific configuration requirements in the monitoring execution template. Thus, in response to the event selection operation in the monitoring configuration page, the configuration parameters input for each target buried point event can be used to further optimize and configure each target buried point event according to the monitoring configuration logic in the monitoring execution template.

[0077] For example, for each configuration information in the monitoring execution template set under the interval monitoring module (interval), the target buried points in each buried point event under each business application can be configured by dragging to the corresponding starting point of the global serial number (Start), transaction log 1 (INNER1) to transaction log n (INNERn), and the end point of the global serial number (End), and then the target buried point events under the starting point of the global serial number (Start), transaction log 1 (INNER1) to transaction log n (INNERn), and the end point of the global serial number (End) can be further configured under optimized conditions to enable the actual monitoring functions of each buried point event, such as performing further internal monitoring configuration on transaction log 1 (INNER1).

[0078] S530, in response to the configuration completion operation in the monitoring configuration page, according to the business application where the converted buried point event is located, combine and generate transaction monitoring events for each business application.

[0079] Optionally, by repeating the configuration process in S520 under different abstract listening logics for each buried point event in the listening configuration page, further combined configuration conversion can be performed on each buried point event under each business application, so that each buried point event after configuration conversion can perform a more accurate real listening function. Therefore, after completing the further configuration conversion of each buried point event under each business application, a corresponding configuration completion operation will be executed in the listening configuration page.

[0080] At this time, in response to the configuration completion operation in the listening configuration page, the buried point events under each business application can be obtained. At this time, the buried point events under each business application can include the buried point events that are initially generated without combined configuration and only implement the basic listening function, and also include the buried point events that are converted to implement each abstract listening logic under each conditional listening category or judgment listening category after combined configuration. Therefore, according to the business application where each buried point event is currently configured, the buried point events that exist after configuration conversion under each business application can be combined to generate the transaction listening events under each business transaction.

[0081] In addition, subsequently, by triggering the "Deploy" button set in the listening configuration page, the transaction listening events under each business transaction can be deployed into the business application.

[0082] S540, deploy the transaction listening events under each business application into the business application to monitor the execution status of the target business transaction on each business application.

[0083] The technical solution provided by the embodiment of the present application generates at least one buried point event under each business application according to the buried point configuration file of each business application facing the target business transaction, and then further combines and configures each buried point event in the constructed listening configuration page by using different abstract listening logics to generate the transaction listening events under each business application, and then deploys the transaction listening events under each business application into the business application to monitor the execution status of the target business transaction on each business application. Thus, by combining and configuring the buried point events under each business application through the set different abstract listening logics, the execution status monitoring of the business transaction on each business application can be realized, redundant data in the execution process of the business transaction can be filtered from the source, and there is no need to write separate listening codes for each implementation class, method parameter, and return content that need to be monitored in each business application, which greatly reduces the code writing workload in the early stage of business transaction monitoring and improves the application scalability of business transaction monitoring.

[0084] Figure 6 It is a principle block diagram of a monitoring device for a business transaction shown in the embodiment of the present application. As Figure 6 shown, the device 600 may include:

[0085] The buried point generation module 610 is configured to generate at least one buried point event under the service application according to the buried point configuration file of each service application for the target service transaction.

[0086] The buried point configuration module 620 is configured to generate a transaction monitoring event under each service application according to the combined configuration of each buried point event under different set abstract monitoring logics.

[0087] The transaction monitoring module 630 is configured to deploy the transaction monitoring event under each service application into the service application to monitor the execution status of the target service transaction on each service application.

[0088] Further, the buried point configuration module 620 may include:

[0089] The configuration conversion unit is configured to perform configuration conversion on each buried point event under different abstract monitoring logics in response to the combined configuration operation of each buried point event in the constructed monitoring configuration page.

[0090] The event generation unit is configured to, in response to the configuration completion operation in the monitoring configuration page, combine and generate a transaction monitoring event under each service application according to the service application where the converted buried point event is located.

[0091] Wherein, two or more than two kinds of abstract monitoring logics are set in the monitoring configuration page.

[0092] Further, the configuration conversion unit may specifically be configured to:

[0093] In response to the triggering operation of any abstract monitoring logic in the monitoring configuration page, display the monitoring execution template set under the abstract monitoring logic.

[0094] In response to the event selection operation in the monitoring configuration page, perform configuration conversion on the selected target buried point event according to the monitoring execution template.

[0095] Further, the transaction monitoring module 630 may specifically be configured to:

[0096] During the process of executing the target service transaction on each service application, dynamically display the execution status of the target service transaction at each buried point position according to the buried point position pointed to by the transaction monitoring event under the service application.

[0097] Further, the abstract monitoring logic is at least divided into three types: basic monitoring category, conditional monitoring category, and judgment monitoring category.

[0098] Further, the monitoring device 600 for the service transaction may further include:

[0099] A test report generation module, configured to generate an execution test report for the target business transaction according to the execution status of the buried point events under the determined monitoring category configured for the association between the business applications.

[0100] In the embodiments of the present application, at least one buried point event under each business application is generated according to the buried point configuration file of each business application for the target business transaction. Then, according to the combined configuration of the execution of each buried point event using different abstract monitoring logics, a transaction monitoring event under each business application is generated. Furthermore, the transaction monitoring event under each business application is deployed into the business application to monitor the execution status of the target business transaction on each business application. Thus, by combining and configuring the buried point events under each business application through the set different abstract monitoring logics, the monitoring of the execution status of the business transaction on each business application can be realized, redundant data in the execution process of the business transaction can be filtered from the source, and there is no need to separately write individual monitoring codes for each implementation class, method parameter, and return content that need to be monitored in each business application, greatly reducing the code writing workload in the early stage of business transaction monitoring and improving the application scalability of business transaction monitoring.

[0101] It should be understood that the device embodiments and the method embodiments can correspond to each other, and similar descriptions can refer to the method embodiments. To avoid repetition, it will not be elaborated here. Specifically, Figure 6 The illustrated device 600 can execute any method embodiment provided by the present application, and the foregoing and other operations and / or functions of each module in the device 600 respectively correspond to the corresponding processes in each method of the embodiments of the present application. For the sake of brevity, it will not be elaborated here.

[0102] The device 600 of the embodiments of the present application has been described above from the perspective of functional modules in conjunction with the drawings. It should be understood that the functional modules can be implemented in the form of hardware, can also be implemented by instructions in software form, or can be implemented by a combination of hardware and software modules. Specifically, the steps of the method embodiments in the present application can be completed by the integrated logic circuit in the hardware in the processor and / or instructions in software form. The steps of the method disclosed in conjunction with the embodiments of the present application can be directly embodied as being executed and completed by the hardware decoding processor, or can be executed and completed by a combination of the hardware and software modules in the decoding processor. Optionally, the software module can be located in a mature storage medium in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an electrically erasable programmable memory, a register, etc. This storage medium is located in the memory, and the processor reads the information in the memory and combines its hardware to complete the steps in the above method embodiments.

[0103] Figure 7 It is a schematic block diagram of an electronic device 700 provided by the embodiments of the present application.

[0104] As shown Figure 7 in the figure, the electronic device 700 may include:

[0105] a memory 710 and a processor 720. The memory 710 is used to store a computer program and transmit the program code to the processor 720. In other words, the processor 720 can call and run the computer program from the memory 710 to implement the method in the embodiments of the present application.

[0106] For example, the processor 720 can be used to execute the above method embodiments according to the instructions in the computer program.

[0107] In some embodiments of the present application, the processor 720 may include but is not limited to:

[0108] a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.

[0109] In some embodiments of the present application, the memory 710 includes but is not limited to:

[0110] Volatile memory and / or non-volatile memory. Among them, the non-volatile memory can be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable PROM (EEPROM), or a flash memory. The volatile memory can be a Random Access Memory (RAM), which is used as an external cache. By way of example but not limitation, many forms of RAM are available, such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double DataRate SDRAM (DDR SDRAM), Enhanced SDRAM (ESDRAM), synch link DRAM (SLDRAM), and Direct Rambus RAM (DR RAM).

[0111] In some embodiments of the present application, the computer program may be divided into one or more modules, and the one or more modules are stored in the memory 710 and executed by the processor 720 to complete the method provided by the present application. The one or more modules may be a series of computer program instruction segments capable of performing specific functions, and the instruction segments are used to describe the execution process of the computer program in the electronic device.

[0112] As Figure 7 shown, the electronic device may further include:

[0113] A transceiver 730, which may be connected to the processor 720 or the memory 710.

[0114] Among them, the processor 720 can control the transceiver 730 to communicate with other devices. Specifically, it can send information or data to other devices, or receive information or data sent by other devices. The transceiver 730 may include a transmitter and a receiver. The transceiver 730 may further include an antenna, and the number of antennas may be one or more.

[0115] It should be understood that each component in the electronic device is connected through a bus system. Among them, the bus system includes, in addition to the data bus, a power bus, a control bus, and a status signal bus.

[0116] The embodiments of the present application also provide a computer storage medium, on which a computer program is stored. When the computer program is executed by a computer, the computer can execute the methods in the above method embodiments. Or rather, the embodiments of the present application also provide a computer program product containing instructions. When the instructions are executed by a computer, the computer executes the methods in the above method embodiments.

[0117] When implemented using 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 processes or functions according to the embodiments of the present application are generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from a website, a computer, a server, or a data center to another website, a computer, a server, or a data center in a wired manner (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or a wireless manner (such as infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or a data center that integrates one or more available media. The available medium can be a magnetic medium (such as a floppy disk, a hard disk, a magnetic tape), an optical medium (such as a digital video disc (DVD)), or a semiconductor medium (such as a solid state disk (SSD)), etc.

[0118] Those of ordinary skill in the art can realize that the modules and algorithm steps of each example described in combination with the embodiments disclosed herein can be implemented by electronic hardware, or by a combination of computer software and electronic hardware. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present application.

[0119] In several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the modules is only a logical function division. In actual implementation, there may be other division methods. For example, multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed couplings or direct couplings or communication connections between each other can be through some interfaces. The indirect couplings or communication connections of the devices or modules can be in electrical, mechanical, or other forms.

[0120] The modules described as separate components may or may not be physically separated. The components shown as modules may or may not be physical modules, that is, they can be located in one place or distributed to multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment. For example, in each embodiment of the present application, the functional modules can be integrated in a processing module, or each module can exist physically alone, or two or more modules can be integrated in one module.

[0121] The above is only the specific implementation manner of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art within the technical scope disclosed by the present application can easily think of changes or substitutions, which should all be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A method for monitoring business transactions, characterized in that, Including: Generating at least one buried point event under the business application according to the buried point configuration file of each business application for the target business transaction; Generating a transaction monitoring event for each business application according to the combined configuration of each buried point event under different set abstract monitoring logics; Deploying the transaction monitoring event for each business application into the business application to monitor the execution status of the target business transaction on each business application; Among them, the generating a transaction monitoring event for each business application according to the combined configuration of each buried point event under different set abstract monitoring logics includes: Responding to the combined configuration operation of each buried point event in the constructed monitoring configuration page, and performing configuration conversion of each buried point event under different abstract monitoring logics; Responding to the configuration completion operation in the monitoring configuration page, and combining and generating a transaction monitoring event for each business application according to the business application where the converted buried point event is located; Among them, two or more abstract monitoring logics are set in the monitoring configuration page.

2. The method according to claim 1, characterized in that, The responding to the combined configuration operation of each buried point event in the constructed monitoring configuration page and performing configuration conversion of each buried point event under different abstract monitoring logics includes: Responding to the triggering operation of any abstract monitoring logic in the monitoring configuration page, and displaying the monitoring execution template set under the abstract monitoring logic; Responding to the event selection operation in the monitoring configuration page, and performing configuration conversion on the selected target buried point event according to the monitoring execution template.

3. The method according to claim 1, wherein The monitoring the execution status of the target business transaction on each business application includes: During the process of executing the target business transaction on each business application, dynamically displaying the execution status of the target business transaction at each buried point location according to the buried point location pointed to by the transaction monitoring event under the business application.

4. The method according to claim 1, wherein The abstract monitoring logic is at least divided into three types: basic monitoring category, conditional monitoring category, and judgment monitoring category.

5. The method according to claim 4, wherein After monitoring the execution status of the target business transaction on each business application, it further includes: Generating an execution test report of the target business transaction according to the execution status of the buried point events under the judgment monitoring category configured among the business applications.

6. A monitoring device for business transactions, characterized in that, Including: A buried point generation module, which is used to generate at least one buried point event under the business application according to the buried point configuration file of each business application for the target business transaction; A buried point configuration module, which is used to generate a transaction monitoring event for each business application according to the combined configuration of each buried point event under different set abstract monitoring logics; A transaction monitoring module, which is used to deploy the transaction monitoring event for each business application into the business application to monitor the execution status of the target business transaction on each business application; Among them, the buried point configuration module is specifically used for: Responding to the combined configuration operation of each buried point event in the constructed monitoring configuration page, and performing configuration conversion of each buried point event under different abstract monitoring logics; In response to the configuration completion operation in the monitoring configuration page, according to the business application where the converted buried point event is located, generate trading monitoring events under each business application by combination. Among them, there are two or more abstract monitoring logics set in the monitoring configuration page.

7. An electronic device, characterized in that, Including: A processor and a memory, the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the monitoring method of the business transaction according to any one of claims 1-5.

8. A computer-readable storage medium, characterized in that, For storing a computer program, the computer program causes a computer to execute the monitoring method of the business transaction according to any one of claims 1-5.

9. A computer program product, comprising a computer program / instructions, characterized in that, When the computer program / instructions are executed by the processor, the monitoring method of the business transaction according to any one of claims 1-5 is implemented.

Images