Application system fault analysis method and device, equipment and storage medium

Abstract

The invention discloses an application system fault analysis method, belongs to the field of automation, and is used for accurately analyzing faults of an application system in real time. The method comprises the following steps: connecting a plurality of application systems based on a preset first connection specification, wherein the first connection specification is a preset connection specification of the application systems; obtaining first fault information of a first system, wherein the first fault information is related information of the first system with a fault in the plurality of application systems; determining a first analysis interface for carrying out fault analysis on the first system based on the first fault information and a preset database rule table, wherein the database rule table comprises the first analysis interface for carrying out fault analysis on a plurality of application systems; and performing fault analysis on the first fault information based on the first analysis interface for performing fault analysis on the first system to obtain a fault analysis result of the first system.

Description

Technical Field

[0001] The present application belongs to the field of automation, and specifically relates to an application system fault analysis method, device, equipment and storage medium. Background Art

[0002] In the operation and maintenance of application systems, the stability of the application system itself will be affected by various factors such as abnormal basic environment of the system, slow peripheral interfaces, system logic and external system failures. Although most of them are repetitive and fixed types, and there are standard solutions, since only the results of the failure can be seen, various tools are still needed to accurately locate the abnormal points based on some fixed phenomena, characteristic logs and data each time, which wastes too much manpower and reduces the efficiency of troubleshooting. In addition, the operation and maintenance personnel of the application system cannot guarantee 24-hour real-time online troubleshooting and analysis. The on-duty personnel also need to conduct step-by-step analysis according to the operation manual, and cannot conduct real-time and accurate analysis of the failures in the application system.

[0003] Therefore, a method is needed to analyze application system failures in real time and accurately. Summary of the invention

[0004] The embodiment of the present application provides an application system fault analysis method, which can accurately analyze the faults of the application system in real time.

[0005] In a first aspect, an embodiment of the present application provides an application system fault analysis method, the method comprising: connecting with multiple application systems based on a preset first connection specification, the first connection specification being a pre-set connection specification of the application system; obtaining first fault information of the first system, the first fault information being relevant information of the first system that has failed among multiple application systems; determining a first analysis interface for performing fault analysis on the first system based on the first fault information and a preset database rule table, the database rule table comprising the first analysis interface for performing fault analysis on multiple application systems; performing fault analysis on the first fault information based on the first analysis interface for performing fault analysis on the first system to obtain a fault analysis result of the first system.

[0006] In a second aspect, an embodiment of the present application provides an application system fault analysis device, which includes: a first connection module, used to connect to multiple application systems based on a preset first connection specification, wherein the first connection specification is a pre-set connection specification of the application system; a first acquisition module, used to obtain first fault information of the first system, wherein the first fault information is relevant information of the first system that has failed among multiple application systems; a first determination module, used to determine a first analysis interface for performing fault analysis on the first system based on the first fault information and a preset database rule table, wherein the database rule table includes the first analysis interface for performing fault analysis on multiple application systems; a first analysis module, used to perform fault analysis on the first fault information based on the first analysis interface for performing fault analysis on the first system, and obtain a fault analysis result of the first system.

[0007] In a third aspect, an embodiment of the present application provides an electronic device, which includes a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the method described in the first aspect.

[0008] In a fourth aspect, an embodiment of the present application provides a readable storage medium, on which a program or instruction is stored, and when the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented.

[0009] In a fifth aspect, an embodiment of the present application provides a chip, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the method described in the first aspect.

[0010] In an embodiment of the present application, multiple application systems are connected based on a preset first connection specification, where the first connection specification is a preset connection specification for the application system; first fault information of the first system is obtained, where the first fault information is related information of the first system that has failed among multiple application systems; a first analysis interface for performing fault analysis on the first system is determined based on the first fault information and a preset database rule table, where the database rule table includes the first analysis interface for performing fault analysis on multiple application systems; fault analysis is performed on the first fault information based on the first analysis interface for performing fault analysis on the first system, and a fault analysis result of the first system is obtained, so that the fault of the application system can be accurately analyzed in real time. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] Figure 1 It is a flowchart of an application system fault analysis method provided in an embodiment of the present application; Figure 2 It is a structural diagram of an application system fault analysis system provided in an embodiment of the present application; Figure 3 It is a schematic diagram of the structure of a database rule table provided in an embodiment of the present application; Figure 4 It is a flow chart of a second application system fault analysis method provided in an embodiment of the present application; Figure 5 It is a flowchart of a third application system fault analysis method provided in an embodiment of the present application; Figure 6 It is a structural diagram of an application system fault analysis device provided in an embodiment of the present application; Figure 7 It is a structural diagram of an application system fault analysis device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0012] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0013] The terms "first", "second", etc. in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the objects distinguished by "first", "second", etc. are generally of one type, and the number of objects is not limited. For example, the first object can be one or more. In addition, "and / or" in the specification and claims represents at least one of the connected objects, and the character " / " generally indicates that the objects associated with each other are in an "or" relationship.

[0014] The following is a detailed description of the application system fault analysis method provided by the embodiment of the present application through specific embodiments and their application scenarios in conjunction with the accompanying drawings.

[0015] Figure 1 An application system fault analysis method provided by an embodiment of the present invention is shown. The method can be executed by an electronic device, and the electronic device may include: a server and / or a terminal device, wherein the terminal device may be, for example, a vehicle-mounted terminal or a mobile phone terminal. In other words, the method can be executed by software or hardware installed in the application system fault analysis device, and the method includes the following steps: Step 102: Connecting with multiple application systems based on a preset first connection specification.

[0016] The first connection specification is a preset connection specification of the application system.

[0017] The fault analysis system is connected to multiple application systems based on a preset first connection specification, wherein the first connection specification is a preset connection specification of the application system, and the application system is a system that provides services to the terminal, such as the third-generation auto insurance underwriting system or the third-generation auto insurance coverage system, etc., which can be connected to the fault analysis system through a unified connection specification. In other words, the fault analysis system is connected to multiple systems that provide services to the terminal through a preset connection specification.

[0018] Step 104: Obtain first fault information of the first system.

[0019] The first fault information is related information of the first system where a fault occurs among the plurality of application systems.

[0020] After the fault analysis system is connected to multiple application systems, the fault analysis system obtains first fault information of the first system, wherein the first fault information is relevant information of the first system, and the first system is the system in which the fault occurs among the multiple application systems connected to the fault analysis system, that is, the fault analysis system obtains relevant information of the first system in which the fault occurs among the multiple application systems connected to it.

[0021] Specifically, the first fault information of the first system may include identity information of the first system and operation information of the first system, wherein the identity information of the first system is used to characterize the identity of the first system, and the operation information of the first system is the operation information when the first system fails.

[0022] More specifically, the fault analysis system can obtain the first fault information of the first system after connecting to multiple application systems based on a preset first connection specification, or can first obtain the first fault information of the first system and then connect to the first system based on the preset first connection specification. When the fault analysis system obtains the fault information of the first system after connecting to the first system, the fault analysis system can directly obtain the first fault information through the first system; when the fault analysis system obtains the first fault information of the first system and then connects to the first system, the fault analysis system can determine the identity of the first system based on the identity information of the first system in the first fault information, and then connect to the first system based on the identity information of the first system and the preset first connection specification, and then obtain the operation information of the first system.

[0023] Step 106: Determine a first analysis interface for performing fault analysis on the first system based on the first fault information and a preset database rule table.

[0024] Wherein, the database rule table includes the first analysis interface for performing fault analysis on the plurality of application systems.

[0025] After obtaining the first fault information, the fault analysis system determines the first analysis interface for performing fault analysis on the first system based on the first fault information and a preset database rule table, wherein the database rule table stores first analysis interfaces for performing fault analysis on multiple application systems. In other words, the database rule table pre-stores the first analysis interface corresponding to each application system, wherein the number of first analysis interfaces corresponding to each application system may be one or more.

[0026] Specifically, the database rule table can store the identity information of each application system and the first analysis interface corresponding to each identity information, and then the fault analysis system can compare the identity information in the first fault information with the identity information of each application system stored in itself, and determine the first analysis interface of the corresponding application system (first system).

[0027] Step 108: Perform fault analysis on the first fault information based on the first analysis interface for performing fault analysis on the first system to obtain a fault analysis result of the first system.

[0028] After determining the first analysis interface for performing fault analysis on the first system, the fault analysis system performs fault analysis on the first fault information based on the determined first analysis interface for performing fault analysis on the first system to obtain a fault analysis result of the first system.

[0029] Specifically, when performing fault analysis on the first fault information based on the first analysis interface, the fault analysis system can perform fault analysis on the operation information in the first fault information according to the first analysis interface, thereby obtaining a fault analysis result of the first system.

[0030] The application system fault analysis method provided in the embodiment of the present invention is connected to multiple application systems based on a preset first connection specification, where the first connection specification is a preset connection specification of the application system; first fault information of the first system is obtained, where the first fault information is related information of the first system that has failed among multiple application systems; a first analysis interface for performing fault analysis on the first system is determined based on the first fault information and a preset database rule table, where the database rule table includes the first analysis interface for performing fault analysis on multiple application systems; fault analysis is performed on the first fault information based on the first analysis interface for performing fault analysis on the first system, and a fault analysis result of the first system is obtained, so that application system faults can be accurately analyzed in real time.

[0031] In one implementation, steps A1-A2 may also be performed: Step A1: receiving a first connection instruction input by a target terminal.

[0032] The target terminal is an installation terminal of the fault analysis system, the first connection instruction is used to instruct the fault analysis system to connect to a second system through the first connection specification, and the second system is the application system to be connected to the fault analysis system.

[0033] The fault analysis system receives a first connection instruction input by a target terminal, wherein the target terminal is an installation terminal of the fault analysis system (i.e., the fault analysis system is installed in the target terminal), and the first connection instruction is used to instruct the fault analysis system to connect to the second system through a first connection specification. In other words, the fault analysis system can receive a connection instruction sent by its installation terminal, and connect to a specified application system based on the connection instruction.

[0034] Specifically, when the fault analysis system is connected with each application system, the connection specification used is a unified connection specification, that is, the first connection specification. Each application system is "inserted" into the fault analysis system by configuration, and the "slot" is designed according to the unified specification (that is, the first connection specification), so that the fault analysis system can be connected with each application system in the same way.

[0035] Step A2: receiving a first disconnection instruction input by the target terminal.

[0036] The first disconnection instruction is used to instruct the fault analysis system to disconnect from the application system.

[0037] The fault analysis system receives a first disconnection instruction input by the target terminal, wherein the first disconnection instruction is used to instruct the fault analysis system to disconnect from the connected application system. In other words, the fault analysis system can receive a disconnection instruction sent by its installation terminal and disconnect from the connected application system based on the disconnection instruction.

[0038] Specifically, the fault analysis system can connect and disconnect multiple application systems through unified connection specifications, thereby achieving a "hot plug" effect for the application system. As a result, it can not only perform fault analysis on the failed application system when multiple application systems fail, thereby determining the fault analysis results, but also expand the analysis scope of the fault analysis system by adding new application systems.

[0039] In one implementation, steps B1-B2 may also be performed: Step B1: receiving a second connection instruction input by the target terminal.

[0040] Among them, the target terminal is the installation terminal of the fault analysis system, the second connection instruction is used to instruct the fault analysis system to connect to the second analysis interface, the second analysis interface has the same generation specification as the first analysis interface and is used to perform fault analysis on the application system.

[0041] The fault analysis system receives a second connection instruction input by a target terminal, wherein the target terminal is an installation terminal of the fault analysis system (i.e., the fault analysis system is installed in the target terminal), and the second connection instruction is used to instruct the fault analysis system to connect to a second analysis interface, and the second analysis interface has the same generation specification as the first analysis interface and is used to perform fault analysis on the application system (i.e., the second analysis interface is the first analysis interface to be connected to the fault analysis interface). In other words, the fault analysis system can receive a connection instruction sent by its installation terminal, and connect to the designated first analysis interface to be connected to the fault analysis interface based on the connection instruction.

[0042] Step B2: receiving a second disconnection instruction input by the target terminal.

[0043] The second disconnection instruction is used to instruct the fault analysis system to disconnect from the first analysis interface.

[0044] The fault analysis system receives a second disconnection instruction input by the target terminal, wherein the second disconnection instruction is used to instruct the fault analysis system to disconnect from the first analysis interface that has been connected. In other words, the fault analysis system can receive a disconnection instruction sent by its installation terminal, and disconnect from the first analysis interface that has been connected based on the disconnection instruction.

[0045] Specifically, the fault analysis system can connect and disconnect multiple first connection interfaces through a unified connection specification, so that it can add and delete first analysis interfaces for analyzing application systems, achieve a "hot plug" effect of the first analysis interface, and further continuously improve and update the analysis operations performed on each application system.

[0046] More specifically, after the fault analysis system receives the second connection instruction and / or the second disconnection instruction of the target terminal, it can update the database rule table based on the second connection instruction and / or the second disconnection instruction, so that after receiving the fault information of the application system, it can determine the first analysis interface corresponding to the faulty application system based on the updated database rule table and perform fault analysis on the faulty application system based on the determined first analysis interface.

[0047] Figure 2 is a schematic diagram of the structure of an application system fault analysis system provided in an embodiment of this specification, such as Figure 2 As shown, the application system fault analysis system includes: a fault analysis subsystem, a first analysis interface and a first subsystem. The fault analysis subsystem receives a second connection instruction sent by the target terminal to connect to the first analysis interface based on the second connection instruction. After receiving the first connection instruction sent by the target terminal, the fault analysis subsystem connects to the first subsystem in the application system to determine the first analysis interface for performing fault analysis on the first subsystem based on the database rule table and the first fault information after receiving the first fault information, and to perform fault analysis on the first fault information through the first analysis interface and determine the fault analysis result. The fault analysis subsystem can also receive a first disconnection instruction and a second disconnection instruction sent by the target terminal, wherein the first disconnection instruction instructs the fault analysis subsystem to disconnect from the first subsystem, and the second disconnection instruction is used to instruct the fault analysis subsystem to disconnect from the first analysis interface. In this way, by using unified specifications to connect and disconnect the fault analysis subsystem with each application subsystem, and by using unified specifications to connect and disconnect the fault analysis subsystem with each first analysis interface, a "hot plug" effect is achieved between the fault analysis subsystem, the application system, and the first analysis interface. This not only makes it possible to determine the application system fault in real time and accurately for analysis, but also increases the application scope of the fault analysis subsystem by connecting multiple application systems according to unified specifications, and increases the fault identification capability of the fault analysis subsystem by adding and updating the first analysis interface for analyzing the application system.

[0048] In one implementation, before determining the first analysis interface for performing fault analysis on the first system based on the first fault information and a preset database rule table (step 106), steps C1-C3 may also be performed: Step C1: Determine terminal access data based on the first fault information.

[0049] The terminal access data is related data accessed by the target terminal within a preset time, and the target terminal is an installation terminal of the fault analysis system.

[0050] Before the fault analysis system determines the first analysis interface for analyzing the first system based on the first fault information and the database rule table, the fault analysis system can determine the terminal access data based on the first fault information, wherein the terminal access data is the data accessed by the target terminal within a preset time (the preset time may be ten minutes or twenty minutes), and the target terminal is the installation terminal of the fault analysis system (i.e., the fault analysis system is installed in the target terminal).

[0051] Step C2: Determine whether the first data exists in the terminal access data.

[0052] The first data is data that will cause the first system to malfunction after being accessed by the target terminal.

[0053] After determining the terminal access data, the fault analysis system determines whether there is first data in the terminal access data, wherein the first data is data that may cause the first system to fail after the target terminal accesses it. In other words, the fault analysis system pre-sets data that may cause the application system to fail after access, namely, the first data, and then the fault analysis system determines whether the first data is included in the acquired terminal access data, namely, whether the target terminal has accessed the data that may cause the application system to fail.

[0054] Step C3: If yes, determine that the fault analysis result is a non-application system fault.

[0055] After the fault analysis system determines whether the first data is stored in the terminal access data, the fault analysis system determines whether the fault of the application system is caused by the application system according to the determination result. Specifically, after determining that the first data does not exist in the terminal access data, the fault analysis system can determine that the fault analysis result is an application system fault, that is, a fault caused by a problem in the application system; after determining that the first data exists in the terminal access data, the fault analysis system can determine that the fault analysis result is a non-application system fault, that is, a fault of the application system caused by the first data accessed by the target terminal.

[0056] Specifically, when the first system is a third-generation auto insurance underwriting system and a failure occurs in the third-generation auto insurance underwriting system causing an alarm, the fault analysis system can determine whether it is a non-system problem caused by abnormal access to the target terminal. For example, when a certain IP accesses a .php type URL, the system success rate becomes low, thereby causing a system failure.

[0057] In one implementation, the determining of the first analysis interface for performing fault analysis on the first system based on the first fault information and a preset database rule table (step 106) may include executing steps D1-D2: Step D1: Obtain identification information of the first system in the first fault information.

[0058] The fault analysis system obtains identification information of the first system in the first fault information, wherein the identification information is used to characterize the identity of the first system, and the identification information may be a system name, system code, organization code, etc. of the application system.

[0059] Step D2: determining a plurality of first analysis interfaces and a first order corresponding to the identification information from the database rule table based on the identification information.

[0060] The first sequence is the sequence in which the fault analysis system performs fault analysis on the first system based on the plurality of the first analysis interfaces.

[0061] After obtaining the identification information in the first fault information, the fault analysis system determines the multiple first analysis interfaces and the first order corresponding to the identification information from the database rule table based on the identification information, wherein the first order is the order in which the fault analysis system analyzes the first fault information based on the multiple first analysis interfaces. In other words, the database rule table pre-stores the multiple first analysis interfaces corresponding to each application system and the order in which the analysis is performed based on the multiple first analysis interfaces corresponding to each application system.

[0062] Specifically, when performing fault analysis on the first fault information of the first system based on multiple first analysis interfaces, each first analysis interface can be used to verify the specific scenario of the application system. Each application system includes multiple business scenarios that provide services to users. Therefore, when performing fault analysis on the application system based on multiple first analysis interfaces, one first analysis interface can correspond to a scenario of the application system, so that fault analysis can be performed on each scenario included in the application system through multiple first analysis results.

[0063] More specifically, the first order is determined based on the degree of impact of the application system scenarios analyzed by each first analysis interface. Since each application system includes multiple different scenarios, the fault problems when a fault occurs in each scenario are also different and the degree of impact of each fault problem is also different. Therefore, when performing fault analysis on the application system based on multiple first analysis interfaces, the scenario with the greatest degree of impact of the fault problem can be analyzed first, and then the scenario with the least degree of impact of the fault problem can be analyzed, thereby improving the accuracy of fault problem identification. Furthermore, Figure 3FIG. 1 is a schematic diagram showing the structure of a database rule table provided in an embodiment of the present specification. Figure 3 As shown, the database rule table stores system names (third-generation motor vehicle insurance underwriting system and third-generation motor vehicle insurance underwriting system) that can be analyzed through the fault analysis system, system codes corresponding to the system names (the system code of the third-generation motor vehicle insurance underwriting system is 0001, and the system code of the third-generation motor vehicle insurance underwriting system is 0002), institution names corresponding to the system names (the institution name corresponding to the third-generation motor vehicle insurance underwriting system is 32000, and the institution name corresponding to the third-generation motor vehicle insurance underwriting system is 11000), address information of multiple first analysis interfaces for fault analysis corresponding to the system names, judgment information and judgment order (fault analysis of the third-generation motor vehicle insurance underwriting system The address information of the multiple first analysis interfaces analyzed are respectively the first address for determining the first fault cause and the second address for determining the second fault cause, and the judgment order of the first analysis interface of the first address is "1", and the judgment order of the first analysis interface of the second address is "2"; the address information of the multiple first analysis interfaces for fault analysis of the third-generation motor insurance underwriting system are respectively the third address for determining the third fault cause, the first address for determining the first fault cause, and the second address for determining the second fault cause, and the judgment order of the first analysis interface of the third address is "1", the judgment order of the first analysis interface of the first address is "2", and the judgment order of the first analysis interface of the second address is "3").

[0064] Figure 4 FIG. 1 is a flow chart of a second method for analyzing a failure of an application system provided in an embodiment of the present specification. Figure 4 As shown, the schematic diagram includes: Step 402: Connecting with multiple application systems based on a preset first connection specification.

[0065] The first connection specification is a preset connection specification of the application system.

[0066] Step 404: Obtain first fault information of the first system.

[0067] The first fault information is related information of the first system where a fault occurs among the plurality of application systems.

[0068] Step 406: Obtain identification information of the first system in the first fault information.

[0069] Step 408: Determine, based on the identification information, from the database rule table a plurality of first analysis interfaces and a first order corresponding to the identification information.

[0070] The first sequence is the sequence in which the fault analysis system performs fault analysis on the first system based on the plurality of the first analysis interfaces, and the database rule table includes the first analysis interfaces for performing fault analysis on the plurality of the application systems.

[0071] Step 410: Perform fault analysis on the first fault information based on the first sequence and the plurality of first analysis interfaces for performing fault analysis on the first system to obtain a fault analysis result of the first system.

[0072] This embodiment sets up multiple first analysis interfaces for performing fault analysis on each application system, and analyzes multiple business scenarios of the first system based on each first analysis interface. This not only enables more real-time and accurate identification of faults occurring in the first system, but also enables continuous increase in the types and number of first analysis interfaces to continuously supplement and improve the scenarios for fault identification of the first system, thereby continuously improving the analysis capability of the fault analysis system.

[0073] In one implementation, the first analysis interface for performing fault analysis on the first system performs fault analysis on the first fault information to obtain a fault analysis result of the first system (step 108), and steps E1-E5 may be performed: Step E1: Obtain the operation log data in the first fault information.

[0074] The operation log data is log data when the first system is running.

[0075] The fault analysis system obtains the operation log data in the first fault information, wherein the operation log data is the log data generated when the first system is running. Specifically, the operation log data included in the first fault information is the operation log data of the first system within a preset time, such as the log data generated by the operation within the last ten minutes or twenty minutes.

[0076] Step E2: Determine whether there is first fault data in the operation log data.

[0077] The first fault data is generated based on log data generated when a node pseudo-death fault occurs in the first system.

[0078] After obtaining the operation log data, the fault analysis system can determine whether there is first fault data in the operation log data through the first analysis interface, wherein the first fault data is generated based on the log data generated when a node pseudo-death fault occurs in the first system, that is, the fault analysis system compares the first fault data with the data in the operation log data through the first analysis interface to determine whether there is the first fault data in the operation log data. Furthermore, the first fault data compared with the operation log data can characterize the characteristic data when a node pseudo-death fault occurs in the first system, and therefore it can be determined whether a node pseudo-death fault occurs in the first system by determining whether there is the first fault data in the operation log data.

[0079] Step E3: If yes, determine that the fault analysis result is a node pseudo-death fault.

[0080] When different faults occur in the application system, the fault data generated are also different. Therefore, it is possible to determine whether the fault corresponding to the fault data occurs by determining whether the fault data exists in the operation log data. Specifically, after the fault analysis system compares the first fault data with the operation log data, the fault analysis system determines that a node pseudo-death fault has occurred in the first system when the first fault data is included in the operation log data, that is, the fault analysis result is determined to be a node pseudo-death fault. When the first fault data is not included in the operation log data, it is determined that no node pseudo-death fault has occurred in the first system, that is, the fault analysis result is determined to be a non-node pseudo-death fault.

[0081] Specifically, when the first system is a third-generation motor vehicle insurance underwriting system and a fault occurs in the third-generation motor vehicle insurance underwriting system, causing an alarm, the fault analysis system can detect the first fault information through a first analysis interface that analyzes the system's node pseudo-death fault, thereby determining whether the fault occurring in the system is a node pseudo-death fault.

[0082] Step E4: Determine whether there is second fault data in the operation log data.

[0083] The second fault data is generated based on log data generated when a line congestion fault occurs in the first system.

[0084] After determining that the first system does not have a node pseudo-death fault, the fault analysis system determines whether there is second fault data in the operation log data, wherein the second fault data is generated based on the log data generated when the first system has a line congestion fault, that is, the fault analysis system compares the second fault data with the data in the operation log data to determine whether there is the second fault data in the operation log data. Further, the second fault data compared with the operation log data can characterize the characteristic data when the first system has a line congestion fault, so it is possible to determine whether the first system has a line congestion fault by determining whether there is the second fault data in the operation log data.

[0085] Step E5: If yes, then determine that the fault analysis result is a line blocking fault.

[0086] After the fault analysis system compares the second fault data with the operation log data, the fault analysis system determines that a line congestion fault has occurred in the first system when the second fault data is included in the operation log data, that is, the fault analysis result is a line congestion fault, and determines that no line congestion fault has occurred in the first system when the second fault data is not included in the operation log data, that is, the fault analysis result is determined to be a non-node pseudo-death fault. After determining that the fault analysis result is a non-node pseudo-death fault, the fault analysis system can also compare the operation log data with other data to determine whether other faults have occurred in the first system, which will not be elaborated here.

[0087] Specifically, when the first system is a third-generation motor vehicle insurance underwriting system and a fault occurs in the third-generation motor vehicle insurance underwriting system causing an alarm, the fault analysis system can detect the first fault information through a first analysis interface that analyzes the system's line congestion fault, thereby determining whether the fault occurring in the system is a line congestion fault.

[0088] In an implementation manner, before obtaining the operation log data in the first fault information (step E1), steps F1-F2 may also be performed: Step F1: Obtain rule change data in the first fault information.

[0089] The rule change data is generated based on the operation rules of the first system change.

[0090] Before the fault analysis system obtains the operation log data in the first fault information, the fault analysis system can first obtain the rule change data in the first fault information, wherein the rule change data is generated based on the operation rule changed by the first system. Specifically, the rule change data included in the first fault information is the rule change data within a preset time of the first system, such as the rule change data within ten minutes or twenty minutes.

[0091] More specifically, the rule change data in the first fault information may be operating rule data at multiple time points. The fault analysis system can determine whether the operating rules within the time period have changed based on the operating rule data at multiple time points, and further determine the rule change data.

[0092] Step F2: If it is determined based on the rule change data that the operation rule of the first system has changed, then the fault analysis result is determined to be a rule change fault.

[0093] After the fault analysis system determines the rule change data, the fault analysis system can determine that the fault analysis result is a rule change fault after determining that the operating rules of the first system have changed based on the rule change data, and can determine that the fault analysis result is non-rule change data after determining that the operating rules of the first system have not changed based on the rule change data. Specifically, when the operating rules of the first system are changed, it may cause an operating fault of the first system, so the fault analysis result of the first system can be determined by determining whether the rule change data in the first fault information has changed.

[0094] Specifically, when the first system is a third-generation auto insurance underwriting system and a fault occurs in the third-generation auto insurance underwriting system, resulting in an alarm, the fault analysis system can detect the first fault information through the first analysis interface for analyzing the system rule change fault, thereby determining whether the fault of the system is a rule change fault. For example, the third-generation auto insurance underwriting system first determines whether it is caused by the release of the underwriting rule by calling the rule interface (http: / / localhost / analyse / rule). If so, the "Is it terminated" field in the configuration table is yes, then the fault analysis result is directly returned to the main process of the fault analysis system. The main process of the fault analysis system merges the current diagnostic information and returns it to the target terminal to determine that the cause of the fault is a rule change.

[0095] Figure 5 FIG. 1 is a flow chart of a third method for analyzing application system failures provided in an embodiment of the present application. Figure 5 As shown, the schematic diagram includes: Step 502: Connecting with multiple application systems based on a preset first connection specification.

[0096] The first connection specification is a preset connection specification of the application system.

[0097] Step 504: Obtain first fault information of the first system.

[0098] The first fault information is related information of the first system where a fault occurs among the plurality of application systems.

[0099] Step 506: Determine terminal access data based on the first fault information, where the terminal access data is relevant data accessed by the target terminal within a preset time.

[0100] Wherein, the target terminal is an installation terminal of the fault analysis system.

[0101] Step 508: Determine whether the terminal access data contains first data.

[0102] The first data is data that will cause the first system to malfunction after being accessed by the target terminal.

[0103] Step 510: If yes, determine that the fault analysis result is a non-application system fault.

[0104] Step 512: Determine a first analysis interface for performing fault analysis on the first system based on the first fault information and a preset database rule table.

[0105] Wherein, the database rule table includes the first analysis interface for performing fault analysis on the plurality of application systems.

[0106] Step 514: Obtain rule change data in the first fault information.

[0107] The rule change data is generated based on the operation rules of the first system change.

[0108] Step 516: If it is determined based on the rule change data that the operating rule of the first system has changed, then the fault analysis result is determined to be a rule change fault.

[0109] Step 518: Obtain the operation log data in the first fault information.

[0110] The operation log data is log data when the first system is running.

[0111] Step 520: Determine whether there is first fault data in the operation log data.

[0112] The first fault data is generated based on log data generated when a node pseudo-death fault occurs in the first system.

[0113] Step 522: If yes, determine that the fault analysis result is a node pseudo-death fault.

[0114] Step 524: Determine whether there is second fault data in the operation log data.

[0115] The second fault data is generated based on log data generated when a line congestion fault occurs in the first system.

[0116] Step 526: If yes, determine that the fault analysis result is a line congestion fault.

[0117] When the fault analysis system of the present embodiment performs fault analysis on the first system, it first determines whether the fault is caused by the application system by checking whether the first data exists in the terminal access data, then determines whether the fault is caused by a rule change by checking whether the rule change data exists in the first fault information, and finally determines whether the fault is a node pseudo-death fault or a line congestion fault by checking whether the first fault data or the second fault data exists in the first fault information. In this way, the causes of each fault are analyzed according to the order of the impact on the application system after the fault occurs, so that the root cause of the fault in the first system can be accurately determined, thereby improving the accuracy of the fault analysis.

[0118] It should be noted that the application system fault analysis method provided in the embodiment of the present application can be executed by an application system fault analysis device, or a control module in the application system fault analysis device for executing the application system fault analysis method. In the embodiment of the present application, the application system fault analysis device provided in the embodiment of the present application is described by taking the application system fault analysis device executing the application system fault analysis method as an example.

[0119] Figure 6 FIG. 1 is a schematic diagram of the structure of an application system fault analysis device according to an embodiment of the present invention. Figure 6 As shown, the application system fault analysis device includes: a first connection module 602 , a first acquisition module 604 , a first determination module 606 , and a first analysis module 608 .

[0120] A first connection module 602, configured to connect to a plurality of application systems based on a preset first connection specification, where the first connection specification is a preset connection specification of the application system; A first acquisition module 604 is used to acquire first fault information of a first system, where the first fault information is related information of the first system having a fault in the plurality of application systems; A first determination module 606, configured to determine a first analysis interface for performing fault analysis on the first system based on the first fault information and a preset database rule table, wherein the database rule table includes the first analysis interfaces for performing fault analysis on a plurality of the application systems; The first analysis module 608 is used to perform fault analysis on the first fault information based on the first analysis interface for performing fault analysis on the first system to obtain a fault analysis result of the first system.

[0121] The application system fault analysis device in the embodiment of the present application can be a device, or a component, integrated circuit, or chip in a terminal. The device can be a mobile electronic device or a non-mobile electronic device. Exemplarily, the mobile electronic device can be a mobile phone, a tablet computer, a laptop computer, a PDA, an in-vehicle electronic device, a wearable device, an ultra-mobile personal computer (UMPC), a netbook, or a personal digital assistant (PDA), etc. The non-mobile electronic device can be a server, a network attached storage (NAS), a personal computer (PC), a television (TV), a teller machine or a self-service machine, etc., which is not specifically limited in the embodiment of the present application.

[0122] The application system fault analysis device in the embodiment of the present application may be a device having an operating system. The operating system may be an Android operating system, an iOS operating system, or other possible operating systems, which are not specifically limited in the embodiment of the present application.

[0123] The application system fault analysis device provided in the embodiment of the present application can achieve Figures 1 to 5 To avoid repetition, the various processes implemented in the method embodiment are not described here.

[0124] Based on the same technical concept, an embodiment of the present application further provides an electronic device, which is used to execute the above-mentioned application system fault analysis method. Figure 7 A schematic diagram of the structure of an electronic device for implementing various embodiments of the present application. The electronic device may have relatively large differences due to different configurations or performances, and may include a processor (processor) 702, a communication interface (Communications Interface) 704, a memory (memory) 706 and a communication bus 708, wherein the processor 702, the communication interface 704, and the memory 706 communicate with each other through the communication bus 708. The processor 702 may call a computer program stored in the memory 706 and executable on the processor 702 to perform the following steps: Connecting with multiple application systems based on a preset first connection specification, where the first connection specification is a preset connection specification of the application system; Acquire first fault information of a first system, where the first fault information is related information of the first system having a fault in the plurality of application systems; Determine a first analysis interface for performing fault analysis on the first system based on the first fault information and a preset database rule table, wherein the database rule table includes the first analysis interface for performing fault analysis on a plurality of the application systems; The first fault information is subjected to fault analysis based on the first analysis interface for performing fault analysis on the first system to obtain a fault analysis result of the first system.

[0125] In one implementation, the method further includes: Receiving a first connection instruction input by a target terminal, the target terminal being an installation terminal of the fault analysis system, the first connection instruction being used to instruct the fault analysis system to connect to a second system through the first connection specification, the second system being the application system to be connected to the fault analysis system; A first disconnection instruction input by the target terminal is received, where the first disconnection instruction is used to instruct the fault analysis system to disconnect from the application system.

[0126] In one implementation, the method further includes: Receiving a second connection instruction input by a target terminal, the target terminal being an installation terminal of the fault analysis system, the second connection instruction being used to instruct the fault analysis system to connect to a second analysis interface, the second analysis interface having the same generation specification as the first analysis interface and being used to perform fault analysis on the application system; A second disconnection instruction input by the target terminal is received, where the second disconnection instruction is used to instruct the fault analysis system to disconnect from the first analysis interface.

[0127] In one implementation, before determining a first analysis interface for performing fault analysis on the first system based on the first fault information and a preset database rule table, the method further includes: Determine terminal access data based on the first fault information, where the terminal access data is relevant data accessed by a target terminal within a preset time, and the target terminal is an installation terminal of the fault analysis system; Determining whether there is first data in the terminal access data, where the first data is data that will cause the first system to fail after being accessed by the target terminal; If so, it is determined that the fault analysis result is a non-application system fault.

[0128] In one implementation, determining a first analysis interface for performing fault analysis on the first system based on the first fault information and a preset database rule table includes: Obtaining identification information of the first system in the first fault information; Based on the identification information, multiple first analysis interfaces and a first order corresponding to the identification information are determined from the database rule table, where the first order is the order in which the fault analysis system performs fault analysis on the first system based on the multiple first analysis interfaces.

[0129] In one implementation, the performing fault analysis on the first fault information based on the first analysis interface for performing fault analysis on the first system to obtain a fault analysis result of the first system includes: Obtaining operation log data in the first fault information, where the operation log data is log data when the first system is running; Determine whether there is first fault data in the operation log data, where the first fault data is generated based on log data generated when a node pseudo-death fault occurs in the first system; If yes, then determine that the fault analysis result is a node pseudo-death fault; Determining whether there is second fault data in the operation log data, where the second fault data is generated based on log data generated when a line blocking fault occurs in the first system; If so, it is determined that the fault analysis result is a line congestion fault.

[0130] In one implementation, before obtaining the operation log data in the first fault information, the method further includes: Acquire rule change data in the first fault information, where the rule change data is generated based on the changed operation rule of the first system; If it is determined based on the rule change data that the operation rule of the first system has changed, then the fault analysis result is determined to be a rule change fault.

[0131] The specific execution steps can refer to the various steps of the above-mentioned application system fault analysis method embodiment, and can achieve the same technical effect. To avoid repetition, they will not be repeated here.

[0132] It should be noted that the electronic devices in the embodiments of the present application include: servers, terminals, or other devices except terminals.

[0133] The above electronic device structure does not constitute a limitation on the electronic device. The electronic device may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently. For example, the input unit may include a graphics processing unit (GPU) and a microphone, and the display unit may be configured with a display panel in the form of a liquid crystal display, an organic light-emitting diode, etc. The user input unit includes a touch panel and at least one of other input devices. The touch panel is also called a touch screen. Other input devices may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.

[0134] The memory can be used to store software programs and various data. The memory may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, an application program or instructions required for at least one function (such as a sound playback function, an image playback function, etc.), etc. In addition, the memory may include a volatile memory or a non-volatile memory, or the memory may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM) and direct memory bus random access memory (DRRAM).

[0135] The processor may include one or more processing units; optionally, the processor integrates an application processor and a modem processor, wherein the application processor mainly processes operations related to the operating system, user interface, and application programs, and the modem processor mainly processes wireless communication signals, such as a baseband processor. It is understandable that the modem processor may not be integrated into the processor.

[0136] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, each process of the above-mentioned application system fault analysis method embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0137] The processor is the processor in the electronic device described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0138] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned application system fault analysis method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0139] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0140] It should be noted that, in this article, the terms "comprise", "include" or any other variant thereof are intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise one..." do not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved, for example, the described method may be performed in an order different from that described, and various steps may also be added, omitted, or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0141] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, a magnetic disk, or an optical disk), and includes a number of instructions for a terminal (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods described in each embodiment of the present application.

[0142] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms without departing from the purpose of the present application and the scope of protection of the claims, all of which are within the protection of the present application.

Claims

1. An application system fault analysis method, applied to a fault analysis system, comprising: Connecting with multiple application systems based on a preset first connection specification, where the first connection specification is a preset connection specification of the application system; Acquire first fault information of a first system, where the first fault information is related information of the first system having a fault in the plurality of application systems; Determine a first analysis interface for performing fault analysis on the first system based on the first fault information and a preset database rule table, wherein the database rule table includes the first analysis interface for performing fault analysis on a plurality of the application systems; The first fault information is subjected to fault analysis based on the first analysis interface for performing fault analysis on the first system to obtain a fault analysis result of the first system.

2. The method according to claim 1, further comprising: Receiving a first connection instruction input by a target terminal, the target terminal being an installation terminal of the fault analysis system, the first connection instruction being used to instruct the fault analysis system to connect to a second system through the first connection specification, the second system being the application system to be connected to the fault analysis system; A first disconnection instruction input by the target terminal is received, where the first disconnection instruction is used to instruct the fault analysis system to disconnect from the application system.

3. The method according to claim 1, further comprising: Receiving a second connection instruction input by a target terminal, the target terminal being an installation terminal of the fault analysis system, the second connection instruction being used to instruct the fault analysis system to connect to a second analysis interface, the second analysis interface having the same generation specification as the first analysis interface and being used to perform fault analysis on the application system; A second disconnection instruction input by the target terminal is received, where the second disconnection instruction is used to instruct the fault analysis system to disconnect from the first analysis interface.

4. The method according to claim 1, before determining a first analysis interface for performing fault analysis on the first system based on the first fault information and a preset database rule table, the method further comprises: Determine terminal access data based on the first fault information, where the terminal access data is relevant data accessed by a target terminal within a preset time, and the target terminal is an installation terminal of the fault analysis system; Determining whether there is first data in the terminal access data, where the first data is data that will cause the first system to fail after being accessed by the target terminal; If so, it is determined that the fault analysis result is a non-application system fault.

5. The method according to claim 1, wherein determining a first analysis interface for performing fault analysis on the first system based on the first fault information and a preset database rule table comprises: Obtaining identification information of the first system in the first fault information; Based on the identification information, multiple first analysis interfaces and a first order corresponding to the identification information are determined from the database rule table, where the first order is the order in which the fault analysis system performs fault analysis on the first system based on the multiple first analysis interfaces.

6. The method according to claim 1, wherein the performing fault analysis on the first fault information based on the first analysis interface for performing fault analysis on the first system to obtain a fault analysis result of the first system comprises: Obtaining operation log data in the first fault information, where the operation log data is log data when the first system is running; Determine whether there is first fault data in the operation log data, where the first fault data is generated based on log data generated when a node pseudo-death fault occurs in the first system; If yes, then determine that the fault analysis result is a node pseudo-death fault; Determining whether there is second fault data in the operation log data, where the second fault data is generated based on log data generated when a line blocking fault occurs in the first system; If so, it is determined that the fault analysis result is a line congestion fault.

7. The method according to claim 6, before obtaining the operation log data in the first fault information, the method further comprises: Acquire rule change data in the first fault information, where the rule change data is generated based on the changed operation rule of the first system; If it is determined based on the rule change data that the operation rule of the first system has changed, then the fault analysis result is determined to be a rule change fault.

8. An application system fault analysis device, comprising: A first connection module, used to connect with multiple application systems based on a preset first connection specification, where the first connection specification is a preset connection specification of the application system; A first acquisition module is used to acquire first fault information of a first system, where the first fault information is related information of the first system having a fault in the plurality of application systems; A first determination module, configured to determine a first analysis interface for performing fault analysis on the first system based on the first fault information and a preset database rule table, wherein the database rule table includes the first analysis interfaces for performing fault analysis on a plurality of the application systems; The first analysis module is used to perform fault analysis on the first fault information based on the first analysis interface for performing fault analysis on the first system to obtain a fault analysis result of the first system.

9. A computer device, characterized in that: The device comprises: Processor; and A memory arranged to store computer executable instructions, the executable instructions being configured to be executed by the processor, the executable instructions comprising instructions for performing the steps in the method according to any one of claims 1 to 7.

10. A storage medium, characterized in that: The storage medium is used to store computer-executable instructions, and the executable instructions enable a computer to execute the method according to any one of claims 1 to 7.

Images