Order status flow troubleshooting method and device, electronic device, and storage medium

Abstract

The present application provides an order status flow troubleshooting method and device, electronic device, and storage medium, the method comprising: obtaining abnormal order data of an abnormal order with abnormal status flow, the abnormal order data including order type and abnormal status code; determining the target business process state code flow chain corresponding to the abnormal order according to the order type; determining the target middleware that the abnormal order depends on according to the target business process state code flow chain and the abnormal status code; obtaining the target labeling information corresponding to the target middleware; performing corresponding operations according to the service health maintenance information in the target labeling information to eliminate the obstacles that cause the abnormal status flow of the abnormal order. It can be achieved that the middleware that the corresponding service depends on can be quickly located according to the status code of the abnormal order, and the obstacles that cause the abnormal status flow of the abnormal order can be quickly eliminated based on the labeling information corresponding to the middleware that records the service health maintenance information, thereby improving the troubleshooting efficiency.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to an order status flow troubleshooting method and device, an electronic device, and a storage medium. Background Art

[0002] Middleware shields the complexity of the underlying operating system, allowing program developers to face a simple and unified development environment, reducing the complexity of program design, focusing on their own business, and no longer having to repeat work for porting programs to different system software, thereby greatly reducing the technical burden.

[0003] In the process of maintaining the underlying capability interface of the order class, the related technology has the following problems: (1) When the order status flow is abnormal, it is impossible to quickly locate the project service that causes the business process interruption based on the truncation point of the order status, delaying the troubleshooting of the problem. (2) When the service depends on the restart of the middleware node, the order status change message is blocked. If the consumer's "pseudo-death" situation is not eliminated in time, the corresponding state will be delayed and the order will be invalid. (3) The middleware resources are not replaced regularly, and the corresponding service maintenance is delayed, which reduces the effective order generation rate. Summary of the invention

[0004] In view of the above problems, the present application is proposed to provide an order status flow troubleshooting method and device, electronic device, and storage medium that overcome the above problems or at least partially solve the above problems, including:

[0005] A method for troubleshooting order status flow, the method comprising:

[0006] Acquire abnormal order data of an abnormal order with abnormal state flow, wherein the abnormal order data includes an order type and an abnormal state code of the abnormal order;

[0007] Determine the target business process state code flow chain corresponding to the abnormal order according to the order type;

[0008] Determine the target middleware that the abnormal order depends on according to the target business process status code flow chain and the abnormal status code;

[0009] Acquire target labeling information corresponding to the target middleware, wherein the target labeling information records service health maintenance information corresponding to the target middleware;

[0010] Execute corresponding operations according to the service health maintenance information to eliminate obstacles that cause abnormal status flow of the abnormal order.

[0011] Optionally, before obtaining the target labeling information corresponding to the target middleware, the method further includes:

[0012] Establish label information corresponding to each middleware based on the platform.

[0013] Optionally, the establishing of label information corresponding to each middleware based on the platform includes:

[0014] For each platform, obtain the existing order categories of the platform and the status codes corresponding to each existing order category;

[0015] Determine the business process status code flow chain corresponding to each existing order category;

[0016] Determine in sequence the middleware corresponding to two adjacent status codes in the business process status code flow chain;

[0017] The labeling information of the middleware is determined according to the business logic of the middleware and the historical service health maintenance data.

[0018] Optionally, determining the labeling information of the middleware according to the business logic of the middleware and the historical service health maintenance data further includes:

[0019] Sending a blank tagged information registration form corresponding to the middleware, wherein the blank tagged information registration form includes service health maintenance information to be filled in;

[0020] Receive return information for the blank tag information registration table, and determine the tag information corresponding to the middleware.

[0021] Optionally, the labeling information further includes a pre-state code and a post-state code of the middleware; and the method further includes:

[0022] In response to a restart or switch operation on the first middleware, obtaining first labeling information corresponding to the first middleware;

[0023] Determine, according to the pre-state code and the post-state code in the first labeled information, a first order corresponding to the pre-state code and a second order corresponding to the post-state code;

[0024] Send abnormal warning information for the first order and the second order.

[0025] Optionally, the obtaining of the existing order categories on the platform and the status codes corresponding to the existing order categories further includes:

[0026] Determine whether the status code corresponding to the existing order category meets the preset specification;

[0027] If not, the status code is added to a status code library of a preset specification.

[0028] Optionally, determining the business process status code flow chain corresponding to each existing order category includes:

[0029] Determine whether the existing order category has a corresponding business process status code flow chain;

[0030] If yes, then obtain the business process status code flow chain corresponding to the existing order category;

[0031] If not, a business process status code flow chain corresponding to the existing order category is generated according to the business process corresponding to the existing order category and the status code in the preset standard status code library.

[0032] An order status flow troubleshooting device, the device comprising:

[0033] A first acquisition module is used to acquire abnormal order data of an abnormal order with abnormal state flow, wherein the abnormal order data includes an order type and an abnormal state code of the abnormal order;

[0034] A first determination module is used to determine a target business process state code flow chain corresponding to the abnormal order according to the order type;

[0035] A second determination module is used to determine the target middleware that the abnormal order depends on according to the target business process state code flow chain and the abnormal state code;

[0036] A second acquisition module is used to acquire target labeling information corresponding to the target middleware, wherein the target labeling information records service health maintenance information corresponding to the target middleware;

[0037] The troubleshooting processing module is used to perform corresponding operations according to the service health maintenance information to eliminate the obstacles that cause the abnormal state flow of the abnormal order.

[0038] Optionally, the device further comprises:

[0039] The label information generation module is used to establish the label information corresponding to each middleware based on the platform.

[0040] Optionally, the label information generating module includes:

[0041] An existing order acquisition module is used to acquire, for each platform, the existing order categories of the platform and the status codes corresponding to each existing order category;

[0042] A circulation chain determination module is used to determine the business process status code circulation chain corresponding to each existing order category;

[0043] A middleware determination module, used to sequentially determine the middleware corresponding to two adjacent state codes in the business process state code flow chain;

[0044] The labeling information determination module is used to determine the labeling information of the middleware according to the business logic of the middleware and the historical service health maintenance data.

[0045] Optionally, the label information determination module is further used to:

[0046] Sending a blank tagged information registration form corresponding to the middleware, wherein the blank tagged information registration form includes service health maintenance information to be filled in;

[0047] Receive return information for the blank tag information registration table, and determine the tag information corresponding to the middleware.

[0048] Optionally, the labeling information further includes a pre-state code and a post-state code of the middleware; and the device further includes:

[0049] A first label information acquisition module, configured to acquire first label information corresponding to the first middleware in response to a restart or switch operation on the first middleware;

[0050] An order determination module, configured to determine, according to a pre-state code and a post-state code in the first labeled information, a first order corresponding to the pre-state code and a second order corresponding to the post-state code;

[0051] An alarm information sending module is used to send abnormal alarm information for the first order and the second order.

[0052] Optionally, the existing order acquisition module further includes:

[0053] A specification judgment module, used to judge whether the status code corresponding to the existing order category meets the preset specification;

[0054] The normalization processing module is used for adding the state code to a state code library of a preset standard if no.

[0055] Optionally, the circulation chain determination module includes:

[0056] A circulation chain determination module, used to determine whether the existing order category has a corresponding business process status code circulation chain;

[0057] A circulation chain acquisition module, used for acquiring the business process status code circulation chain corresponding to the existing order category;

[0058] The circulation chain generation module is used to generate a business process status code circulation chain corresponding to the existing order category according to the business process corresponding to the existing order category and the status code in the preset standard status code library.

[0059] An electronic device includes a processor, a memory, and a computer program stored in the memory and capable of running on the processor, wherein the computer program, when executed by the processor, implements the steps of the order status flow troubleshooting method as described above.

[0060] A computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the order status flow troubleshooting method described above are implemented.

[0061] This application has the following advantages:

[0062] In an embodiment of the present application, abnormal order data of an abnormal order with abnormal state flow is obtained, and the abnormal order data includes the order type and abnormal state code of the abnormal order; the target business process state code flow chain corresponding to the abnormal order is determined according to the order type; the target middleware that the abnormal order depends on is determined according to the target business process state code flow chain and the abnormal state code; the target labeling information corresponding to the target middleware is obtained, and the target labeling information records the service health maintenance information corresponding to the target middleware; the corresponding operation is performed according to the service health maintenance information to eliminate the obstacle that causes the abnormal state flow of the abnormal order. It can be achieved that the middleware that the corresponding service depends on can be quickly located according to the state code of the abnormal order, and the obstacle that causes the abnormal state flow of the abnormal order can be quickly eliminated based on the labeling information corresponding to the middleware that records the service health maintenance information, thereby improving the troubleshooting efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0063] In order to more clearly illustrate the technical solution of the present application, the drawings required for use in the description of the present application will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0064] Figure 1 This is a flowchart of the steps of an order status flow troubleshooting method according to an embodiment of the present application;

[0065] Figure 2 This is a schematic diagram of labeling information of a middleware in an embodiment of the present application;

[0066] Figure 3A flow chart for designing middleware labeling information in an embodiment of the present application;

[0067] Figure 4 This is a schematic diagram of an order status troubleshooting method based on middleware labeling information according to an embodiment of the present application;

[0068] Figure 5 This is a structural block diagram of an order status flow troubleshooting device according to an embodiment of the present application. DETAILED DESCRIPTION

[0069] In order to make the above-mentioned purposes, features and advantages of the present application more obvious and easy to understand, the present application is further described in detail below in conjunction with the accompanying drawings and specific implementation methods. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.

[0070] One of the main technical concepts of the embodiment of the present application is to implement order status flow abnormality troubleshooting based on the label information of the middleware, which can reduce the order status flow abnormality caused by reliance on middleware failures and reduce the online order failure rate. According to the abnormal monitoring feedback of the middleware management personnel and order troubleshooting personnel, the project service corresponding to the order problem status can be quickly located to perform health maintenance of the instance node.

[0071] Reference Figure 1 , shows a flowchart of a method for troubleshooting order status flow provided by an embodiment of the present application. In the embodiment of the present application, the method for troubleshooting order status flow may include the following steps:

[0072] Step 101, acquiring abnormal order data of an abnormal order with abnormal state flow, wherein the abnormal order data includes an order type and an abnormal state code of the abnormal order;

[0073] Step 102, determining the target business process state code flow chain corresponding to the abnormal order according to the order type;

[0074] Step 103, determining the target middleware that the abnormal order depends on according to the target business process state code flow chain and the abnormal state code;

[0075] Step 104, obtaining target labeling information corresponding to the target middleware, wherein the target labeling information records service health maintenance information corresponding to the target middleware;

[0076] Step 105, performing corresponding operations according to the service health maintenance information to eliminate the obstacles that cause the abnormal state flow of the abnormal order.

[0077] In an embodiment of the present application, abnormal order data of an abnormal order with abnormal state flow is obtained, and the abnormal order data includes the order type and abnormal state code of the abnormal order; the target business process state code flow chain corresponding to the abnormal order is determined according to the order type; the target middleware that the abnormal order depends on is determined according to the target business process state code flow chain and the abnormal state code; the target labeling information corresponding to the target middleware is obtained, and the target labeling information records the service health maintenance information corresponding to the target middleware; the corresponding operation is performed according to the service health maintenance information to eliminate the obstacle that causes the abnormal state flow of the abnormal order. It can be achieved to quickly locate the middleware that the corresponding service depends on according to the state code of the abnormal order, and based on the labeling information corresponding to the middleware that records the service health maintenance information, the obstacle that causes the abnormal state flow of the abnormal order can be quickly eliminated, thereby improving the troubleshooting efficiency.

[0078] Next, the method for troubleshooting the order status flow in this exemplary embodiment will be further described.

[0079] In step 101, abnormal order data of an abnormal order with abnormal state flow is obtained, and the abnormal order data includes the order type and abnormal state code of the abnormal order.

[0080] In this embodiment, an order with an abnormal state flow is determined as an abnormal order, and the relevant data of the abnormal order is determined as abnormal order data. The abnormal order can be determined through the feedback of the order troubleshooting personnel on the order abnormality monitoring, or it can also be determined that the order with a retention time exceeding the specified time at a certain processing node of the processing flow is an abnormal order by monitoring that the order is detained for more than a specified time. When it is determined that an abnormal order has occurred, the abnormal order data of the abnormal order is obtained. In addition to the order identifier of the abnormal order, the abnormal order data also includes the order type and abnormal status code of the abnormal order.

[0081] Taking telecommunications card services as an example, order types may include Internet card types, traffic package types, equity types, and other order types. The processing procedures for orders of different order types may be different. The status code is used to indicate the processing node where the order is located. The status code of an abnormal order is determined as an abnormal status code. It can be understood that the abnormal status code is used to indicate the processing node where the abnormal order is located when a failure occurs in the processing flow.

[0082] In step 102, the target business process state code flow chain corresponding to the abnormal order is determined according to the order type.

[0083] The processing flow of orders of different order types may be different, and in one processing flow, the status code flow is involved. Therefore, according to the processing flow of the order, the business process status code flow chain corresponding to the order can be generated, that is, the business process status code flow chain corresponding to each order type can be determined.

[0084] For example, the processing flow of order type A may include waiting for payment - paying - successful payment - system review, and the processing flow of order type B may include waiting for payment - paying - successful payment - activation. The status code corresponding to waiting for payment is S002, the status code corresponding to paying is S003, the status code corresponding to successful payment is S004, the status code corresponding to system review is S005, and the status code corresponding to activation is U001. That is, the business process status code flow chain corresponding to order type A is S002-S003-S004-S005; the business process status code flow chain corresponding to order type B is S002-S003-S004-U001.

[0085] After obtaining the order type of the abnormal order, the target business process state code flow chain corresponding to the abnormal order can be determined.

[0086] In step 103, the target middleware that the abnormal order depends on is determined according to the target business process state code flow chain and the abnormal state code.

[0087] In the business process status code flow chain, two adjacent status codes correspond to one middleware. Therefore, according to the target business process status code flow chain and the abnormal status code, the target middleware that the abnormal order depends on can be determined.

[0088] Continuing with the above example, the middleware that S002—S003 depends on is mq_001; the middleware that S003—S004 depends on is mq_002; the middleware that S004—S005 depends on is mq_003; and the middleware that S004—U001 depends on is mq_005.

[0089] For example, if the order type of the abnormal order is order type B, and the abnormal status code is S004, then according to the order type, the target business process status code flow chain can be determined to be S002-S003-S004-U001, and according to the target business process status code flow chain, the middleware corresponding to the abnormal status code can be determined to be the middleware that S004-U001 depends on, that is, the target middleware is mq_005.

[0090] In step 1004, target labeling information corresponding to the target middleware is obtained, and the target labeling information records service health maintenance information corresponding to the target middleware.

[0091] In the embodiment of the present application, each middleware is provided with corresponding label information, and the label information records the service health maintenance information corresponding to the middleware. The service health maintenance information is used for service health maintenance, and can include restart operations, contact information and other necessary troubleshooting information.

[0092] Middleware is software between the operating system and the application. When people use middleware, they often integrate a group of middleware together to form a platform (including a development platform and an operating platform); therefore, when setting corresponding label information for each middleware, the embodiment of the present application needs to establish the label information corresponding to each middleware based on the platform. That is, the standard rules for the timing information of the business line in the label information should be based on the platform, not the service item. The specific process may include:

[0093] For each platform, obtain the existing order categories of the platform and the status codes corresponding to each existing order category;

[0094] Determine the business process status code flow chain corresponding to each existing order category;

[0095] Determine in sequence the middleware corresponding to two adjacent status codes in the business process status code flow chain;

[0096] The labeling information of the middleware is determined according to the business logic of the middleware and the historical service health maintenance data.

[0097] In this embodiment, existing orders on each platform can be obtained, and existing order categories corresponding to each existing order and status codes corresponding to each existing order category, that is, status codes of each processing node of each existing order category, can be determined. Then, the business process status code flow chain corresponding to each existing order category can be determined, and the middleware corresponding to two adjacent status codes in each business process status code flow chain can be determined in turn. According to the business logic of the middleware and the historical service health maintenance data, the labeling information of the middleware can be determined.

[0098] In an optional example, determining the labeling information of the middleware according to the business logic of the middleware and the historical service health maintenance data may also include:

[0099] Sending a blank tagged information registration form corresponding to the middleware, wherein the blank tagged information registration form includes service health maintenance information to be filled in;

[0100] Receive return information for the blank tag information registration table, and determine the tag information corresponding to the middleware.

[0101] In this example, a blank tagged information registration form corresponding to the middleware can be sent to relevant personnel to guide them to fill in the items in the blank tagged information registration form to obtain tagged information and store the tagged information in a structured manner.

[0102] like Figure 2 FIG. 1 is a schematic diagram of labeling information of a middleware in an embodiment of the present application. Figure 2 As shown, the labeled information may include middleware code, platform code, service code, processing status code, pre-flow status code, platform code of the pre-flow status, post-flow status code, platform code of the post-flow status, service health maintenance operations, service maintenance contact information, and notes and other related items.

[0103] Among them, the status codes stored in the middleware's tagged information should all exist in the complete business line status flow chain, such as "Payment Success S001" - "System Review S002" - "Upload Photo S004" - "Identity Review Failed U002". When a status code flows across platforms, the tag storage structure must contain corresponding remarks. This remarks information can be considered as an extension of health maintenance operations and can be filled in by relevant personnel based on historical experience.

[0104] The above-mentioned obtaining of the existing order categories of the platform and the status codes corresponding to each existing order category also includes:

[0105] Determine whether the status code corresponding to the existing order category meets the preset specification;

[0106] If not, the status code is added to a status code library of a preset specification.

[0107] In this embodiment, after obtaining the status code corresponding to the existing order category, it is determined whether the status code is stored in the preset standard status code library. If not, it means that the status code does not meet the preset specification, then the status code is standardized and stored in the preset status code library so that a mapping relationship between the status code and the corresponding middleware can be established. The status codes corresponding to different platforms use different letters at the beginning to distinguish them.

[0108] The business process status code flow chain corresponding to each existing order category is determined above, including:

[0109] Determine whether the existing order category has a corresponding business process status code flow chain;

[0110] If yes, then obtain the business process status code flow chain corresponding to the existing order category;

[0111] If not, a business process status code flow chain corresponding to the existing order category is generated according to the business process corresponding to the existing order category and the status code in the preset standard status code library.

[0112] In this embodiment, after obtaining multiple existing order categories, it is possible to check whether there is an existing business process status code flow chain corresponding to the existing order category. If so, the business process status code flow chain corresponding to the existing order category is obtained for the subsequent generation of labeled information for the middleware; if not, the business process status code flow chain corresponding to the existing order category is generated based on the business process corresponding to the existing order category and the status code in the preset standard status code library to prevent omissions.

[0113] like Figure 3 The figure shows a flow chart of the middleware labeling information design in one embodiment of the present application. Figure 3 As shown, firstly, the existing order categories and their corresponding status codes of the existing orders are counted, and then it is determined whether the order status flow of the existing order categories is in accordance with the platform standardized coding, that is, it is determined whether the status codes involved in the existing order categories are stored in the standardized coding library. If the order status flow of the existing order categories is in accordance with the platform standardized coding, then it is determined whether the order category has a complete status code flow chain (also called the business process status code flow chain). If the order status flow of the existing order categories is not in accordance with the platform standardized coding, the status codes are standardized and stored in the warehouse; if the order category has a complete status code flow chain, then based on the status code flow chain, the dependent middleware tags involved in the order status service are designed, that is, the corresponding labeling information is designed for the dependent middleware in the complete status code flow chain; if the order category does not have a complete status code flow chain, then the status code flow chain is updated according to the business line process and the order status code inventory to obtain a complete status code flow chain, and then the corresponding labeling information is designed for the dependent middleware in the complete status code flow chain. The order status code and middleware code contained in the tagged information can generate a two-way key-value mapping relationship between the order status code and the dependent middleware. When the order status is abnormal or the middleware problem alarm occurs, the corresponding tagged information can be quickly located based on the two-way key-value mapping relationship between the order status code and the dependent middleware, so as to maintain the service based on the service health maintenance information in the tagged information. Among them, when the order status flows across platforms, the corresponding status code design rules may change. For example, the "successful order push" status code of the access platform is "S008" starting with S. When it is connected to the order processing center, it needs to be converted to another set of codes starting with U, "system review" status "U001".

[0114] In step 105, corresponding operations are performed according to the service health maintenance information to eliminate obstacles that cause abnormal status flow of the abnormal order.

[0115] In this embodiment, since the service health maintenance information is recorded in the labeled information, corresponding operations can be performed according to the service health maintenance information in the labeled information to eliminate obstacles that cause abnormal state flow of abnormal orders.

[0116] Exemplarily, when the middleware is restarted but the consumer process is not restarted, the order status flow will be abnormal; the label information corresponding to the middleware records the middleware restart operation, and optionally, the time of the middleware restart operation can be recorded. When the target label information of the target middleware corresponding to the abnormal order is obtained, according to the restart operation recorded in the label information, it can be determined that the corresponding troubleshooting method is to restart the consumer process, thereby resolving the order abnormality caused by the middleware restart.

[0117] Further, in the embodiment of the present application, the labeling information also includes the pre-state code and the post-state code of the middleware, and the method further includes:

[0118] In response to a restart or switch operation on the first middleware, obtaining first labeling information corresponding to the first middleware;

[0119] Determine, according to the pre-state code and the post-state code in the first labeled information, a first order corresponding to the pre-state code and a second order corresponding to the post-state code;

[0120] Send abnormal warning information for the first order and the second order.

[0121] In this embodiment, the first middleware is any middleware, and the labeling information corresponding to the first middleware is determined as the first labeling information. When the first middleware is restarted or switched, the first labeling information corresponding to the first middleware is obtained. Since the first middleware is restarted or switched, it may affect the orders it serves. Therefore, according to the previous state code and the next state code in the first labeling information, the first order corresponding to the previous state code and the second order corresponding to the next state code can be determined, and then abnormal alarm information for the first order and the second order is sent to troubleshooting and other related personnel to remind troubleshooting and other related personnel to perform relevant troubleshooting on the first order and the second order, thereby improving troubleshooting efficiency.

[0122] In order to facilitate the understanding of the present invention by those skilled in the art, Figure 4 Provide an exemplary explanation.

[0123] Figure 4This is a schematic diagram of an order status troubleshooting method based on middleware labeling information according to an embodiment of the present application. When the order retention status exceeds the preset time, an alarm mechanism can be triggered, that is, service health maintenance can be triggered; or, when the middleware node restarts or switches operations, an alarm mechanism can be triggered, that is, service health maintenance can be triggered; after the service health maintenance is triggered, a problem server rapid location strategy can be implemented through the state coding chain of order flow, middleware labeling registration storage (also called labeling information), and a bidirectional key-value mapping relationship between middleware coding and status coding. The embodiment of the present application can reduce the order status retention timeout caused by reliance on middleware failures and reduce the failure rate of online orders. According to the abnormal monitoring feedback of middleware managers and order troubleshooting personnel, the project service corresponding to the order problem status can be quickly located to perform health maintenance of instance nodes.

[0124] Compared with the prior art, the main advantage of the embodiments of the present application is that, when an abnormal order status problem occurs, the problem service can be quickly located, the failure rate of problem order remediation can be reduced, and the problem processing delay caused by communication between troubleshooting staff and developers can be reduced; the order status coding of different platforms can be standardized and stored in the warehouse; when the middleware resources change, the maintainability of the corresponding middleware server is enhanced, and the method of first counting and then checking the problem orders in the prior art is abandoned, thereby reducing the retention time of the abnormal order status; the use of middleware is added to business specifications, the frequency of service problems caused by dependent resources is reduced, and the resource loss caused by business services caused by middleware problems is reduced.

[0125] In an embodiment of the present application, abnormal order data of an abnormal order with abnormal state flow is obtained, and the abnormal order data includes the order type and abnormal state code of the abnormal order; the target business process state code flow chain corresponding to the abnormal order is determined according to the order type; the target middleware that the abnormal order depends on is determined according to the target business process state code flow chain and the abnormal state code; the target labeling information corresponding to the target middleware is obtained, and the target labeling information records the service health maintenance information corresponding to the target middleware; the corresponding operation is performed according to the service health maintenance information to eliminate the obstacle that causes the abnormal state flow of the abnormal order. It can be achieved to quickly locate the middleware that the corresponding service depends on according to the state code of the abnormal order, and based on the labeling information corresponding to the middleware that records the service health maintenance information, the obstacle that causes the abnormal state flow of the abnormal order can be quickly eliminated, thereby improving the troubleshooting efficiency.

[0126] It should be noted that, for the method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that the embodiments of the present application are not limited by the described order of actions, because according to the embodiments of the present application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions involved are not necessarily required by the embodiments of the present application.

[0127] Reference Figure 5 , shows a structural block diagram of an embodiment of an order status flow troubleshooting device of the present application. In the example of the present application, the device may include the following modules:

[0128] The first acquisition module 501 is used to acquire abnormal order data of an abnormal order with abnormal state flow, wherein the abnormal order data includes an order type and an abnormal state code of the abnormal order;

[0129] A first determination module 502 is used to determine a target business process state code flow chain corresponding to the abnormal order according to the order type;

[0130] A second determination module 503 is used to determine the target middleware that the abnormal order depends on according to the target business process state code flow chain and the abnormal state code;

[0131] The second acquisition module 504 is used to acquire target labeling information corresponding to the target middleware, wherein the target labeling information records service health maintenance information corresponding to the target middleware;

[0132] The troubleshooting module 505 is used to perform corresponding operations according to the service health maintenance information to eliminate the obstacles that cause the abnormal state flow of the abnormal order.

[0133] Optionally, the device further comprises:

[0134] The label information generation module is used to establish the label information corresponding to each middleware based on the platform.

[0135] Optionally, the label information generating module includes:

[0136] An existing order acquisition module is used to acquire, for each platform, the existing order categories of the platform and the status codes corresponding to each existing order category;

[0137] A circulation chain determination module is used to determine the business process status code circulation chain corresponding to each existing order category;

[0138] A middleware determination module, used to sequentially determine the middleware corresponding to two adjacent state codes in the business process state code flow chain;

[0139] The labeling information determination module is used to determine the labeling information of the middleware according to the business logic of the middleware and the historical service health maintenance data.

[0140] Optionally, the label information determination module is further used to:

[0141] Sending a blank tagged information registration form corresponding to the middleware, wherein the blank tagged information registration form includes service health maintenance information to be filled in;

[0142] Receive return information for the blank tag information registration table, and determine the tag information corresponding to the middleware.

[0143] Optionally, the labeling information further includes a pre-state code and a post-state code of the middleware; and the device further includes:

[0144] A first label information acquisition module, configured to acquire first label information corresponding to the first middleware in response to a restart or switch operation on the first middleware;

[0145] An order determination module, configured to determine, according to a pre-state code and a post-state code in the first labeled information, a first order corresponding to the pre-state code and a second order corresponding to the post-state code;

[0146] An alarm information sending module is used to send abnormal alarm information for the first order and the second order.

[0147] Optionally, the existing order acquisition module further includes:

[0148] A specification judgment module, used to judge whether the status code corresponding to the existing order category meets the preset specification;

[0149] The normalization processing module is used for adding the state code to a state code library of a preset standard if no.

[0150] Optionally, the circulation chain determination module includes:

[0151] A circulation chain determination module, used to determine whether the existing order category has a corresponding business process status code circulation chain;

[0152] A circulation chain acquisition module, used for acquiring the business process status code circulation chain corresponding to the existing order category;

[0153] The circulation chain generation module is used to generate a business process status code circulation chain corresponding to the existing order category according to the business process corresponding to the existing order category and the status code in the preset standard status code library.

[0154] As for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0155] An embodiment of the present application also discloses an electronic device, including a processor, a memory, and a computer program stored in the memory and capable of running on the processor, wherein the computer program implements the steps of the order status flow troubleshooting method as described above when executed by the processor.

[0156] An embodiment of the present application also discloses a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the order status flow troubleshooting method as described above are implemented.

[0157] The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the various embodiments can be referenced to each other.

[0158] Those skilled in the art will appreciate that the embodiments of the present application can be provided as methods, devices, or computer program products. Therefore, the present application can adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application can adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0159] The embodiments of the present application are described with reference to the flowcharts and / or block diagrams of the methods, terminal devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing terminal device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing terminal device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0160] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing terminal device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured product including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0161] These computer program instructions can also be loaded onto a computer or other programmable data processing terminal device so that a series of operating steps are executed on the computer or other programmable terminal device to produce a computer-implemented process, thereby providing instructions for implementing the process in the computer or other programmable terminal device. Figure 1 A process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0162] Although the preferred embodiments of the present application have been described, those skilled in the art may make additional changes and modifications to these embodiments once they have learned the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the embodiments of the present application.

[0163] Finally, it should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or terminal device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or terminal device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or terminal device including the elements.

[0164] The above is a detailed introduction to an order status flow troubleshooting method and device, electronic device and storage medium provided by the present application. Specific examples are used in this article to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core idea; at the same time, for general technical personnel in this field, according to the idea of ​​the present application, there will be changes in the specific implementation method and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.

Claims

1. A method for troubleshooting order status flow, characterized in that: The method comprises: Acquire abnormal order data of an abnormal order with abnormal state flow, wherein the abnormal order data includes an order type and an abnormal state code of the abnormal order; Determine the target business process state code flow chain corresponding to the abnormal order according to the order type; Determine the target middleware that the abnormal order depends on according to the target business process state code flow chain and the abnormal state code; Acquire target labeling information corresponding to the target middleware, wherein the target labeling information records service health maintenance information corresponding to the target middleware; Execute corresponding operations according to the service health maintenance information to eliminate obstacles that cause abnormal state flow of the abnormal order; Before obtaining the target labeling information corresponding to the target middleware, the method further includes: Establish label information corresponding to each middleware based on the platform; The tag information corresponding to each middleware is established based on the platform, including: For each platform, obtain the existing order categories of the platform and the status codes corresponding to each existing order category; Determine the business process status code flow chain corresponding to each existing order category; Determine in sequence the middleware corresponding to two adjacent status codes in the business process status code flow chain; The labeling information of the middleware is determined according to the business logic of the middleware and the historical service health maintenance data.

2. The method according to claim 1, characterized in that The step of determining the labeling information of the middleware according to the business logic of the middleware and the historical service health maintenance data further includes: Sending a blank tagged information registration form corresponding to the middleware, wherein the blank tagged information registration form includes service health maintenance information to be filled in; Receive return information for the blank tag information registration table, and determine the tag information corresponding to the middleware.

3. The method according to claim 2, characterized in that The labeling information also includes the pre-state code and the post-state code of the middleware; the method also includes: In response to a restart or switch operation on the first middleware, obtaining first labeling information corresponding to the first middleware; Determine, according to the pre-state code and the post-state code in the first labeled information, a first order corresponding to the pre-state code and a second order corresponding to the post-state code; Send abnormal warning information for the first order and the second order.

4. The method according to claim 1, characterized in that: The obtaining of the existing order categories on the platform and the status codes corresponding to the existing order categories further includes: Determine whether the status code corresponding to the existing order category meets the preset specification; If not, the status code is added to a status code library of a preset specification.

5. The method according to claim 4, characterized in that The step of determining the business process status code flow chain corresponding to each existing order category includes: Determine whether the existing order category has a corresponding business process status code flow chain; If yes, then obtain the business process status code flow chain corresponding to the existing order category; If not, a business process status code flow chain corresponding to the existing order category is generated according to the business process corresponding to the existing order category and the status code in the preset standard status code library.

6. An order status flow troubleshooting device, characterized in that: The device comprises: A first acquisition module is used to acquire abnormal order data of an abnormal order with abnormal state flow, wherein the abnormal order data includes an order type and an abnormal state code of the abnormal order; A first determination module is used to determine a target business process state code flow chain corresponding to the abnormal order according to the order type; A second determination module is used to determine the target middleware that the abnormal order depends on according to the target business process state code flow chain and the abnormal state code; A second acquisition module is used to acquire target labeling information corresponding to the target middleware, wherein the target labeling information records service health maintenance information corresponding to the target middleware; A troubleshooting module, used to perform corresponding operations according to the service health maintenance information to eliminate the obstacles that cause the abnormal state flow of the abnormal order; Wherein, the device further comprises: A label information generation module is used to establish label information corresponding to each middleware based on the platform; Wherein, the label information generation module includes: An existing order acquisition module is used to acquire, for each platform, the existing order categories of the platform and the status codes corresponding to each existing order category; A circulation chain determination module is used to determine the business process status code circulation chain corresponding to each existing order category; A middleware determination module, used to sequentially determine the middleware corresponding to two adjacent state codes in the business process state code flow chain; The labeling information determination module is used to determine the labeling information of the middleware according to the business logic of the middleware and the historical service health maintenance data.

7. An electronic device, characterized in that: The method comprises a processor, a memory and a computer program stored in the memory and capable of running on the processor, wherein the computer program, when executed by the processor, implements the steps of the order status flow troubleshooting method as described in any one of claims 1 to 5.

8. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the order status flow troubleshooting method as described in any one of claims 1 to 5 are implemented.

Images