[0036] like figure 1 As shown, in one embodiment, an abnormality monitoring method includes the following steps:
[0037] Step S10, detecting the abnormal key information, and identifying the abnormal type and abnormal level according to the abnormal key information.
[0038] Abnormal key information is the monitoring information dynamically obtained in the process of monitoring the system running status, including application software running information and environmental information such as CPU usage, memory usage, port status, and network bandwidth.
[0039] The abnormal key information in the present invention does not refer to the error information when the error occurs, but information related to the abnormality. As long as the abnormal key information does not meet the set conditions, it is considered that an abnormality has occurred and needs to be repaired.
[0040] In one embodiment, the exception type and exception level can be set, and the exception type includes application software itself exception and environment exception, wherein the environment exception includes CPU exception, memory exception, operating system exception, port exception, network exception and other types. Further, anomalies can be divided into different levels in advance, for example, level 1 anomaly is the lowest level anomaly, such as the lowest alarm information of the application software, etc.; level 5 anomaly is the highest level anomaly, such as downtime alarm anomaly.
[0041] Different exception key information corresponds to different exception types and exception levels. For example, if it is detected that the CPU occupancy rate does not meet the set condition, the abnormal type is identified as CPU abnormality. When a downtime alarm occurs, the abnormality level is identified as level 5 abnormality.
[0042] Step S20: Obtain a preset exception handling scheme corresponding to the exception type and exception level.
[0043] In one embodiment, an exception handling scheme may be preset, and a mapping relationship between exception types and exception levels and exception handling schemes may be established, that is, different exception handling schemes correspond to different exception types and exception levels. A corresponding exception handling scheme can be obtained according to the identified exception type and exception level.
[0044] Step S30, executing an exception handling solution.
[0045] Exception handling solutions include patch information required to resolve exceptions, application guidance steps, exception handling prompts, and display methods for key exception information. Different exception handling schemes can be set on the server in advance for different exception types and exception levels. In addition, for different application environments, the exception type, exception level and corresponding exception handling scheme can be extended. Further, in one embodiment, after identifying the abnormality type and abnormality level, the corresponding abnormality handling solution can be automatically downloaded from the server, including patch information required for solving the abnormality, application guidance step process, abnormality handling prompt information and abnormality. Key information display methods, etc.
[0046] In one embodiment, the flow of application guidance steps can be obtained and displayed according to the exception scheme. Then the user can operate the application software according to the application guidance step flow and so on.
[0047] In this embodiment or another embodiment, the exception handling prompt information may also be acquired according to the exception handling scheme and displayed on the abnormal operation prompt interface. Application software exceptions can be displayed logically. After the exception type and exception level are identified according to the key exception information, the exception handling prompt information can be obtained according to the corresponding exception handling plan, and the user can be prompted to operate. In this embodiment, a user operation may be received through an exception handling operation prompt interface, and an exception may be handled according to the user operation.
[0048]For example, when abnormal key information that cannot be performed by the image upload function of the application software is detected, the abnormal key information is displayed and the user is prompted to perform operations such as upgrading the application software to fix the abnormality. For another example, when an abnormality in which the CPU occupancy rate exceeds a certain threshold is detected, abnormal information may be displayed and the user may be prompted to close some processes to repair the abnormality.
[0049] In one embodiment, the abnormal key information display mode can also be obtained according to the exception handling scheme, and the abnormal key information is displayed according to the abnormal key information display mode. In this embodiment, the abnormal key information display mode includes more than one of icons, data lists, images, comparison charts, and line charts. In other embodiments, exception handling prompt information and the like may also be displayed according to these display methods. Further, each display interface can be switched according to the user operation, so that the user can view various types of anomalies.
[0050] In one embodiment, patch information required for resolving the exception may also be acquired according to the exception handling scheme, and data required for exception handling may be automatically downloaded from the server according to the patch information required for resolving the exception. Some exceptions are due to the low version of the application software or the occurrence of loopholes. Patch information corresponding to these types and levels of exceptions can be set and automatically updated according to the patch information, so as to automatically process the exceptions.
[0051] In addition, in this embodiment, the processing result may also be displayed. For example, when it is detected that the application software itself is abnormal or the operating system is abnormal, the corresponding abnormal processing method is to automatically download the upgrade package of the application software or operating system, and then upgrade the application software or operating system according to the upgrade package to repair Detected exception.
[0052] In the above abnormality monitoring method, a preset abnormality processing scheme can be stored in the abnormality monitoring device, and the abnormality detection device can be set as a handheld device with an interface. When a system to be monitored (such as various application software clients) needs to be monitored, a device equipped with the system to be monitored can be connected through an interface (such as a USB interface). After the handheld device is connected to the device to be monitored, it can also connect to the server through the network, and download the updated exception handling solution from the server.
[0053] When the handheld device is connected to the device to be monitored, a pre-stored exception handling scheme can be installed first, and then real-time monitoring of the system to be monitored can be started. In addition, for different application environments, the exception handling scheme on the device to be monitored or the server can be extended and updated.
[0054] like figure 2 As shown, in one embodiment, an abnormality monitoring device includes an abnormality identification module 10, a scheme identification module 20 and a scheme execution module 30, wherein:
[0055] The abnormality identification module 10 is used for detecting abnormal key information, and identifying the abnormal type and abnormal level according to the abnormal key information.
[0056] Abnormal key information is the monitoring information dynamically obtained in the process of monitoring the system running status, including application software running information and environmental information such as CPU usage, memory usage, port status, and network bandwidth.
[0057] The abnormal key information in the present invention does not refer to the error information when the error occurs, but information related to the abnormality. As long as the abnormal key information does not meet the set conditions, it is considered that an abnormality has occurred and needs to be repaired.
[0058] In one embodiment, the exception type and exception level may be preset, and the exception type includes application software exceptions and environmental exceptions, and the environmental exceptions include CPU exceptions, memory exceptions, operating system exceptions, port exceptions, network exceptions, and other types. . Further, anomalies can be divided into different levels in advance, for example, level 1 anomaly is the lowest level anomaly, such as the lowest alarm information of the application software, etc.; level 5 anomaly is the highest level anomaly, such as downtime alarm anomaly.
[0059] Different exception key information corresponds to different exception types and exception levels. For example, the abnormality identification module 10 detects that the CPU occupancy rate does not meet the set condition, and then recognizes that the abnormality type is CPU abnormality. When a downtime alarm occurs, the abnormality level is identified as level 5 abnormality.
[0060] The solution identification module 20 is configured to acquire a preset exception handling solution corresponding to the exception type and exception level.
[0061] In one embodiment, an exception handling scheme may be preset, and a mapping relationship between exception types and exception levels and exception handling schemes may be established, that is, different exception handling schemes correspond to different exception types and exception levels. A corresponding exception handling scheme can be obtained according to the identified exception type and exception level.
[0062] The solution execution module 30 is used for executing the exception handling solution.
[0063] In one embodiment, the exception handling solution includes patch information required to resolve the exception, application guidance step flow, exception handling prompt information, and a manner of displaying key exception information. like image 3 As shown, the solution execution module 30 may include a presentation module 310 and an exception handling module 320, wherein:
[0064] The display module 310 is configured to obtain and display the application guidance step flow according to the exception handling scheme; and/or to obtain exception handling prompt information according to the exception handling scheme and display it on the exception handling operation prompt interface.
[0065] The exception handling module 320 is configured to receive a user operation through the exception handling operation prompt interface, and handle the exception according to the user operation.
[0066] In one embodiment, the display module 310 is further configured to obtain a method for displaying abnormal key information according to the exception handling scheme, and display the abnormal key information according to the abnormal key information display method. In this embodiment, the abnormal key information display manner includes more than one of a chart, a data list, an image, a comparison chart, and a line chart. Further, the display module 310 can also switch each display interface according to the user operation, so that the user can view various types of anomalies.
[0067] In one embodiment, as image 3 As shown, the solution execution module 30 may further include an automatic update module 330, wherein: the automatic update module 330 is configured to obtain patch information required for solving the exception according to the exception handling The server downloads the data required for exception handling. In this embodiment, the exception processing module 320 is further configured to process the exception according to the data required for the exception processing.
[0068] Some exceptions are due to the low version of the application software or the occurrence of loopholes. Patch information corresponding to these types and levels of exceptions can be set and automatically updated according to the patch information, so as to automatically process the exceptions. In addition, in this embodiment, the processing result may also be displayed. For example, when it is detected that the application software itself is abnormal or the operating system is abnormal, the corresponding abnormal processing method is to automatically download the upgrade package of the application software or operating system, and then upgrade the application software or operating system according to the upgrade package to repair Detected exception.
[0069] As described above, the exception types may include one or more of operating system exceptions, memory exceptions, CPU exceptions, network exceptions, port occupancy exceptions, and application software error exceptions. like Figure 4 As shown, in one embodiment, the abnormality monitoring device may further include: an extension module 40 and a download module 50, wherein:
[0070] The extension module 40 is used to set an exception handling scheme corresponding to the exception type and exception level. In this embodiment, the abnormality monitoring device may further include a solution storage module 60 for storing a preset abnormality processing solution. In other embodiments, the exception handling scheme can also be stored in the server, and when the exception monitoring device is connected to the server through the network, the latest exception handling scheme is automatically downloaded from the server.
[0071] The downloading module 50 is configured to download the corresponding exception handling solution from the server according to the exception type and exception level.
[0072] In one embodiment, as Figure 5 As shown, the abnormality monitoring device may further include an interface module 70 . Preferably, the interface module 70 can be a USB interface, and the abnormality monitoring device can be set as a handheld device, which is connected to the device to be monitored through the interface module 70 . The to-be-monitored system (such as various application software systems) is run on the to-be-monitored device, and the abnormality monitoring device is used to monitor abnormal key information of the to-be-monitored system during the running process.
[0073] In this embodiment, when the abnormality monitoring device is connected to the device to be monitored through the interface module 70, the pre-stored abnormality handling solution can be installed first, or the latest abnormality handling solution can be downloaded and installed from the server through the network, and then the system to be monitored can be monitored in real time. . After the abnormal key information is detected, and the abnormal level and abnormal type are identified according to the abnormal key information, the abnormal key information can be displayed in different display methods. When solving an exception, the exception handling prompt information can be displayed through the exception handling operation interface, and the user can perform corresponding operations according to the exception handling prompt information and finally resolve the exception.
[0074] In the present invention, the hand-held device is connected with the device to be monitored through the USB interface, so that the device to be monitored can be monitored in real time for abnormality. And when an abnormality is detected, a corresponding abnormality handling plan can be adopted to prompt the user to operate or automatically download data to repair the abnormality, so it is more flexible.
[0075] The above-mentioned embodiments only represent several embodiments of the present invention, and the descriptions thereof are specific and detailed, but should not be construed as a limitation on the scope of the patent of the present invention. It should be pointed out that for those of ordinary skill in the art, without departing from the concept of the present invention, several modifications and improvements can also be made, which all belong to the protection scope of the present invention. Therefore, the protection scope of the patent of the present invention shall be subject to the appended claims.
