CN112559233A - Method, device, equipment and computer readable medium for identifying fault type - Google Patents
Method, device, equipment and computer readable medium for identifying fault type Download PDFInfo
- Publication number
- CN112559233A CN112559233A CN202011489743.1A CN202011489743A CN112559233A CN 112559233 A CN112559233 A CN 112559233A CN 202011489743 A CN202011489743 A CN 202011489743A CN 112559233 A CN112559233 A CN 112559233A
- Authority
- CN
- China
- Prior art keywords
- error code
- file
- identifying
- type
- existing file
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/079—Root cause analysis, i.e. error or fault diagnosis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F18/00—Pattern recognition
- G06F18/20—Analysing
- G06F18/24—Classification techniques
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Life Sciences & Earth Sciences (AREA)
- Biomedical Technology (AREA)
- Health & Medical Sciences (AREA)
- Quality & Reliability (AREA)
- Artificial Intelligence (AREA)
- Bioinformatics & Cheminformatics (AREA)
- Bioinformatics & Computational Biology (AREA)
- Computer Vision & Pattern Recognition (AREA)
- Evolutionary Biology (AREA)
- Evolutionary Computation (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention discloses a method, a device, equipment and a computer readable medium for identifying fault types, and relates to the technical field of computers. One embodiment of the method comprises: updating an original error code in a configuration file by using a preset classification error code, and establishing a new and old error code comparison table, wherein the new and old error code comparison table is established according to the classification error code and the original error code; replacing the original error codes in the existing file with the classified error codes according to the new and old error code comparison table; scanning the replaced existing file, and identifying the fault type of the existing file with the fault based on the classification error code. This embodiment can improve the speed and accuracy of determining the type of fault.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a method, an apparatus, a device, and a computer readable medium for identifying a fault type.
Background
The error is a phenomenon that software and hardware cannot normally operate when the software and hardware are used. Because the types of errors are many, the system sets error codes for distinguishing the errors, and if the software and the hardware have errors in operation, the software and the hardware are judged and identified through the original setting in the software and the hardware and then are displayed to an operator through an error code display mode.
In the process of implementing the invention, the inventor finds that at least the following problems exist in the prior art: the existing error code can only be positioned to a module which possibly has problems, and the fault type of the problems cannot be clarified. A combination of logs and error codes is required to know the type of failure that is problematic. The above-described manner of determining the type of fault that has a problem is slow and less accurate.
Disclosure of Invention
In view of this, embodiments of the present invention provide a method, an apparatus, a device, and a computer-readable medium for identifying a fault type, which can improve the speed and accuracy of determining the fault type.
To achieve the above object, according to an aspect of an embodiment of the present invention, there is provided a method of identifying a fault type, including:
updating an original error code in a configuration file by using a preset classification error code, and establishing a new and old error code comparison table, wherein the new and old error code comparison table is established according to the classification error code and the original error code;
replacing the original error codes in the existing file with the classified error codes according to the new and old error code comparison table;
scanning the replaced existing file, and identifying the fault type of the existing file with the fault based on the classification error code.
The configuration file comprises the original error code and the location problem position of the original error code.
Before the step of updating the original error codes in the configuration file by the preset classification error codes and establishing the new and old error code comparison table, the method further comprises the following steps:
and presetting the classification error codes according to a preset mode.
The preset mode includes a simple factory mode.
The preset mode comprises a policy mode.
The preset classification error codes comprise one or more of database error codes, logic error codes and third-party error codes.
The preset classification error code is generated by an error code generation interface.
The method for updating the original error codes in the configuration file by the preset classification error codes and establishing a new and old error code comparison table comprises the following steps:
establishing an error code updating table according to the preset classification error codes and the original error codes;
and constructing a key value pair based on the corresponding relation between the classified error codes and the original error codes in the error code updating table, and taking the key value pair as the new and old error code comparison table.
Replacing the original error code in the existing file with the classified error code according to the new and old error code comparison table, including:
and replacing the original error codes in the existing file by the classified error codes of the new and old error code comparison table in the matching file according to the type of the existing file.
Replacing the original error codes in the existing file by the classified error codes of the new and old error code comparison table in the matched file according to the type of the existing file, wherein the classified error codes comprise:
and the type of the existing file is java file and/or property file, and the classification error codes of the new and old error code comparison table in the first preset matching file replace the original error codes in the existing file.
The first predetermined matching file is FileMatchRuleEnum.
Replacing the original error codes in the fault file by the classified error codes of the new and old error code comparison table in the matched file according to the type of the existing file, wherein the method comprises the following steps:
the type of the existing file is java file and/or property file and the existing file comprises an ExcepitonHandler file, and the classification error codes of the new and old error code comparison table in the second matching file replace the original error codes in the existing file.
The second predetermined matching file is errorcode matchrule enum.
Replacing the original error codes in the existing file by the classified error codes of the new and old error code comparison table in the matched file according to the type of the existing file, wherein the classified error codes comprise:
and the type of the existing file is a preset type, and the classification error code of the new error code and the old error code comparison table in the third matching file replaces the original error code in the existing file.
The third predetermined matching file is errorcode matchrule enum.
The scanning the replaced existing file comprises the following steps:
and scanning the replaced existing file according to lines.
The scanning the replaced existing file, and identifying the fault type of the existing file with the fault based on the classification error code, including:
scanning the replaced existing file to obtain a classification error code in the replaced existing file;
identifying a failure type of the existing file that failed based on the learned classification error code.
According to a second aspect of the embodiments of the present invention, there is provided an apparatus for identifying a fault type, including:
the establishing module is used for updating an original error code in a configuration file by using a preset classification error code and establishing a new and old error code comparison table, wherein the new and old error code comparison table is established according to the classification error code and the original error code;
the replacing module is used for replacing the original error codes in the existing file with the classified error codes according to the new and old error code comparison table;
and the identification module is used for scanning the replaced existing file and identifying the fault type of the existing file with the fault based on the classification error code.
According to a third aspect of embodiments of the present invention, there is provided an electronic device that identifies a type of a fault, including:
one or more processors;
a storage device for storing one or more programs,
when executed by the one or more processors, cause the one or more processors to implement the method as described above.
According to a fourth aspect of embodiments of the present invention, there is provided a computer readable medium, on which a computer program is stored, which when executed by a processor, implements the method as described above.
One embodiment of the above invention has the following advantages or benefits: updating an original error code in a configuration file by using a preset classification error code, and establishing a new and old error code comparison table, wherein the new and old error code comparison table is established according to the classification error code and the original error code; replacing the original error codes in the existing file with the classified error codes according to the new and old error code comparison table; scanning the replaced existing file, and identifying the fault type of the existing file with the fault based on the classification error code. The fault type is identified according to the classified error code, so that the speed and the accuracy of determining the fault type can be improved.
Further effects of the above-mentioned non-conventional alternatives will be described below in connection with the embodiments.
Drawings
The drawings are included to provide a better understanding of the invention and are not to be construed as unduly limiting the invention. Wherein:
FIG. 1 is a schematic diagram of the main flow of a method of identifying a fault type according to an embodiment of the invention;
FIG. 2 is a diagram illustrating a classification error code according to an embodiment of the present invention;
FIG. 3 is a flowchart illustrating the process of creating a new error code and old error code comparison table according to an embodiment of the present invention;
FIG. 4 is a schematic flow chart illustrating the process of identifying the failure type of an existing file that has failed according to an embodiment of the present invention;
fig. 5 is a schematic diagram of the main structure of an apparatus for identifying a fault type according to an embodiment of the present invention;
FIG. 6 is an exemplary system architecture diagram in which embodiments of the present invention may be employed;
fig. 7 is a schematic block diagram of a computer system suitable for use in implementing a terminal device or server of an embodiment of the invention.
Detailed Description
Exemplary embodiments of the present invention are described below with reference to the accompanying drawings, in which various details of embodiments of the invention are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
Currently, the error code in the system is generally defined in the format: module name-number. The error code can only be positioned to a module with a problem, the fault type with the problem cannot be determined, and the fault type with the problem can be known only by combining the log and the error code when the problem is checked. The above-described manner of determining the type of problem fault is slow and less accurate.
With the development of services, project modules are gradually increased, and when error codes are defined, a set of unified standards is not provided, so that the difficulty in troubleshooting after a fault occurs is increased. In order to quickly locate the fault type, a unified error code execution standard is established. In order to implement the new standard, the code needs to be reconstructed, replacing the error codes that already existed before. Because the whole engineering code amount is large, no uniform processing tool is used for replacing the error codes existing before, and the manual replacement has the problems of large code amount and repeated error codes.
Therefore, there are the following technical problems: the mode of determining the fault type with the problems is slow and low in accuracy.
In order to solve the problem of determining the fault type, the speed is low and the accuracy is low, and the following technical scheme in the embodiment of the invention can be adopted.
Referring to fig. 1, fig. 1 is a schematic diagram of a main flow of a method for identifying a failure type according to an embodiment of the present invention, in which a classification error code is used to replace an original error code to identify a failure type of an existing file that has failed. As shown in fig. 1, the method specifically comprises the following steps:
s101, updating original error codes in a configuration file by using preset classification error codes, and establishing a new and old error code comparison table, wherein the new and old error code comparison table is established according to the classification error codes and the original error codes.
Considering that the fault type cannot be directly identified by the existing error code, in the embodiment of the invention, the existing error code is replaced by the classified error code. In the embodiment of the present invention, the existing error code is referred to as the original error code.
The original error code is stored in a configuration file. In one embodiment of the invention, the configuration file includes the original error code and the location of the positioning problem of the original error code. As an example, the original error code is 001, and the location problem location of the original error code is the first module.
In one embodiment of the invention, the configuration file is a Properties file. The Properties file is a property file that stores data in a key value format and can be read by Properties class.
In the embodiment of the present invention, before updating the original error codes in the configuration file, the classification error codes need to be preset according to a preset mode. The classified error code is an error code set according to an error type. The error type can be directly known based on the classification error code.
In one embodiment of the invention, the preset mode may include a simple factory mode and a policy mode.
The simple factory mode belongs to a creativity mode, also called a static factory method mode, which belongs to a class creativity mode. In the simple factory mode, instances of different classes can be returned depending on the parameters. Simple factory patterns specifically define a class to be responsible for creating instances of other classes, the created instances typically all having a common parent class.
The policy model is a behavior model which defines a series of algorithms and encapsulates each algorithm, and the algorithms can be replaced with each other. The policy model allows the algorithm to be varied independently of the customer using it.
In the embodiment of the invention, the classification error code generation rule is preset according to a simple factory mode or a strategy mode. And various classification error code generation rules are supported, and the extension of the classification error code generation rules can be supported. That is, according to the preset pattern, the classification error code can be preset based on the classification error code generation rule.
In the embodiment of the invention, the preset classification error code is generated by the error code generation interface. That is, a preset classification error code is generated through the error code generation interface. The error code generation interface may set the corresponding classification error code based on the service scenario.
As one example, the predetermined classification error codes include one or more of a database error code, a logical error code, and a third party error code.
The database error code is used to identify a database error. The logical error code is used to identify a logical error. The third party error code is used to identify a third party error.
Referring to fig. 2, fig. 2 is a diagram illustrating a classification error code according to an embodiment of the present invention. The errorcodecocontext is defined in fig. 2 for generating the classification error code.
In fig. 2, the error code generation interface generates three predefined subclasses of classified error codes: DbErrorCode, LogicErrorCode and ThirdErrorCode. Wherein, DbErrorCode belongs to database error code; the LogicErrorCode belongs to a logical error code; third party error codes.
Illustratively, the database error code is the XDB beginning; the logical error code is the beginning of the YBL; the third party error code is the beginning of the XAC.
Referring to fig. 3, fig. 3 is a schematic flowchart of a process for establishing a new error code comparison table according to an embodiment of the present invention, which specifically includes the following steps:
s301, establishing an error code updating table according to the preset classification error codes and the original error codes.
To replace the original error codes, an error code update table may be established according to the predetermined classification error codes and the original error codes.
The corresponding relation between the preset classification error code and the original error code is preset. The correspondence may be one-to-many, many-to-many, or many-to-one. And establishing an error code updating table based on the corresponding relation. As an embodiment, the error code update table is an excel table.
S302, based on the corresponding relation between the classified error codes and the original error codes in the error code updating table, key value pairs are constructed, and the key value pairs are used as a new error code comparison table and an old error code comparison table.
In consideration of the requirement of extension without modifying the existing code or data, a key value pair mode can be adopted to establish a new and old error code comparison table.
The error code update table includes the corresponding relationship between the classification error code and the original error code. Then, based on the corresponding relationship between the classification error code and the original error code in the error code update table, a key-value pair is constructed. Then, the key value pair is used as a new and old error code comparison table. As an example, key in the key pair is the original error code and value in the key pair is the classified error code.
In the embodiment of fig. 3, the key value pair is used to construct the new and old error code comparison table, which is suitable for expansion without modifying the existing code or data.
S102, replacing the original error codes in the existing file with the classified error codes according to the new and old error code comparison table.
The new and old error code comparison table includes key value pairs, i.e. the corresponding relationship between the original error codes and the classified error codes. And then, according to the type of the existing file, replacing the original error codes in the existing file by the classification error codes of the new and old error code comparison table in the matching file. Wherein the existing file includes existing code or data.
Specifically, according to the type of the existing file, the classification error code matching the new and old error code comparison tables in the file can be determined, and then the original error code in the existing file is replaced by the classification error code. Wherein, the matching file comprises a new error code and an old error code comparison table.
In specific implementation, the original error codes can be replaced by the classified error codes of the new and old error code comparison table in different matching files according to different existing file types. Thereby improving the replacement efficiency.
In one embodiment of the present invention, the type of the existing file is java file and/or property file, and the classification error code of the new and old error code comparison table in the first preset matching file replaces the original error code in the existing file.
Wherein, the java file is a file with a suffix name of java. A property file is a file with the suffix name property. The first pre-defined matching file is FileMatchRuleEnum.
In one embodiment of the invention, the type of the existing file is java file and/or property file and the existing file comprises an ExcepitonHandler file, and the classification error codes of the new and old error code comparison table in the second matching file replace the original error codes in the existing file.
Wherein the ExcepitonHandler file is used for capturing the exception in the program and generating the dump file. The second pre-set match file is errorcode matchrule enum.
In one embodiment of the present invention, for an existing file of a predetermined type, i.e., the type of the existing file is a predetermined type, the classification error codes of the old and new error code comparison tables in the third matching file replace the original error codes in the existing file. The third pre-set match file is errorcode matchrule enum.
That is, a preset type may be set, and then the original error code may be replaced with the classified error code of the new and old error code comparison table in the third preset matching file.
S103, scanning the replaced existing file, and identifying the fault type of the existing file with the fault based on the classification error code.
After replacing the original error code with the classification error code, the error code in the existing file is the classification error code. Then, after the failure occurs, the replaced existing file is scanned, and based on the classification error code, the failure type of the existing file with the failure can be identified.
Referring to fig. 4, fig. 4 is a schematic flowchart of identifying a failure type of an existing file that has failed according to an embodiment of the present invention, which specifically includes the following steps:
s401, scanning the replaced existing file, and obtaining the classification error code in the replaced existing file.
In order to know the classification error code, the replaced existing file needs to be scanned. Then, the classification error code in the existing file after replacement is known.
In one embodiment of the present invention, the replaced existing document may be scanned in lines in order to improve the accuracy of the scan.
S402, based on the obtained classification error codes, identifying the fault type of the existing file with the fault.
Since the classification error code is used to identify the type of failure, the type of failure of an existing file that has failed can be quickly identified based on the learned classification error code.
In the embodiment of fig. 4, by scanning an existing file, the type of failure of the existing file that has failed can be quickly identified based on the classification error code.
In the above embodiment, the original error codes in the configuration file are updated with the preset classification error codes, and a new and old error code comparison table is established, where the new and old error code comparison table is established according to the classification error codes and the original error codes; replacing the original error codes in the existing file with the classified error codes according to the new and old error code comparison table; scanning the replaced existing file, and identifying the fault type of the existing file with the fault based on the classification error code. The fault type is identified according to the classified error code, so that the speed and the accuracy of determining the fault type can be improved.
The embodiment of the invention can be applied to PLPM systems. The PLPM system is mainly used for managing the whole process of loan.
The PLPM system has been operated stably for many years, with the development of services, the code quantity is huge, the whole java code packet has about 500 million, and if the error code is replaced manually, the time consumption is long and the replacement error occurs. By adopting the technical scheme in the embodiment of the invention, the error code can be replaced in a short time, and the speed and the accuracy for identifying the fault type can be further improved.
Referring to fig. 5, fig. 5 is a schematic diagram of a main structure of an apparatus for identifying a fault type according to an embodiment of the present invention, where the apparatus for identifying a fault type may implement a method for identifying a fault type, and as shown in fig. 5, the apparatus for identifying a fault type specifically includes:
an establishing module 501, configured to update an original error code in a configuration file with a preset classification error code, and establish a new and old error code comparison table, where the new and old error code comparison table is established according to the classification error code and the original error code;
a replacing module 502, configured to replace the original error code in the existing file with the classified error code according to the new and old error code comparison table;
the identifying module 503 is configured to scan the replaced existing file, and identify a failure type of the existing file that has a failure based on the classification error code.
In one embodiment of the invention, the configuration file comprises the original error code and the location of the positioning problem of the original error code.
In an embodiment of the present invention, the establishing module 501 is further configured to preset the classification error code according to a preset mode.
In one embodiment of the invention, the preset mode comprises a simple factory mode.
In one embodiment of the invention, the preset mode comprises a policy mode.
In one embodiment of the present invention, the predetermined classification error codes include one or more of a database error code, a logical error code, and a third party error code.
In one embodiment of the present invention, the predetermined classification error code is generated by an error code generation interface.
In an embodiment of the present invention, the establishing module 501 is specifically configured to establish an error code update table according to the preset classification error code and the original error code;
and constructing a key value pair based on the corresponding relation between the classified error codes and the original error codes in the error code updating table, and taking the key value pair as the new and old error code comparison table.
In an embodiment of the present invention, the replacing module 502 is specifically configured to replace the original error codes in the existing file with the classification error codes matching the new and old error code comparison tables in the file according to the type of the existing file.
In an embodiment of the present invention, the replacing module 502 is specifically configured to replace the original error codes in the existing file with the classification error codes of the new and old error code comparison table in the first preset matching file, where the type of the existing file is java file and/or proprietary file.
In one embodiment of the present invention, the first predetermined matching file is filematchrule enum.
In an embodiment of the present invention, the replacing module 502 is specifically configured to replace the original error codes in the existing file with the classification error codes of the new and old error code comparison table in the second matching file, where the type of the existing file is java file and/or property file and the existing file includes an excepton handler file.
In one embodiment of the invention, the second predetermined matching file is errorcodematchrule enum.
In an embodiment of the present invention, the replacing module 502 is specifically configured to replace the original error codes in the existing file with the classified error codes of the new and old error code comparison table in the third matching file, where the type of the existing file is a preset type.
In one embodiment of the invention, the third predetermined matching file is errorcodematchrule enum.
In an embodiment of the present invention, the replacing module 503 is specifically configured to scan the replaced existing file by lines.
In an embodiment of the present invention, the replacing module 503 is specifically configured to scan the replaced existing file, and obtain the classification error code in the replaced existing file;
identifying a failure type of the existing file that failed based on the learned classification error code.
Fig. 6 illustrates an exemplary system architecture 600 to which the method of identifying a fault type or the apparatus for identifying a fault type of the embodiments of the present invention may be applied.
As shown in fig. 6, the system architecture 600 may include terminal devices 601, 602, 603, a network 604, and a server 605. The network 604 serves to provide a medium for communication links between the terminal devices 601, 602, 603 and the server 605. Network 604 may include various types of connections, such as wire, wireless communication links, or fiber optic cables, to name a few.
A user may use the terminal devices 601, 602, 603 to interact with the server 605 via the network 604 to receive or send messages or the like. The terminal devices 601, 602, 603 may have installed thereon various communication client applications, such as shopping applications, web browser applications, search applications, instant messaging tools, mailbox clients, social platform software, etc. (by way of example only).
The terminal devices 601, 602, 603 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like.
The server 605 may be a server providing various services, such as a background management server (for example only) providing support for shopping websites browsed by users using the terminal devices 601, 602, 603. The backend management server may analyze and perform other processing on the received data such as the product information query request, and feed back a processing result (for example, target push information, product information — just an example) to the terminal device.
It should be noted that the method for identifying the fault type provided by the embodiment of the present invention is generally executed by the server 605, and accordingly, the apparatus for identifying the fault type is generally disposed in the server 605.
It should be understood that the number of terminal devices, networks, and servers in fig. 6 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
Referring now to FIG. 7, shown is a block diagram of a computer system 700 suitable for use with a terminal device implementing an embodiment of the present invention. The terminal device shown in fig. 7 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present invention.
As shown in fig. 7, the computer system 700 includes a Central Processing Unit (CPU)701, which can perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM)702 or a program loaded from a storage section 708 into a Random Access Memory (RAM) 703. In the RAM 703, various programs and data necessary for the operation of the system 700 are also stored. The CPU 701, the ROM 702, and the RAM 703 are connected to each other via a bus 704. An input/output (I/O) interface 705 is also connected to bus 704.
The following components are connected to the I/O interface 705: an input portion 706 including a keyboard, a mouse, and the like; an output section 707 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage section 708 including a hard disk and the like; and a communication section 709 including a network interface card such as a LAN card, a modem, or the like. The communication section 709 performs communication processing via a network such as the internet. A drive 710 is also connected to the I/O interface 705 as needed. A removable medium 711 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 710 as necessary, so that a computer program read out therefrom is mounted into the storage section 708 as necessary.
In particular, according to the embodiments of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program can be downloaded and installed from a network through the communication section 709, and/or installed from the removable medium 711. The computer program performs the above-described functions defined in the system of the present invention when executed by the Central Processing Unit (CPU) 701.
It should be noted that the computer readable medium shown in the present invention can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present invention, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present invention, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The modules described in the embodiments of the present invention may be implemented by software or hardware. The described modules may also be provided in a processor, which may be described as: a processor includes an establishment module, a replacement module, and an identification module. Where the names of these modules do not in some cases constitute a limitation of the module itself, for example, the creation module may also be described as "for updating the original error codes in the configuration file with preset classification error codes, and creating a new and old error code comparison table, which is created from the classification error codes and the original error codes".
As another aspect, the present invention also provides a computer-readable medium that may be contained in the apparatus described in the above embodiments; or may be separate and not incorporated into the device. The computer readable medium carries one or more programs which, when executed by a device, cause the device to comprise:
updating an original error code in a configuration file by using a preset classification error code, and establishing a new and old error code comparison table, wherein the new and old error code comparison table is established according to the classification error code and the original error code;
replacing the original error codes in the existing file with the classified error codes according to the new and old error code comparison table;
scanning the replaced existing file, and identifying the fault type of the existing file with the fault based on the classification error code.
According to the technical scheme of the embodiment of the invention, the original error codes in the configuration file are updated by the preset classification error codes, and a new and old error code comparison table is established according to the classification error codes and the original error codes; replacing the original error codes in the existing file with the classified error codes according to the new and old error code comparison table; scanning the replaced existing file, and identifying the fault type of the existing file with the fault based on the classification error code. The fault type is identified according to the classified error code, so that the speed and the accuracy of determining the fault type can be improved.
The above-described embodiments should not be construed as limiting the scope of the invention. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions can occur, depending on design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (20)
1. A method of identifying a type of fault, comprising:
updating an original error code in a configuration file by using a preset classification error code, and establishing a new and old error code comparison table, wherein the new and old error code comparison table is established according to the classification error code and the original error code;
replacing the original error codes in the existing file with the classified error codes according to the new and old error code comparison table;
scanning the replaced existing file, and identifying the fault type of the existing file with the fault based on the classification error code.
2. The method of identifying a type of fault as recited in claim 1, wherein the configuration file includes an original error code and a location problem location of the original error code.
3. The method for identifying fault types according to claim 1, wherein before updating the original error codes in the configuration file with the preset classification error codes and building the new and old error code comparison table, further comprising:
and presetting the classification error codes according to a preset mode.
4. The method of identifying a type of fault as recited in claim 3, wherein the preset mode comprises a simple factory mode.
5. The method of identifying a type of fault as recited in claim 3, wherein the preset pattern comprises a policy pattern.
6. The method for identifying fault types according to claim 1, wherein the preset classification error codes comprise one or more of database error codes, logic error codes and third party error codes.
7. The method for identifying fault types according to claim 1, wherein the preset classification error code is generated by an error code generation interface.
8. The method for identifying fault types according to claim 1, wherein the updating original error codes in the configuration file with the preset classification error codes and establishing the new and old error code comparison table comprises:
establishing an error code updating table according to the preset classification error codes and the original error codes;
and constructing a key value pair based on the corresponding relation between the classified error codes and the original error codes in the error code updating table, and taking the key value pair as the new and old error code comparison table.
9. The method for identifying fault types according to claim 1, wherein the step of replacing the original error codes in the existing file with classified error codes according to the new and old error code comparison table comprises:
and replacing the original error codes in the existing file by the classified error codes of the new and old error code comparison table in the matching file according to the type of the existing file.
10. The method for identifying a fault type according to claim 9, wherein replacing the original error codes in the existing file with the classification error codes matching the new and old error code comparison tables in the file according to the type of the existing file comprises:
and the type of the existing file is java file and/or property file, and the classification error codes of the new and old error code comparison table in the first preset matching file replace the original error codes in the existing file.
11. The method of identifying a fault type of claim 10, wherein the first predetermined matching file is filematchrule enum.
12. The method for identifying a fault type according to claim 9, wherein the step of replacing the original error codes in the fault file with the classified error codes matching the new and old error code comparison tables in the file according to the type of the existing file comprises:
the type of the existing file is java file and/or property file and the existing file comprises an ExcepitonHandler file, and the classification error codes of the new and old error code comparison table in the second matching file replace the original error codes in the existing file.
13. The method of identifying a fault type of claim 12, wherein the second predetermined matching file is errorcode matchrule enum.
14. The method for identifying a fault type according to claim 9, wherein replacing the original error codes in the existing file with the classification error codes matching the new and old error code comparison tables in the file according to the type of the existing file comprises:
and the type of the existing file is a preset type, and the classification error code of the new error code and the old error code comparison table in the third matching file replaces the original error code in the existing file.
15. The method of identifying a fault type of claim 14, wherein the third predetermined matching file is errorcode matchrule enum.
16. The method for identifying a fault type according to claim 1, wherein the scanning the replaced existing file comprises:
and scanning the replaced existing file according to lines.
17. The method for identifying a failure type according to claim 1, wherein the scanning the replaced existing file to identify the failure type of the existing file having a failure based on the classification error code comprises:
scanning the replaced existing file to obtain a classification error code in the replaced existing file;
identifying a failure type of the existing file that failed based on the learned classification error code.
18. An apparatus for identifying a type of fault, comprising:
the establishing module is used for updating an original error code in a configuration file by using a preset classification error code and establishing a new and old error code comparison table, wherein the new and old error code comparison table is established according to the classification error code and the original error code;
the replacing module is used for replacing the original error codes in the existing file with the classified error codes according to the new and old error code comparison table;
and the identification module is used for scanning the replaced existing file and identifying the fault type of the existing file with the fault based on the classification error code.
19. An electronic device for identifying a type of fault, comprising:
one or more processors;
a storage device for storing one or more programs,
when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-17.
20. A computer-readable medium, on which a computer program is stored, which, when being executed by a processor, carries out the method according to any one of claims 1-17.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011489743.1A CN112559233B (en) | 2020-12-14 | 2020-12-14 | Method, device, equipment and computer readable medium for identifying fault type |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011489743.1A CN112559233B (en) | 2020-12-14 | 2020-12-14 | Method, device, equipment and computer readable medium for identifying fault type |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112559233A true CN112559233A (en) | 2021-03-26 |
| CN112559233B CN112559233B (en) | 2023-01-10 |
Family
ID=75064100
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011489743.1A Active CN112559233B (en) | 2020-12-14 | 2020-12-14 | Method, device, equipment and computer readable medium for identifying fault type |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112559233B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117235107A (en) * | 2023-11-10 | 2023-12-15 | 恒生电子股份有限公司 | Data access processing method and device, electronic equipment and storage medium |
Citations (18)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070022321A1 (en) * | 2005-07-07 | 2007-01-25 | Mediatek Incorporation | Exception analysis methods and systems |
| CN102361014A (en) * | 2011-10-20 | 2012-02-22 | 上海大学 | State monitoring and fault diagnosis method for large-scale semiconductor manufacture process |
| US8336030B1 (en) * | 2009-09-11 | 2012-12-18 | The Mathworks, Inc. | System and method for coding standard testing |
| US20140109065A1 (en) * | 2012-10-17 | 2014-04-17 | International Business Machines Corporation | Identifying errors using context based class names |
| CN103970997A (en) * | 2014-05-06 | 2014-08-06 | 南昌华梦达航空科技发展有限公司 | Method for rapidly diagnosing unmanned helicopter sensor faults |
| US20150019916A1 (en) * | 2013-07-11 | 2015-01-15 | Empirix Inc. | System and method for identifying problems on a network |
| US8978012B1 (en) * | 2008-03-28 | 2015-03-10 | Symantec Operating Corporation | Method and system for error reporting and correction in transaction-based applications |
| BR102015015690A2 (en) * | 2014-07-02 | 2016-01-05 | Schneider Electric Ind Sas | modular remote equipment |
| US20160098310A1 (en) * | 2014-10-07 | 2016-04-07 | International Business Machines Corporation | Device driver error isolation on devices wired via fsi chained interface |
| US20170249206A1 (en) * | 2016-02-29 | 2017-08-31 | Seagate Technology Llc | On-the-fly error detection algorithm during retry procedure |
| CN108109287A (en) * | 2017-12-29 | 2018-06-01 | 深圳怡化电脑股份有限公司 | Method, apparatus, equipment and the storage medium reported for withdrawal device Errors |
| CN108920314A (en) * | 2018-06-26 | 2018-11-30 | 郑州云海信息技术有限公司 | A kind of faulty hardware localization method, device, system and readable storage medium storing program for executing |
| US20180357558A1 (en) * | 2017-06-08 | 2018-12-13 | International Business Machines Corporation | Facilitating classification of equipment failure data |
| US20190155722A1 (en) * | 2017-11-20 | 2019-05-23 | Cognizant Technology Solutions India Pvt. Ltd. | System and method for predicting performance failures in a computer program |
| CN110347560A (en) * | 2019-07-19 | 2019-10-18 | 深圳前海微众银行股份有限公司 | Abnormal prompt method, apparatus, system, equipment and the medium of big data product |
| CN110413490A (en) * | 2019-08-01 | 2019-11-05 | 北京百度网讯科技有限公司 | Determine method, the error message code classification method and device of type of error message |
| US20200159622A1 (en) * | 2018-11-19 | 2020-05-21 | Hewlett Packard Enterprise Development Lp | Rule based failure addressing |
| CN112039706A (en) * | 2020-09-01 | 2020-12-04 | 三星电子（中国）研发中心 | Fault processing method, device, equipment and storage medium |
-
2020
- 2020-12-14 CN CN202011489743.1A patent/CN112559233B/en active Active
Patent Citations (18)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070022321A1 (en) * | 2005-07-07 | 2007-01-25 | Mediatek Incorporation | Exception analysis methods and systems |
| US8978012B1 (en) * | 2008-03-28 | 2015-03-10 | Symantec Operating Corporation | Method and system for error reporting and correction in transaction-based applications |
| US8336030B1 (en) * | 2009-09-11 | 2012-12-18 | The Mathworks, Inc. | System and method for coding standard testing |
| CN102361014A (en) * | 2011-10-20 | 2012-02-22 | 上海大学 | State monitoring and fault diagnosis method for large-scale semiconductor manufacture process |
| US20140109065A1 (en) * | 2012-10-17 | 2014-04-17 | International Business Machines Corporation | Identifying errors using context based class names |
| US20150019916A1 (en) * | 2013-07-11 | 2015-01-15 | Empirix Inc. | System and method for identifying problems on a network |
| CN103970997A (en) * | 2014-05-06 | 2014-08-06 | 南昌华梦达航空科技发展有限公司 | Method for rapidly diagnosing unmanned helicopter sensor faults |
| BR102015015690A2 (en) * | 2014-07-02 | 2016-01-05 | Schneider Electric Ind Sas | modular remote equipment |
| US20160098310A1 (en) * | 2014-10-07 | 2016-04-07 | International Business Machines Corporation | Device driver error isolation on devices wired via fsi chained interface |
| US20170249206A1 (en) * | 2016-02-29 | 2017-08-31 | Seagate Technology Llc | On-the-fly error detection algorithm during retry procedure |
| US20180357558A1 (en) * | 2017-06-08 | 2018-12-13 | International Business Machines Corporation | Facilitating classification of equipment failure data |
| US20190155722A1 (en) * | 2017-11-20 | 2019-05-23 | Cognizant Technology Solutions India Pvt. Ltd. | System and method for predicting performance failures in a computer program |
| CN108109287A (en) * | 2017-12-29 | 2018-06-01 | 深圳怡化电脑股份有限公司 | Method, apparatus, equipment and the storage medium reported for withdrawal device Errors |
| CN108920314A (en) * | 2018-06-26 | 2018-11-30 | 郑州云海信息技术有限公司 | A kind of faulty hardware localization method, device, system and readable storage medium storing program for executing |
| US20200159622A1 (en) * | 2018-11-19 | 2020-05-21 | Hewlett Packard Enterprise Development Lp | Rule based failure addressing |
| CN110347560A (en) * | 2019-07-19 | 2019-10-18 | 深圳前海微众银行股份有限公司 | Abnormal prompt method, apparatus, system, equipment and the medium of big data product |
| CN110413490A (en) * | 2019-08-01 | 2019-11-05 | 北京百度网讯科技有限公司 | Determine method, the error message code classification method and device of type of error message |
| CN112039706A (en) * | 2020-09-01 | 2020-12-04 | 三星电子（中国）研发中心 | Fault processing method, device, equipment and storage medium |
Non-Patent Citations (3)
| Title |
|---|
| LAZAR I 等: ""Rapid Prototyping of Service-Oriented Applications on OSGi Platform"", 《PROCEEDINGS OF FOURTH BALKAN CONFERENCE IN INFORMATICS》 * |
| 程惠勤: "远程可视主机故障诊错系统的研究与设计", 《福建电脑》 * |
| 董高云等: "嵌入式系统下位机故障定位及分析方案研究", 《铁路计算机应用》 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117235107A (en) * | 2023-11-10 | 2023-12-15 | 恒生电子股份有限公司 | Data access processing method and device, electronic equipment and storage medium |
| CN117235107B (en) * | 2023-11-10 | 2024-01-26 | 恒生电子股份有限公司 | Data access processing method and device, electronic equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112559233B (en) | 2023-01-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109766330B (en) | Data slicing method and device, electronic equipment and storage medium | |
| CN111190888A (en) | Method and device for managing graph database cluster | |
| CN111460129B (en) | Method, device, electronic equipment and storage medium for generating identification | |
| WO2020233081A1 (en) | Client plugin-ization implementation method, apparatus, computer device and storage medium | |
| US20230259358A1 (en) | Documentation enforcement during compilation | |
| CN112988770A (en) | Method and device for updating serial number, electronic equipment and storage medium | |
| CN112559233B (en) | Method, device, equipment and computer readable medium for identifying fault type | |
| CN111522617B (en) | Method and device for maintaining system and electronic equipment | |
| CN116151631A (en) | Service decision processing system, service decision processing method and device | |
| CN112073395B (en) | File distribution method and device | |
| CN113778780B (en) | Application stability determining method and device, electronic equipment and storage medium | |
| CN113726885A (en) | Method and device for adjusting flow quota | |
| CN113282489A (en) | Interface testing method and device | |
| CN111737218A (en) | File sharing method and device | |
| CN110866002A (en) | Method and device for processing sub-table data | |
| CN113626409B (en) | Test data processing method, device, equipment and storage medium | |
| CN113268488B (en) | Method and device for data persistence | |
| CN110262756B (en) | Method and device for caching data | |
| CN113760745A (en) | Interface automation test case generation method and device | |
| CN117675846A (en) | Cache cluster maintenance method, device, electronic equipment and computer readable medium | |
| CN118069539A (en) | Data processing method, device, electronic equipment and storage medium | |
| CN117032777A (en) | Low-code platform configuration method, device, electronic equipment and readable storage medium | |
| CN114500485A (en) | Data processing method and device | |
| CN115955327A (en) | Interception authentication method and device based on document system | |
| CN113220559A (en) | Service interface abnormity simulation method, device and system and client |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20220926 Address after: 25 Financial Street, Xicheng District, Beijing 100033 Applicant after: CHINA CONSTRUCTION BANK Corp. Address before: 12 / F, 15 / F, No. 99, Yincheng Road, Shanghai pilot Free Trade Zone, 200120 Applicant before: Jianxin Financial Science and Technology Co.,Ltd. |
|
| TA01 | Transfer of patent application right | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |