Abnormality processing method and device, electronic equipment and computer readable medium

Abstract

The invention discloses an exception handling method and device, electronic equipment and a computer readable medium, and relates to the technical field of big data processing.The method comprises the steps that in response to acquired exception information, a historical processed exception portrait is called, the exception information is matched with a label of the historical processed exception portrait, and a matching result is obtained; determining a target processing node corresponding to the abnormal information according to the matched label; pushing the abnormal information to a target processing node, and obtaining a processing state identifier of the target processing node to the abnormal information within a preset time; determining an alarm level corresponding to the abnormal information and an upgrading node corresponding to the target processing node in response to the fact that the processing state identifier corresponds to unprocessed; pushing the abnormal information and the alarm level to an upgrading node, and determining the type of processing result data in response to the obtained processing result data of the upgrading node on the abnormal information; and performing error marking on the abnormal information in response to the data of which the type is error marking. And the exception handling efficiency and response speed are improved.

Description

Technical Field

[0001] The present application relates to the field of big data processing technology, and in particular to an exception handling method, device, electronic device and computer-readable medium. Background Art

[0002] At present, with the expansion of business needs, each abnormal situation between systems must maintain a set of rules separately, resulting in duplication of many functional requirements. When an abnormality occurs in the system, the alarm platform may not notify the operation and maintenance personnel in time, resulting in the inability to handle the abnormality and solve the problem in time. Summary of the invention

[0003] In view of this, the embodiments of the present application provide an exception handling method, device, electronic device and computer-readable medium, which can solve the problem that when an exception occurs in the existing system, the alarm platform may not notify the operation and maintenance personnel in time, resulting in the inability to handle the exception in time.

[0004] To achieve the above object, according to one aspect of an embodiment of the present application, a method for handling an exception is provided, including:

[0005] In response to the acquired exception information, the historical processed exception portrait is called, the exception information is matched with the label of the historical processed exception portrait, and the target processing node corresponding to the exception information is determined according to the matched label;

[0006] Push the exception information to the target processing node, and obtain the target processing node's processing status identification of the exception information within a preset time;

[0007] In response to the processing state identifier corresponding to unprocessed, determining an alarm level corresponding to the abnormal information and an upgrade node corresponding to the target processing node;

[0008] Pushing the exception information and the alarm level to the upgrade node, and determining the type of the processing result data in response to obtaining the processing result data of the exception information by the upgrade node;

[0009] In response to the type being error marking data, error marking is performed on the exception information.

[0010] Optionally, matching the exception information with the labels of the historically processed exception portraits, and determining the target processing node corresponding to the exception information according to the matched labels, includes:

[0011] Obtain the processed exception information corresponding to the label of the historical processed exception portrait, perform similarity matching between the exception information and the processed exception information, and determine the target processing node corresponding to the exception information based on the label corresponding to the matched processed exception information.

[0012] Optionally, before determining the alarm level corresponding to the abnormal information and the upgrade node corresponding to the target processing node, the method further includes:

[0013] The reminder number threshold corresponding to the target processing node is obtained. After the reminder number for the target processing node reaches the reminder number threshold, if the processing state indicator still corresponds to unprocessed, an upgrade reminder process is executed.

[0014] Optionally, determining an alarm level corresponding to the abnormal information includes:

[0015] Keywords in the abnormal information are extracted, the keywords are matched with definition data corresponding to each alarm level, and the alarm level corresponding to the matched definition data is determined as the alarm level corresponding to the abnormal information.

[0016] Optionally, determine the type of the processing result data, including:

[0017] In response to the error flag in the processing result data being non-empty, determining the type of the processing result data as error flag data.

[0018] Optionally, before pushing the abnormal information and the alarm level to the upgrade node, the method further includes:

[0019] The exception information is matched with the historical exception information marked as errors for similarity, and if the match is successful, an error mark is marked for the exception information.

[0020] In addition, the present application also provides an exception handling device, including:

[0021] A matching unit is configured to, in response to acquiring the exception information, call a historically processed exception portrait, match the exception information with a label of the historically processed exception portrait, and determine a target processing node corresponding to the exception information according to the matched label;

[0022] An acquisition unit is configured to push the abnormal information to a target processing node and acquire a processing status identifier of the abnormal information by the target processing node within a preset time;

[0023] A determination unit configured to determine, in response to the processing state identifier corresponding to unprocessed, an alarm level corresponding to the abnormal information and an upgrade node corresponding to the target processing node;

[0024] a push unit configured to push the abnormal information and the alarm level to the upgrade node, and determine the type of the processing result data in response to obtaining the processing result data of the abnormal information by the upgrade node;

[0025] The error marking unit is configured to perform error marking on the abnormal information in response to the type of error marking data.

[0026] Optionally, the matching unit is further configured to:

[0027] Obtain the processed exception information corresponding to the label of the historical processed exception portrait, perform similarity matching between the exception information and the processed exception information, and determine the target processing node corresponding to the exception information based on the label corresponding to the matched processed exception information.

[0028] Optionally, the device further comprises an upgrade reminder unit configured to:

[0029] The reminder number threshold corresponding to the target processing node is obtained. After the reminder number for the target processing node reaches the reminder number threshold, if the processing state indicator still corresponds to unprocessed, an upgrade reminder process is executed.

[0030] Optionally, the determining unit is further configured to:

[0031] Keywords in the abnormal information are extracted, the keywords are matched with definition data corresponding to each alarm level, and the alarm level corresponding to the matched definition data is determined as the alarm level corresponding to the abnormal information.

[0032] Optionally, the push unit is further configured to:

[0033] In response to the error flag in the processing result data being non-empty, determining the type of the processing result data as error flag data.

[0034] Optionally, the matching unit is further configured to:

[0035] The exception information is matched with the historical exception information marked as errors for similarity, and if the match is successful, an error mark is marked for the exception information.

[0036] In addition, the present application also provides an exception handling electronic device, including: one or more processors; a storage device for storing one or more programs, when the one or more programs are executed by one or more processors, the one or more processors implement the exception handling method as described above.

[0037] In addition, the present application also provides a computer-readable medium on which a computer program is stored, and when the program is executed by a processor, the above-mentioned exception handling method is implemented.

[0038] To achieve the above objective, according to another aspect of the embodiments of the present application, a computer program product is provided.

[0039] A computer program product according to an embodiment of the present application includes a computer program, and when the program is executed by a processor, the exception handling method provided by the embodiment of the present application is implemented.

[0040] One embodiment of the above invention has the following advantages or beneficial effects: the present application calls the historical processed exception portrait in response to the acquisition of exception information, matches the exception information with the label of the historical processed exception portrait, and determines the target processing node corresponding to the exception information according to the matched label; pushes the exception information to the target processing node, obtains the processing status mark of the target processing node for the exception information within a preset time; in response to the processing status mark corresponding to unprocessed, determines the alarm level corresponding to the exception information and the upgrade node corresponding to the target processing node; pushes the exception information and the alarm level to the upgrade node, and in response to the acquisition of the processing result data of the upgrade node for the exception information, determines the type of the processing result data; in response to the type being error mark data, performs error marking on the exception information. Thus, the exception processing efficiency and the exception processing response speed are improved.

[0041] The further effects of the above-mentioned non-conventional optional manner will be described below in conjunction with the specific implementation manner. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] The accompanying drawings are used to better understand the present application and do not constitute an improper limitation on the present application.

[0043] Figure 1 is a schematic diagram of the main process of an exception handling method according to an embodiment of the present application;

[0044] Figure 2 is a schematic diagram of the main process of an exception handling method according to an embodiment of the present application;

[0045] Figure 3 It is a main flow chart of an exception handling method according to an embodiment of the present application;

[0046] Figure 4 is a schematic diagram of main units of an exception handling device according to an embodiment of the present application;

[0047] Figure 5 is an exemplary system architecture diagram to which the embodiments of the present application can be applied;

[0048] Figure 6 It is a structural diagram of a computer system of a terminal device or server suitable for implementing an embodiment of the present application. DETAILED DESCRIPTION

[0049] The following is a description of the exemplary embodiments of the present application in conjunction with the accompanying drawings, including various details of the embodiments of the present application to facilitate understanding, and they should be considered as merely exemplary. Therefore, those of ordinary skill in the art should recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the present application. Similarly, for the sake of clarity and conciseness, the description of known functions and structures is omitted in the following description. It should be noted that the acquisition, transmission, storage, use, and processing of data in the technical solution of the present application are in compliance with the relevant provisions of national laws and regulations. It should be noted that in the embodiments of the present application, certain software, components, models, and other existing solutions in the industry may be mentioned, which should be considered as exemplary, and their purpose is only to illustrate the feasibility of the implementation of the technical solution of the present application, but it does not mean that the applicant has or must have used the solution. In the technical solution of the present application, the collection, analysis, use, transmission, storage, and other aspects of the user's personal information involved are in compliance with the provisions of relevant laws and regulations, and are used for legal and reasonable purposes, and are not shared, leaked, or sold outside of these legal uses, and are subject to supervision and management by regulatory authorities. Take necessary measures to prevent illegal access to such personal information, ensure that persons with access to personal information comply with relevant laws and regulations, and ensure the security of personal information. Once such personal information is no longer needed, risks should be minimized by limiting or even prohibiting data collection and / or deleting data.

[0050] When used, including in certain related applications, user privacy is protected by de-identifying data, such as by removing specific identifiers when used, controlling the amount or specificity of data stored, controlling how data is stored, and / or other methods of de-identification.

[0051] Figure 1 is a schematic diagram of the main process of the exception handling method according to an embodiment of the present application, such as Figure 1 As shown, the exception handling method mainly includes the following steps S101 to S105.

[0052] Step S101, in response to obtaining the exception information, calling the historical processed exception portrait, matching the exception information with the label of the historical processed exception portrait, and determining the target processing node corresponding to the exception information according to the matched label.

[0053] In this embodiment, the execution subject of the exception handling method (for example, it can be a server) can obtain the exception information through a wired connection or a wireless connection. After obtaining the exception information, the execution subject can call the historical processed exception portrait, and when the exception information matches the label of the historical processed exception portrait, that is, the exception information is the information corresponding to the exception that has appeared in the history, then the execution subject can obtain the matched label as the target processing node for processing the obtained exception information. For example, the matched label can be the name or number of the handler who handled the exception that has appeared in the history, and the target processing node can be the handler or terminal corresponding to the name or number of the handler who handled the exception that has appeared in the history.

[0054] Step S102: Push the exception information to the target processing node, and obtain the target processing node's processing status identifier for the exception information within a preset time.

[0055] The preset time can be determined based on the number of currently unprocessed exception handling tasks of the target processing node. The execution subject can obtain the number of currently unprocessed exception handling tasks of the target processing node, and the average time for the target processing node to process an exception handling task, and determine the time required for the target processing node to complete the currently unprocessed exception handling tasks based on the number and the average time, and then determine the preset time based on the required time. It can be understood that the preset time is a preset time range, that is, the time range reserved for the target processing node to process the currently acquired exception information, and obtain the processing status mark of the target processing node for the exception information within this time range. For example, the processing status mark can be Y or N, when the processing status mark is Y, it means it has been processed, and when the processing status mark is N, it means it has not been processed.

[0056] Step S103, in response to the processing state identifier corresponding to unprocessed, determining the alarm level corresponding to the abnormal information and the upgrade node corresponding to the target processing node.

[0057] Specifically, determining the alarm level corresponding to the abnormal information includes: extracting keywords in the abnormal information, matching the keywords with definition data corresponding to each alarm level, and determining the alarm level corresponding to the matched definition data as the alarm level corresponding to the abnormal information.

[0058] In some embodiments, the executing entity can obtain preset alarm keywords, determine the number of preset alarm keywords contained in the abnormal information, and determine the alarm level based on the number. The larger the number, the higher the alarm level, thereby enabling important abnormal information to be processed at a higher level and improving the response speed and processing efficiency of abnormal processing.

[0059] Step S104: Push the exception information and the alarm level to the upgrade node, and determine the type of the processing result data in response to obtaining the processing result data of the exception information by the upgrade node.

[0060] Specifically, before pushing the abnormal information and the alarm level to the upgrade node, the method further includes: performing similarity matching between the abnormal information and the abnormal information marked as an error in history, and marking an error mark for the abnormal information if the match succeeds.

[0061] Before pushing the exception information and the alarm level to the upgrade node, if it is determined that the exception information is not actually abnormal, the exception information can be marked with an error mark, and the exception information marked with the error mark can be pushed to the upgrade node together with the alarm level, so that the upgrade node can reconfirm whether the exception information is actually not abnormal, thereby improving the accuracy of exception handling.

[0062] Specifically, determining the type of the processing result data includes: in response to an error mark in the processing result data being non-empty, determining the type of the processing result data to be error mark data.

[0063] If there is an error mark in the processing result data, it can be determined that the type of the processing result data is error mark data.

[0064] Step S105: in response to the type being error marking data, performing error marking on the abnormal information.

[0065] If the type of the processing result data after the upgraded node reconfirms the abnormal information is error marking data, the abnormal information can be finally error marked to ensure the accuracy and timeliness of the abnormal processing.

[0066] In this embodiment, in response to obtaining the exception information, calling the historical processed exception portrait, matching the exception information with the label of the historical processed exception portrait, determining the target processing node corresponding to the exception information according to the matched label; pushing the exception information to the target processing node, obtaining the target processing node's processing status mark for the exception information within a preset time; in response to the processing status mark corresponding to unprocessed, determining the alarm level corresponding to the exception information and the upgrade node corresponding to the target processing node; pushing the exception information and the alarm level to the upgrade node, determining the type of the processing result data in response to obtaining the processing result data of the exception information by the upgrade node; and performing error marking on the exception information in response to the type being error marking data. This improves the exception handling efficiency and the exception handling response speed.

[0067] Figure 2 is a schematic diagram of the main flow of an exception handling method according to an embodiment of the present application, such as Figure 2 As shown, the exception handling method mainly includes the following steps S201 to S206.

[0068] Step S201, in response to obtaining the exception information, calling the historical processed exception portrait.

[0069] The execution subject can detect the abnormal information in real time or at a fixed time, and obtain the abnormal information in time. When the abnormal information is obtained, the historical processed abnormal profile can be called.

[0070] Step S202, obtaining the processed exception information corresponding to the label of the historical processed exception portrait, performing similarity matching between the exception information and the processed exception information, and determining the target processing node corresponding to the exception information according to the label corresponding to the matched processed exception information.

[0071] The label of the historical processed exception portrait can be the name or number of the person who processed the exception that occurred in the history. The processed exception information corresponding to the label of the historical processed exception portrait is matched with the exception information obtained by the execution subject by cosine similarity. If there is a cosine similarity greater than the preset threshold, the target processing node corresponding to the exception information obtained by the execution subject is determined according to the label corresponding to the processed exception information corresponding to the cosine similarity greater than the preset threshold. This avoids the problem of repeated exception processing and improves the response speed and processing efficiency of exception processing.

[0072] Step S203: Push the exception information to the target processing node, and obtain the target processing node's processing status identifier for the exception information within a preset time.

[0073] If the number of exception information is higher than the preset number threshold, the execution entity can generate an asynchronous task based on the exception information, call the thread pool to process the asynchronous task and push the exception information to the target processing node, thereby improving the efficiency of pushing exception information and improving the exception processing response speed.

[0074] The preset time can be determined by the historical exception processing duration of the target processing node. The processing status identifier of the target processing node for the exception information is obtained within the preset time, and subsequent exception processing logic is performed according to the processing status identifier to ensure the accuracy of exception processing.

[0075] Step S204 , in response to the processing status identifier corresponding to unprocessed, determining the alarm level corresponding to the abnormal information and the upgrade node corresponding to the target processing node.

[0076] When determining the upgrade node corresponding to the target processing node, the pushable nodes associated with the target processing node can be obtained, the first authority corresponding to each pushable node and the second authority corresponding to the target processing node can be obtained, and the pushable node corresponding to the first authority higher than the second authority can be determined as the upgrade node corresponding to the target processing node, so as to improve the efficiency and accuracy of determining the upgrade node.

[0077] Step S205: Push the exception information and the alarm level to the upgrade node, and determine the type of the processing result data in response to obtaining the processing result data of the exception information by the upgrade node.

[0078] When the upgrade node receives the abnormal information and the alarm level, it can verify the abnormal information and the alarm level, that is, reconfirm, to obtain the verification result data. If the verification result data corresponds to the verification passing, the abnormal information is processed accordingly based on the alarm level to obtain the processing result data. If the verification result data corresponds to the verification failing, the abnormal information is annotated with error marking data to obtain the processing result data. The execution subject obtains the processing result data of the abnormal information by the upgrade node, and determines the type of the processing result data according to the content of the processing result data. For example, the type of the processing result data may include error marking data and abnormal information processing result data.

[0079] Step S206: In response to the type being error marking data, error marking is performed on the abnormal information.

[0080] When the type of the processing result data is error marking data, error marking is performed on the exception information to ensure the accuracy of exception processing.

[0081] Figure 3 is a schematic diagram of the main flow of an exception handling method according to an embodiment of the present application, such as Figure 3 As shown, the exception handling method mainly includes the following steps S301 to S306.

[0082] Step S301, in response to obtaining the exception information, calling the historical processed exception portrait, matching the exception information with the label of the historical processed exception portrait, and determining the target processing node corresponding to the exception information according to the matched label.

[0083] The execution subject can determine the type of abnormal information, determine the label corresponding to the type from the historical processed abnormal profiles according to the type of abnormal information (such as the name or number of the handler), and determine the node that can handle the abnormal information of this type according to the determined label (such as the name or number of the handler) as the target processing node. This improves the flexibility and accuracy of determining the target processing node.

[0084] Step S302: Push the exception information to the target processing node, and obtain the target processing node's processing status identifier for the exception information within a preset time.

[0085] Step S303, in response to the processing status identifier corresponding to unprocessed, obtain the reminder number threshold corresponding to the target processing node, and after the reminder number of the target processing node reaches the reminder number threshold, if the processing status identifier still corresponds to unprocessed, execute the upgrade reminder process.

[0086] Before enabling the upgrade node for exception handling, the execution subject can first verify the reminder times, obtain the reminder times threshold corresponding to the target processing node, and after the reminder times for the target processing node reaches the reminder times threshold, if the processing status indicator still corresponds to unprocessed, the upgrade reminder process is executed. When the alarm reminder times reaches the reminder times threshold of the target processing node, if the exception information has not been processed by the target processing node, the upgrade reminder process is executed to ensure the timeliness and efficiency of exception handling.

[0087] Step S304, determining the alarm level corresponding to the abnormal information and the upgrade node corresponding to the target processing node.

[0088] The alarm level corresponding to the exception information can be determined based on the component identifier in the exception information. Specifically, the execution subject can obtain the component identifier in the exception information, determine the importance value of the corresponding component based on the component identifier, and determine the alarm level based on the importance value to ensure that when an exception occurs in an important component, there will be a corresponding alarm level to accurately remind the target processing node that the exception needs to be handled as soon as possible, thereby improving the response speed and efficiency of exception handling.

[0089] Step S305: Push the exception information and the alarm level to the upgrade node, and determine the type of the processing result data in response to obtaining the processing result data of the exception information by the upgrade node.

[0090] The execution entity can combine the abnormal information and the alarm level into prompt information, push the prompt information to the upgrade node, and can strongly remind the upgrade node when the prompt information reaches the upgrade node to avoid being ignored by the upgrade node, thereby improving the response speed and efficiency of abnormal processing. For example, the prompt information can be voice, video or text, and the embodiment of the present application does not specifically limit the form and content of the prompt information. After obtaining the processing result data of the upgrade node on the abnormal information, determine the type of the processing result data.

[0091] Step S306: In response to the type being error marking data, error marking is performed on the abnormal information.

[0092] When the type of the processing result data is error marking data, error marking is performed on the exception information to ensure the accuracy of exception processing.

[0093] The exception handling method of the embodiment of the present application can be applied to trigger an alarm when an abnormal problem occurs in multiple system applications. The platform can formulate alarm rules between each system, and then set the corresponding abnormal information, alarm time, number of times, etc. according to the alarm rules. Alarm claim: After the abnormal information is processed by a person, the same abnormal information will be notified to the handler first in the future, which can avoid the abnormal information from being repeatedly processed. The handler can also push it to other handlers. False alarm marking and shielding: During the operation of the system, erroneous abnormal information may be generated. The corresponding rules can be configured on the platform. If similar abnormal information appears, it can be marked as erroneous abnormal information. Alarm upgrade: When the abnormal information appears for a period of time, the abnormality is still not handled. The operation and maintenance personnel can be reminded again according to the set rules, and the alarm level is indicated. The exception handling method of the embodiment of the present application involves a system platform and a server, wherein the system platform: manages the configuration of the abnormal information rules between each system, and sets the content of the abnormal information, the alarm time, the alarm number, and other information. Server: The server is each application system, and the information of each system needs to be entered into the system platform for the monitoring and management of the platform.

[0094] The embodiments of the present application can improve the processing speed of abnormal information, can quickly process abnormal information, and promptly notify the corresponding operation and maintenance personnel, thereby improving the efficiency of processing abnormal information and making the user experience more comfortable. The efficiency of operation and maintenance can be improved, and the operation and maintenance or development personnel can be reminded simply, accurately, and efficiently.

[0095] Figure 4 Schematic diagram of the main units of the exception handling device according to an embodiment of the present application. Figure 4 As shown, the exception handling device 400 includes a matching unit 401 , an acquiring unit 402 , a determining unit 403 , a pushing unit 404 and an error marking unit 405 .

[0096] The matching unit 401 is configured to call the historical processed exception portrait in response to the acquired exception information, match the exception information with the label of the historical processed exception portrait, and determine the target processing node corresponding to the exception information according to the matched label.

[0097] The acquisition unit 402 is configured to push the abnormal information to the target processing node, and acquire the processing status identifier of the abnormal information by the target processing node within a preset time.

[0098] The determining unit 403 is configured to determine the alarm level corresponding to the abnormal information and the upgrade node corresponding to the target processing node in response to the processing state identifier corresponding to unprocessed.

[0099] The pushing unit 404 is configured to push the abnormal information and the alarm level to the upgrade node, and determine the type of the processing result data in response to obtaining the processing result data of the abnormal information by the upgrade node.

[0100] The error marking unit 405 is configured to perform error marking on the abnormal information in response to the type of error marking data.

[0101] In some embodiments, the matching unit 401 is further configured to: obtain processed exception information corresponding to the label of the historical processed exception portrait, perform similarity matching between the exception information and the processed exception information, and determine the target processing node corresponding to the exception information based on the label corresponding to the matched processed exception information.

[0102] In some embodiments, the exception handling device further includes Figure 4 The upgrade reminder unit not shown in the figure is configured to: obtain the reminder number threshold corresponding to the target processing node, and after the reminder number of the target processing node reaches the reminder number threshold, if the processing status identifier still corresponds to unprocessed, execute the upgrade reminder process.

[0103] In some embodiments, the determination unit 403 is further configured to: extract keywords from the abnormal information, match the keywords with definition data corresponding to each alarm level, and determine the alarm level corresponding to the matched definition data as the alarm level corresponding to the abnormal information.

[0104] In some embodiments, the pushing unit 404 is further configured to: in response to the error mark in the processing result data being non-empty, determine that the type of the processing result data is error mark data.

[0105] In some embodiments, the matching unit 401 is further configured to: perform similarity matching between the abnormal information and the abnormal information marked as errors in history, and if the match is successful, mark an error mark for the abnormal information.

[0106] It should be noted that the exception handling method and the exception handling device of the present application have a corresponding relationship in terms of specific implementation contents, so the repeated contents will not be described again.

[0107] Figure 5 An exemplary system architecture 500 to which the exception handling method or exception handling device according to the embodiment of the present application can be applied is shown.

[0108] like Figure 5As shown, system architecture 500 may include terminal devices 501, 502, 503, a network 504 and a server 505. Network 504 is used to provide a medium for communication links between terminal devices 501, 502, 503 and server 505. Network 504 may include various connection types, such as wired, wireless communication links or optical fiber cables, etc.

[0109] Users can use terminal devices 501, 502, 503 to interact with server 505 through network 504 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 501, 502, 503, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social platform software, etc. (only for example).

[0110] The terminal devices 501, 502, 503 may be various electronic devices having an exception processing screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop computers, desktop computers, and the like.

[0111] Server 505 can be a server that provides various services, such as a background management server (only as an example) that provides support for the exception information obtained by the user using terminal devices 501, 502, and 503. In response to obtaining the exception information, the background management server can call the historical processed exception portrait, match the exception information with the label of the historical processed exception portrait, and determine the target processing node corresponding to the exception information according to the matched label; push the exception information to the target processing node, and obtain the processing status mark of the target processing node for the exception information within a preset time; in response to the processing status mark corresponding to unprocessed, determine the alarm level corresponding to the exception information and the upgrade node corresponding to the target processing node; push the exception information and the alarm level to the upgrade node, and in response to obtaining the processing result data of the upgrade node for the exception information, determine the type of the processing result data; in response to the type being error marking data, perform error marking on the exception information. Thereby improving the efficiency of exception processing and the response speed of exception processing.

[0112] It should be noted that the exception handling method provided in the embodiment of the present application is generally executed by the server 505 , and accordingly, the exception handling device is generally set in the server 505 .

[0113] It should be understood that Figure 5 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to implementation requirements.

[0114] Reference below Figure 6 , which shows a schematic diagram of the structure of a computer system 600 of a terminal device suitable for implementing an embodiment of the present application. Figure 6 The terminal device shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0115] like Figure 6 As shown, the computer system 600 includes a central processing unit (CPU) 601, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 602 or a program loaded from a storage part 608 into a random access memory (RAM) 603. In the RAM 603, various programs and data required for the operation of the computer system 600 are also stored. The CPU 601, the ROM 602, and the RAM 603 are connected to each other via a bus 604. An input / output (I / O) interface 605 is also connected to the bus 604.

[0116] The following components are connected to the I / O interface 605: an input section 606 including a keyboard, a mouse, etc.; an output section 607 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 608 including a hard disk, etc.; and a communication section 609 including a network interface card such as a LAN card, a modem, etc. The communication section 609 performs communication processing via a network such as the Internet. A drive 610 is also connected to the I / O interface 605 as needed. A removable medium 611, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 610 as needed, so that a computer program read therefrom is installed into the storage section 608 as needed.

[0117] In particular, according to the embodiments disclosed in the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program contains program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 609, and / or installed from the removable medium 611. When the computer program is executed by the central processing unit (CPU) 601, the above-mentioned functions defined in the system of the present application are executed.

[0118] It should be noted that the computer-readable medium shown in the present application may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. Computer-readable storage media may include, for example, but are not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or devices, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, 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 disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, device or device. In the present application, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries a computer-readable program code. This propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, optical cable, RF, etc., or any suitable combination of the above.

[0119] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the above-mentioned module, program segment or a part of a code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flow chart, and the combination of the boxes in the block diagram or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0120] The units involved in the embodiments described in the present application may be implemented by software or hardware. The units described may also be set in a processor, for example, it may be described as: a processor includes a matching unit, an acquisition unit, a determination unit, a push unit, and an error marking unit. The names of these units do not, in some cases, constitute limitations on the units themselves.

[0121] As another aspect, the present application also provides a computer-readable medium, which may be included in the device described in the above embodiment; or it may exist independently and not be assembled into the device. The above computer-readable medium carries one or more programs, and when the above one or more programs are executed by a device, the device responds to the acquisition of abnormal information, calls the historical processed abnormal image, matches the abnormal information with the label of the historical processed abnormal image, and determines the target processing node corresponding to the abnormal information according to the matched label; pushes the abnormal information to the target processing node, obtains the processing status mark of the target processing node for the abnormal information within a preset time; in response to the processing status mark corresponding to unprocessed, determines the alarm level corresponding to the abnormal information and the upgrade node corresponding to the target processing node; pushes the abnormal information and the alarm level to the upgrade node, and in response to the acquisition of the processing result data of the upgrade node for the abnormal information, determines the type of the processing result data; in response to the type being error marking data, performs error marking on the abnormal information.

[0122] The computer program product of the present application includes a computer program, and when the computer program is executed by a processor, the exception handling method in the embodiment of the present application is implemented.

[0123] According to the technical solution of the embodiment of the present application, the exception handling efficiency and exception handling response speed can be improved.

[0124] The above specific implementations do not constitute a limitation on the protection scope of this application. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may occur depending on design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of this application should be included in the protection scope of this application.

Claims

1. An exception handling method, characterized in that: include: In response to obtaining the exception information, calling the historical processed exception portrait, matching the exception information with the label of the historical processed exception portrait, and determining the target processing node corresponding to the exception information according to the matched label; Pushing the exception information to the target processing node, and obtaining a processing status identifier of the exception information by the target processing node within a preset time; In response to the processing status identifier corresponding to unprocessed, determining an alarm level corresponding to the abnormal information and an upgrade node corresponding to the target processing node; Pushing the abnormal information and the alarm level to the upgrade node, and in response to obtaining the processing result data of the abnormal information by the upgrade node, determining the type of the processing result data; In response to the type being error marking data, error marking is performed on the exception information.

2. The method according to claim 1, characterized in that The step of matching the exception information with the label of the historically processed exception portrait, and determining the target processing node corresponding to the exception information according to the matched label, includes: The processed exception information corresponding to the label of the historical processed exception portrait is obtained, the exception information is matched with the processed exception information for similarity, and the target processing node corresponding to the exception information is determined according to the label corresponding to the matched processed exception information.

3. The method according to claim 1, characterized in that: Before determining the alarm level corresponding to the abnormal information and the upgrade node corresponding to the target processing node, the method further includes: A reminder number threshold corresponding to the target processing node is obtained, and after the reminder number for the target processing node reaches the reminder number threshold, if the processing status identifier still corresponds to unprocessed, an upgrade reminder process is executed.

4. The method according to claim 1, characterized in that: The determining the alarm level corresponding to the abnormal information includes: Keywords in the abnormal information are extracted, the keywords are matched with definition data corresponding to each alarm level, and the alarm level corresponding to the matched definition data is determined as the alarm level corresponding to the abnormal information.

5. The method according to claim 1, characterized in that The determining the type of the processing result data includes: In response to the error mark in the processing result data being non-empty, determining the type of the processing result data as error mark data.

6. The method according to claim 1, characterized in that Before pushing the abnormal information and the alarm level to the upgrade node, the method further includes: The abnormal information is matched with the abnormal information marked as an error in history for similarity, and if the match is successful, an error mark is marked for the abnormal information.

7. An exception handling device, characterized in that: include: A matching unit is configured to, in response to acquiring the exception information, call a historically processed exception portrait, match the exception information with a label of the historically processed exception portrait, and determine a target processing node corresponding to the exception information according to the matched label; An acquisition unit is configured to push the abnormal information to the target processing node, and acquire a processing status identifier of the abnormal information by the target processing node within a preset time; A determining unit, configured to determine, in response to the processing status identifier corresponding to unprocessed, an alarm level corresponding to the abnormal information and an upgrade node corresponding to the target processing node; a pushing unit configured to push the abnormal information and the alarm level to the upgrading node, and determine a type of the processing result data in response to obtaining processing result data of the abnormal information by the upgrading node; The error marking unit is configured to perform error marking on the abnormal information in response to the type of the data being error marking data.

8. The device according to claim 7, characterized in that The matching unit is further configured to: The processed exception information corresponding to the label of the historical processed exception portrait is obtained, the exception information is matched with the processed exception information for similarity, and the target processing node corresponding to the exception information is determined according to the label corresponding to the matched processed exception information.

9. The device according to claim 7, characterized in that The device further comprises an upgrade reminder unit configured to: A reminder number threshold corresponding to the target processing node is obtained, and after the reminder number for the target processing node reaches the reminder number threshold, if the processing status identifier still corresponds to unprocessed, an upgrade reminder process is executed.

10. The device according to claim 7, characterized in that The determining unit is further configured to: Keywords in the abnormal information are extracted, the keywords are matched with definition data corresponding to each alarm level, and the alarm level corresponding to the matched definition data is determined as the alarm level corresponding to the abnormal information.

11. The device according to claim 7, characterized in that The push unit is further configured to: In response to the error mark in the processing result data being non-empty, determining the type of the processing result data as error mark data.

12. The device according to claim 7, characterized in that The matching unit is further configured to: The abnormal information is matched with the abnormal information marked as an error in history for similarity, and if the match is successful, an error mark is marked for the abnormal information.

13. An abnormality handling electronic device, characterized in that: include: one or more processors; a storage device for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 1 to 6.

14. A computer readable medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the method according to any one of claims 1 to 6 is implemented.

15. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the method according to any one of claims 1 to 6 is implemented.

Images