Fault scene identification method and device

Abstract

The invention provides a fault scene identification method and device. The method comprises the following steps: acquiring state information of each component in a target system; according to the component information corresponding to the to-be-identified fault scene and the state information of each component in the target system, determining the state information of each component corresponding to the to-be-identified fault scene; obtaining a fault code corresponding to the to-be-identified fault scene according to the state information of each component corresponding to the to-be-identified fault scene; and determining an identification result corresponding to the to-be-identified fault scene according to the fault code corresponding to the to-be-identified fault scene and a preset fault code set. According to the method provided by the embodiment of the invention, the accurate identification of the fault scene is realized, the problem that in the prior art, an independent code needs to be independently developed for fault judgment and identification for each fault in a system, and the overall program complexity is relatively high is solved, and the code development amount is greatly reduced.

Description

Technical Field

[0001] The present invention relates to the technical field of fault identification, and in particular to a method and device for identifying a fault scenario. Background Art

[0002] In order to ensure the normal operation of various systems, it is necessary to regularly judge and identify system faults in order to understand the health status of the system in real time, extend the service life of the equipment, and ensure the normal operation of the system.

[0003] In the related art, for each fault in the system, it is necessary to develop independent code separately for fault judgment and identification, and the overall program complexity is relatively high. Summary of the Invention

[0004] The present invention provides a method and device for identifying a fault scenario, which realizes accurate identification of the fault scenario, overcomes the problem in the prior art that for each fault in the system, it is necessary to develop independent code separately for fault judgment and identification, and the overall program complexity is relatively high, and greatly reduces the amount of code development.

[0005] The present invention provides a method and device for identifying a fault scenario, including the following steps.

[0006] Obtain the status information of each component in the target system; According to the component information corresponding to the fault scenario to be identified and the status information of each component in the target system, determine the status information of each component corresponding to the fault scenario to be identified; According to the status information of each component corresponding to the fault scenario to be identified, obtain the fault code corresponding to the fault scenario to be identified; According to the fault code corresponding to the fault scenario to be identified and a preset set of fault codes, determine the identification result corresponding to the fault scenario to be identified.

[0007] According to the method for identifying a fault scenario provided by the present invention, the step of obtaining the fault code corresponding to the fault scenario to be identified according to the status information of each component corresponding to the fault scenario to be identified includes: Combine the status information of each component corresponding to the fault scenario to be identified to obtain the fault code corresponding to the fault scenario to be identified.

[0008] According to the method for identifying a fault scenario provided by the present invention, the step of combining the status information of each component corresponding to the fault scenario to be identified to obtain the fault code corresponding to the fault scenario to be identified includes: According to the state information of each component corresponding to the fault scenario to be identified at the preset position in the fault code, combine the state information of each component corresponding to the fault scenario to be identified to obtain the fault code corresponding to the fault scenario to be identified.

[0009] According to a method for identifying a fault scenario provided by the present invention, the determining the identification result corresponding to the fault scenario to be identified according to the fault code corresponding to the fault scenario to be identified and a preset set of fault codes includes: Match the fault code corresponding to the fault scenario to be identified with the preset set of fault codes to obtain a matching result; According to the matching result, determine the identification result corresponding to the fault scenario to be identified.

[0010] According to a method for identifying a fault scenario provided by the present invention, the matching the fault code corresponding to the fault scenario to be identified with the preset set of fault codes to obtain a matching result; and determining the identification result corresponding to the fault scenario to be identified according to the matching result includes: When the matching result is a matching failure, determine that the fault scenario does not exist in the target system; When the matching result is a matching success, determine that the fault scenario exists in the target system.

[0011] According to a method for identifying a fault scenario provided by the present invention, after determining that the fault scenario exists in the target system when the matching result is a matching success, it further includes: Execute the fault handling operation corresponding to the fault scenario in the target system.

[0012] The present invention further provides an apparatus for identifying a fault scenario, including the following modules: An acquisition module, configured to acquire the state information of each component in the target system; A determination module, configured to determine the state information of each component corresponding to the fault scenario to be identified according to the component information corresponding to the fault scenario to be identified and the state information of each component in the target system; A processing module, configured to obtain the fault code corresponding to the fault scenario to be identified according to the state information of each component corresponding to the fault scenario to be identified; An identification module, configured to determine the identification result corresponding to the fault scenario to be identified according to the fault code corresponding to the fault scenario to be identified and a preset set of fault codes.

[0013] The present invention also provides an electronic device, including a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the program, the method for identifying a fault scenario as described in any one of the above is implemented.

[0014] The present invention also provides a non-transitory computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the method for identifying a fault scenario as described in any one of the above is implemented.

[0015] The present invention also provides a computer program product, including a computer program. When the computer program is executed by a processor, the method for identifying a fault scenario as described in any one of the above is implemented.

[0016] The method and device for identifying a fault scenario provided by the present invention consider the correlation between various components during the fault migration process, identify the fault scenario, can accurately implement the fault migration, and effectively avoid the interruption of services in the system. Moreover, according to the status information of each component corresponding to the fault scenario to be identified in the target system, the fault code corresponding to the fault scenario to be identified is determined, realizing an accurate description of the fault scenario to be identified. Furthermore, by analyzing and matching the fault code corresponding to the fault scenario to be identified and the preset fault code set, it is possible to determine whether there is a fault code that needs attention and timely processing in the fault code set in the target system, realizing an accurate identification of the fault scenario in the target system, effectively overcoming the problem in the prior art that for each fault in the system, independent code needs to be developed separately for fault judgment and identification, with a relatively high overall program complexity, and greatly reducing the amount of code development. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to more clearly illustrate the technical solutions in the present invention or the prior art, the following will briefly introduce the drawings required for use in the description of the embodiments or the prior art. Obviously, the drawings in the following description are some embodiments of the present invention. For those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on these drawings.

[0018] Figure 1 is one of the flow diagrams of the method for identifying a fault scenario provided by the present invention.

[0019] Figure 2 is another flow diagram of the method for identifying a fault scenario provided by the present invention.

[0020] Figure 3 is the structural diagram of the device for identifying a fault scenario provided by the present invention.

[0021] Figure 4 is the structural diagram of the electronic device provided by the present invention. Specific Embodiments

[0022] To make the objectives, technical solutions and advantages of the present invention clearer, the technical solutions in the present invention will be clearly and completely described below with reference to the accompanying drawings in the present invention. Apparently, the described embodiments are some, but not all, of the embodiments of the present invention. All other embodiments obtained by those of ordinary skill in the art based on the embodiments in the present invention without making creative efforts shall fall within the protection scope of the present invention.

[0023] The following will describe Figures 1-4 the method and device for identifying fault scenarios of the present invention.

[0024] To facilitate a clearer understanding of the technical solutions of the embodiments of the present application, some technical content related to the embodiments of the present application will be introduced first.

[0025] Figure 1 is a schematic flowchart of the method for identifying fault scenarios provided by the present invention, and the method includes the following: Step 101: Obtain the status information of each component in the target system.

[0026] Specifically, in the prior art, for each fault in the system, independent code needs to be developed separately for fault judgment and identification. The overall program complexity is relatively high, which is not conducive to interaction with other systems, nor is it conducive to automated and intelligent fault handling. In addition, for the modification of the fault identification program, it is necessary to understand and modify it by referring to the code. Moreover, faults usually include information in dimensions such as preconditions and component roles, resulting in obvious drawbacks in the maintenance of the fault identification program.

[0027] To solve the above problems, in the embodiments of the present application, the status information of each component in the target system is first obtained. Optionally, the target system is a system that needs to be regularly inspected, that is, a system that needs to be regularly judged and identified for faults. Optionally, the target system can be various business systems, such as a payment system, a query system, etc. The target system includes multiple components, such as a database, a cache, a message queue, an API, etc. Optionally, the status information of the component includes a fault status and a normal status.

[0028] For example, the status information of each component in the system can be periodically collected and cached, so as to accurately obtain the status information of all components in the target system.

[0029] Step 102: Determine the status information of each component corresponding to the fault scenario to be identified according to the component information corresponding to the fault scenario to be identified and the status information of each component in the target system.

[0030] Specifically, after obtaining the status information of all components in the target system, in the embodiments of the present application, according to the component information corresponding to the fault scenario to be identified and the status information of each component in the target system, the status information of each component corresponding to the fault scenario to be identified is determined. Optionally, in a system, when a component inside it fails, the subsystem (or the entire system) where the component is located needs to be migrated to the backup site as a whole. However, during the migration process, different migration processes (i.e., different operation logics, steps, and preconditions) are used due to different faulty components. For different component failures within the same subsystem, the operation logics and preconditions are different when performing the migration operation. Therefore, considering the correlation between components during the fault migration process, identifying the fault scenario can more accurately and precisely achieve fault migration and effectively avoid interruption of services in the system.

[0031] Optionally, a system involves many components. When a certain component fails, the corresponding subsystem needs to be migrated. The migration scope that needs to be triggered for component failure is called a fault scenario. For example, component A, the database it depends on, and its corresponding backup site can form a fault scenario A, and its corresponding migration strategy is X. Component B, the API it depends on, and its corresponding backup site can form a fault scenario B, and its corresponding migration strategy is Y. Determining the status information of each component corresponding to the fault scenario to be identified is also determining the status information of component A, the database it depends on, and its corresponding backup site in fault scenario A.

[0032] Step 103: Obtain the fault code corresponding to the fault scenario to be identified according to the status information of each component corresponding to the fault scenario to be identified.

[0033] Specifically, the status information of each component corresponding to the fault scenario to be identified can be represented by 0 and 1; where 0 indicates that the component status is normal, and 1 indicates that the component status is abnormal. Optionally, after determining the status information of each component corresponding to the fault scenario to be identified, according to the status information of each component corresponding to the fault scenario to be identified, the fault code corresponding to the fault scenario to be identified can be accurately obtained. Optionally, the fault code corresponding to the fault scenario to be identified can be obtained by performing permutation and combination or logical operation on the status information of each component corresponding to the fault scenario to be identified, so as to accurately represent the current situation of the fault scenario to be identified.

[0034] Step 104: Determine the recognition result corresponding to the fault scenario to be identified according to the fault code corresponding to the fault scenario to be identified and the preset fault code set.

[0035] Specifically, after obtaining the fault code corresponding to the fault scenario to be recognized, in the embodiments of the present application, the recognition result corresponding to the fault scenario to be recognized is determined according to the fault code corresponding to the fault scenario to be recognized and a preset fault code set. Optionally, the preset fault code set includes the fault codes that need to be concerned about and processed in a timely manner in each fault scenario. Optionally, by analyzing and matching the fault code corresponding to the fault scenario to be recognized and the fault codes that need to be concerned about and processed in a timely manner in the fault code set, it is determined whether there is a fault code that needs to be concerned about and processed in a timely manner in the fault code set in the target system, so as to accurately recognize the fault scenario of the target system.

[0036] The method of the above embodiment takes into account the correlation between each component in the fault migration process, recognizes the fault scenario, can accurately implement the fault migration, and effectively avoids the interruption of services in the system. Moreover, according to the status information of each component corresponding to the fault scenario to be recognized in the target system, the fault code corresponding to the fault scenario to be recognized is determined, so as to accurately describe the fault scenario to be recognized. Furthermore, by analyzing and matching the fault code corresponding to the fault scenario to be recognized and the preset fault code set, it can also be determined whether there is a fault code that needs to be concerned about and processed in a timely manner in the fault code set in the target system, so as to accurately recognize the fault scenario of the target system, effectively overcoming the problem that in the prior art, independent codes need to be developed separately for each fault in the system for fault judgment and recognition, and the overall program complexity is relatively high, and greatly reducing the code development volume.

[0037] In one embodiment, obtaining the fault code corresponding to the fault scenario to be recognized according to the status information of each component corresponding to the fault scenario to be recognized includes: Combining the status information of each component corresponding to the fault scenario to be recognized to obtain the fault code corresponding to the fault scenario to be recognized.

[0038] Specifically, in the embodiments of the present application, by combining the status information of each component corresponding to the fault scenario to be recognized, the fault code corresponding to the fault scenario to be recognized can be accurately and quickly obtained, so as to accurately represent the current situation of the fault scenario to be recognized.

[0039] For example, component A, database component B on which component A depends, and its corresponding backup site component C can form a fault scenario A. Optionally, the status information of each component corresponding to the fault scenario to be recognized can be represented by 0 and 1; where 0 indicates that the component status is normal, and 1 indicates that the component status is abnormal. If component A fails while components B and C are both normal, then the status information of each component corresponding to the fault scenario to be recognized is combined to obtain the fault code corresponding to the fault scenario to be recognized as 100.

[0040] In one embodiment, the status information of each component corresponding to the fault scenario to be recognized is combined to obtain a fault code corresponding to the fault scenario to be recognized, including: According to the preset positions of the status information of each component corresponding to the fault scenario to be recognized in the fault code, the status information of each component corresponding to the fault scenario to be recognized is combined to obtain a fault code corresponding to the fault scenario to be recognized.

[0041] Specifically, in the process of combining the status information of each component corresponding to the fault scenario to be recognized in the embodiments of the present application, considering that different combination orders will lead to differences in the combination results, which will in turn affect the fault code corresponding to the fault scenario to be recognized. In order to accurately and effectively represent the current situation of the fault scenario to be recognized by the fault code, in the embodiments of the present application, according to the preset positions of the status information of each component corresponding to the fault scenario to be recognized in the fault code, the status information of each component corresponding to the fault scenario to be recognized is combined, so as to more accurately obtain the fault code corresponding to the fault scenario to be recognized. Optionally, the preset positions of the status information of each component corresponding to the fault scenario to be recognized in the fault code can be determined based on the importance or interaction degree of the association relationship between the faulty component and the dependent components, or can be determined based on other methods, which are not specifically limited in the embodiments of the present application.

[0042] In the method of the above embodiment, in the process of combining the status information of each component corresponding to the fault scenario to be recognized, considering that different combination orders will lead to differences in the combination results, in the embodiments of the present application, according to the preset positions of the status information of each component corresponding to the fault scenario to be recognized in the fault code, the status information of each component corresponding to the fault scenario to be recognized is combined, so that the finally obtained fault code can accurately represent the current situation of the fault scenario to be recognized, and can also make each fault scenario to be recognized correspond to a unique fault code, effectively improving the recognition efficiency and accuracy of the fault scenario.

[0043] In one embodiment, according to the fault code corresponding to the fault scenario to be recognized and a preset fault code set, the recognition result corresponding to the fault scenario to be recognized is determined, including: Matching the fault code corresponding to the fault scenario to be recognized with the preset fault code set to obtain a matching result; According to the matching result, the recognition result corresponding to the fault scenario to be recognized is determined.

[0044] Specifically, in the embodiments of the present application, after determining the fault code corresponding to the fault scenario to be identified, the fault code corresponding to the fault scenario to be identified is matched with a preset fault code set to obtain a matching result. Furthermore, based on the matching result, it is possible to quickly and accurately determine whether there is a fault code in the fault code set that needs attention and timely handling in the target system, realizing the accurate identification of the fault scenario of the target system, effectively overcoming the problem in the prior art that for each fault in the system, independent code needs to be developed separately for fault judgment and identification, and the overall program complexity is relatively high, and greatly reducing the code development volume.

[0045] In one embodiment, the fault code corresponding to the fault scenario to be identified is matched with a preset fault code set to obtain a matching result; according to the matching result, the identification result corresponding to the fault scenario to be identified is determined, including: In the case where the matching result is a matching failure, it is determined that there is no fault scenario in the target system; In the case where the matching result is a matching success, it is determined that there is a fault scenario in the target system.

[0046] Specifically, in the embodiments of the present application, the fault code corresponding to the fault scenario to be identified is matched with a preset fault code set. If the matching result is a matching failure, it indicates that there is no fault code in the fault code set that needs attention and timely handling in the target system, which also indicates that the target system is operating normally. If the matching result is a matching success, it indicates that there is a fault code in the fault code set that needs attention and timely handling in the target system, and the fault scenario needs to be migrated.

[0047] In one embodiment, after determining that there is a fault scenario in the target system in the case where the matching result is a matching success, it further includes: Performing a fault handling operation corresponding to the fault scenario in the target system.

[0048] Specifically, in the case where the matching result of the fault code corresponding to the fault scenario to be identified and the preset fault code set is a matching success, it indicates that there is a fault code in the fault code set that needs attention and timely handling in the target system, and a fault handling operation corresponding to the fault scenario can be performed in the target system, thereby realizing automated and intelligent fault handling.

[0049] In addition, it should be noted that in the embodiments of the present application, through the fault code, not only the description of different scenarios and the mapping of the disposal solutions are realized, and the accurate management and matching of the fault scenario and the fault disposal solution are realized with this coding as a bridge, but also the shielding of the fault can be realized through the fault code, realizing the standard docking with other systems, and the downstream system can be accessed without perception to realize automated and intelligent fault handling.

[0050] The method of the above embodiments shields faults through fault codes. Only the fault codes are needed to determine the corresponding handling measures, that is, the description of different scenarios and the mapping of disposal solutions are realized through fault codes. The downstream system can be accessed without perception to achieve automated and intelligent fault handling.

[0051] Exemplarily, as Figure 2 shown, an embodiment of the present application provides a method for identifying a fault scenario, and the specific process is as follows: The "data acquisition module" regularly reads the "fault scenario description database" to obtain all component information in the system. Optionally, after reading the component information, the operating status of each component can be further collected, and the component UID and the operating status of the component are combined into key-value pairs and written into the cache database.

[0052] The "fault scenario identification module" regularly reads the "fault scenario description database" to obtain each component corresponding to the fault scenario to be identified, obtains the status information of each component corresponding to the fault scenario to be identified from the cache database, and combines them to obtain the fault code corresponding to the fault scenario to be identified. Optionally, in the embodiment of the present application, the description of the scenario fault is expressed through the fault code. For example: Component A fails while the database relied on by Component A is normal, and the corresponding backup site system runs normally. This scenario can be expressed by "011" to represent the information of "Component A fails & database normal & backup site normal". That is, the fault scenario encoding is a string composed of 1 and 0 to represent a unique system fault. This string of numbers is called the fault code, and the fault code is unique in a system.

[0053] The "fault scenario identification module" generates a fault code and then matches it with a preset set of fault codes. If a fault code is matched, it means that the fault needs to be processed or other further measures need to be taken, so as to migrate the traffic to the backup node to keep the service uninterrupted and achieve fault transfer.

[0054] Exemplarily, the data structure in the fault scenario description database is schematically shown as follows: system: Represents the name of the business system; subsystem: Used to describe the subsystem information within the business system; system_name: Used to describe the name of the subsystem; core_resources: Used to describe the resource information relied on by the subsystem; compones: Used to describe component information; type: Describes the resource type of the component; uid: Describes the unique value of the resource, which can be an IP or a resource name, etc., and needs to be ensured to be unique; index: The position of the component's running status value in the fault code, which is required to be counted from 0; fid: A set of fault scenario codes. The running status of each component is represented by 0 or 1, where 0 indicates abnormal component status; 1 indicates normal component running status. (fid is the abbreviation of failure id). The fid that needs to be concerned about should be written in this part, that is, to form a fault code. When the fault scenario determines that this fault code is triggered, corresponding operations are performed. For example, "1101", "1011", "0111" are fault codes.

[0055] additional: Additional descriptions added for faults can be customized according to the implementation situation.

[0056] [{ "system": "Payment system", "subsystems": [{ "system_name": "Payment subsystem 01", "core_resources": { "compones": [{ "type": "POD", "uid": "xxxx", "index": 0 }, { "type": "POD", "uid": "xxxx", "index": 1 }, { "type": "TDSQL", "uid": "192.168.1.1:3306", "index": 2 }, { "type": "POD", "uid": "xxxx", "index": 3 }, } "fid": { "1101": {"additional": {"k1","v1",...}}, ​"1011": {"additional": {"k1","v1",...}}, "0111": {"additional": {"k1","v1",...}}, } }] }] The method of the above embodiments describes a fault scenario from multiple dimensions, reducing the complexity of the upstream and downstream systems. Thus, the fault description function can be accessed without the upstream and downstream systems being aware, realizing the unified management of complex fault scenarios, reducing the complexity of data collection, and flexibly adding or deleting fault scenarios without modifying the code, accurately and conveniently realizing the identification and processing of fault scenarios.

[0057] The following describes the fault scenario identification device provided by the present invention. The fault scenario identification device described below can be correspondingly referred to the fault scenario identification method described above. The fault scenario identification device of the embodiments of the present application is as Figure 3 shown and includes: An acquisition module 310, configured to acquire the status information of each component in the target system; A determination module 320, configured to determine the status information of each component corresponding to the fault scenario to be identified according to the component information corresponding to the fault scenario to be identified and the status information of each component in the target system; A processing module 330, configured to obtain the fault code corresponding to the fault scenario to be identified according to the status information of each component corresponding to the fault scenario to be identified; An identification module 340, configured to determine the identification result corresponding to the fault scenario to be identified according to the fault code corresponding to the fault scenario to be identified and a preset fault code set.

[0058] Optionally, the processing module 330 is specifically configured to: Combine the status information of each component corresponding to the fault scenario to be identified to obtain the fault code corresponding to the fault scenario to be identified.

[0059] Optionally, the processing module 330 is specifically configured to: According to the preset positions of the status information of each component corresponding to the fault scenario to be identified in the fault code, combine the status information of each component corresponding to the fault scenario to be identified to obtain the fault code corresponding to the fault scenario to be identified.

[0060] Optionally, the identification module 340 is specifically configured to: Match the fault code corresponding to the fault scenario to be identified with the preset fault code set to obtain a matching result; Determine the recognition result corresponding to the fault scenario to be recognized according to the matching result.

[0061] Optionally, the recognition module 340 is specifically configured to: When the matching result is a matching failure, determine that there is no fault scenario in the target system; When the matching result is a matching success, determine that there is a fault scenario in the target system.

[0062] Optionally, the recognition module 340 is further configured to: Execute the fault handling operation corresponding to the fault scenario in the target system.

[0063] Figure 4 FIG. illustrates a schematic physical structure diagram of an electronic device, which may include: a processor 410, a communication interface 420, a memory 430, and a communication bus 440. Among them, the processor 410, the communication interface 420, and the memory 430 complete mutual communication through the communication bus 440. The processor 410 can call the logical instructions in the memory 430 to execute the recognition method of the fault scenario, and the method includes: obtaining the status information of each component in the target system; determining the status information of each component corresponding to the fault scenario to be recognized according to the component information corresponding to the fault scenario to be recognized and the status information of each component in the target system; obtaining the fault code corresponding to the fault scenario to be recognized according to the status information of each component corresponding to the fault scenario to be recognized; determining the recognition result corresponding to the fault scenario to be recognized according to the fault code corresponding to the fault scenario to be recognized and the preset fault code set.

[0064] In addition, when the logical instructions in the above-mentioned memory 430 are implemented in the form of software function units and sold or used as an independent product, they can be stored in a computer-readable storage medium. Based on such an understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or a part of this technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of the present invention. The foregoing storage medium includes: various media such as a USB flash drive, a mobile hard disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a magnetic disk, or an optical disc that can store program codes.

[0065] On the other hand, the present invention also provides a computer program product, which includes a computer program that can be stored on a non-transitory computer-readable storage medium. When the computer program is executed by a processor, the computer can execute the method for identifying a fault scenario provided by each of the above methods. The method includes: obtaining the status information of each component in the target system; determining the status information of each component corresponding to the fault scenario to be identified according to the component information corresponding to the fault scenario to be identified and the status information of each component in the target system; obtaining the fault code corresponding to the fault scenario to be identified according to the status information of each component corresponding to the fault scenario to be identified; and determining the identification result corresponding to the fault scenario to be identified according to the fault code corresponding to the fault scenario to be identified and a preset set of fault codes.

[0066] In another aspect, the present invention also provides a non-transitory computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, it realizes the method for identifying a fault scenario provided by each of the above methods. The method includes: obtaining the status information of each component in the target system; determining the status information of each component corresponding to the fault scenario to be identified according to the component information corresponding to the fault scenario to be identified and the status information of each component in the target system; obtaining the fault code corresponding to the fault scenario to be identified according to the status information of each component corresponding to the fault scenario to be identified; and determining the identification result corresponding to the fault scenario to be identified according to the fault code corresponding to the fault scenario to be identified and a preset set of fault codes.

[0067] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed to multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment. A person of ordinary skill in the art can understand and implement it without creative labor.

[0068] Through the description of the above embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, it can also be implemented by hardware. Based on this understanding, the essence of the above technical solution, or the part that contributes to the prior art, can be embodied in the form of a software product. The computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disc, etc., and includes several instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in each embodiment or some parts of the embodiments.

[0069] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it; although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that they can still modify the technical solutions recorded in the foregoing embodiments, or perform equivalent replacements for some of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the various embodiments of the present invention.

Claims

1. A method for identifying a fault scenario, characterized in that: include: Obtain status information of each component in the target system; Determine the status information of each component corresponding to the fault scenario to be identified according to the component information corresponding to the fault scenario to be identified and the status information of each component in the target system; Obtaining a fault code corresponding to the fault scenario to be identified according to status information of each component corresponding to the fault scenario to be identified; According to the fault code corresponding to the fault scenario to be identified and a preset fault code set, an identification result corresponding to the fault scenario to be identified is determined.

2. The method for identifying a fault scenario according to claim 1, characterized in that: The obtaining, according to the status information of each component corresponding to the fault scenario to be identified, a fault code corresponding to the fault scenario to be identified, comprises: The status information of each component corresponding to the fault scenario to be identified is combined to obtain a fault code corresponding to the fault scenario to be identified.

3. The method for identifying a fault scenario according to claim 1, characterized in that: The combining the status information of each component corresponding to the fault scenario to be identified to obtain the fault code corresponding to the fault scenario to be identified includes: According to the preset position of the status information of each component corresponding to the fault scenario to be identified in the fault code, the status information of each component corresponding to the fault scenario to be identified is combined to obtain the fault code corresponding to the fault scenario to be identified.

4. The method for identifying a fault scenario according to any one of claims 1 to 3, characterized in that: The determining, according to the fault code corresponding to the fault scenario to be identified and a preset fault code set, an identification result corresponding to the fault scenario to be identified includes: Matching the fault code corresponding to the fault scenario to be identified with a preset fault code set to obtain a matching result; According to the matching result, an identification result corresponding to the fault scenario to be identified is determined.

5. The method for identifying a fault scenario according to claim 4, characterized in that: The fault code corresponding to the fault scenario to be identified is matched with a preset fault code set to obtain a matching result; Determining, according to the matching result, an identification result corresponding to the fault scenario to be identified, including: In the case where the matching result is a matching failure, determining that the fault scenario does not exist in the target system; When the matching result is a successful match, it is determined that the fault scenario exists in the target system.

6. The method for identifying a fault scenario according to claim 5, characterized in that: In the case where the matching result is a successful match, after determining that the fault scenario exists in the target system, the method further includes: Execute a fault handling operation corresponding to the fault scenario in the target system.

7. A fault scene identification device, characterized in that: include: The acquisition module is used to obtain the status information of each component in the target system; A determination module, configured to determine the status information of each component corresponding to the fault scenario to be identified according to the component information corresponding to the fault scenario to be identified and the status information of each component in the target system; A processing module, configured to obtain a fault code corresponding to the fault scenario to be identified according to status information of each component corresponding to the fault scenario to be identified; The identification module is used to determine the identification result corresponding to the fault scenario to be identified according to the fault code corresponding to the fault scenario to be identified and a preset fault code set.

8. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the program, the method for identifying the fault scenario according to any one of claims 1 to 6 is implemented.

9. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method for identifying a fault scenario as described in any one of claims 1 to 6 is implemented.

10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the method for identifying a fault scenario as described in any one of claims 1 to 6 is implemented.

Images