Business system monitoring method and device and computer equipment

Abstract

The invention relates to the technical field of system testing, and particularly discloses a service system monitoring method and device and computer equipment, and the method comprises the steps: determining a service link in a tested service system, and obtaining a service interface in the service link according to the calling sequence of the service link; configuring an assertion rule corresponding to the service interface according to the service link; executing the service link, and writing a return result of a service interface in the service link into a test log corresponding to the service link; and analyzing the test log according to the assertion rule, and determining error reporting information of the service system. According to the method and the device, the service link can be completely monitored according to the service logic, the error report information of each subsystem node in the service system can be efficiently and accurately determined, and the test efficiency is greatly improved while the service logic relevance is ensured.

Description

Technical Field

[0001] The present disclosure relates to the technical field of system testing, and in particular to a monitoring method, device and computer equipment for a business system. Background Art

[0002] With the development of artificial intelligence and digitalization of business processes, business systems tend to be more complex. Business systems can include multiple subsystems, and business links are long, often involving multiple subsystems. For example, banking systems include peripheral channel systems, product systems, core banking systems, gateway systems, etc. Transaction business is often initiated from the peripheral channel system, and needs to go through a series of product systems and then to the core banking system. Therefore, the complexity of business systems also puts higher requirements on development quality. When the business system completes the development of the functional stage, a large number of test cases need to be executed in the test environment.

[0003] In related technologies, the monitoring of business systems often depends on the generation of transaction business, and is performed through logs generated by transactions, which have a low correlation with business logic. In addition, if a problem occurs in a system in the business chain, the test case is difficult to execute, which greatly reduces the efficiency of the test. Summary of the invention

[0004] Based on this, it is necessary to provide a monitoring method, device, computer equipment, storage medium and computer program product for a business system in response to the above technical problems.

[0005] In a first aspect, the present disclosure provides a method for monitoring a business system. The method comprises:

[0006] Determine the service link in the tested service system, and obtain the service interface in the service link according to the calling sequence of the service link;

[0007] Configure the assertion rule corresponding to the service interface according to the service link;

[0008] Execute the service link, and write the return result of the service interface in the service link into the test log corresponding to the service link;

[0009] The test log is parsed according to the assertion rule to determine the error information of the business system.

[0010] In one embodiment, executing the service link includes:

[0011] Initiating a service test in batches, the service test is used to execute the service link;

[0012] Generate a serial number for the business test, where the serial number is used to generate a test log corresponding to the business test.

[0013] In one embodiment, parsing the test log according to the assertion rule to determine the error information of the business system includes:

[0014] Obtaining a return result of the service interface in the test log, wherein the return result includes a digital code; the digital code includes a success code and an error code;

[0015] Performing assertion analysis on the digital code returned by the service interface according to the calling sequence of the service link;

[0016] The error information of the node in the service link is determined according to the assertion analysis result of the service interface.

[0017] In one embodiment, performing assertion analysis on the digital code returned by the service interface according to the calling order of the service link includes:

[0018] In the case where there is at least one digital code as an error code in the test log, the error code is matched with a first assertion rule; the first assertion rule is an assertion rule corresponding to the first-order service interface in the calling sequence of the service link;

[0019] When the error code successfully matches the first assertion rule, determining error information of the node corresponding to the service interface of the first priority;

[0020] If the error code fails to match the first assertion rule, the error code is matched with a second assertion rule; the second assertion rule is an assertion rule corresponding to the second-ranked service interface in the calling sequence of the service link;

[0021] When the error code successfully matches the second assertion rule, error information of the node corresponding to the service interface of the second priority is determined.

[0022] In one embodiment, the method further comprises:

[0023] The smooth rate of the service link and the smooth rate of the nodes in the service link are determined to obtain a monitoring report of the service system.

[0024] In one embodiment, before executing the service link, the method further includes:

[0025] The property file of the business system is read, where the property file at least includes database information and a storage path of the test log.

[0026] In a second aspect, the present disclosure further provides a monitoring device for a business system. The device comprises:

[0027] A service link module is used to determine the service link in the tested service system and obtain the service interface in the service link according to the calling sequence of the service link;

[0028] An assertion rule module, used to configure an assertion rule corresponding to the service interface according to the service link;

[0029] A test execution module, used to execute the service link and write the return result of the service interface in the service link into the test log corresponding to the service link;

[0030] The test log module is used to parse the test log according to the assertion rule to determine the error information of the business system.

[0031] In one embodiment, the test execution module includes:

[0032] An execution unit, used for initiating a service test in batches, wherein the service test is used for executing the service link;

[0033] The serial unit is used to generate a serial number for the business test, and the serial number is used to generate a test log corresponding to the business test.

[0034] In one embodiment, the test log module includes:

[0035] A digital coding unit, used to obtain the return result of the service interface in the test log, wherein the return result includes a digital code; the digital code includes a success code and an error code;

[0036] An assertion analysis unit, used to perform assertion analysis on the digital code returned by the service interface according to the calling order of the service link;

[0037] An error reporting unit is used to determine error reporting information of a node in the service link according to an assertion analysis result of the service interface.

[0038] In one embodiment, the assertion analysis unit includes:

[0039] A first priority subunit is used to match the error code with a first assertion rule when at least one digital code is an error code in the test log; the first assertion rule is an assertion rule corresponding to the first priority service interface in the calling sequence of the service link;

[0040] A node corresponding subunit, used for determining the error information of the node corresponding to the service interface of the first priority when the error code successfully matches the first assertion rule;

[0041] A second priority subunit is used to match the error code with a second assertion rule when the error code fails to match the first assertion rule; the second assertion rule is an assertion rule corresponding to the second priority service interface in the calling sequence of the service link;

[0042] The node corresponding subunit is further configured to determine error information of a node corresponding to the service interface of the second priority when the error code successfully matches the second assertion rule.

[0043] In one embodiment, the device further comprises:

[0044] The monitoring report module is used to determine the smooth rate of the service link and the smooth rate of the nodes in the service link to obtain a monitoring report of the service system.

[0045] In one embodiment, the device further comprises:

[0046] The business system attribute module is used to read the attribute file of the business system, and the attribute file at least includes database information and the storage path of the test log.

[0047] In a third aspect, the present disclosure further provides a computer device, wherein the computer device comprises a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the steps of the monitoring method of the business system are implemented.

[0048] In a fourth aspect, the present disclosure further provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the steps of the above-mentioned monitoring method of the business system are implemented.

[0049] In a fifth aspect, the present disclosure further provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, the steps of the monitoring method of the business system are implemented.

[0050] The above-mentioned monitoring method, device, computer equipment, storage medium and computer program product of the business system have at least the following beneficial effects:

[0051] The present invention obtains the business link in the business system through business logic, executes the business link from the starting end of the business link, writes the return results of each business interface in the business link into the test log, and then parses the test log according to the assertion rule to obtain the error information of the business system. The complete monitoring of the business link can be achieved according to the business logic, and the error information of each subsystem node in the business system can be determined efficiently and accurately, which greatly improves the efficiency of the test while ensuring the relevance of the business logic. BRIEF DESCRIPTION OF THE DRAWINGS

[0052] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure or the conventional technology, the drawings required for use in the embodiments or the conventional technology descriptions will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present disclosure, and for ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0053] Figure 1 An application environment diagram of a method for monitoring a business system in an embodiment;

[0054] Figure 2 A flowchart of a method for monitoring a business system in one embodiment;

[0055] Figure 3 A schematic diagram of a flow chart of executing steps of a service link in an embodiment;

[0056] Figure 4 A schematic diagram of a flow chart of a step of determining error information of a business system in one embodiment;

[0057] Figure 5 A schematic diagram of a flow chart of an assertion analysis step in an embodiment;

[0058] Figure 6 A schematic diagram of a flow chart of an error code matching process in an embodiment;

[0059] Figure 7 is a structural block diagram of a monitoring device for a business system in an embodiment;

[0060] Figure 8 A structural block diagram of a test execution module in one embodiment;

[0061] Fig. 9 A structural block diagram of a test log module in an embodiment;

[0062] Fig.10 is a structural block diagram of an assertion analysis unit in one embodiment;

[0063] Fig.11 FIG. 4 is a block diagram of the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0064] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0065] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by those skilled in the art to which the present disclosure belongs. The terms used herein in the specification of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.

[0066] It should be noted that the terms "first", "second", etc. in the specification and claims of the present disclosure and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present disclosure described here can be implemented in an order other than those illustrated or described here. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present disclosure. On the contrary, they are only examples of devices and methods consistent with some aspects of the present disclosure as detailed in the attached claims. The terms "include", "comprise" or any other variant thereof are intended to cover non-exclusive inclusion, so that the process, method, product or device including a series of elements includes not only those elements, but also other elements that are not explicitly listed, or also includes elements inherent to such process, method, product or device. In the absence of more restrictions, it is not excluded that there are other identical or equivalent elements in the process, method, product or device including the elements. For example, if the words first, second, etc. are used to represent the name, they do not represent any specific order.

[0067] When used herein, the singular forms "a", "an", and "said / the" may also include plural forms, unless the context clearly indicates otherwise. It should also be understood that the terms "include / comprise" or "have" and the like specify the presence of stated features, wholes, steps, operations, components, parts, or combinations thereof, but do not exclude the possibility of the presence or addition of one or more other features, wholes, steps, operations, components, parts, or combinations thereof. At the same time, in this specification, the term "and / or" includes any and all combinations of the relevant listed items.

[0068] The monitoring method of the business system provided by the embodiment of the present disclosure can be applied to Figure 1In the application environment shown. Among them, the terminal 102 communicates with the server 104 through the network. The data storage system can store the data that the server 104 needs to process. The data storage system can be integrated on the server 104, or it can be placed on the cloud or other network servers. The server 104 can be implemented with an independent server or a server cluster composed of multiple servers. A business system is deployed on the server 104, and the business system can include several subsystem nodes. The business logic on the business system can form a business link on several subsystem nodes by calling an interface. For example, the business system includes three nodes, system A, system B, and system C, and a certain business link is "A->B->C". After the development and deployment of the business system, it is often necessary to test it in a test environment. The server can send a request to the starting end of the business link, that is, system A, through an automated script execution tool, and can also receive a return from system A. System A can send a request to system B and receive a return, and system B can send a request to system C and receive a return. The server 104 can also collect the test logs generated by each subsystem node of the business system through a log collection tool, and parse the test logs through a log analysis tool, and can send the parsing results to the terminal 102 for visual display. The terminal 102 may be, but is not limited to, various personal computers, laptop computers, smart phones, tablet computers, etc.

[0069] In some embodiments of the present disclosure, Figure 2 As shown, a monitoring method for a business system is provided, and the method is applied to Figure 1 The server in the example is used to illustrate the following steps:

[0070] Step 210: determine the service links in the tested service system, and obtain the service interfaces in the service links according to the calling sequence of the service links.

[0071] For example, the server can sort out the services provided by the business system and generate business links in the business system. Business links can include transactional services and non-transactional services. The calling order of business links can be the order of subsystem nodes that the business request needs to pass through according to the business logic, for example Figure 1 The business link "A->B->C" in the example. The business link can call the subsystem node through the business interface. The server can obtain each business interface in the business link according to the calling sequence of the business link, and there is a corresponding relationship between the business interface and the subsystem node.

[0072] Step 220: configure an assertion rule corresponding to the service interface according to the service link.

[0073] Exemplarily, after obtaining the business interface of the business link, the server configures assertion rules for each business interface. Assertions can generally refer to a first-order logic in a program (such as a logical judgment formula with a true or false result), the purpose of which is to express the expected result of the business system developer. The server sets an assertion at each business interface. When the program executes to the assertion position, the corresponding assertion is true, which means that the business interface returns successfully. If the assertion is not true, it means that the business interface returns a failure, and an error message is given according to the assertion rule.

[0074] Step 230: execute the service link, and write the return result of the service interface in the service link into the test log corresponding to the service link.

[0075] For example, the server can execute the service link from the starting end of the service link according to a pre-written automation script, obtain the return results of each service interface in the service link, and write the return results into the test log corresponding to the service link, and each service link corresponds to a test log in one execution. The return results at least include the assertion results at the service interface.

[0076] Step 240: parse the test log according to the assertion rule to determine the error information of the business system.

[0077] Exemplarily, after the server aggregates the return results of each service interface in the service link into the test log, the test log can be parsed, for example, the error information of each subsystem node in the service system can be counted. The error information is obtained according to the assertion result returned by the service interface, which can be directly a result of the assertion result being false, or can be triggered by the result of the assertion result being false.

[0078] In the above-mentioned business system monitoring method, the business link in the business system is obtained through the business logic, and the business link is executed from the starting end of the business link, and the return results of each business interface in the business link are written into the test log, and then the test log is parsed according to the assertion rule to obtain the error information of the business system. The complete monitoring of the business link can be achieved according to the business logic, and the error information of each subsystem node in the business system can be determined efficiently and accurately, which greatly improves the efficiency of the test while ensuring the relevance of the business logic.

[0079] In some embodiments of the present disclosure, Figure 3 As shown, step 230 includes:

[0080] Step 232: initiate a batch service test, where the service test is used to execute the service link.

[0081] Exemplarily, the server can initiate business tests in batches so that business links are executed in batches. For example, the server can implement batch initiation of business tests through continuous integration tools, that is, multiple business links can be tested at the same time, thereby improving test efficiency. Among them, continuous integration generally refers to the practice of software development, through automated construction, compilation, testing and deployment, verification and discovery of problems. The continuous integration tool may include jenkins (jenkins is an open source software project, a continuous integration tool developed based on Java, used to monitor continuous and repeated work, and aims to provide an open and easy-to-use software platform so that software projects can be continuously integrated), jenkins has the support of more plug-in packages, and jenkins can call up the automated interface test script through the jmeter plug-in (interface automated test plug-in), and initiate business tests from the business link initiator. In some embodiments, the server can also execute the written automated interface test script once every period of time through a timer, parse the execution result, obtain the return result therein, and monitor whether the business link is unblocked.

[0082] Step 234, generating a serial number for the business test, wherein the serial number is used to generate a test log corresponding to the business test.

[0083] Exemplarily, the server may generate a serial number for the service test, so that the test process of each service link corresponds to a unique serial number, and generate a test log corresponding to the service link according to the serial number.

[0084] This embodiment greatly improves the efficiency of service testing by initiating service testing in batches, and facilitates tracking of the test process through serial numbers.

[0085] In some embodiments of the present disclosure, Figure 4 As shown, step 240 includes:

[0086] Step 242, obtaining the return result of the business interface in the test log, wherein the return result includes a digital code; the digital code includes a success code and an error code.

[0087] Exemplarily, the server can read the return results of each business interface in the test log, and the return results can be in digital coding form or in other coding forms. Among them, the digital code includes a success code and an error code, and the coding rules of the digital code can be set according to the assertion rules corresponding to the business interface. The success code can be uniformly set to the same format, and the error code can include the subsystem node information corresponding to the business interface.

[0088] Step 244: perform assertion analysis on the digital code returned by the service interface according to the calling sequence of the service link.

[0089] For example, the server analyzes the digital codes returned by the service interface from the test log according to the calling order of the service link. The calling order of the service link usually refers to the calling order of each subsystem node in the service link, that is, the return results of the service interface are analyzed in sequence according to the calling order. Figure 1 In the business link "A->B->C", the server first asserts the digital code returned by the business interface of system A, and then asserts the digital code returned by system B and system C.

[0090] Step 246: Determine error information of the node in the service link according to the assertion analysis result of the service interface.

[0091] The assertion analysis result may refer to an analysis result based on the return result of the business interface and the assertion rule corresponding to the business interface, which is used to characterize the assertion rule corresponding to the returned digital code.

[0092] Exemplarily, the server may match the digital code returned by the business interface with the business interface according to the assertion analysis result of the business interface, and then with the subsystem node, and may obtain error information of each subsystem node.

[0093] This embodiment can quickly distinguish between successful and failed returns of a service interface through digital coding, and locate error information of nodes in a service link through assertion analysis results in a test log, thereby accurately and efficiently implementing monitoring of a service system.

[0094] In some embodiments of the present disclosure, Figure 5 As shown, step 244 includes:

[0095] Step 2442, when there is at least one digital code as an error code in the test log, match the error code with a first assertion rule; the first assertion rule is the assertion rule corresponding to the first-order business interface in the calling sequence of the business link.

[0096] The digital code may be a multi-digit number, and the first few digits (eg, the first two digits) may be configured to uniquely identify the subsystem node, and the remaining digits may be configured to represent information such as the error type and error field.

[0097] Exemplarily, when the server reads the test log and determines that there is at least one error code in the test log, each error code is matched with the business interface. For example, all digits of the digitally encoded success code can be set to 0, so that the server can quickly extract the error code from the test log. The server matches the error code with the first assertion rule, and the first assertion rule is the assertion rule corresponding to the first-ranked business interface in the calling sequence of the business link. For example, the server can compare the subsystem node corresponding to the first few digits of the error code with the subsystem node to which the business node corresponding to the first assertion rule belongs to determine whether they are the same, and if they are the same, the match is successful. The composition format of the error code can also be matched with the first assertion rule to determine whether the composition format of the error code complies with the first assertion rule, and if it does, the match is successful. The composition format may include the number of digits of the error code, the numbers involved, etc.

[0098] Step 2444: when the error code successfully matches the first assertion rule, determine the error information of the node corresponding to the service interface of the first priority.

[0099] For example, when the server determines that the error code successfully matches the first assertion rule, it can determine that the error code is returned by the business interface corresponding to the first assertion rule, and can determine the subsystem node corresponding to the error code, thereby determining the error information of the node corresponding to the first-order business interface. At this point, the server does not need to continue matching the error code.

[0100] Step 2446, when the error code fails to match the first assertion rule, match the error code with a second assertion rule; the second assertion rule is the assertion rule corresponding to the second-ranked business interface in the calling sequence of the business link.

[0101] Exemplarily, when the server determines that the error code fails to match the first assertion rule, it can be determined that the error code is not returned by the business interface corresponding to the first assertion rule. The server can match the error code with the second assertion rule, which is the assertion rule corresponding to the second-ranked business interface in the calling order of the business link.

[0102] Step 2448: When the error code successfully matches the second assertion rule, determine the error information of the node corresponding to the second-ranked business interface.

[0103] For example, when the server determines that the error code successfully matches the second assertion rule, it can determine that the error code is returned by the business interface corresponding to the second assertion rule, and can determine the subsystem node corresponding to the error code, thereby determining the error information of the node corresponding to the second-ranked business interface. At this point, the server does not need to continue matching the error code.

[0104] Similarly, when the server determines that the error code fails to match the second assertion rule, it can determine that the error code is not returned by the business interface corresponding to the second assertion rule. The server can match the error code with the third assertion rule, which is the assertion rule corresponding to the second-ranked business interface in the calling order of the business link, and so on, until the error code matches the assertion rule successfully, or until the error code matches the assertion rule corresponding to the last-ranked business interface in the business link.

[0105] For example Figure 1 A service link in the example is "A->B->C". The matching process of the server is as follows: Figure 6 As shown. The server reads the test log of a business link and extracts the error code from it. First, use the assertion rules and error code of system A to match. If the match is successful, it can be determined that the source subsystem node of the error code is system A, and stop matching the error code. If the match is unsuccessful, match the assertion rules and error code of system B according to the calling order of the business link. If the match is successful, it can be determined that the source subsystem node of the error code is system B, and stop matching the error code. If the match is unsuccessful, match the assertion rules and error code of system C according to the calling order of the business link. If the match is successful, it can be determined that the source subsystem node of the error code is system C, and stop matching the error code.

[0106] This embodiment can quickly locate the source subsystem node of the error code by matching the error code with the assertion rules of each business interface in the calling order, so as to obtain the error information of the node corresponding to each business interface in the business system, thereby improving the monitoring stability of the business system and reducing omissions.

[0107] In some embodiments of the present disclosure, the method further includes:

[0108] Step 250, determine the smooth rate of the service link and the smooth rate of the nodes in the service link, and obtain a monitoring report of the service system.

[0109] Exemplarily, after determining the error information of the nodes corresponding to each business interface in the business system, the server can calculate the smooth rate of each node in the business link according to the error information of each node, and generate a monitoring report. For example, the server can calculate the smooth rate of the entire business link, that is, the number of smooth business links in a period of time; it can also calculate the smooth rate of each node, that is, the number of smooth nodes in a period of time. The server can generate a monitoring report for the business system based on the error information of the node and information such as the smooth rate, and the server can visualize the monitoring report through the terminal. The server can also calculate information such as the response time of each node, and write information such as the response time of each node into the monitoring report.

[0110] This embodiment can calculate the smooth rate of each node in the business link through the error information of the nodes in the business system, and generate a monitoring report based on the error information and smooth rate of each node, so that the monitoring report collects the monitoring information of the business system, improves the monitoring efficiency of the business system, and the monitoring report is easy to be visualized through the terminal.

[0111] In some embodiments of the present disclosure, before step 230, the following steps are further included:

[0112] The property file of the business system is read, where the property file at least includes database information and a storage path of the test log.

[0113] Exemplarily, before executing the business link, the server can also determine the database information of the business system and the storage path of the test log by reading the property file of the business system. The business system has its own property file, which at least includes the database information of the business system, and the database information may include the data storage path generated by the business system during the execution of the business test. The property file also includes the storage path of the test log. The property file may also include information such as the printing format of the test log.

[0114] This embodiment can also determine the database information of the business system and the storage path of the test log by reading the property file of the business system before executing the business link, so as to quickly obtain the return result of the business interface and the storage path of the test log.

[0115] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0116] Based on the same inventive concept, the embodiment of the present disclosure also provides a monitoring device for a business system for implementing the monitoring method for the business system involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in the embodiments of the monitoring device for one or more business systems provided below can refer to the limitations of the monitoring method for the business system above, and will not be repeated here.

[0117] In some embodiments of the present disclosure, Figure 7 As shown, a monitoring device for a business system is provided. The device 700 includes:

[0118] The service link module 710 is used to determine the service link in the tested service system, and obtain the service interface in the service link according to the calling sequence of the service link;

[0119] An assertion rule module 720, configured to configure an assertion rule corresponding to the service interface according to the service link;

[0120] A test execution module 730 is used to execute the service link and write the return result of the service interface in the service link into the test log corresponding to the service link;

[0121] The test log module 740 is used to parse the test log according to the assertion rule to determine the error information of the business system.

[0122] In some embodiments of the present disclosure, Figure 8 As shown, the test execution module 730 includes:

[0123] An execution unit 732 is used to initiate a service test in batches, where the service test is used to execute the service link;

[0124] The serial unit 734 is used to generate a serial number for the business test, and the serial number is used to generate a test log corresponding to the business test.

[0125] In some embodiments of the present disclosure, Fig. 9 As shown, the test log module 740 includes:

[0126] A digital coding unit 742 is used to obtain the return result of the service interface in the test log, wherein the return result includes a digital code; the digital code includes a success code and an error code;

[0127] An assertion analysis unit 744, configured to perform assertion analysis on the digital code returned by the service interface according to the calling sequence of the service link;

[0128] The error reporting unit 746 is used to determine the error reporting information of the node in the service link according to the assertion analysis result of the service interface.

[0129] In some embodiments of the present disclosure, Fig.10 As shown, the assertion analysis unit 744 includes:

[0130] The first priority subunit 7442 is used to match the error code with a first assertion rule when there is at least one digital code as an error code in the test log; the first assertion rule is an assertion rule corresponding to the first priority service interface in the calling sequence of the service link;

[0131] The node corresponding subunit 7444 is used to determine the error information of the node corresponding to the service interface of the first priority when the error code successfully matches the first assertion rule;

[0132] A second priority subunit 7446 is used to match the error code with a second assertion rule when the error code fails to match the first assertion rule; the second assertion rule is an assertion rule corresponding to the second priority service interface in the calling sequence of the service link;

[0133] The node corresponding subunit 7444 is further used to determine the error information of the node corresponding to the second-order service interface when the error code successfully matches the second assertion rule.

[0134] In one embodiment, the device further comprises:

[0135] The monitoring report module is used to determine the smooth rate of the service link and the smooth rate of the nodes in the service link to obtain a monitoring report of the service system.

[0136] In one embodiment, the device further comprises:

[0137] The business system attribute module is used to read the attribute file of the business system, and the attribute file at least includes database information and the storage path of the test log.

[0138] Each module in the monitoring device of the above-mentioned business system can be implemented in whole or in part by software, hardware and a combination thereof. Each of the above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory in the computer device in the form of software, so that the processor can call and execute the operations corresponding to each of the above modules. It should be noted that the division of modules in the embodiments of the present disclosure is schematic and is only a logical function division. There may be other division methods in actual implementation.

[0139] Based on the above-mentioned description of the embodiment of the monitoring method of the business system, in another embodiment provided by the present disclosure, a computer device is provided, which may be a server, and its internal structure diagram may be as follows: Fig.11 As shown. The computer device includes a processor, a memory, an input / output interface (Input / Output, referred to as I / O) and a communication interface. Among them, the processor, the memory and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store data. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a monitoring method of a business system is implemented.

[0140] Those skilled in the art will understand that Fig.11 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0141] Based on the description of the embodiment of the monitoring method of the aforementioned business system, in another embodiment provided in the present disclosure, a computer-readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.

[0142] Based on the description of the embodiment of the monitoring method of the aforementioned business system, in another embodiment provided in the present disclosure, a computer program product is provided, including a computer program, which implements the steps in the above-mentioned method embodiments when executed by a processor.

[0143] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant laws, regulations and standards of relevant countries and regions.

[0144] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, etc., but are not limited to this.

[0145] In the description of this specification, the description with reference to the terms "some embodiments", "other embodiments", "ideal embodiments", etc. means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present invention. In this specification, the schematic descriptions of the above terms do not necessarily refer to the same embodiment or example.

[0146] It is understandable that the various embodiments of the above method in this specification are described in a progressive manner, and the same / similar parts between the various embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. For related parts, refer to the description of other method embodiments.

[0147] The technical features of the above-mentioned embodiments can be combined arbitrarily. In order to make the description concise, not all possible combinations of the technical features of the above-mentioned embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0148] The above-described embodiments only express several implementation methods of the present disclosure, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the patent application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present disclosure, and these all belong to the protection scope of the present disclosure. Therefore, the protection scope of the patent of the present disclosure shall be subject to the attached claims.

Claims

1. A method for monitoring a business system, characterized in that: The method comprises: Determine the service link in the tested service system, and obtain the service interface in the service link according to the calling sequence of the service link; Configure the assertion rule corresponding to the service interface according to the service link; Execute the service link, and write the return result of the service interface in the service link into the test log corresponding to the service link; The test log is parsed according to the assertion rule to determine the error information of the business system.

2. The method according to claim 1, characterized in that The executing the service link comprises: Initiating a service test in batches, the service test is used to execute the service link; Generate a serial number for the business test, where the serial number is used to generate a test log corresponding to the business test.

3. The method according to claim 1, characterized in that The parsing of the test log according to the assertion rule to determine the error information of the business system includes: Obtaining the return result of the service interface in the test log, wherein the return result includes a digital code; the digital code includes a success code and an error code; Performing assertion analysis on the digital code returned by the service interface according to the calling sequence of the service link; The error information of the node in the service link is determined according to the assertion analysis result of the service interface.

4. The method according to claim 3, characterized in that: The assertion analysis of the digital code returned by the service interface according to the calling sequence of the service link includes: In the case where there is at least one digital code as an error code in the test log, the error code is matched with a first assertion rule; the first assertion rule is an assertion rule corresponding to the first-order service interface in the calling sequence of the service link; When the error code successfully matches the first assertion rule, determining error information of the node corresponding to the service interface of the first priority; If the error code fails to match the first assertion rule, the error code is matched with a second assertion rule; the second assertion rule is an assertion rule corresponding to the second-ranked service interface in the calling sequence of the service link; When the error code successfully matches the second assertion rule, error information of the node corresponding to the service interface of the second priority is determined.

5. The method according to claim 3, characterized in that: The method further comprises: The smooth rate of the service link and the smooth rate of the nodes in the service link are determined to obtain a monitoring report of the service system.

6. The method according to claim 1, characterized in that Before executing the service link, the method further includes: The property file of the business system is read, where the property file at least includes database information and a storage path of the test log.

7. A monitoring device for a business system, characterized in that: The device comprises: A service link module is used to determine the service link in the tested service system and obtain the service interface in the service link according to the calling sequence of the service link; An assertion rule module, used to configure an assertion rule corresponding to the service interface according to the service link; A test execution module, used to execute the service link and write the return result of the service interface in the service link into the test log corresponding to the service link; The test log module is used to parse the test log according to the assertion rule to determine the error information of the business system.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images