Intelligent diagnosis and repair method and device for a service system

Abstract

The application belongs to the field of data processing, and provides an intelligent diagnosis and repair method and device for a business system to solve the problem of high complexity of current business system diagnosis and poor user experience. The intelligent diagnosis and repair method for the business system comprises determining milestone nodes and obtaining expected return information of each milestone node; reproducing problems of a business process, comparing the consistency of actual return information of the business process running to each milestone node with corresponding expected return information layer by layer, and finding a first problem node; finding an abnormal configuration position and its cause according to the generation logic of the expected return information of the first problem node, matching a corresponding abnormal repair strategy to perform abnormal repair; after the first problem node is repaired, the business process is continued to be run, the next problem node, the abnormal configuration position and its cause are found, and the corresponding abnormal repair strategy is matched, until all problem nodes are repaired. It can conveniently and accurately locate the root cause of the problem and improve user experience.

Description

Technical Field

[0001] This invention belongs to the field of data processing, and in particular relates to an intelligent diagnosis and repair method and apparatus for a business system. Background Technology

[0002] The statements in this section are merely background information related to the present invention and do not necessarily constitute prior art.

[0003] A business system refers to a system that automates and integrates the management of a company's core business processes through a combination of software and hardware components. Its implementation can effectively simplify business processes and improve data accuracy and decision-making efficiency. Business systems encompass various types, including ERP, CRM, and SCM, and are designed for different business scenarios. When a business system encounters issues such as error messages, process blockages, or functional errors, traditional methods require professional operations and maintenance (O&M) intervention for troubleshooting. While professional O&M personnel may be able to resolve simple problems within tens of minutes, for issues where the system message doesn't match the root cause (such as a "database error" when saving a form, which is actually due to an incorrect field type configuration), the complexity of diagnosis increases, raising the risk of business process interruptions. This not only consumes manpower and time costs but also reduces the user experience of the business system. Summary of the Invention

[0004] To address the aforementioned technical problems, this invention provides an intelligent diagnostic and repair method and apparatus for business systems, which can conveniently and accurately locate the root cause of problems and improve the user experience of business systems.

[0005] To achieve the above objectives, the present invention adopts the following technical solution:

[0006] The first aspect of the present invention provides an intelligent diagnostic and repair method for a business system.

[0007] In one or more embodiments, an intelligent diagnosis and repair method for a business system is provided, comprising:

[0008] Based on the actual business process, set the data change nodes in the business process as milestone nodes and obtain the expected return information of each milestone node;

[0009] To reproduce the problem in the business process, the first problem node was identified by comparing the actual return information with the expected return information at each milestone node of the business process.

[0010] Based on the expected return information generation logic of the first problem node, find the location and cause of the abnormal configuration, and match the corresponding abnormal repair strategy to perform abnormal repair.

[0011] Once the first problematic node is fixed, the business process continues to run. By comparing the actual returned information of each milestone node with the corresponding expected returned information, the next problematic node is identified. Then, based on the generation logic of the expected returned information of the corresponding problematic node, the location and cause of the abnormal configuration are found and the corresponding abnormal repair strategy is matched, until all problematic nodes are fixed.

[0012] As one implementation method, the process of finding the first problem node is as follows:

[0013] When the business process reaches the first milestone node, the actual return information of the first milestone node is obtained and compared with the corresponding expected return information. If the two are inconsistent, the milestone node is determined to be the first problem node; if the two are consistent, the business process continues to run and the consistency between the actual return information of the next milestone node and the corresponding expected return information is compared until the first problem node is found.

[0014] The advantage of the above technical solution is that by comparing the actual return information of each milestone node with the corresponding expected return information layer by layer, the problem node can be located layer by layer, that is, the scope of the problem, thus improving the efficiency of finding the root cause of the problem.

[0015] As one implementation method, the process of finding the location of abnormal configurations is as follows:

[0016] Based on the generation logic of the expected return information of the corresponding problem node, check whether there is any abnormality in the value of each step in the generation logic. If there is an abnormality, determine that the current position point is an abnormal configuration position.

[0017] The advantage of the above technical solution is that it can check abnormal items step by step according to the generation logic, so as to quickly and accurately locate the abnormal configuration.

[0018] As one implementation method, if the values ​​of each step in the logic for generating the expected return information of the corresponding problem node are normal during the process of finding the abnormal configuration location, then the abnormal configuration location is determined to be the business system cache.

[0019] The advantage of the above technical solution is that it can exclude various configuration items in the generation logic, accurately determine the location of abnormal configurations, and lay the foundation for further anomaly repair strategies.

[0020] As one implementation method, the causes of the anomaly include system configuration issues and user configuration issues.

[0021] The advantage of the above technical solution is that by classifying the causes of anomalies, corresponding anomaly repair strategies can be matched, thereby improving the efficiency of business system diagnosis and repair.

[0022] As one implementation method, when the cause of the anomaly is a system configuration issue, the anomaly repair strategy is to repair it according to the preset system configuration procedure.

[0023] The advantage of the above technical solution is that it can automatically repair anomalies caused by system configuration issues by using a preset system configuration program, thereby improving the repair efficiency of business systems.

[0024] As one implementation method, when the cause of the anomaly is a user configuration issue, the anomaly repair strategy is: based on the recorded location of the anomaly configuration and adjustment suggestions, the user makes the adjustment decision.

[0025] The advantage of the above technical solution is that it can repair anomalies caused by user configuration based on user decision adjustment strategies, thereby satisfying users' personalized configuration needs while ensuring the stable and normal operation of the business system.

[0026] As one implementation method, during the repair process of the corresponding problem node, the inspection record in the log is obtained, the inspection information list is fed back, and if a certain inspection passes, the inspection item information and inspection pass indicator are returned.

[0027] If a check fails, the reason for the failure and the solution will be displayed; if it can be fixed directly through the preset system configuration program, the solution will indicate that the system configuration program has been modified; if the user needs to further confirm the configuration, the solution will indicate the specific location of the abnormal configuration and modification suggestions.

[0028] The advantages of the above technical solution are that, during the process of repairing problem nodes, by recording and marking the pass status of each inspection, the problems of missed inspections and repeated inspections are avoided. Moreover, the reasons and solutions for failed inspections are given, which improves the efficiency of problem node repair.

[0029] A second aspect of the present invention provides an intelligent diagnostic and repair device for a business system.

[0030] In one or more embodiments, an intelligent diagnostic and repair device for a business system includes:

[0031] The milestone node determination module is used to set data change nodes in the business process as milestone nodes according to the actual business process and obtain the expected return information of each milestone node.

[0032] The first problem node finding module is used to reproduce problems in the business process. It finds the first problem node by comparing the consistency between the actual return information and the corresponding expected return information of the business process at each milestone node.

[0033] The exception repair matching execution module is used to find the location and cause of the exception configuration based on the expected return information of the first problem node, and match the corresponding exception repair strategy to perform exception repair.

[0034] The business process repair module is used to continue running the business process after the first problem node is repaired. It finds the next problem node by comparing the actual return information of the milestone nodes with the corresponding expected return information layer by layer. Then, according to the generation logic of the expected return information of the corresponding problem node, it finds the location and cause of the abnormal configuration and matches the corresponding abnormal repair strategy until all problem nodes are repaired.

[0035] A third aspect of the present invention provides an electronic device.

[0036] An electronic device includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the program, it implements the steps in the intelligent diagnosis and repair method of the business system described above.

[0037] Compared with the prior art, the beneficial effects of the present invention are:

[0038] This invention sets data change nodes in the business process as milestone nodes. By comparing the consistency between the actual return information and the expected return information at each milestone node in the business process layer by layer, problem nodes are found. Then, based on the generation logic of the expected return information of the problem node, the location and cause of the abnormal configuration are found, and the corresponding abnormal repair strategy is matched to repair the abnormality. This achieves accurate positioning of the root cause of the problem layer by layer, improves the efficiency of abnormal repair of the business process, reduces the risk of business process interruption, and enhances the user experience of the business system. Attached Figure Description

[0039] The accompanying drawings, which form part of this invention, are used to provide a further understanding of the invention. The illustrative embodiments of the invention and their descriptions are used to explain the invention and do not constitute an improper limitation of the invention.

[0040] Figure 1 This is a flowchart illustrating the intelligent diagnosis and repair method for a business system according to an embodiment of the present invention.

[0041] Figure 2 This is a schematic diagram of the intelligent diagnostic and repair device structure of the business system according to an embodiment of the present invention;

[0042] Figure 3 This is a schematic diagram of an electronic device according to an embodiment of the present invention;

[0043] Figure 4 This is a diagram illustrating the intelligent diagnosis and repair process of the "Open Budget Sheet" business process in an embodiment of the present invention. Detailed Implementation

[0044] The present invention will be further described below with reference to the accompanying drawings and embodiments.

[0045] It should be noted that the following detailed description is illustrative and intended to provide further explanation of the invention. Unless otherwise specified, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention pertains.

[0046] It should be noted that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the scope of exemplary embodiments according to the invention. As used herein, the singular form is intended to include the plural form as well, unless the context clearly indicates otherwise. Furthermore, it should be understood that when the terms "comprising" and / or "including" are used in this specification, they indicate the presence of features, steps, operations, devices, components, and / or combinations thereof.

[0047] Figure 1 This is a flowchart illustrating an intelligent diagnosis and repair method for a business system according to an embodiment of the present invention, such as... Figure 1 The intelligent diagnosis and repair method for the business system shown in this embodiment may include the following steps S101 to S104.

[0048] The specific implementation process of steps S101 to S104 is as follows:

[0049] Step S101: Based on the actual business process, set the data change nodes in the business process as milestone nodes and obtain the expected return information of each milestone node.

[0050] The returned information here is either a specific value or a dataset. The business process can choose the appropriate option based on the actual situation.

[0051] The following business process takes the example of a business person opening a budget table to prepare a budget. Before executing the "open budget table" operation, a key-value pair is generated in Redis with the key being the current user ID and the value being the current time point, as a marker to enable tracking for the current user. At the same time, when logging in the future, this ID will also be used as the filtering condition for the current user's logs.

[0052] Combination Figure 4 The process of "opening the budget sheet" can be divided into four parts: row information generation completed, column information generation completed, cell information generation completed, and format loading begins. Among them, cell information generation is based on the previous row and column information, and format loading is based on the complete cell information. Therefore, the current tracking of the "opening the budget sheet" business process can be divided into four milestone nodes according to this standard.

[0053] The expected return information for the four milestones of the "Open Budget Sheet" business process includes the following:

[0054] After the row information generation process is complete, the current budget table should contain at least one row of information.

[0055] Once the column information is generated, the current budget table should contain at least one column.

[0056] After the cell information is generated, the current budget table should contain at least one cell, and the cell information should include detailed row and column positions and dimension information.

[0057] When the format loads, the data received by the front end should contain at least one data entry, and the row and column information and numeric fields should be complete.

[0058] Step S102: Reproduce the problem in the business process. By comparing the actual return information of the business process at each milestone node with the corresponding expected return information, the first problem node can be identified.

[0059] In step S102, the process of finding the first problem node is as follows:

[0060] When the business process reaches the first milestone node, the actual return information of the first milestone node is obtained and compared with the corresponding expected return information. If they do not match, the milestone node is determined to be the first problem node; if they match, the business process continues to run, and the consistency between the actual return information and the corresponding expected return information of the next milestone node is compared until the first problem node is found. In this way, by comparing the actual return information of each milestone node with the corresponding expected return information layer by layer, the problem node, i.e., the scope of the problem, is located layer by layer, improving the efficiency of finding the root cause of the problem.

[0061] Step S103: Based on the generation logic of the expected return information of the first problem node, find the location and cause of the abnormal configuration, and match the corresponding abnormal repair strategy to perform abnormal repair.

[0062] In step S103, the process of finding the abnormal configuration location is as follows:

[0063] Based on the generation logic of the expected returned information for the corresponding problem node, the system verifies whether there are any anomalies in the values ​​taken at each step of the generation logic. If an anomaly is found, the current position is determined to be an abnormal configuration position. This allows for step-by-step checking of anomalies based on the generation logic, achieving the goal of quickly and accurately locating the abnormal configuration position.

[0064] Specifically, during the process of locating the abnormal configuration, if the values ​​of each step in the generation logic of the expected return information for the corresponding problem node are normal, then the abnormal configuration location is determined to be the business system cache. This allows for the elimination of various configuration items in the generation logic, accurately identifying the abnormal configuration location, and laying the foundation for further anomaly repair strategies.

[0065] In this embodiment of the invention, the causes of anomalies include system configuration issues and user configuration issues. Classifying the causes of anomalies allows for the matching of appropriate anomaly repair strategies, thereby improving the efficiency of business system diagnosis and repair.

[0066] When the cause of the anomaly is a system configuration issue, the anomaly repair strategy is to repair it according to the preset system configuration procedure. Using the preset system configuration procedure to repair anomalies caused by system configuration issues enables automatic anomaly repair, improving the efficiency of business system repair.

[0067] When the cause of the anomaly is user configuration-related, the anomaly repair strategy is as follows: based on the recorded location of the anomaly configuration and adjustment suggestions, the user makes the adjustment decision. Repairing anomalies caused by user configuration-related issues based on this user-determined adjustment strategy can satisfy users' personalized configuration needs while ensuring the stable and normal operation of the business system.

[0068] Step S104: After the first problem node is repaired, continue running the business process. By comparing the actual returned information of the milestone nodes with the corresponding expected returned information, find the next problem node. Then, according to the generation logic of the expected returned information of the corresponding problem node, find the location of the abnormal configuration and its cause, and match the corresponding abnormal repair strategy until all problem nodes are repaired.

[0069] Specifically, during the repair process of the corresponding problem node, the inspection record in the log is obtained, the inspection information list is fed back, and if a certain inspection passes, the inspection item information and inspection pass indicator are returned.

[0070] If a check fails, the reason for the failure and the solution will be displayed; if it can be fixed directly through the preset system configuration program, the solution will indicate that the system configuration program has been modified; if the user needs to further confirm the configuration, the solution will indicate the specific location of the abnormal configuration and modification suggestions.

[0071] In this way, by recording and marking the pass status of each check during the problem node repair process, the problems of missed checks and duplicate checks are avoided. Moreover, the reasons and solutions are given for the failed checks, which improves the efficiency of problem node repair.

[0072] Combination Figure 4When users reproduce the problem process, check whether the actual returned information of each milestone node is consistent with the expected returned information. For example, after the row information is generated, the returned value should contain at least one row information, but the actual returned information is empty. Since the budget table has no row information, it will cause the compiled row to be unable to be obtained after opening the table. Therefore, the milestone node is abnormal.

[0073] At this point, further analysis is conducted on the row information generation process. The row information of the budget table is generated based on four items: dimension dictionary, category data, data permissions, and dimension combination. Here, the data is checked item by item. First, it is checked whether the corresponding dimension data can be obtained according to the dictionary conditions. If the data is not obtained, the problem lies here. If the data can be obtained, the category data is further checked to see if the data can be obtained according to the category conditions. If it cannot be obtained, this is the problem.

[0074] If data can be obtained, the dictionary and category data are further combined, and the intersection is checked to see if data can be obtained. If not, there is an inconsistency between the dictionary data and the category data. If data can be obtained, the intersection is further associated with data permissions. If no data can be obtained, it means that the user's assigned permissions are inconsistent with the existing dictionary or category data. If data can be obtained, the dimensions are further combined and checked to see if data can be obtained. If no data can be obtained, it means that there is an anomaly in the configuration of the dimension combination information.

[0075] If data can be obtained after completing the above four checks, it indicates a problem with the system cache, which needs to be cleaned up. All check results are logged, and the log ID is the user's ID.

[0076] According to the log of the investigation process, return detailed result information. If the dimension dictionary data is found to be empty, it means that the editable dimension data of the current organization is empty, and the user needs to check whether dimension data has been created under the current organization. If the category data query is empty, it means that there is data in the dictionary, but the organization of the data added to the category is not the current organization or its parent organization, or the validity period of the category is not within the current time range, and the user needs to investigate and confirm. If the combination is empty, it means that the dictionary data may have been deleted in the background after being added to the category, and the user needs to confirm whether there is development synchronization data outside of the standard product. If the data is empty after associating permissions, it means that the current user has not been assigned the corresponding dimension data permissions. If the dimension combination is empty after association, it means that the dimension combination maintained by the user does not exist in the current table, and the dimension combination settings need to be further investigated. If so, it is determined that there is a problem with the system cache, and automatic cleanup and repair are performed according to the corresponding ID.

[0077] like Figure 2As shown, the intelligent diagnosis and repair device for a business system provided in this embodiment of the invention can be implemented in software. The intelligent diagnosis and repair device for a business system includes the following software modules: milestone node determination module 201, first problem node search module 202, anomaly repair matching execution module 203, and business process repair module 204.

[0078] The functions of each software module in the intelligent diagnostic and repair device of the business system are described below:

[0079] The milestone node determination module 201 is used to set data change nodes in the business process as milestone nodes according to the actual business process and obtain the expected return information of each milestone node.

[0080] The returned information here is either a specific value or a dataset. The business process can choose the appropriate option based on the actual situation.

[0081] The first problem node finding module 202 is used to reproduce problems in the business process. It finds the first problem node by comparing the consistency between the actual return information and the corresponding expected return information of the business process at each milestone node.

[0082] In the first problem node lookup module 202, the process of finding the first problem node is as follows:

[0083] When the business process reaches the first milestone node, the actual return information of the first milestone node is obtained and compared with the corresponding expected return information. If they do not match, the milestone node is determined to be the first problem node; if they match, the business process continues to run, and the consistency between the actual return information and the corresponding expected return information of the next milestone node is compared until the first problem node is found. In this way, by comparing the actual return information of each milestone node with the corresponding expected return information layer by layer, the problem node, i.e., the scope of the problem, is located layer by layer, improving the efficiency of finding the root cause of the problem.

[0084] The exception repair matching execution module 203 is used to find the location and cause of the exception configuration according to the generation logic of the expected return information of the first problem node, and match the corresponding exception repair strategy to perform exception repair.

[0085] In the exception repair matching execution module 203, the process of finding the location of the exception configuration is as follows:

[0086] Based on the generation logic of the expected returned information for the corresponding problem node, the system verifies whether there are any anomalies in the values ​​taken at each step of the generation logic. If an anomaly is found, the current position is determined to be an abnormal configuration position. This allows for step-by-step checking of anomalies based on the generation logic, achieving the goal of quickly and accurately locating the abnormal configuration position.

[0087] Specifically, during the process of locating the abnormal configuration, if the values ​​of each step in the generation logic of the expected return information for the corresponding problem node are normal, then the abnormal configuration location is determined to be the business system cache. This allows for the elimination of various configuration items in the generation logic, accurately identifying the abnormal configuration location, and laying the foundation for further anomaly repair strategies.

[0088] In this embodiment of the invention, the causes of anomalies include system configuration issues and user configuration issues. Classifying the causes of anomalies allows for the matching of appropriate anomaly repair strategies, thereby improving the efficiency of business system diagnosis and repair.

[0089] When the cause of the anomaly is a system configuration issue, the anomaly repair strategy is to repair it according to the preset system configuration procedure. Using the preset system configuration procedure to repair anomalies caused by system configuration issues enables automatic anomaly repair, improving the efficiency of business system repair.

[0090] When the cause of the anomaly is user configuration-related, the anomaly repair strategy is as follows: based on the recorded location of the anomaly configuration and adjustment suggestions, the user makes the adjustment decision. Repairing anomalies caused by user configuration-related issues based on this user-determined adjustment strategy can satisfy users' personalized configuration needs while ensuring the stable and normal operation of the business system.

[0091] The business process repair module 204 is used to continue running the business process after the first problem node is repaired. It finds the next problem node by comparing the actual return information of the milestone node with the corresponding expected return information layer by layer. Then, according to the generation logic of the expected return information of the corresponding problem node, it finds the location and cause of the abnormal configuration and matches the corresponding abnormal repair strategy until all problem nodes are repaired.

[0092] Specifically, during the repair process of the corresponding problem node, the inspection record in the log is obtained, the inspection information list is fed back, and if a certain inspection passes, the inspection item information and inspection pass indicator are returned.

[0093] If a check fails, the reason for the failure and the solution are displayed; if the problem is directly fixed using the preset system configuration program, the solution indicates that the system configuration program has been modified; if further user confirmation of the configuration is required, the solution indicates the specific location of the abnormal configuration and suggested modifications. In this way, by recording and marking the pass / fail status of each check during the problem node repair process, the problems of missed or duplicate checks are avoided, and the reasons and solutions for failed checks are provided, thus improving the efficiency of problem node repair.

[0094] This embodiment sets data change nodes in the business process as milestone nodes. By comparing the consistency between the actual return information and the corresponding expected return information at each milestone node in the business process layer by layer, problem nodes are found. Then, based on the generation logic of the expected return information of the problem node, the abnormal configuration location and its cause are found. The corresponding abnormal repair strategy is matched to repair the abnormality. This achieves accurate positioning of the root cause of the problem layer by layer, improves the efficiency of abnormal repair of the business process, reduces the risk of business process interruption, and enhances the user experience of the business system.

[0095] The structure of the electronic device according to an embodiment of the present invention will be described in detail below. Figure 3 This is a schematic diagram of the composition structure of an electronic device provided in an embodiment of the present invention. It can be understood that... Figure 3 The diagram shows only an exemplary structure of the electronic device, not the entire structure. Some or all of the structures shown may be implemented as needed.

[0096] The electronic device provided in this embodiment of the invention includes: at least one processor 301, a memory 302, a user interface 303, and at least one network interface 304. The various components in the intelligent diagnostic and repair device of the business system are coupled together via a bus system 305. It can be understood that the bus system 305 is used to realize the connection and communication between these components. In addition to a data bus, the bus system 305 also includes a power bus, a control bus, and a status signal bus. However, for clarity, in... Figure 3 The general designated all buses as Bus System 305.

[0097] The user interface 303 may include a monitor, keyboard, mouse, trackball, click wheel, buttons, touchpad, or touch screen.

[0098] It is understood that memory 302 can be volatile memory or non-volatile memory, or both. In this embodiment of the invention, memory 302 is capable of storing data to support the operation of the terminal. Examples of this data include any computer programs used to operate on the terminal, such as operating systems and applications. The operating system includes various system programs, such as framework layers, core library layers, driver layers, etc., used to implement various basic services and handle hardware-based tasks. Applications can include various applications.

[0099] In some embodiments, the intelligent diagnostic and repair device 300 for a business system provided in this invention can be implemented using a combination of hardware and software. For example, the intelligent diagnostic and repair device 300 for a business system provided in this invention can be a processor in the form of a hardware decoding processor, which is programmed to execute the intelligent diagnostic and repair method for the business system provided in this invention. For instance, the processor in the form of a hardware decoding processor can employ one or more application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field-programmable gate arrays (FPGAs), or other electronic components.

[0100] As an example, processor 301 can be an integrated circuit chip with signal processing capabilities, such as a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc., wherein the general-purpose processor can be a microprocessor or any conventional processor, etc.

[0101] As an example of the hardware implementation of the intelligent diagnosis and repair device 300 for the business system provided in this embodiment of the invention, the device provided in this embodiment of the invention can be directly executed by a processor 301 in the form of a hardware decoding processor. For example, it can be executed by one or more application specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field-programmable gate arrays (FPGAs), or other electronic components to implement the intelligent diagnosis and repair method for the business system provided in this embodiment of the invention.

[0102] The memory 302 in this embodiment of the invention is used to store various types of data to support the operation of the intelligent diagnostic and repair device of the business system, or to store data for execution. Figure 1The program code for the method shown. Examples of this data include: any executable instructions for operation on the intelligent diagnostic and repair device of the business system, such as executable instructions, and programs implementing the intelligent diagnostic and repair method of the business system according to embodiments of the present invention may be included in the executable instructions.

[0103] Specifically, according to embodiments of this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program including functions for executing... Figure 1 The program code for the method shown. In such an embodiment, the computer program can be downloaded and installed from a network via a communication component, and / or installed from a removable medium. When the computer program is executed by the central processing unit, it performs the various functions defined in the apparatus of this application.

[0104] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, as well as combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0105] The above description is merely a preferred embodiment of the present invention and is not intended to limit the invention. Various modifications and variations can be made to the present invention by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.

Claims

1. An intelligent diagnosis and repair method for a business system, characterized in that, include: Based on the actual business process, data change nodes in the business process are set as milestone nodes, and the expected return information of each milestone node is obtained; the return information is a certain value or a certain dataset. To reproduce the problem in the business process, the first problem node was identified by comparing the actual return information with the expected return information at each milestone node of the business process. Based on the expected return information generation logic of the first problem node, find the location and cause of the abnormal configuration, and match the corresponding abnormal repair strategy to perform abnormal repair. Once the first problematic node is fixed, the business process continues to run. By comparing the actual returned information of each milestone node with the corresponding expected returned information, the next problematic node is identified. Then, based on the generation logic of the expected returned information of the corresponding problematic node, the location and cause of the abnormal configuration are found and the corresponding abnormal repair strategy is matched until all problematic nodes are fixed. The causes of the anomaly can be system configuration issues or user configuration issues. When the cause of the anomaly is system configuration, the anomaly repair strategy is to repair it according to the preset system configuration procedure. When the cause of the anomaly is user configuration, the anomaly repair strategy is to allow the user to make the adjustment based on the recorded location of the anomaly and adjustment suggestions. The process of finding the abnormal configuration location is as follows: Based on the generation logic of the expected return information of the corresponding problem node, check whether there is an abnormality in the value of each step in the generation logic. If there is an abnormality, then the current location point is determined to be the abnormal configuration location. In the process of finding the abnormal configuration location, if the value of each step in the generation logic of the expected return information of the corresponding problem node is normal, then the abnormal configuration location is determined to be the business system cache. The process involves logging the investigation process and returning detailed results. For example, if the dimension dictionary data is empty, it indicates that the currently editable dimension data for the organization is empty, and the user needs to check if dimension data has been created under the current organization. If the category data query is empty, it means that data exists in the dictionary, but the organization to which the data was added in the category is not the current organization or its parent organization, or the category's validity period is outside the current time range, requiring the user to investigate and confirm. If the combination is empty, it means that the dictionary data may have been deleted in the background after being added to the category, requiring the user to confirm whether there is any development synchronization data outside of the standard product. If the data is empty after associating permissions, it means that the current user has not been assigned the corresponding dimension data permissions. If the data is empty after associating dimension combinations, it means that the dimension combination maintained by the user does not exist in the current table, requiring further investigation of the dimension combination settings. If so, it indicates a problem with the system cache, and automatic cleanup and repair are performed based on the corresponding ID. During the repair process of the corresponding problem node, the system retrieves the inspection records from the logs and provides a list of inspection information. If an inspection passes, it returns the inspection item information and a pass indicator; if an inspection fails, it displays the reason for the failure and the solution; if the repair is performed directly through the preset system configuration program, the solution indicates that the system configuration program has been modified; if further user confirmation of the configuration is required, the solution indicates the specific location of the abnormal configuration and modification suggestions.

2. The intelligent diagnosis and repair method for a business system as described in claim 1, characterized in that, The process of finding the first problem node is as follows: When the business process reaches the first milestone node, the actual return information of the first milestone node is obtained and compared with the corresponding expected return information. If the two are inconsistent, the milestone node is determined to be the first problem node; if the two are consistent, the business process continues to run and the consistency between the actual return information of the next milestone node and the corresponding expected return information is compared until the first problem node is found.

3. An intelligent diagnostic and repair device for a business system, characterized in that, The intelligent diagnosis and repair method for the business system as described in any one of claims 1-2 is adopted, comprising: The milestone node determination module is used to set data change nodes in the business process as milestone nodes according to the actual business process and obtain the expected return information of each milestone node. The first problem node finding module is used to reproduce problems in the business process. It finds the first problem node by comparing the consistency between the actual return information and the corresponding expected return information of the business process at each milestone node. The exception repair matching execution module is used to find the location and cause of the exception configuration based on the expected return information of the first problem node, and match the corresponding exception repair strategy to perform exception repair. The business process repair module is used to continue running the business process after the first problem node is repaired. It finds the next problem node by comparing the actual return information of the milestone nodes with the corresponding expected return information layer by layer. Then, according to the generation logic of the expected return information of the corresponding problem node, it finds the location and cause of the abnormal configuration and matches the corresponding abnormal repair strategy until all problem nodes are repaired.

4. An electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the steps in the intelligent diagnosis and repair method for the business system as described in any one of claims 1-2.

Images