CN116957797A - Transaction success rate monitoring method, device, equipment and storage medium - Google Patents

Abstract

The application provides a method, a device, equipment and a storage medium for monitoring transaction success rate, which relate to the field of financial science and technology or other fields and are applied to a monitoring platform and comprise the following steps: receiving a transaction success rate monitoring request triggered by a monitoring user; acquiring at least one transaction flow log corresponding to each application system in a preset monitoring time period; determining corresponding transaction states according to at least one transaction flow log, and calculating the technical transaction failure quantity, the service transaction failure quantity and the total transaction quantity corresponding to each application system according to the at least one transaction state; calculating technical transaction success rate and business transaction success rate; and generating and displaying transaction success rate monitoring responses corresponding to each application system according to the technical transaction success rate and the business transaction success rate. The application adopts the head field of the failure code in the transaction flow log to determine the transaction state, and further calculates the technical transaction success rate and the business transaction success rate respectively.

Description

Transaction success rate monitoring method, device, equipment and storage medium

Technical Field

The present application relates to the field of financial science and technology, and in particular, to a method, an apparatus, a device, and a storage medium for monitoring a transaction success rate.

Background

With the continuous development of financial science and technology, the situation that users realize transactions by adopting online banks is more and more, in order to ensure the stable operation of online transactions, related enterprises adopt a monitoring platform to monitor user transactions and calculate success rates, so that enterprise users know the success conditions of the transactions.

In the prior art, a monitoring platform receives a running log corresponding to a transaction sent by each application system in a preset monitoring time period, determines whether the transaction is successful or not based on the content in the running log, obtains the successful transaction quantity, and calculates the success rate based on the total transaction quantity and the successful transaction quantity of the application systems in the preset monitoring time period.

However, the success rate obtained in the prior art represents the overall success rate, so that the monitoring user is inconvenient to purposefully conduct operation and maintenance processing on the failed transaction.

Disclosure of Invention

The application provides a method, a device, equipment and a storage medium for monitoring transaction success rate, which are used for solving the problem that a user cannot conduct operation and maintenance processing on failed transactions in a targeted manner.

In a first aspect, the present application provides a method for monitoring success rate of transactions, where the method is applied to a monitoring platform, and the method includes:

Receiving a transaction success rate monitoring request triggered by a monitoring user; the transaction success rate monitoring request comprises a preset monitoring time period;

acquiring at least one transaction flow log corresponding to each application system in a preset monitoring time period;

determining a corresponding transaction state according to at least one transaction flow log, and calculating the technical transaction failure quantity, the service transaction failure quantity and the total transaction quantity corresponding to each application system according to at least one transaction state; the transaction state comprises one of a technical failure state, a business failure state and a transaction success state;

calculating technical transaction success rate and business transaction success rate according to the technical transaction failure quantity, the business transaction failure quantity and the total transaction quantity;

and generating and displaying transaction success rate monitoring response corresponding to each application system according to the technical transaction success rate and the business transaction success rate, so that a monitoring user monitors the transaction success rate corresponding to each application system.

In a second aspect, the present application provides a device for monitoring success rate of transactions, the device being located on a monitoring platform, the device comprising:

the receiving module is used for receiving a transaction success rate monitoring request triggered by a monitoring user; the transaction success rate monitoring request comprises a preset monitoring time period;

The acquisition module is used for acquiring at least one transaction flow log corresponding to each application system in a preset monitoring time period;

the determining module is used for determining corresponding transaction states according to at least one transaction flow log, and the calculating module is used for calculating the technical transaction failure quantity, the service transaction failure quantity and the total transaction quantity corresponding to each application system according to at least one transaction state; the transaction state comprises one of a technical failure state, a business failure state and a transaction success state;

the calculation module is also used for calculating the technical transaction success rate and the service transaction success rate according to the technical transaction failure quantity, the service transaction failure quantity and the total transaction quantity;

and the generation module is used for generating and displaying transaction success rate monitoring response corresponding to each application system according to the technical transaction success rate and the business transaction success rate so as to enable the monitoring user to monitor the transaction success rate corresponding to each application system.

In a third aspect, the present application provides a monitoring platform comprising: a processor, and a memory and transceiver communicatively coupled to the processor;

the memory stores computer-executable instructions; the transceiver is used for receiving and transmitting data;

The processor executes computer-executable instructions stored in the memory to implement the method described in the first aspect or any one of the ways.

In a fourth aspect, the present application provides a computer-readable storage medium having stored therein computer-executable instructions which, when executed by a processor, are adapted to carry out the method of the first aspect or any of the aspects.

In a fifth aspect, the application provides a computer program product comprising a computer program which, when executed by a processor, implements a method as described in the first aspect or any of the modes above.

According to the method, the device, the equipment and the storage medium for monitoring the transaction success rate, the monitoring platform receives the transaction success rate monitoring request triggered by the monitoring user, and further at least one transaction flow log corresponding to each application system in a preset monitoring time period is obtained, wherein the transaction success rate monitoring request comprises the preset monitoring time period. Further, the monitoring platform determines the corresponding transaction state according to at least one transaction running log, so as to determine the technical transaction failure number, the service transaction failure number and the transaction total number corresponding to each application system according to the transaction state.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application.

FIG. 1 is an application scenario diagram of a method for monitoring transaction success rate provided by the application;

FIG. 2 is a block diagram of a system for monitoring transaction success rate according to the present application;

fig. 3 is a flow chart of a method for monitoring success rate of transaction according to the first embodiment;

fig. 4 is a flow chart of a method for monitoring success rate of transaction according to the second embodiment;

fig. 5 is a flow chart of a method for monitoring success rate of transaction according to the third embodiment;

fig. 6 is a flow chart of a method for monitoring success rate of transaction according to the fourth embodiment;

fig. 7 is a flow chart of a method for monitoring success rate of transaction according to the sixth embodiment;

fig. 8 is a schematic structural diagram of a monitoring device for transaction success rate according to a seventh embodiment;

fig. 9 is a schematic structural diagram of a monitoring platform according to an eighth embodiment.

Specific embodiments of the present application have been shown by way of the above drawings and will be described in more detail below. The drawings and the written description are not intended to limit the scope of the inventive concepts in any way, but rather to illustrate the inventive concepts to those skilled in the art by reference to the specific embodiments.

Detailed Description

Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with the application. Rather, they are merely examples of apparatus and methods consistent with aspects of the application as detailed in the accompanying claims.

In the prior art, a monitoring platform receives a running log corresponding to a transaction sent by each application system in a preset monitoring time period, determines whether the transaction is successful based on the content in the running log to obtain the successful transaction quantity, and meanwhile, calculates the total transaction quantity in the preset monitoring time period, and determines the ratio as the transaction success rate based on the ratio of the calculated successful transaction quantity to the total transaction quantity.

However, the success rate obtained in the prior art represents the overall success rate, so that the monitoring user can monitor the overall success rate, and further, the monitoring user is inconvenient to carry out targeted operation and maintenance processing on the failed transaction.

In order to solve the defects of the prior art, the inventor of the scheme designs a new scheme through creative research. The technical transaction success rate and the total transaction number can be calculated by the monitoring platform according to at least one transaction state corresponding to each application system, so that further the technical transaction success rate and the total transaction success rate can be calculated by the monitoring platform. Therefore, the method and the system can calculate more refined transaction success rate, and further monitor the transaction success rate which a user needs to pay attention to according to the technical transaction success rate and the business transaction success rate, so that the monitoring user can know each transaction success rate in a targeted manner, and can know the technical transaction success rate in a targeted manner according to the technical transaction success rate, and further conduct operation and maintenance processing in a targeted manner.

The application provides a method, a device, equipment and a storage medium for monitoring transaction success rate.

Fig. 1 is an application scenario diagram of a method for monitoring transaction success rate provided by the application. As shown in fig. 1, the application scenario diagram includes a monitoring platform 101 and an application system 102.

The application system 102 may include a plurality of application systems 1021 and 1022, as an example, in fig. 1. Wherein application system 1021 and application system 1022 have calling and called relationships. For a description of the relationship of the application system 1221 and the application system 1022, reference is made below, and no further description is given here. The application system 102 may be, among other things, a server or the like that implements the transaction operations.

The monitoring platform 101 may be a mobile device, a fixed device, or other devices, such as a mobile phone or a tablet, without limitation. The monitoring platform 101 includes a device for monitoring the success rate of the transaction, and is used for realizing the tasks such as calculating the success rate of the transaction.

Specifically, the monitoring user triggers a transaction success rate monitoring request through the monitoring platform 102, where the transaction success rate monitoring request includes a preset monitoring time period.

Further, the monitoring platform 101 obtains at least one transaction flow log corresponding to the application system 102 in a preset monitoring period from the log file, the monitoring platform 101 determines a corresponding transaction state according to the at least one transaction flow log, and then the monitoring platform 101 calculates the technical transaction failure number, the service transaction failure number and the transaction total number corresponding to the application system 1021 and the application system 1022 according to the at least one transaction state. Wherein the application system 1021 and the application system 1022 generate corresponding transaction flow logs and store in log files.

Further, the monitoring platform 101 calculates the technical transaction success rate and the business transaction success rate according to the technical transaction failure number, the business transaction failure number and the total number of transactions.

Further, the monitoring platform 101 generates and displays a transaction success rate monitoring response corresponding to each application system according to the technical transaction success rate and the business transaction success rate, so that the monitoring user monitors the transaction success rate corresponding to each application system.

It should be noted that, the user information (including but not limited to user equipment information, user personal information, etc.) and the data (including but not limited to data for analysis, stored data, presented data, etc.) related to the present application are information and data authorized by the user or fully authorized by each party, and the collection, use and processing of the related data need to comply with related laws and regulations and standards, and provide corresponding operation entries for the user to select authorization or rejection.

It should be noted that the method, the device, the equipment and the storage medium for monitoring the transaction success rate provided by the application can be applied to the field of financial science and technology, and can also be applied to any field except the financial science and technology, and the application field of the application is not limited.

Fig. 2 is a schematic diagram of a system for monitoring transaction success rate according to the present application. As shown in fig. 2, the method specifically includes: a first application system 201, a second application system 202, and a monitoring platform 203.

Wherein the first application system 201 and the second application system 202 may be used to implement a financial transaction.

For example, when a target user adopts a terminal to implement a certain financial service, where multiple application systems are required to implement at least one transaction operation included in the financial service, it is assumed that the financial service includes a first transaction operation and a second transaction operation, and when the financial service is completed, the first application system 201 needs to implement the first transaction operation and then the second application system 202 needs to implement the second transaction operation, so specifically, after receiving a transaction success rate monitoring request triggered by the monitoring user, the monitoring platform 203 sends the transaction success rate monitoring request to the first application system 201, so as to generate a transaction request message, the first application system 201 sends the transaction request message to the second application system 202, and then the second application system 202 fills fields needing to be filled in the transaction request message, so as to generate a transaction response message, where the transaction response message includes contents for calculating a transaction success rate. The second application system 202 sends the transaction response message to the first application system 201, so that the first application system 201 parses the transaction response message, obtains the content about the calculated transaction success rate in the transaction response message, generates a first transaction running log based on the content about the calculated transaction success rate, and stores the first transaction running log in the log file 204.

Further, since the second application system 202 is the application system corresponding to the last transaction operation of the financial service, after receiving the transaction request message sent by the first application system 201, the second application system 202 generates a second transaction running log for the second transaction operation of the financial service, and stores the second transaction running log in the log file 204.

It should be noted that, the first application system 201 is a calling system, the second application system 202 is a called system, and the first transaction operation and the second transaction operation can be completed through the first application system 201 and the second application system 202, so as to implement the financial service.

Further, the monitoring platform 203 obtains the first transaction flow log and the second transaction flow log from the log file 204. So that the monitoring platform 203 obtains the transaction flow log from the log file 204.

It should be noted that, the transaction request message sent by the first application system includes a field to be filled. The message includes a message header, a message body, an additional message and message authentication, and the message header of the request message includes a transaction status code, where the content of the transaction status code is empty, which represents that filling is needed. The message body of the request message includes a failure code, and at this time, the content of the failure code is empty, which represents that filling is needed. After the request message is sent from the first application system 201 to the second application system 202, the second application system 202 fills the portion to be filled, and illustratively, the filling transaction status code is a success status code or other status codes, and the filling failure code is a technical failure code line or other code lines. Wherein the success status code indicates that the transaction was successful and the technical failure code row indicates that the transaction was a technical failure. The specific description will refer to the following examples, and will not be repeated here. The message comprises a transaction request message and a transaction response message.

The message header is used for routing and tracking the transaction and comprises technical information related to message routing, processing, tracking and state, and the information elements of the technical information must be strictly and sequentially specified.

Wherein the message body is related business information describing the transaction.

The additional message refers to unstructured information carried along with the message, such as pictures, audio, video, and the like.

The message Wen Jian is used to identify whether the message is tampered during the transmission process between the application systems.

It can be understood that, in the present application, the transaction request message includes a part of code content that needs to be filled, and the transaction response message is a message after filling the code content that needs to be filled.

Note that, the log file 204 may be plural, and one log file is illustrated as an example as shown in fig. 2.

It should be noted that, the message may also include content such as application system code, time of generating the message, etc., which is not limited herein.

As shown in fig. 2, 01-04 marked on the first application system and the second application system are four time points, which respectively represent:

01: the method comprises the steps that a first application system receives a time point of a transaction success rate monitoring request sent by a monitoring platform, and a second application system receives a time point of a transaction request message sent by the first application system;

02: the method comprises the steps that a first application system sends a transaction request message to a second application system, and the second application system sends the transaction request message to a downstream application system, wherein the downstream application system refers to a next called application system corresponding to the downstream application system;

03: the first application system receives the time point of the second application system transaction response message and the time point of the second application system generating the second transaction flow log;

04: the first application system parses and generates a point in time of the first transaction flow log from the transaction response message.

The application provides a method for monitoring transaction success rate, which aims to solve the technical problems in the prior art.

The following describes the technical scheme of the present application and how the technical scheme of the present application solves the above technical problems in detail with specific embodiments. The following embodiments may be combined with each other, and the same or similar concepts or processes may not be described in detail in some embodiments. Embodiments of the present application will be described below with reference to the accompanying drawings.

Example 1

The execution subject of the application is a monitoring device for success rate of transaction (hereinafter referred to as monitoring device), and the monitoring device is positioned on a monitoring platform.

Fig. 3 is a flowchart of a method for monitoring success rate of transactions according to a first embodiment. As shown in fig. 3, the specific steps are as follows.

S301, receiving a transaction success rate monitoring request triggered by a monitoring user; the transaction success rate monitoring request comprises a preset monitoring time period.

The preset monitoring time period refers to a preset monitoring time period. For example, the preset monitoring period may be 2023, 6, 1, 12:00, 2023, 6, 1, 12:05, wherein the preset time interval is 5 minutes.

In the application, the monitoring interval can be set to realize long-term monitoring of the success rate of the transaction.

Specifically, the monitoring user clicks a component for monitoring the transaction success rate on a monitoring page of the monitoring platform, so that a transaction success rate monitoring request is triggered.

S302, at least one transaction flow log corresponding to each application system in a preset monitoring time period is obtained.

Where transaction flow logs refer to any transaction information about transactions, exemplary, transaction codes, transaction status, transaction invoker, transaction invoicer, transaction time, and any other information related to transactions, without limitation herein.

Specifically, at least one transaction flow log corresponding to each application system is stored in the log file, so that the monitoring platform obtains at least one transaction flow log corresponding to each application system from the log file.

In one mode, each application system generates a flow log and then sends the flow log to a storage area of the monitoring platform, so that the monitoring platform obtains at least one transaction flow log corresponding to each application system from the storage area of the monitoring platform.

S303, determining a corresponding transaction state according to at least one transaction flow log, and calculating the technical transaction failure quantity, the service transaction failure quantity and the total transaction quantity corresponding to each application system according to the at least one transaction state; the transaction state includes one of a technology failure state, a business failure state, and a transaction success state.

The technical transaction failure number refers to the number of transaction failures caused by technical problems. Illustratively, the transaction fails due to an application system's own drawbacks. It will be appreciated that the corresponding state of the transaction whose technical transaction failed is a technical failure state.

The number of failed business transactions refers to the number of failed business transactions due to business problems. Illustratively, the transaction fails due to the target user operating on the terminal with errors. It will be appreciated that the corresponding state of the transaction whose business transaction fails is a business failure state.

The total transaction number refers to the total transaction number corresponding to at least one service by each application system.

It is understood that the transaction success state refers to a state corresponding to a transaction that is successful. Wherein the transaction state includes one of a technology failure state, a business failure state, and a transaction success state. It will be appreciated that a transaction can only correspond to one state.

S304, calculating the technical transaction success rate and the business transaction success rate according to the technical transaction failure quantity, the business transaction failure quantity and the total transaction quantity.

The technical transaction success rate refers to the probability corresponding to the successful transaction of the technical class.

The success rate of business transaction refers to the probability corresponding to the successful transaction of the business class.

In one approach, the monitoring platform may calculate a technical failure rate based on the number of technical failures and the total number of transactions, then calculate a difference between the value 1 and the technical failure rate, and determine the difference as a technical transaction success rate. Similarly, the success rate of business transaction can be calculated by the same method.

S305, generating and displaying transaction success rate monitoring response corresponding to each application system according to the technical transaction success rate and the business transaction success rate, so that a monitoring user monitors the transaction success rate corresponding to each application system.

The transaction success rate monitoring response comprises a technical transaction success rate and a business transaction success rate. It can be understood that the transaction success rate monitoring response is displayed on the monitoring platform, so that the monitoring user can monitor the transaction success rate corresponding to each application system.

It should be noted that, the application can calculate the transaction success rate corresponding to each application system and display the transaction success rate monitoring response corresponding to each application system. The transaction success rate comprises technical transaction success rate and business transaction success rate.

In the application, corresponding alarm thresholds are set in advance for the technical transaction success rate and the service transaction success rate respectively, and when the technical transaction success rate is smaller than or equal to the corresponding preset technical alarm threshold, the monitoring platform gives an alarm; and simultaneously, when the success rate of the business transaction is smaller than or equal to a corresponding preset business alarm threshold value, the monitoring platform gives an alarm. The alarm mode can be sending a short message or making a call to a corresponding monitoring user or the monitoring platform sends a sound to remind.

It should be noted that, the application realizes the calculation of the technical transaction success rate and the business transaction success rate respectively by differentiating the transaction states.

The embodiment provides a method for monitoring transaction success rate, wherein a monitoring platform receives a transaction success rate monitoring request triggered by a monitoring user, and further obtains at least one transaction flow log corresponding to each application system in a preset monitoring time period, wherein the transaction success rate monitoring request comprises the preset monitoring time period. Further, the monitoring platform determines the corresponding transaction state according to at least one transaction running log, so as to determine the technical transaction failure number, the service transaction failure number and the transaction total number corresponding to each application system according to the transaction state.

Example two

Further refinements of any of the embodiments described above are provided for this embodiment. In this embodiment, the transaction flow log includes a transaction status code and a failure code.

Wherein the transaction status code refers to a code regarding the status of a transaction, which is used to characterize the status of a corresponding transaction. For example, if the transaction status code is 00, this represents that the transaction was successful; if the transaction status code is 01, this represents failure. Where 00 is a success status code and 01 is a failure status code.

In one approach, the transaction status code may also be 02, representing an unknown status. Where 02 is an unknown state code.

Wherein the failure code refers to a transaction failure type code. The failure code may be a technical failure code row or a service failure code row.

It will be appreciated that when the failure code is a technical failure code line, the transaction is represented as a technical failure; when the failure code is a business failure code row, the transaction is represented as business failure.

This embodiment is an alternative way of determining the corresponding transaction status from at least one transaction flow log.

Fig. 4 is a flow chart of a method for monitoring success rate of transaction according to the second embodiment. As shown in fig. 4, the specific steps are as follows.

S401, in response to determining that the transaction state code is a failure state code and the failure code is a technology failure code row, determining that the transaction state is a technology failure state.

Specifically, the monitoring platform determines that the transaction state code is a failed state code, at this time, the transaction can be determined to be a failed transaction, and further, the failed code is determined to be a technical failure code row, so that the monitoring platform determines that the transaction state is a technical failure state.

S402, in response to determining that the transaction state code is a failure state code and the failure code is a business failure code row, determining that the transaction state is a technical failure state.

The specific implementation refers to S401, and will not be described herein.

S403, in response to determining that the transaction status code is a success status code, determining that the transaction status is a transaction success status.

Specifically, the monitoring platform determines the transaction status code as a success code, thereby determining that the transaction is a successful transaction, so that the transaction status is determined to be a transaction success status.

It should be noted that technical success and business success are presented for successful transactions, i.e. on behalf of the transaction.

The embodiment provides a method for monitoring a transaction success rate, in this embodiment, a transaction state is determined according to a transaction state code and a failure code included in a transaction flow log, when the transaction state code is the failure state code and the failure code is a technical failure code, the transaction state is determined to be a technical failure state, and likewise, the transaction state can be determined to be a service failure state or a transaction success state, so that the transaction state can be subdivided in this embodiment, and the transaction state can be determined in a targeted manner.

In this embodiment, a mode optional mode is further included, where the mode is: the step of determining the failure code as a technical failure code row is specifically as follows.

And determining the failure code as a technical failure code row in response to the beginning field in the failure code being a technical failure field.

For example, assuming that the failure code is E1234C00 eight fields, the monitoring platform determines that the first field in the failure code is E, where E is preset as the technology failure field, so that the monitoring platform determines that the first field in the failure code is the technology failure field, and thus determines that the failure code is a technology failure code line.

In this embodiment, a mode optional mode is further included, where the mode is: the step of determining the failure code as the service failure code row is as follows.

And determining the failure code as a service failure code row in response to the beginning field in the failure code as the service failure field.

For example, assuming that the failure code is S1234B00 eight fields, the monitoring platform determines that the beginning field in the failure code is S, where S is preset as the service failure field, so that the monitoring platform determines that the beginning field in the failure code is the service failure field, and thus determines that the failure code is a service failure code line.

It should be noted that all the exemplary examples or descriptions of the present application, such as S1234B00 and E1234C00, are for illustration only, and do not represent actual situations.

It should be noted that, the failure code exists in the message body of the transaction response message, the failure code is a unique identification code of failure, and is generated according to a certain specification, and should be applied, issued and managed in a unified way. The transaction response message is sent by the called system to the calling system.

Table 1: failure code specification.

As shown in Table 1, the failure classifications are primary, secondary, tertiary, and quaternary. The first class classification is to define error information execution, the length is 1 bit, and the format is E-service type field or S-technology type field. The key point of the application is first class classification, wherein E in E-service class field is positioned in the beginning field, namely service failure field; s in the S-technology class field is located in the beginning field, namely the technology failure field.

The embodiment provides a method for monitoring transaction success rate, in which a monitoring platform determines a technical failure field or a service failure field from a beginning field in a failure code, so as to determine that the failure code is a technical failure code row or a service failure code row in a targeted manner respectively.

Example III

This embodiment is a further refinement of the first or second embodiment.

The present embodiment is an optional way to calculate the technical transaction failure number, the service transaction failure number and the total number of transactions corresponding to each application system according to at least one transaction state.

Fig. 5 is a flow chart of a method for monitoring success rate of transaction according to the third embodiment. As shown in fig. 5, the specific steps are as follows.

S501, calculating the number of technical failure states from at least one transaction state to obtain the technical transaction failure number.

S502, calculating the number of the business failure states from at least one transaction state to obtain the business transaction failure number.

S503, determining the number of at least one transaction state as the total number of transactions.

For example, assuming that three transaction flow logs corresponding to the first application system are used for the first application system, each transaction flow log corresponds to one transaction state and is respectively a first transaction state, a second transaction state and a third transaction state.

Further, the monitoring platform determines three transaction states, and presumes that the first transaction state is a technical failure state, the second transaction state is a business failure state, and the third transaction state is a transaction success state, so that the monitoring platform calculates that the number of the technical failure states is 1, the number of the business failure states is 1, and the total number of the three transaction states is 3. Wherein the number (1) of transaction failure states is determined as a technical transaction failure number, and the number (1) of business failure states is determined as a business transaction failure number.

The embodiment provides a method for monitoring a transaction success rate, wherein a monitoring platform in the embodiment accurately calculates the number of technical failure states and the number of service failure states from at least one transaction state according to the technical failure states and the service failure states, thereby obtaining the number of technical transaction failures and the number of service transaction failures.

Example IV

Further refinements of any of the embodiments described above are provided for this embodiment. The present embodiment is an alternative way of calculating the technical transaction success rate and the business transaction success rate according to the technical transaction failure number, the business transaction failure number and the total number of transactions.

Fig. 6 is a flow chart of a method for monitoring success rate of transaction according to the fourth embodiment. As shown in fig. 6, the specific steps are as follows.

S601, calculating a first difference value between the total number of transactions and the number of technical transaction failures; the first difference is the number of successful technical transactions.

According to an example of embodiment three, the total number of transactions is 3, the number of technical transaction failures is 1, and thus the first difference is calculated to be 3-1=2, and thus the number of technical transaction successes is 2.

S602, calculating a second difference value between the total number of transactions and the number of failed business transactions; the second difference is the successful number of business transactions.

According to an example of embodiment three, the total number of transactions is 3, the number of failed business transactions is 1, and thus the second difference is calculated to be 3-1=2, and thus the number of successful business transactions is 2.

S603, calculating technical transaction success rate and business transaction success rate according to the first difference value, the second difference value and the total transaction amount.

The embodiment provides a method for monitoring a transaction success rate, which calculates a first difference and a second difference according to a total number of transactions, a technical transaction failure number and a service transaction failure number, wherein the first difference is a technical transaction success number, and the second difference is a service transaction success number, so that the technical transaction success number and the service transaction success number can be accurately calculated, and further the technical transaction success rate and the service transaction success rate can be calculated.

Example five

This embodiment is a further refinement of any of the embodiments described above. The embodiment is an optional way of calculating the technical transaction success rate and the business transaction success rate according to the first difference value, the second difference value and the total transaction number, and the specific contents are as follows.

Calculating a first ratio of the first difference value to the total number of transactions, and determining the first ratio as a technical transaction success rate; and calculating a second ratio of the second difference value to the total number of transactions, and determining the second ratio as the success rate of the business transactions.

According to the above embodiment, assuming that the number of successful technical transactions is 2, the number of successful business transactions is 2, and the total number of transactions is 3, a first ratio is calculated to be 2/3, and a second ratio is calculated to be 2/3, where the first ratio (2/3) is the success rate of technical transactions and the second ratio (2/3) is the success rate of business transactions.

The embodiment provides a method for monitoring the success rate of a transaction, wherein a monitoring platform in the embodiment calculates a first ratio according to a first difference value and the total number of the transactions, and the first ratio is the success rate of the technical transaction; meanwhile, a second ratio is calculated according to the second difference and the total transaction amount, and the second ratio is the service transaction success rate, so that the technical transaction success rate and the service transaction success rate can be accurately calculated in the embodiment.

Example six

Further refinements of any of the embodiments described above are provided for this embodiment. The transaction flow log in this embodiment further includes a description of the failure of the transaction.

Wherein, the failure description is a complete and accurate description for the failure information. Illustratively, "the channel cannot modify the credential type".

It should be noted that the failure description exists in the message body of the transaction response message, and is parsed from the transaction response message by the calling application system and generated into the flow log. The transaction response message is sent to the calling system by the called system. It should be noted that the failure code is uniquely matched to the failure description.

Fig. 7 is a flowchart of a method for monitoring success rate of transactions according to a sixth embodiment. As shown in fig. 7, the specific steps are as follows.

S701, obtaining corresponding failure description in at least one transaction flow log aiming at each application system.

For example, assume that, for a first application system, at least one transaction flow log corresponding to the first application system is obtained from a log file, then a failure description code is identified in the at least one transaction flow log, and content corresponding to the failure description code is obtained, so that a corresponding failure description is obtained.

It should be noted that, in at least one transaction flow log, only if the transaction status code is a failure status code, the failure description will have corresponding content, and when the transaction status code is a success status code, the transaction status is a transaction success status at this time, so the failure description in the corresponding transaction flow log is null, that is, the failure description content is not included.

It will be appreciated that for the first application system, it is assumed that there are three transaction pipeline logs, some of which may have corresponding failure description content and some may be null.

S702, calculating the occurrence times of each failure description content based on at least one failure description.

For example, it is assumed that the first application system corresponds to three failure descriptions, namely, a first failure description, a second failure description and a third failure description, wherein the first failure description is "the channel cannot modify the document type", the second failure description is "the transaction operation is not displayed" and the third failure description is "the channel cannot modify the document type", so that the occurrence number of the failure description content is "the channel cannot modify the document type" is calculated to be 2 times, and the occurrence number of the failure description content is "the transaction operation is not displayed" to be 1 time.

S703, storing and displaying the occurrence times of the failure description contents so as to monitor the statistics of the failure descriptions corresponding to the application systems by the monitoring user.

Further, the monitoring platform stores the failure description content of which the number of occurrences of the channel cannot modify the certificate type is 2 times and the failure description content of which the number of occurrences of the transaction operation is not displayed is 1 time in the own storage area, and at the same time, the monitoring platform displays the number of occurrences of each failure description content.

Further, the monitoring user monitors the statistics of the failure descriptions corresponding to the application systems through the display of the monitoring platform.

In this embodiment, since the transaction flow log includes failure descriptions of transactions, the monitoring platform acquires the failure descriptions from at least one flow log, and further calculates the occurrence times of each failure description content, so that the monitoring platform can display the occurrence times of each failure description content, and further, the monitoring user monitors statistics of the failure descriptions, which is beneficial to the monitoring user to know the failure descriptions.

Example seven

The following are device embodiments of the present application. Fig. 8 is a schematic structural diagram of a device for monitoring success rate of transactions according to a seventh embodiment. The monitoring device 800 is located on a monitoring platform, and the monitoring device 800 includes the following modules.

A receiving module 801, configured to receive a transaction success rate monitoring request triggered by a monitoring user; the transaction success rate monitoring request comprises a preset monitoring time period;

an obtaining module 802, configured to obtain at least one transaction flow log corresponding to each application system in a preset monitoring period;

a determining module 803, configured to determine a corresponding transaction state according to at least one transaction running log, and a calculating module 804, configured to calculate a technical transaction failure number, a service transaction failure number and a total number of transactions corresponding to each application system according to the at least one transaction state; the transaction state comprises one of a technology failure state, a business failure state and a transaction success state;

The calculating module 804 is further configured to calculate a technical transaction success rate and a service transaction success rate according to the technical transaction failure number, the service transaction failure number and the total number of transactions;

and the generating module 805 is configured to generate and display a transaction success rate monitoring response corresponding to each application system according to the technical transaction success rate and the business transaction success rate, so that the monitoring user monitors the transaction success rate corresponding to each application system.

In one form, the transaction flow log includes a transaction status code and a failure code;

the determining module 803 is specifically configured to, when determining the corresponding transaction status according to the at least one transaction flow log:

in response to determining that the transaction status code is a failed status code and the failed code is a technology failed code row, determining that the transaction status is a technology failed status; in response to determining that the transaction state code is a failure state code and the failure code is a business failure code row, determining that the transaction state is a technical failure state; in response to determining that the transaction status code is a success status code, determining that the transaction status is a transaction success status.

In one manner, the determining module 803 is specifically configured to, when determining that the failure code is a technology failure code line:

Responding to the beginning field in the failure code as a technical failure field, and determining the failure code as a technical failure code row;

the determining module 803 is specifically configured to, when determining that the failure code is a service failure code row:

and determining the failure code as a service failure code row in response to the beginning field in the failure code as the service failure field.

In one manner, the calculating module 804 is specifically configured to, when calculating, according to at least one transaction state, the number of technical transaction failures, the number of service transaction failures, and the total number of transactions corresponding to each application system:

calculating the number of technical failure states from at least one transaction state to obtain the technical transaction failure number; calculating the number of business failure states from at least one transaction state to obtain the business transaction failure number; the number of at least one transaction state is determined as the total number of transactions.

In one manner, the calculating module 804 is specifically configured to, when calculating the technical transaction success rate and the business transaction success rate according to the technical transaction failure number, the business transaction failure number and the total number of transactions:

calculating a first difference between the total number of transactions and the number of technical transaction failures; the first difference value is the number of successful technical transactions; calculating a second difference between the total number of transactions and the number of failed business transactions; the second difference value is the successful business transaction quantity; and calculating technical transaction success rate and business transaction success rate according to the first difference value, the second difference value and the total transaction amount.

In one manner, the calculating module 804 is specifically configured to, when calculating the technical transaction success rate and the business transaction success rate according to the first difference value, the second difference value, and the total number of transactions:

calculating a first ratio of the first difference value to the total number of transactions, and determining the first ratio as a technical transaction success rate; and calculating a second ratio of the second difference value to the total number of transactions, and determining the second ratio as the success rate of the business transactions.

In one manner, the transaction flow log further includes a failure description of the transaction, and the embodiment provides a device for monitoring a success rate of the transaction, which further includes: a storage and display module;

the acquiring module 802 is further configured to acquire, for each application system, a corresponding failure description in at least one transaction flow log;

a calculating module 804, configured to calculate the occurrence number of each failure description content based on at least one failure description;

and the storage and display module is used for storing and displaying the occurrence times of the failure description contents so as to monitor the statistics of the failure description corresponding to each application system.

Example eight

Fig. 9 is a schematic structural diagram of a monitoring platform according to an eighth embodiment. As shown in fig. 9, the monitoring platform 900 may include: a processor 901, and a memory 902 and a transceiver 903 communicatively coupled to the processor 901. Wherein the memory 902 stores computer-executable instructions; a transceiver 903 for transmitting and receiving data; the processor 901 executes computer-executable instructions stored in the memory 902 to implement any one of the method embodiments of the first to sixth embodiments, and the specific implementation manner and technical effect are similar, and are not repeated here.

In this embodiment, the transceiver 903, the memory 902, and the processor 901 are connected by a bus. The bus may be an industry standard architecture (Industry Standard Architecture, abbreviated ISA) bus, an external device interconnect (Peripheral Component Interconnect, abbreviated PCI) bus, or an extended industry standard architecture (Extended Industry Standard Architecture, abbreviated EISA) bus, among others. The buses may be divided into address buses, data buses, control buses, etc. For ease of illustration, only one thick line is shown in fig. 9, but not only one bus or one type of bus.

Example nine

The present application provides a computer readable storage medium, in which computer executable instructions are stored, where the computer executable instructions are used to implement any one of the method embodiments of the first to sixth embodiments when executed by a processor, and the specific implementation manner and technical effects are similar, and are not repeated here.

Examples ten

The present application provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, implements any one of the method embodiments from the first embodiment to the sixth embodiment, and the specific implementation manner and technical effect are similar, and are not repeated herein.

In the several embodiments provided by the present invention, it should be understood that the disclosed apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of modules is merely a logical function division, and there may be additional divisions of actual implementation, e.g., multiple modules or components may be combined or integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or modules, which may be in electrical, mechanical, or other forms.

The modules illustrated as separate components may or may not be physically separate, and components shown as modules may or may not be physical modules, i.e., may be located in one place, or may be distributed over a plurality of network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional module in each embodiment of the present invention may be integrated into one processing module, or each module may exist alone physically, or two or more modules may be integrated into one module. The integrated modules may be implemented in hardware or in hardware plus software functional modules.

Program code for carrying out methods of the present invention may be written in any combination of one or more programming languages. These program code may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable interrupt processing apparatus, such that the program code, when executed by the processor or controller, causes the functions/operations specified in the flowchart and/or block diagram block or blocks to be implemented. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.

In the context of the present invention, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

Moreover, although operations are depicted in a particular order, this should be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are included in the above discussion, these should not be construed as limiting the scope of the application. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single implementation. Conversely, various features that are described in the context of a single implementation can also be implemented in multiple implementations separately or in any suitable subcombination.

Other embodiments of the application will be apparent to those skilled in the art from consideration of the specification and practice of the application disclosed herein. This application is intended to cover any variations, uses, or adaptations of the application following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the application pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.

It is to be understood that the application is not limited to the precise arrangements and instrumentalities shown in the drawings, which have been described above, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the application is limited only by the appended claims.

Claims (10)

1. A method for monitoring success rate of transactions, wherein the method is applied to a monitoring platform, and the method comprises:

receiving a transaction success rate monitoring request triggered by a monitoring user; the transaction success rate monitoring request comprises a preset monitoring time period;

acquiring at least one transaction flow log corresponding to each application system in a preset monitoring time period;

determining a corresponding transaction state according to at least one transaction flow log, and calculating the technical transaction failure quantity, the service transaction failure quantity and the total transaction quantity corresponding to each application system according to at least one transaction state; the transaction state comprises one of a technical failure state, a business failure state and a transaction success state;

calculating technical transaction success rate and business transaction success rate according to the technical transaction failure quantity, the business transaction failure quantity and the total transaction quantity;

and generating and displaying transaction success rate monitoring response corresponding to each application system according to the technical transaction success rate and the business transaction success rate, so that a monitoring user monitors the transaction success rate corresponding to each application system.

2. The method of claim 1, wherein the transaction flow log includes a transaction status code and a failure code;

the determining the corresponding transaction state according to at least one transaction flow log includes:

in response to determining that the transaction state code is a failed state code and the failed code is a technology failed code row, determining that the transaction state is a technology failed state;

determining that the transaction state is a technical failure state in response to determining that the transaction state code is a failure state code and the failure code is a business failure code row;

in response to determining that the transaction status code is a success status code, determining that the transaction status is a transaction success status.

3. The method of claim 2, wherein the step of determining the failure code as a row of technology failure codes comprises:

determining that the failure code is a technical failure code row in response to the beginning field in the failure code being a technical failure field;

the step of determining the failure code as a service failure code row comprises the following steps:

and determining the failure code as a service failure code row in response to the beginning field in the failure code as a service failure field.

4. The method of claim 1, wherein calculating the number of technical transactions failed, the number of business transactions failed, and the total number of transactions for each application system based on at least one of the transaction states comprises:

calculating the number of technical failure states from at least one of the transaction states to obtain the technical transaction failure number;

calculating the number of business failure states from at least one of the transaction states to obtain the business transaction failure number;

a number of at least one of the transaction states is determined as a total number of transactions.

5. The method of claim 4, wherein said calculating technical transaction success rate and business transaction success rate from said technical transaction failure number, said business transaction failure number, and said total number of transactions comprises:

calculating a first difference between the total number of transactions and the number of technical transaction failures; the first difference value is the number of successful technical transactions;

calculating a second difference between the total number of transactions and the number of business transactions failed; the second difference value is the successful quantity of the business transaction;

and calculating technical transaction success rate and business transaction success rate according to the first difference value, the second difference value and the total transaction amount.

6. The method of claim 5, wherein calculating technical and business transaction success rates from the first difference, the second difference, and the total number of transactions comprises:

calculating a first ratio of the first difference value to the total number of transactions, and determining the first ratio as a technical transaction success rate;

and calculating a second ratio of the second difference value to the total number of the transactions, and determining the second ratio as a service transaction success rate.

7. The method of any of claims 1-6, further comprising a failure description of the transaction in the transaction flow log, the method comprising:

for each application system, obtaining corresponding failure description in at least one transaction flow log;

calculating the occurrence number of each failure description content based on at least one failure description;

and storing and displaying the occurrence times of the failure description contents so as to monitor the statistics of the failure descriptions corresponding to the application systems by the monitoring user.

8. A device for monitoring success rate of transactions, wherein the device is located on a monitoring platform, the device comprising:

the receiving module is used for receiving a transaction success rate monitoring request triggered by a monitoring user; the transaction success rate monitoring request comprises a preset monitoring time period;

The acquisition module is used for acquiring at least one transaction flow log corresponding to each application system in a preset monitoring time period;

the determining module is used for determining corresponding transaction states according to at least one transaction flow log, and the calculating module is used for calculating the technical transaction failure quantity, the service transaction failure quantity and the total transaction quantity corresponding to each application system according to at least one transaction state; the transaction state comprises one of a technical failure state, a business failure state and a transaction success state;

the calculation module is also used for calculating the technical transaction success rate and the service transaction success rate according to the technical transaction failure quantity, the service transaction failure quantity and the total transaction quantity;

and the generation module is used for generating and displaying transaction success rate monitoring response corresponding to each application system according to the technical transaction success rate and the business transaction success rate so as to enable the monitoring user to monitor the transaction success rate corresponding to each application system.

9. A monitoring platform, comprising: a processor, and a memory and transceiver communicatively coupled to the processor;

the memory stores computer-executable instructions; the transceiver is used for receiving and transmitting data;

The processor executes computer-executable instructions stored in the memory to implement the method of any one of claims 1-7.

10. A computer readable storage medium having stored therein computer executable instructions which when executed by a processor are adapted to carry out the method of any one of claims 1-7.