CN114238104A

CN114238104A - Monitoring method, device, equipment and storage medium for business transaction

Info

Publication number: CN114238104A
Application number: CN202111515050.XA
Authority: CN
Inventors: 李琛
Original assignee: Neusoft Group Beijing Co ltd; Neusoft Corp
Current assignee: Neusoft Group Beijing Co ltd; Neusoft Corp
Priority date: 2021-12-13
Filing date: 2021-12-13
Publication date: 2022-03-25

Abstract

The application provides a method, a device, equipment and a storage medium for monitoring business transactions. The method comprises the following steps: generating at least one buried point event under each service application according to a buried point configuration file of each service application facing to target service transaction; generating a transaction monitoring event under each service 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 service application into the service application so as to monitor the execution state of the target service transaction on each service application. According to the method and the device, the embedded point events under each service application are combined and configured through the set different abstract monitoring logics, so that the execution state monitoring of the service transaction on each service application can be realized, redundant data in the service transaction execution process is filtered from the source, the code compiling workload in the early stage of service transaction monitoring is greatly reduced, and the application expandability of service transaction monitoring is improved.

Description

Monitoring method, device, equipment and storage medium for business transaction

Technical Field

The embodiment of the application relates to the technical field of data processing, in particular to a method, a device, equipment and a storage medium for monitoring business transactions.

Background

With the rapid development of internet technology, various business transactions initiated by users generally need to pass through a plurality of associated business application systems, such as a back-end transaction system and a front-end user system. Therefore, in order to test the execution correctness of each service transaction, it is necessary to monitor various transaction process data generated under the service transaction, such as a global transaction number, transaction information, and user information, on each service application system through which the service transaction passes, according to different transaction scenarios, so as to determine whether the service transaction is executed correctly.

At present, in order to avoid the problems of data redundancy and manual supplement of non-log data when monitoring corresponding business transactions by capturing various transaction logs of the business transactions, implementation codes for business transaction monitoring are written for specific implementation classes, method parameters and return contents of key information in a business application system of a business transaction institute, and then execution process data of the business transactions under the specific implementation classes, method parameters and return contents are monitored by adopting a probe technology.

However, in the face of a huge service application system, the execution correctness test of each service transaction requires service transaction monitoring on each implementation class and method parameter and return content in various different service applications, so that separate codes for service transaction data monitoring need to be written for each implementation class and method parameter and return content in each service application respectively for realization, the code writing workload in the early stage of service transaction monitoring is increased, and the application expandability of service transaction monitoring is reduced.

Disclosure of Invention

The application provides a monitoring method, a device, equipment and a storage medium for business transaction, which are used for carrying out combined configuration on a buried point event under each business application through different set abstract monitoring logics, thereby realizing the monitoring of the execution state of the business transaction on each business application, greatly reducing the code compiling workload before the business transaction monitoring and improving the application expandability of the business transaction monitoring.

In a first aspect, an embodiment of the present application provides a method for monitoring a business transaction, where the method includes:

generating at least one buried point event under each service application according to a buried point configuration file of each service application facing to target service transaction;

generating a transaction monitoring event under each service 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 service application into the service application so as to monitor the execution state of the target service transaction on each service application.

Further, the generating of the transaction monitoring event under each service application according to the combined configuration of each of the burial point events 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 under different abstract monitoring logics on each buried point event;

responding to configuration completion operation in the monitoring configuration page, and combining and generating a transaction monitoring event under each service application according to the service application where the converted embedded point event is located;

wherein, two or more abstract monitoring logics are set in the monitoring configuration page.

Further, in response to the combined configuration operation of each buried point event in the constructed monitoring configuration page, performing configuration conversion under different abstract monitoring logics on each buried point event; the method comprises the following steps:

responding to the triggering operation of any abstract monitoring logic in the monitoring configuration page, and displaying a monitoring execution template set under the abstract monitoring logic;

and 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.

Further, the monitoring the execution state of the target service transaction on each service application includes:

and dynamically displaying the execution state of the target business transaction on each embedded point position according to the embedded point position pointed by the transaction monitoring event under the business application in the process of executing the target business transaction on each business application.

Further, the abstract monitoring logic is at least divided into a basic monitoring category, a conditional monitoring category and a decision monitoring category.

Further, after monitoring the execution state of the target business transaction on each business application, the method further includes:

and generating an execution test report of the target service transaction according to the execution state of the embedded point event under the judgment monitoring type configured by the association between the service applications.

In a second aspect, an embodiment of the present application provides an apparatus for monitoring a business transaction, where the apparatus includes:

the system comprises a buried point generating module, a buried point generating module and a processing module, wherein the buried point generating module is used for generating at least one buried point event under the service application according to a buried point configuration file of each service application for target service transaction;

the embedded point configuration module is used for generating transaction monitoring events under each service application according to the combined configuration of the embedded point events under different set abstract monitoring logics;

and the transaction monitoring module is used for deploying the transaction monitoring event under each service application into the service application so as to monitor the execution state of the target service transaction on each service application.

In a third aspect, an embodiment of the present application provides an electronic device, including:

the processor is used for calling and running the computer program stored in the memory so as to execute the service transaction monitoring method provided in the first aspect of the present application.

In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium for storing a computer program, where the computer program makes a computer execute the method for listening to a business transaction as provided in the first aspect of the present application.

In a fifth aspect, the present application provides a computer program product, which includes computer program/instructions, and is characterized in that the computer program/instructions, when executed by a processor, implement the method for listening to a business transaction as provided in the first aspect of the present application.

The embodiment of the application provides a monitoring method, a device, equipment and a storage medium for business transaction, at least one embedded point event under each business application is generated according to an embedded point configuration file facing target business transaction of each business application, then a transaction monitoring event under each business application is generated according to combined configuration executed on each embedded point event by adopting different abstract monitoring logics, the transaction monitoring event under each business application is further deployed into the business application to monitor the execution state of the target business transaction on each business application, the embedded point events under each business application are combined and configured through the set different abstract monitoring logics, the execution state monitoring of the business transaction on each business application can be realized, redundant data in the business transaction execution process is filtered from a source, and independent monitoring agent is not required to be compiled for each implementation class, method parameters and return content which need to be monitored in each business application The code greatly reduces the code compiling workload in the early stage of business transaction monitoring and improves the application expandability of the business transaction monitoring.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

Fig. 1 is a flowchart illustrating a method for monitoring a business transaction according to an embodiment of the present application;

fig. 2 is a schematic diagram illustrating a monitoring process of a business transaction according to an embodiment of the present application;

FIG. 3 is a schematic diagram of configured abstract snoop logics according to an embodiment of the present disclosure;

fig. 4 is a schematic diagram illustrating a principle that different abstract snoop logics are used to configure each buried point event in a snoop configuration page according to an embodiment of the present application;

fig. 5 is a flowchart illustrating another monitoring method for a business transaction according to an embodiment of the present application;

fig. 6 is a schematic block diagram of a monitoring apparatus for business transaction according to an embodiment of the present application;

fig. 7 is a schematic block diagram of an electronic device provided in an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be obtained by a person skilled in the art without any inventive step based on the embodiments of the present invention, are within the scope of the present invention.

It should be noted that the terms "first," "second," and the like in the description and claims of the present invention and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the invention described herein are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or server that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

Aiming at the problem that when monitoring the execution business transaction in each business application in the prior art, separate monitoring codes need to be compiled for each implementation class and method parameter and return content which need to be monitored in each business application, so that the workload of code compiling in the early stage of business transaction monitoring is very large, the embodiment of the application designs a business transaction monitoring mode which is universal among all business applications, by carrying out abstract analysis on various monitoring functions existing when the business transaction is executed on each business application, presetting a plurality of different abstract monitoring logics, carrying out further combined configuration optimization on a buried point event under each business application through different abstract monitoring logics, so that the execution state monitoring of the business transaction in each business application can be realized, redundant data in the business transaction execution process is filtered from a source, and the workload of code compiling in the early stage of business transaction monitoring is greatly reduced, the application expandability of the business transaction monitoring is improved.

Fig. 1 is a flowchart illustrating a method for monitoring a business transaction according to an embodiment of the present application. Referring to fig. 1, the method may specifically include the following steps:

s110, generating at least one buried point event under the service application according to the buried point configuration file of each service application facing the target service transaction.

The target business transaction in the application is a business transaction which is initiated when a certain business is executed and can pass through a plurality of business applications. At this time, when testing the execution situation of the target service transaction, it is necessary to monitor various transaction state data generated by the target service transaction on each service application passed by the target service transaction. However, considering that the transaction scenarios of the target service transaction on different service applications are different, so that the transaction data monitored on different service applications are also different, the present application may perform the embedding on each service application, so as to monitor only the transaction execution state at the embedding position on each service application.

As an optional implementation scheme in this embodiment, according to an actual monitoring requirement for a target service transaction on each service application, a corresponding buried point configuration file is generated for each service application in advance, where a buried point location where data monitoring needs to be performed when the target service application is executed on the service application is recorded in the buried point configuration file of each service application, for example, a certain method in an execution code of the service application is monitored.

Optionally, when monitoring the execution state of the target service transaction on each service application, a buried point configuration file generated for each service application facing the target service transaction in advance is first obtained. Then, as shown in fig. 2, the buried point configuration file of each service application is analyzed, so that the buried point position of each service application, at which the target service transaction needs to be monitored, can be obtained. Furthermore, a corresponding buried point event can be generated according to the buried point definition at each buried point position, so that at least one buried point event under the service application can be obtained for each service application.

And the embedded point event under each service application is used for realizing the basic monitoring function defined by the service application to the embedded point.

It should be noted that the buried point configuration file of each service application can be described by using the code content.

And S120, generating transaction monitoring events under each service application according to the combined configuration of the buried point events under different set abstract monitoring logics.

Considering that a buried point event under each service application is mainly used for realizing a basic monitoring function defined by the service application on the buried point, and in the whole execution process of a target service transaction on the service application, a personalized monitoring requirement of a specific position, a specific condition and the like may exist on a certain buried point event, or a specific sequence or a peer-to-peer personalized monitoring requirement exists among a plurality of buried point events, so that each buried point event generated according to a buried point configuration file cannot realize the personalized monitoring function, and therefore, the monitoring function of each buried point event needs to be further optimally configured according to the personalized monitoring requirement of a target service request.

In the application, in order to ensure further convenient configuration of each buried point event of each service application, abstract analysis is performed on actual monitoring logic meeting various monitoring requirements when target service transaction is executed on each service application, so that various different abstract monitoring logics are preset aiming at various different monitoring functions in the service application, and each abstract monitoring logic can respectively execute abstract implementation under different monitoring functions.

It should be noted that, as shown in fig. 3, each abstract snooping logic in the present application can be represented by a functional module having the corresponding snooping function of the abstract snooping logic.

After obtaining each buried point event under each service application, the actual monitoring requirement of each buried point event under each service application and whether there is a correlation monitoring requirement among each buried point event can be analyzed, so as to judge whether each buried point event needs to execute the optimized configuration under the corresponding abstract monitoring logic. Then, according to the actual monitoring requirement of each embedded point event, the set different abstract monitoring logics can be adopted to perform further single embedded point optimal configuration and multiple embedded point combined configuration on each embedded point event, so that the transaction monitoring event under each service application is generated according to the service application to which the embedded point event after further configuration belongs, and the realization of the real monitoring function of the target service request under each service application is ensured.

It should be understood that the combined configuration of the buried point events by using different abstract monitoring logics may be further combined configuration of the buried point events under the same service application, or may also be further combined configuration of the buried point events under different service applications.

Illustratively, when monitoring key contents of a certain log output method (e.g., log. info (), log. out (), etc.) in a business application, since the log output method is a global general method, when a target business transaction is executed in the business application, there are calls in many places, so for a buried point event of the buried point of the log output method, abstract hierarchical monitoring logic or conditional filtering logic may be adopted to further optimize and configure the buried point event, and further determine actual monitored contents of the log output method.

In addition, each abstract monitoring logic set in the present application is at least divided into a basic monitoring category, a conditional monitoring category and a decision monitoring category. As shown in fig. 3, abstract snoop logic represented by a normal snoop module (common) and a mirror snoop module (image) may be included under the basic snoop category, abstract snoop logic represented by an interval snoop module (interval), an internal snoop module (inner), a condition filtering snoop module (filter), a hierarchy snoop module (hierarchy) and an order call snoop module (order) may be included under the condition snoop category, and abstract snoop logic represented by an order snoop module (sequence), a statistics snoop module (static) and a comparison snoop module (match) may be included under the decision snoop category.

S130, the transaction monitoring event under each service application is deployed into the service application to monitor the execution state of the target service transaction on each service application.

After the transaction monitoring event under each service application is generated, the transaction monitoring event under each service application can be deployed into the service application by adopting a JAVA probe technology, so that when the target service transaction is executed on each service application, the transaction monitoring event deployed on the service application can be called to capture the transaction execution data of the target service transaction on the service application, thereby monitoring the execution state of the target service transaction on each service application.

For example, since the transaction monitoring event under each service application is obtained by combining and configuring the buried point events under the service application, the transaction monitoring event under each service application also points to the buried point position in the service application where monitoring needs to be performed, so that the execution state of the monitored target service transaction on each service application may specifically be: and in the process of executing the target business transaction on each business application, dynamically displaying the execution state of the target business transaction on each embedded point according to the embedded point position pointed by the transaction monitoring event under the business application.

That is to say, in the process of executing the target service transaction on each service application, the embedded point positions, which are pointed by the transaction monitoring event under the service application and need to execute the monitoring function, are firstly analyzed to capture the transaction data executed by the target service transaction at the embedded point positions in the service application, and the execution states corresponding to the embedded point positions are generated to be dynamically displayed, so that the intuitiveness of service transaction monitoring is improved.

In addition, each abstract monitoring logic set in the application is at least divided into a basic monitoring category, a conditional monitoring category and a judgment monitoring category. Therefore, when the combined configuration is performed on each embedded point event, the abstract interception logic under the judgment interception category can be adopted to perform the pre-configuration of various judgment rules among the embedded point events of each service application in advance, for example, the abstract interception logic expressed by a sequence interception module (sequence) is adopted to further configure the execution sequence of the embedded point events of different service applications, and the abstract interception logic expressed by a statistical interception module (statistical) is adopted to further configure the transaction data statistical rules of the embedded point events of different service applications.

Therefore, after monitoring the execution state of the target service transaction on each service application, an execution test report of the target service transaction is generated according to the execution state of the buried point event under the judgment monitoring category configured by the association between each service application. The execution state of the embedded point event under the judgment monitoring type configured by the association between the business applications is obtained, and the execution state of each embedded point event is analyzed according to the judgment rule configured by the abstract monitoring logic under the judgment monitoring type for the embedded point event configured by the association between the business applications, so that the execution test report of the target business transaction is generated.

At this time, various judgment rules are further combined and configured for the embedded point events of each service application in advance by adopting the abstract monitoring logic under the judgment monitoring category, so that after the execution state of the target service transaction on each service application is monitored, the integral execution condition of the target service transaction among each service application can be uniformly analyzed directly according to the abstract monitoring logic under various judgment monitoring categories which are combined and configured in advance, the execution correctness test of the target service transaction among each service application is automatically completed, and after the transaction execution data of the target service transaction on each service application is extracted, a tester manually inputs the corresponding judgment rules on a retrieval and analysis page to test the execution condition of the target service transaction, so that the test efficiency of the target service transaction execution is improved.

The technical scheme provided by the embodiment of the application generates at least one embedded point event under each service application according to the embedded point configuration file of each service application facing to the target service transaction, then generates the transaction monitoring event under each service application according to the combined configuration executed on each embedded point event by adopting different abstract monitoring logics, further deploys the transaction monitoring event under each service application into the service application to monitor the execution state of the target service transaction on each service application, thereby carrying out the combined configuration on the embedded point event under each service application through the set different abstract monitoring logics, realizing the execution state monitoring of the service transaction on each service application, filtering redundant data in the service transaction execution process from a source, and not compiling separate monitoring codes for each implementation class and method parameter and return content needing to be monitored in each service application respectively, the code compiling workload in the early stage of business transaction monitoring is greatly reduced, and the application expandability of the business transaction monitoring is improved.

As an optional implementation scheme in the embodiment of the present application, when different abstract monitoring logics are adopted to perform combined configuration on each embedded point event under each service application according to an actual monitoring requirement of each embedded point event, in order to ensure further convenient configuration of each embedded point event, a monitoring configuration page is pre-constructed in the present application, and the monitoring configuration page displays two or more set abstract monitoring logics and displays each embedded point event under each service application in a partitioned manner according to each service application.

As shown in fig. 4, for the display of each abstract monitoring logic, the abstract monitoring logic under each monitoring category may be respectively displayed under three monitoring categories, namely, a basic monitoring category, a conditional monitoring category and a decision monitoring category, which are pre-divided, so that when a certain abstract monitoring logic is subsequently used to perform combined configuration on each embedded point event, the abstract monitoring logic can be quickly found under the corresponding monitoring category by analyzing the monitoring category to which the abstract monitoring logic belongs.

In the following embodiments, a detailed explanation is mainly given to a specific process of performing combined configuration on each buried point event under each service application by using different abstract listening logics in a constructed listening configuration page.

Fig. 5 is a flowchart illustrating another method for monitoring a business transaction according to an embodiment of the present application. As shown in fig. 5, the method may specifically include the following steps:

s510, generating at least one buried point event under each service application according to the buried point configuration file of each service application facing to the target service transaction.

And S520, responding to the combined configuration operation of each embedded point event in the constructed monitoring configuration page, and performing configuration conversion under different abstract monitoring logics on each embedded point event.

Optionally, after generating each buried point event under each service application according to the buried point configuration file of each service application, the generated buried point event can only execute a basic monitoring function defined by the buried point in the buried point configuration file, that is, execute a monitoring function of the abstract monitoring logic under the basic monitoring category. Therefore, as shown in fig. 4, for each service application, a partition shows each buried event under the service application in the constructed listening configuration page. Meanwhile, in the monitoring configuration page, abstract monitoring logics belonging to each monitoring category are respectively displayed under each monitoring category, and the abstract monitoring function executed by each abstract monitoring logic is set.

Specifically, for various actual monitoring requirements to be further configured and realized among various embedded point events under various service applications, any corresponding abstract monitoring logic can be triggered in a monitoring configuration page, and after a triggering operation of a certain abstract monitoring logic is detected, various pieces of information, which are set by the abstract monitoring logic and need to be optimally configured, of an abstract monitoring function can be displayed in the monitoring configuration page, so that a specific embedded point event needing to be configured with the abstract monitoring logic is determined in various embedded point events under various service applications in a dragging or clicking mode, wherein the determined specific embedded point event can be an embedded point event under the same service application or an embedded point event under different service applications, and thus, the combined configuration among the embedded point events under different service applications is realized. And then, according to the configuration information of the abstract monitoring function set under the triggered abstract monitoring logic, carrying out further optimized configuration on each determined concrete buried point event. By adopting the same mode, further combined configuration under different abstract monitoring logics can be executed on each buried point event under each service application, so that configuration conversion of each buried point event under different abstract monitoring logics is realized, and the buried point position of each buried point event definition needing to execute a monitoring function is more accurate.

For example, the present application may set a corresponding snoop execution template for each abstract snoop logic, so as to uniformly display various pieces of information that the abstract snoop logic has set the abstract snoop function and needs to be optimally configured. Therefore, the configuration conversion of each buried point event under different abstract monitoring logics can be mainly divided into: responding to the triggering operation of any abstract monitoring logic in the monitoring configuration page, and displaying a monitoring execution template set under the abstract monitoring logic; and 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.

That is to say, when any corresponding abstract monitoring logic is triggered in a monitoring configuration page according to various actual monitoring requirements to be further configured and realized among various embedded point events, in response to the triggering operation of any abstract monitoring logic in the monitoring configuration page, a monitoring execution template set under the abstract monitoring logic is displayed in the monitoring configuration page, and various pieces of information and monitoring configuration logic which are required to be optimally configured for the abstract monitoring function and are set in the monitoring execution template.

As shown in fig. 4, taking the abstract snooping logic represented by the interval snooping module (interval) as an example, the snooping execution template displays a global serial number starting point (Start), a transaction log 1(INNER1) to a transaction log n (innenren) and a global serial number terminal (End) that need to be configured.

Then, a dragging or clicking mode is adopted to select a suitable target embedded point event aiming at each set configuration information in the monitoring execution template from each embedded point event under each service application displayed in the monitoring configuration page, and the configuration parameters of each selected target embedded point event are input according to the specific configuration requirements in the monitoring execution template. Therefore, in response to the event selection operation in the monitoring configuration page, the configuration parameters input for each target buried point event can be adopted, and the target buried point events are further optimally configured according to the monitoring configuration logic in the monitoring execution template.

For example, for each configuration information in the monitoring execution template set under the interval monitoring module (interval), the target embedded point in each embedded point event under each service application may be configured to the corresponding global serial number starting point (Start), transaction log 1(INNER1) until the transaction log n (innern) and the global serial number terminal (End) in a dragging manner, and then the configuration under the further optimized condition is performed on the global serial number starting point (Start), the transaction log 1(INNER1) until the transaction log n (innern) and the target embedded point event under the global serial number terminal (End), so that the actual monitoring function of each embedded point event is realized, for example, further internal monitoring is performed on the transaction log 1(INNER 1).

And S530, responding to the configuration completion operation in the monitoring configuration page, and combining and generating the transaction monitoring event under each service application according to the service application where the converted embedded point event is located.

Optionally, the configuration process in S520 is repeatedly executed under different abstract monitoring logics for each embedded point event in the monitoring configuration page, so that each embedded point event under each service application can be further combined, configured and converted, and each embedded point event after configuration conversion can execute a more accurate real monitoring function. Therefore, after the further configuration conversion of each buried point event under each service application is completed, the corresponding configuration completion operation is executed in the listening configuration page.

At this time, in response to the configuration completion operation in the monitoring configuration page, a buried point event under each service application may be acquired, where the buried point event under each service application may include a buried point event that is initially generated and that is not configured in a combined manner but only implements a basic monitoring function, and a buried point event that is configured in a combined manner and then is converted into abstract monitoring logics that implement each conditional monitoring category or determine each monitoring category. Therefore, according to the service application where each embedded point event completed by the current configuration is located, each embedded point event existing after the configuration conversion is completed under each service application can be combined, so that a transaction monitoring event under each service transaction is generated.

In addition, the transaction monitoring event under each service transaction can be deployed into the service application by triggering a "deployment" button set in the monitoring configuration page.

And S540, the transaction monitoring event under each service application is deployed into the service application so as to monitor the execution state of the target service transaction on each service application.

The technical scheme provided by the embodiment of the application generates at least one embedded point event under each service application according to an embedded point configuration file of each service application facing to target service transaction, then adopts different abstract monitoring logics to carry out further combined configuration on each embedded point event in a constructed monitoring configuration page so as to generate a transaction monitoring event under each service application, further deploys the transaction monitoring event under each service application into the service application so as to monitor the execution state of the target service transaction on each service application, thereby carrying out combined configuration on the embedded point events under each service application through the set different abstract monitoring logics, realizing the monitoring of the execution state of the service transaction on each service application, filtering redundant data in the execution process of the service transaction, and not compiling separate monitoring codes for each implementation class and method parameter and return content needing to be monitored in each service application respectively, the code compiling workload in the early stage of business transaction monitoring is greatly reduced, and the application expandability of the business transaction monitoring is improved.

Fig. 6 is a schematic block diagram of a monitoring apparatus for business transaction according to an embodiment of the present application. As shown in fig. 6, the apparatus 600 may include:

a buried point generating module 610, configured to generate at least one buried point event under each service application according to a buried point configuration file of each service application for a target service transaction;

a buried point configuration module 620, 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;

the transaction monitoring module 630 is configured to deploy a transaction monitoring event under each service application into the service application to monitor an execution state of the target service transaction on each service application.

Further, the buried point configuration module 620 may include:

the configuration conversion unit is used for responding to the combined configuration operation of each buried point event in the constructed monitoring configuration page and performing configuration conversion under different abstract monitoring logics on each buried point event;

the event generating unit is used for responding to configuration completion operation in the monitoring configuration page and combining and generating transaction monitoring events under each service application according to the service application where the converted embedded point event is located;

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

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

Further, the apparatus 600 for monitoring a service transaction may further include:

and the test report generation module is used for generating an execution test report of the target service transaction according to the execution state of the buried point event under the judgment monitoring type configured by the association among the service applications.

In the embodiment of the application, at least one embedded point event under each service application is generated according to an embedded point configuration file of each service application facing to target service transaction, then transaction monitoring events under each service application are generated according to combined configuration executed on each embedded point event by adopting different abstract monitoring logics, further the transaction monitoring events under each service application are deployed into the service application to monitor the execution state of the target service transaction on each service application, so that the embedded point events under each service application are combined and configured through the set different abstract monitoring logics, the execution state monitoring of the service transaction on each service application can be realized, redundant data in the execution process of the service transaction is filtered from a source, and independent monitoring codes do not need to be written for each implementation class and method parameters and return contents needing to be monitored in each service application, the code compiling workload in the early stage of business transaction monitoring is greatly reduced, and the application expandability of the business transaction monitoring is improved.

It is to be understood that apparatus embodiments and method embodiments may correspond to one another and that similar descriptions may refer to method embodiments. To avoid repetition, further description is omitted here. Specifically, the apparatus 600 shown in fig. 6 may perform any method embodiment provided in the present application, and the foregoing and other operations and/or functions of each module in the apparatus 600 are respectively for implementing corresponding processes in each method of the embodiment of the present application, and are not described herein again for brevity.

The apparatus 600 of the embodiments of the present application is described above in connection with the figures from the perspective of functional modules. It should be understood that the functional modules may be implemented by hardware, by instructions in software, or by a combination of hardware and software modules. Specifically, the steps of the method embodiments in the present application may be implemented by integrated logic circuits of hardware in a processor and/or instructions in the form of software, and the steps of the method disclosed in conjunction with the embodiments in the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. Alternatively, the software modules may be located in random access memory, flash memory, read only memory, programmable read only memory, electrically erasable programmable memory, registers, and the like, as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps in the above method embodiments in combination with hardware thereof.

Fig. 7 is a schematic block diagram of an electronic device 700 provided in an embodiment of the present application.

As shown in fig. 7, the electronic device 700 may include:

a memory 710 and a processor 720, the memory 710 for storing a computer program and transferring the program code to the processor 720. In other words, the processor 720 may call and run a computer program from the memory 710 to implement the method in the embodiment of the present application.

For example, the processor 720 may be configured to perform the above-described method embodiments according to instructions in the computer program.

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

general purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components, and the like.

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

volatile memory and/or non-volatile memory. The non-volatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable PROM (EEPROM), or a flash Memory. Volatile Memory can be Random Access Memory (RAM), which acts as external cache Memory. By way of example, but not limitation, many forms of RAM are available, such as Static random access memory (Static RAM, SRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic random access memory (Synchronous DRAM, SDRAM), Double Data Rate Synchronous Dynamic random access memory (DDR SDRAM), Enhanced Synchronous SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), and Direct Rambus RAM (DR RAM).

In some embodiments of the present application, the computer program may be partitioned into one or more modules, which are stored in the memory 710 and executed by the processor 720 to perform the methods provided herein. The one or more modules may be a series of computer program instruction segments capable of performing certain functions, the instruction segments describing the execution of the computer program in the electronic device.

As shown in fig. 7, the electronic device may further include:

a transceiver 730, the transceiver 730 being connectable to the processor 720 or the memory 710.

The processor 720 may control the transceiver 730 to communicate with other devices, and specifically, may transmit information or data to the other devices or receive information or data transmitted by the 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.

It should be understood that the various components in the electronic device are connected by a bus system that includes a power bus, a control bus, and a status signal bus in addition to a data bus.

Embodiments of the present application also provide a computer storage medium having a computer program stored thereon, where the computer program, when executed by a computer, enables the computer to execute the method of the above method embodiments. In other words, the present application also provides a computer program product containing instructions, which when executed by a computer, cause the computer to execute the method of the above method embodiments.

When implemented in software, may 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. The procedures or functions described in accordance with the embodiments of the present application occur, in whole or in part, when the computer program instructions are loaded and executed on a computer. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website, computer, server, or data center to another website, computer, server, or data center via wire (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., 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, a data center, etc., that includes one or more of the available media. The usable medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a Digital Video Disk (DVD)), or a semiconductor medium (e.g., a Solid State Disk (SSD)), among others.

Those of ordinary skill in the art will appreciate that the various illustrative modules and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the module is merely a logical division, and other divisions may be realized in practice, for example, a plurality of modules or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or modules, and may be in an electrical, mechanical or other form.

Modules described as separate parts may or may not be physically separate, and parts displayed as modules may or may not be physical modules, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. For example, functional modules in the embodiments of the present application may be integrated into one processing module, or each of the modules may exist alone physically, or two or more modules are integrated into one module.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method for monitoring business transaction, comprising:

2. The method of claim 1, wherein generating transaction monitoring events for each business application according to the combined configuration of the burial point events under different set abstract monitoring logics comprises:

3. The method of claim 2, wherein performing configuration conversion under different abstract snoop logic for each of the buried point events in response to a combined configuration operation of each of the buried point events within the constructed snoop configuration page comprises:

4. The method of claim 1, wherein the monitoring the execution status of the target business transaction on each business application comprises:

5. The method of claim 1, wherein the abstract snoop logic is classified into at least three categories, a base snoop category, a conditional snoop category, and a decision snoop category.

6. The method of claim 5, after monitoring the execution status of the target business transaction on each of the business applications, further comprising:

7. An apparatus for monitoring a transaction, comprising:

8. An electronic device, comprising:

a processor and a memory, the memory for storing a computer program, the processor for invoking and executing the computer program stored in the memory to perform the method of snooping of a business transaction of any one of claims 1-6.

9. A computer-readable storage medium for storing a computer program for causing a computer to execute the method of listening for a business transaction of any one of claims 1-6.

10. A computer program product comprising computer program/instructions, characterized in that the computer program/instructions, when executed by a processor, implement a method of listening for a business transaction according to any of claims 1-6.