Multi-system fault early warning method and device, computer equipment and storage medium

Abstract

The invention discloses a multi-system fault early warning method and device, computer equipment and a storage medium, and relates to the technical field of system fault early warning, and the method comprises the steps: starting monitoring period timing in response to completion of configuration of each system module and a problem type sub-module of the corresponding system module; in response to the fact that the monitoring period is not reached, obtaining fault phenomenon evaluation data of each problem type sub-module, and performing phenomenon entropy evaluation according to each fault phenomenon evaluation data to obtain a phenomenon total entropy value of the problem type sub-module corresponding to the corresponding fault phenomenon evaluation data; determining a problem entropy value of each system module according to the phenomenon total entropy value of the corresponding problem type sub-module in each system module; according to the method, the technical problems that the efficiency is low or the timeliness is low and the like when the problem entropy value of each problem is inquired in the system fault early warning problem inquiry table are solved, the efficiency, the timeliness and the accuracy of system fault early warning are improved, and a fault system is accurately positioned.

Description

Technical Field

[0001] This application relates to the technical field of system fault warning, and particularly relates to a multi-system fault warning method, device, computer device, and storage medium. Background Art

[0002] Currently, a large number of business software are running in the production environments of many customers, and various applications such as basic management, data storage, and external services are dazzling. Although the server forms include physical machines and virtual machines, operating systems are installed on both of them. The business topology covers all operating systems. If there are problems with the business, it may cause losses in aspects such as economy and credit. In order to avoid losses to customers caused by problems, it is necessary to perform fault warning on the operating system.

[0003] However, traditional system fault warning methods have problems such as low efficiency or low timeliness. Summary of the Invention

[0004] This application provides a multi-system fault warning method, device, computer device, and storage medium to at least solve the problems of low efficiency or low timeliness in related technologies.

[0005] In a first aspect, this application provides a multi-system fault warning method, and the method includes: Responding to the completion of the configuration of each system module and the corresponding problem type sub-module of the system module, starting the monitoring cycle timing; the system module is used to represent the corresponding operating system; the problem type sub-module is used to represent the fault problem type of the corresponding system module; Responding to the monitoring cycle not arriving, obtaining the fault phenomenon evaluation data of each problem type sub-module, and obtaining the total phenomenon entropy value of the problem type sub-module corresponding to the corresponding fault phenomenon evaluation data after performing phenomenon entropy value evaluation on each fault phenomenon evaluation data; Determining the problem entropy value of each system module according to the total phenomenon entropy value of the corresponding problem type sub-module in each system module; Querying the system fault warning problem query table according to each problem entropy value to obtain the fault warning information of the corresponding system module.

[0006] In one embodiment, the method further includes: performing module division on each operating system in the server cluster to obtain the corresponding system module; performing sub-module division on the corresponding fault problem types in each system module to obtain the problem type sub-module corresponding to each system module, and determining that the configuration of each system module and the corresponding problem type sub-module of the system module is completed.

[0007] In one embodiment, obtaining the failure phenomenon evaluation data of each problem type sub-module, and obtaining the total phenomenon entropy value of the problem type sub-module corresponding to the corresponding failure phenomenon evaluation data after performing phenomenon entropy value evaluation based on each failure phenomenon evaluation data, includes: obtaining the failure phenomenon evaluation data of each problem type sub-module; the failure phenomenon evaluation data includes each failure phenomenon evaluation index value; the failure phenomenon evaluation index is the index value used to evaluate the failure phenomenon of the corresponding problem type sub-module; judging whether there is a failure phenomenon corresponding to the corresponding failure phenomenon evaluation index value according to each failure phenomenon evaluation index value and the threshold condition of the corresponding failure phenomenon evaluation index value; in response to the existence of a first target failure phenomenon evaluation index value, querying the phenomenon entropy value in the failure phenomenon entropy value evaluation table according to the failure phenomenon corresponding to the first target failure phenomenon evaluation index value to obtain the phenomenon entropy value of the first target failure phenomenon evaluation index value; wherein, the first target failure phenomenon evaluation index value is the evaluation index value corresponding to the existing failure phenomenon; determining the total phenomenon entropy value of the problem type sub-module corresponding to the corresponding failure phenomenon evaluation data according to the sum of the phenomenon entropy values of the first target failure phenomenon evaluation index values corresponding to each failure phenomenon evaluation data.

[0008] In one embodiment, determining the problem entropy value of each system module according to the total phenomenon entropy value of the corresponding problem type sub-module in each system module, includes: based on the problem entropy value statistical algorithm, calculating according to the total phenomenon entropy value of the corresponding problem type sub-module in each system module and the failure problem type weight value of the corresponding problem type sub-module to obtain the failure problem entropy value of each system module.

[0009] In one embodiment, the failure warning information includes the system failure problem induction appearance information, warning problem information and file to be backed up information of the corresponding system module; the method further includes: sending the failure warning information of the corresponding system module to the operating system corresponding to each system module; automatically backing up files according to the file to be backed up information in each failure warning information.

[0010] In one embodiment, the method further includes: querying in the failure solution database according to the warning problem information in each failure warning information to obtain the failure solution of each failure warning information; sending the failure solution of the corresponding system module to the operating system corresponding to each system module; in response to receiving the confirmation information of the failure solution of the target system module, repairing the failure problem of the target system module according to the failure solution of the target system module; wherein, the target system module is any one of the system modules.

[0011] In one embodiment, the method further includes: In response to the monitoring period arriving, clearing the monitoring period and returning to the step of starting the monitoring period timing.

[0012] In a second aspect, a multi-system fault warning device is provided. The device includes a timing start module, a data acquisition module, an entropy value determination module, and a warning generation module.

[0013] Among them, the timing start module is used to start monitoring cycle timing in response to the completion of the configuration of each system module and the problem type sub-module corresponding to the system module; the system module is used to represent the corresponding operating system; the problem type sub-module is used to represent the types of fault problems of the corresponding system module. The data acquisition module is used to obtain the fault phenomenon evaluation data of each problem type sub-module in response to the monitoring cycle not reaching, and obtain the total phenomenon entropy value of the problem type sub-module corresponding to the corresponding fault phenomenon evaluation data after performing phenomenon entropy value evaluation on each fault phenomenon evaluation data. The entropy value determination module is used to determine the problem entropy value of each system module according to the total phenomenon entropy value of the problem type sub-module corresponding to each system module. The warning generation module is used to query the system fault warning problem query table according to each problem entropy value to obtain the fault warning information of the corresponding system module.

[0014] In a third aspect, the present application also provides an electronic device, including: a memory for storing a computer program; a processor for implementing the steps of any of the above multi-system fault warning methods when executing the computer program.

[0015] In a fourth aspect, the present application also provides a computer-readable storage medium, in which a computer program is stored. When the computer program is executed by a processor, the steps of any of the above multi-system fault warning methods are implemented.

[0016] Through the present application, the above multi-system fault warning method, device, computer device, and storage medium start monitoring cycle timing in response to the completion of the configuration of each system module and the problem type sub-module corresponding to the system module; the system module is used to represent the corresponding operating system; the problem type sub-module is used to represent the types of fault problems of the corresponding system module; then, in response to the monitoring cycle not reaching, obtain the fault phenomenon evaluation data of each problem type sub-module, and obtain the total phenomenon entropy value of the problem type sub-module corresponding to the corresponding fault phenomenon evaluation data after performing phenomenon entropy value evaluation on each fault phenomenon evaluation data; then, determine the problem entropy value of each system module according to the total phenomenon entropy value of the problem type sub-module corresponding to each system module; finally, query the system fault warning problem query table according to each problem entropy value to obtain the fault warning information of the corresponding system module. Therefore, technical problems such as low efficiency or low timeliness can be solved, real-time dynamic fault warning of multiple systems is realized, the dimension of fault problems for system fault warning is broadened, the efficiency, timeliness, and accuracy of system fault warning are improved, and the fault system is accurately positioned. Brief Description of the Drawings

[0017] To more clearly illustrate the embodiments of the present application, the drawings required for use in the embodiments will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on these drawings.

[0018] Figure 1 It is an application environment diagram of the multi-system fault warning method in an embodiment; Figure 2 It is a first process schematic diagram of the multi-system fault warning method in an embodiment; Figure 3 It is a second process schematic diagram of the multi-system fault warning method in an embodiment; Figure 4 It is a process schematic diagram of obtaining the fault phenomenon evaluation data of each problem type sub-module, and obtaining the total phenomenon entropy value of the problem type sub-module corresponding to the corresponding fault phenomenon evaluation data after performing phenomenon entropy value evaluation on each fault phenomenon evaluation data; Figure 5 It is a third process schematic diagram of the multi-system fault warning method in an embodiment; Figure 6 It is a structural block diagram of the multi-system fault warning device in an embodiment. Detailed Description of the Embodiments

[0019] Next, the technical solutions in the embodiments of the present application will be clearly and completely described in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only some embodiments of the present application, rather than all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts fall within the protection scope of the present application.

[0020] It should be noted that in the description of the present application, the terms "include", "comprise" or any other variant thereof are intended to cover a non-exclusive inclusion, so that a process, method, article or device including a series of elements not only includes those elements, but also includes other elements not expressly listed, or further includes elements inherent to such process, method, article or device. The terms "first", "second", etc. in the present application are used to distinguish similar objects, rather than to describe a specific order or sequence.

[0021] To enable those skilled in the art of the present technology to better understand the solution of the present application, the present application will be further described in detail below in conjunction with the drawings and specific embodiments.

[0022] The multi-system fault warning method provided by this application can be applied to, for example, Figure 1 the application environment shown. Among them, the terminal 102 communicates with the server 104 through the network. Among them, the terminal 102 can be, but is not limited to, various personal computers, laptop computers, smart phones, tablet computers, and portable wearable devices, and the server 104 can be implemented by an independent server or a server cluster composed of multiple servers.

[0023] In the first aspect, as Figure 2 shown, a multi-system fault warning method is provided. Taking the method applied to the Figure 1 server 104 in it as an example, the following steps 201 to 204 are included.

[0024] Step 201, in response to the completion of the configuration of each system module and the problem type sub-module corresponding to the system module, start monitoring cycle timing.

[0025] Among them, the system module is used to represent the corresponding operating system; the problem type sub-module is used to represent the fault problem type of the corresponding system module. Specifically, the server 104 starts monitoring cycle timing in response to the completion of the configuration of each system module and the problem type sub-module corresponding to the system module.

[0026] In a specific example, the fault problem type can include, but is not limited to, hardware-level problems, system-level problems, and application-level problems. The above are only specific examples, which are flexibly set according to user needs in actual applications and are not limited here.

[0027] In one embodiment, as Figure 3 shown, the method further includes steps 301 and 302.

[0028] Step 301, perform module division according to each operating system in the server cluster to obtain the corresponding system module.

[0029] Step 302, perform sub-module division according to the corresponding fault problem types in each system module to obtain the problem type sub-modules corresponding to each system module, and determine that the configuration of each system module and the problem type sub-module corresponding to the system module is completed.

[0030] Specifically, the server 104 performs module division according to each operating system in the server cluster to obtain the corresponding system module; then, performs sub-module division according to the corresponding fault problem types in each system module to obtain the problem type sub-modules corresponding to each system module, and determines that the configuration of each system module and the problem type sub-module corresponding to the system module is completed, so as to facilitate the realization of multi-system and multi-dimensional fault warning.

[0031] In this embodiment, corresponding system modules are obtained after module division according to the operating systems in the server cluster; then, sub-module division is performed according to the corresponding fault problem types in each system module to obtain the problem type sub-modules corresponding to each system module, and it is determined that each system module and the problem type sub-modules of the corresponding system module are configured, so as to facilitate the realization of multi-system and multi-dimensional fault warning.

[0032] Step 202, in response to the monitoring period not arriving, obtain the fault phenomenon evaluation data of each problem type sub-module, and after performing phenomenon entropy value evaluation according to each fault phenomenon evaluation data, obtain the total phenomenon entropy value of the problem type sub-module corresponding to the corresponding fault phenomenon evaluation data.

[0033] Among them, the fault phenomenon evaluation data is the evaluation data of the corresponding fault phenomenon occurring in the corresponding problem type sub-module. Specifically, server 104, in response to the monitoring period not arriving, obtains the fault phenomenon evaluation data of each problem type sub-module, and after performing phenomenon entropy value evaluation according to each fault phenomenon evaluation data, obtains the total phenomenon entropy value of the problem type sub-module corresponding to the corresponding fault phenomenon evaluation data.

[0034] In one embodiment, as Figure 4 shown, obtaining the fault phenomenon evaluation data of each problem type sub-module, and after performing phenomenon entropy value evaluation according to each fault phenomenon evaluation data, obtaining the total phenomenon entropy value of the problem type sub-module corresponding to the corresponding fault phenomenon evaluation data includes steps 401 to 404.

[0035] Step 401, obtain the fault phenomenon evaluation data of each problem type sub-module.

[0036] Among them, the fault phenomenon evaluation data includes each fault phenomenon evaluation index value. The fault phenomenon evaluation index is the index value used to evaluate the fault phenomenon of the corresponding problem type sub-module. Specifically, server 104 obtains the fault phenomenon evaluation data of each problem type sub-module.

[0037] Step 402, according to each fault phenomenon evaluation index value and the threshold condition of the corresponding fault phenomenon evaluation index value, determine whether there is a fault phenomenon corresponding to the corresponding fault phenomenon evaluation index value.

[0038] Among them, server 104 determines whether there is a fault phenomenon corresponding to the corresponding fault phenomenon evaluation index value according to each fault phenomenon evaluation index value and the threshold condition of the corresponding fault phenomenon evaluation index value.

[0039] Step 403, in response to the existence of the first target fault phenomenon evaluation index value, query the phenomenon entropy value in the fault phenomenon entropy value evaluation table according to the fault phenomenon corresponding to the first target fault phenomenon evaluation index value, and obtain the phenomenon entropy value of the first target fault phenomenon evaluation index value.

[0040] Among them, the first target fault phenomenon evaluation index value is the evaluation index value of the corresponding fault phenomenon. The fault phenomenon entropy value evaluation table includes the corresponding relationship between the fault phenomenon corresponding to the evaluation index value of the fault phenomenon of each problem type sub-module and the phenomenon entropy value of the corresponding fault phenomenon.

[0041] Specifically, in response to the existence of the first target fault phenomenon evaluation index value, the server 104 queries the phenomenon entropy value in the fault phenomenon entropy value evaluation table according to the fault phenomenon corresponding to the first target fault phenomenon evaluation index value, and obtains the phenomenon entropy value of the first target fault phenomenon evaluation index value.

[0042] Step 404, determine the total phenomenon entropy value of the problem type sub-module corresponding to the corresponding fault phenomenon evaluation data according to the sum of the phenomenon entropy values of the first target fault phenomenon evaluation index values corresponding to each fault phenomenon evaluation data.

[0043] Specifically, the server 104 determines the total phenomenon entropy value of the problem type sub-module corresponding to the corresponding fault phenomenon evaluation data according to the sum of the phenomenon entropy values of the first target fault phenomenon evaluation index values corresponding to each fault phenomenon evaluation data, so as to facilitate determining the problem entropy value of each system module according to the total phenomenon entropy value of the problem type sub-module corresponding to each system module, and broaden the fault problem dimension of the system fault warning.

[0044] In a specific example, obtaining the fault phenomenon evaluation data of each problem type sub-module, and after performing phenomenon entropy value evaluation according to each fault phenomenon evaluation data, obtaining the total phenomenon entropy value of the problem type sub-module corresponding to the corresponding fault phenomenon evaluation data, further includes: In response to the existence of the second target fault phenomenon evaluation index value, set the phenomenon entropy value of the second target fault phenomenon evaluation index value to 0; where the second target fault phenomenon evaluation index value is the fault phenomenon evaluation index value that does not have the corresponding fault phenomenon. The above is only a specific example, and it is flexibly set according to user needs in actual applications, and is not limited here.

[0045] In a specific example, after determining the total phenomenon entropy value of the problem type sub-module corresponding to the corresponding fault phenomenon evaluation data according to the sum of the phenomenon entropy values of the first target fault phenomenon evaluation index values corresponding to each of the fault phenomenon evaluation data, further includes: Judge whether the monitoring period has been reached; In response to the monitoring period not arriving, return to the step of obtaining the fault phenomenon evaluation data of each problem type sub-module; In response to the arrival of the monitoring period, clear the monitoring period and return to the step of starting the monitoring period, so as to realize real-time dynamic early warning of system failures. The above is only a specific example, which is flexibly set according to user needs in actual applications and will not be limited here.

[0046] In a specific example, the problem type sub-module includes a hardware-level problem sub-module, a system-level problem sub-module, and an application-level problem sub-module. The failure phenomenon evaluation index values of the hardware-level problem sub-module include memory occupancy rate, CPU occupancy rate, and disk occupancy rate. The failure phenomena corresponding to the failure phenomenon evaluation index values in the hardware-level problem sub-module include the memory suddenly increasing to 80%, the CPU suddenly occupying 80%, and the disk occupancy exceeding 90%. The failure phenomena corresponding to the failure phenomenon evaluation index values in the system-level problem sub-module include the network card becoming slow, the file opening becoming slow, and the process or service being unable to start or stop. The failure phenomena corresponding to the failure phenomenon evaluation index values in the application-level problem sub-module include software error reporting, abnormal software resource occupation, and software non-response.

[0047] The failure phenomenon entropy value evaluation table is as follows:

[0048] The above is only a specific example, which is flexibly set according to user needs in actual applications and will not be limited here.

[0049] In this embodiment, obtain the failure phenomenon evaluation data of each problem type sub-module; then, determine whether there is a failure phenomenon corresponding to the corresponding failure phenomenon evaluation index value according to the failure phenomenon evaluation index value and the threshold condition of the corresponding failure phenomenon evaluation index value; next, in response to the existence of a first target failure phenomenon evaluation index value, in response to the existence of a first target failure phenomenon evaluation index value, query the phenomenon entropy value in the failure phenomenon entropy value evaluation table according to the failure phenomenon corresponding to the first target failure phenomenon evaluation index value to obtain the phenomenon entropy value of the first target failure phenomenon evaluation index value; finally, determine the total phenomenon entropy value of the problem type sub-module corresponding to the corresponding failure phenomenon evaluation data according to the sum of the phenomenon entropy values of the first target failure phenomenon evaluation index values corresponding to each failure phenomenon evaluation data, so as to facilitate determining the problem entropy value of each system module and broaden the failure problem dimension of the system failure early warning.

[0050] Step 203, determine the problem entropy value of each system module according to the total phenomenon entropy value of the corresponding problem type sub-module in each system module.

[0051] Specifically, the server 104 determines the problem entropy value of each system module according to the total phenomenon entropy value of the corresponding problem type sub-module in each system module, so as to facilitate accurately and quickly querying the corresponding failure early warning information according to the problem entropy value of each system module.

[0052] In one embodiment, determining the problem entropy value of each system module according to the total entropy value of the phenomena of the corresponding problem type sub-module in each system module includes: Based on the problem entropy value statistical algorithm, calculate according to the total entropy value of the failure phenomena of the corresponding problem type sub-module in each system module and the weight value of the failure problem types of the corresponding problem type sub-module, and obtain the failure problem entropy value of each system module.

[0053] Specifically, the server 104 calculates according to the total entropy value of the phenomena of the corresponding problem type sub-module in each system module and the weight value of the failure problem types of the corresponding problem type sub-module based on the problem entropy value statistical algorithm, and obtains the failure problem entropy value of each system module, so as to facilitate accurately and quickly querying the corresponding failure warning information according to the problem entropy value of each system module.

[0054] In a specific example, the problem type sub-module includes a hardware-level problem sub-module, a system-level problem sub-module, and an application-level problem sub-module. Calculate the failure problem entropy value of the system module based on the following expression: Value(n) = hand1 × Value(hard) + hand2 × Value(sys) + hand3 × Value(app) ; Wherein, Value(n) is the failure problem entropy value of the n th system module; hand1 is the weight value of the failure problem types of the hardware-level problem sub-module of the n th system module; Value(hard) is the total entropy value of the phenomena of the hardware-level problem sub-module of the n th system module; hand2 is the weight value of the failure problem types of the system-level problem sub-module of the n th system module; Value(sys) is the total entropy value of the phenomena of the system-level problem sub-module of the n th system module; hand3 is the weight value of the failure problem types of the application-level problem sub-module of the n th system module; Value(app) is the total entropy value of the phenomena of the application-level problem sub-module of the n th system module; The above is only a specific example, and it is flexibly set according to user needs in actual applications, and is not limited here.

[0055] In this embodiment, based on the problem entropy value statistical algorithm, calculations are performed according to the total entropy value of the phenomena of the corresponding problem type sub-module in each system module and the weight of the types of fault problems of the corresponding problem type sub-module, to obtain the entropy value of the fault problems of each system module, thereby facilitating accurate and rapid query of the corresponding fault warning information according to the entropy value of the problems of each system module.

[0056] Step 204, query in the system fault warning problem query table according to each problem entropy value to obtain the fault warning information of the corresponding system module.

[0057] Specifically, the server 104 queries in the system fault warning problem query table according to each problem entropy value to obtain the fault warning information of the corresponding system module, realizing real-time dynamic fault warning of multiple systems, broadening the dimension of the fault problems of the system fault warning, and improving the efficiency, timeliness and accuracy of the system fault warning, and accurately positioning the faulty system.

[0058] In a specific example, the system fault warning problem query table includes the correspondence between each problem entropy value interval and the fault warning information of the corresponding problem entropy value interval. Querying in the system fault warning problem query table according to each problem entropy value to obtain the fault warning information of the corresponding system module includes: Determine the problem entropy value interval to which the corresponding problem entropy value belongs according to each problem entropy value; Query in the system fault warning problem query table according to the problem entropy value interval to which each problem entropy value belongs to obtain the fault warning information of the corresponding system module.

[0059] The system fault warning problem query table is as follows:

[0060] The above is only a specific example, and it is flexibly set according to user needs in actual applications, and will not be limited here.

[0061] Based on this, for the above multi-system fault warning method, in response to the completion of the configuration of each system module and the corresponding problem type sub-module of the system module, the monitoring cycle timing is started; the system module is used to represent the corresponding operating system; the problem type sub-module is used to represent the fault problem type of the corresponding system module; then, in response to the monitoring cycle not arriving, the fault phenomenon evaluation data of each problem type sub-module is obtained, and after the phenomenon entropy value evaluation is performed according to each fault phenomenon evaluation data, the total phenomenon entropy value of the problem type sub-module corresponding to the corresponding fault phenomenon evaluation data is obtained; then, the problem entropy value of each system module is determined according to the total phenomenon entropy value of the corresponding problem type sub-module in each system module; finally, the fault warning information of the corresponding system module is queried in the system fault warning problem query table according to each problem entropy value, realizing real-time dynamic fault warning of multiple systems, broadening the fault problem dimension of system fault warning, improving the efficiency, timeliness and accuracy of system fault warning, and accurately positioning the fault system.

[0062] In one embodiment, as Figure 5 shown, the fault warning information includes the system fault problem induction appearance information, warning problem information and file to be backed up information of the corresponding system module; the method further includes steps 501 to 502.

[0063] Step 501, sending the fault warning information of the corresponding system module to the operating system corresponding to each system module.

[0064] Step 502, automatically backing up files according to the file to be backed up information in each fault warning information.

[0065] Specifically, the server 104 sends the fault warning information of the corresponding system module to the operating system corresponding to each system module; then, automatically backs up files according to the file to be backed up information in each fault warning information, facilitating the real-time storage of the file to be backed up information in each fault warning information, enabling fault traceability according to the file to be backed up information, and improving the convenience of multi-system fault warning.

[0066] In this embodiment, the fault warning information of the corresponding system module is sent to the operating system corresponding to each system module; then, automatically backs up files according to the file to be backed up information in each fault warning information, facilitating the real-time storage of the file to be backed up information in each fault warning information, enabling fault traceability according to the file to be backed up information, and improving the convenience of multi-system fault warning.

[0067] In one embodiment, as Figure 5 shown, the method further includes steps 503 to 505.

[0068] Step 503: Query in the fault solution database according to the warning problem information in each fault warning message to obtain the fault solutions for each fault warning message; Step 504: Send the fault solutions for the corresponding system modules to the operating systems corresponding to the respective system modules; Step 505: In response to receiving the confirmation information for the fault solution of the target system module, repair the fault problem of the target system module according to the fault solution of the target system module.

[0069] Among them, the target system module is any one of the system modules. Specifically, the server 104 queries in the fault solution database according to the warning problem information in each fault warning message to obtain the fault solutions for each fault warning message; then, sends the fault solutions for the corresponding system modules to the operating systems corresponding to the respective system modules; and then, in response to receiving the confirmation information for the fault solution of the target system module, repairs the fault problem of the target system module according to the fault solution of the target system module, which facilitates timely repair of the fault problem and improves the convenience of multi-system fault warning.

[0070] In this embodiment, query in the fault solution database according to the warning problem information in each fault warning message to obtain the fault solutions for each fault warning message; then, send the fault solutions for the corresponding system modules to the operating systems corresponding to the respective system modules; and then, in response to receiving the confirmation information for the fault solution of the target system module, repair the fault problem of the target system module according to the fault solution of the target system module, which facilitates timely repair of the fault problem and improves the convenience of multi-system fault warning.

[0071] In one of the embodiments, the method further includes: In response to the monitoring period arriving, clear the monitoring period and return to the step of starting the monitoring period timing.

[0072] Specifically, the server 104, in response to the monitoring period arriving, clears the monitoring period and returns to the step of starting the monitoring period timing, which facilitates cyclic multi-system fault warning.

[0073] In this embodiment, in response to the monitoring period arriving, clear the monitoring period and return to the step of starting the monitoring period timing, which facilitates cyclic multi-system fault warning.

[0074] Through the description of the above embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be implemented by means of software plus a necessary general hardware platform, and of course, it can also be implemented by hardware, but in many cases, the former is a better implementation method. It should be understood that although Figures 2 - 5The steps in the flowchart are shown in sequence according to the arrows, but these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise clearly stated in this document, there is no strict order restriction for the execution of these steps, and these steps can be executed in other orders. Moreover, Figures 2 - 5 at least a part of the steps may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be executed alternately or in turn with at least a part of other steps or sub-steps or stages of other steps.

[0075] In a second aspect, as Figure 6 shown, a multi-system fault warning device is provided. The device includes a timing start module 610, a data acquisition module 620, an entropy value determination module 630, and a warning generation module 640.

[0076] Among them, the timing start module 610 is used to start monitoring cycle timing in response to the completion of the configuration of each system module and the problem type sub-module of the corresponding system module; the system module is used to represent the corresponding operating system; the problem type sub-module is used to represent the types of fault problems of the corresponding system module; the data acquisition module 620 is used to obtain the fault phenomenon evaluation data of each problem type sub-module in response to the monitoring cycle not reaching, and obtain the total entropy value of the phenomenon of the problem type sub-module corresponding to the corresponding fault phenomenon evaluation data after performing phenomenon entropy value evaluation on each fault phenomenon evaluation data; the entropy value determination module 630 is used to determine the problem entropy value of each system module according to the total entropy value of the phenomenon of the corresponding problem type sub-module in each system module; the warning generation module 640 is used to query the system fault warning problem query table according to each problem entropy value to obtain the fault warning information of the corresponding system module.

[0077] In one embodiment, the device further includes a module configuration module.

[0078] Among them, the module configuration module is used to perform module division according to each operating system in the server cluster to obtain the corresponding system module; the module configuration module is used to perform sub-module division according to the corresponding fault problem types in each system module to obtain the problem type sub-module corresponding to each system module, and determine that the configuration of each system module and the problem type sub-module of the corresponding system module is completed.

[0079] In one embodiment, the data acquisition module 620 includes a phenomenon entropy value evaluation unit.

[0080] Among them, the phenomenon entropy value evaluation unit is used to obtain the fault phenomenon evaluation data of each problem type sub-module; the fault phenomenon evaluation data includes the values of each fault phenomenon evaluation index; the fault phenomenon evaluation index is the index value used to evaluate the fault phenomenon of the corresponding problem type sub-module; the phenomenon entropy value evaluation unit is used to judge whether there is a fault phenomenon corresponding to the corresponding fault phenomenon evaluation index value according to the values of each fault phenomenon evaluation index and the threshold condition of the corresponding fault phenomenon evaluation index value; the phenomenon entropy value evaluation unit is used to, in response to the existence of the first target fault phenomenon evaluation index value, query the phenomenon entropy value in the fault phenomenon entropy value evaluation table according to the fault phenomenon corresponding to the first target fault phenomenon evaluation index value, and obtain the phenomenon entropy value of the first target fault phenomenon evaluation index value; among them, the first target fault phenomenon evaluation index value is the evaluation index value corresponding to the existing fault phenomenon; the phenomenon entropy value evaluation unit is used to determine the total phenomenon entropy value of the problem type sub-module corresponding to the corresponding fault phenomenon evaluation data according to the sum of the phenomenon entropy values of the first target fault phenomenon evaluation index values corresponding to each fault phenomenon evaluation data.

[0081] In one embodiment, the entropy value determination module 630 includes an entropy value determination unit.

[0082] Among them, the entropy value determination unit is used to calculate, based on the problem entropy value statistical algorithm, the total phenomenon entropy value of the corresponding problem type sub-module in each system module and the weight of the fault problem types of the corresponding problem type sub-module, to obtain the fault problem entropy value of each system module.

[0083] In one embodiment, the fault warning information includes the system fault problem induction appearance information, the warning problem information, and the file to be backed up information of the corresponding system module; the device further includes a file backup module.

[0084] Among them, the file backup module is used to send the fault warning information of the corresponding system module to the operating system corresponding to each system module; the file backup module is used to automatically back up files according to the file to be backed up information in each fault warning information.

[0085] In one embodiment, the device further includes a fault repair module.

[0086] Among them, the fault repair module is used to query in the fault solution database according to the warning problem information in each fault warning information to obtain the fault solutions of each fault warning information; the fault repair module is used to send the fault solutions of the corresponding system module to the operating system corresponding to each system module; the fault repair module is used to, in response to receiving the confirmation information of the fault solution of the target system module, repair the fault problem of the target system module according to the fault solution of the target system module; among them, the target system module is any system module.

[0087] In one embodiment, the timing start module 610 is further configured to, in response to the arrival of the monitoring period, clear the monitoring period and return to the step of starting the timing of the monitoring period.

[0088] For the specific limitations of the multi-system fault warning device, reference can be made to the limitations of the multi-system fault warning method in the above text, which will not be elaborated here. Each module in the above SATA storage device information transmission multi-system fault warning device can be implemented in whole or in part by software, hardware, and their combination. The above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, or stored in the memory of the computer device in the form of software, so as to facilitate the processor to call and execute the operations corresponding to the above-mentioned modules.

[0089] In a third aspect, the present application further provides an electronic device, including: a memory for storing a computer program; a processor for implementing the steps of any one of the above multi-system fault warning methods when executing the computer program.

[0090] In a fourth aspect, the present application further provides a computer-readable storage medium storing a computer program, wherein the computer program, when executed by a processor, implements the steps of any one of the above multi-system fault warning methods.

[0091] In an exemplary embodiment, the above computer-readable storage medium may include, but is not limited to: various media such as USB flash drives, read-only memories (ROM), random access memories (RAM), mobile hard disks, magnetic disks, or optical discs that can store computer programs.

[0092] In a fifth aspect, an embodiment of the present application further provides a computer program product, where the computer program product includes a computer program, and the computer program, when executed by a processor, implements the steps in any one of the above multi-system fault warning method embodiments.

[0093] An embodiment of the present application further provides another computer program product, including a non-volatile computer-readable storage medium storing a computer program, and the computer program, when executed by a processor, implements the steps in any one of the above multi-system fault warning method embodiments.

[0094] Those skilled in the art may further realize that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be implemented by electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of each example have been generally described according to functions in the above description. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of this application.

[0095] The above has introduced in detail a multi-system fault warning method, device, computer device, and storage medium provided by this application. Specific examples are used herein to elaborate on the principle and implementation manner of this application. The description of the above embodiments is only used to help understand the method and its core idea of this application. It should be noted that for those of ordinary skill in the art in this technical field, without departing from the principle of this application, several improvements and modifications can be made to this application, and these improvements and modifications also fall within the protection scope of this application.

Claims

1. A multi-system fault warning method, characterized in that, The method includes: Upon completion of the configuration of each system module and the corresponding problem type sub-module of the system module, start monitoring cycle timing; the system module is used to represent the corresponding operating system; the problem type sub-module is used to represent the fault problem type of the corresponding system module; Upon the monitoring cycle not arriving, obtain the fault phenomenon evaluation data of each problem type sub-module, and after performing phenomenon entropy value evaluation based on each fault phenomenon evaluation data, obtain the total phenomenon entropy value of the problem type sub-module corresponding to the corresponding fault phenomenon evaluation data; Determine the problem entropy value of each system module according to the total phenomenon entropy value of the corresponding problem type sub-module in each system module; Query in the system fault warning problem query table according to each problem entropy value to obtain the fault warning information of the corresponding system module.

2. The method according to claim 1, wherein The method further includes: After performing module division according to each operating system in the server cluster, obtain the corresponding system module; After performing sub-module division according to the corresponding fault problem type in each system module, obtain the problem type sub-module corresponding to each system module, and determine that the configuration of each system module and the corresponding problem type sub-module of the system module is completed.

3. The method according to claim 1, wherein The obtaining of the fault phenomenon evaluation data of each problem type sub-module and, after performing phenomenon entropy value evaluation based on each fault phenomenon evaluation data, obtaining the total phenomenon entropy value of the problem type sub-module corresponding to the corresponding fault phenomenon evaluation data includes: Obtain the fault phenomenon evaluation data of each problem type sub-module; the fault phenomenon evaluation data includes each fault phenomenon evaluation index value; the fault phenomenon evaluation index is the index value used to evaluate the fault phenomenon of the corresponding problem type sub-module; Judge whether there is a corresponding fault phenomenon for the corresponding fault phenomenon evaluation index value according to each fault phenomenon evaluation index value and the threshold condition of the corresponding fault phenomenon evaluation index value; Upon the existence of a first target fault phenomenon evaluation index value, perform phenomenon entropy value query in the fault phenomenon entropy value evaluation table according to the fault phenomenon corresponding to the first target fault phenomenon evaluation index value, and obtain the phenomenon entropy value of the first target fault phenomenon evaluation index value; wherein, the first target fault phenomenon evaluation index value is the fault phenomenon evaluation index value for which there is a corresponding fault phenomenon; Determine the total phenomenon entropy value of the problem type sub-module corresponding to the corresponding fault phenomenon evaluation data according to the sum of the phenomenon entropy values of the first target fault phenomenon evaluation index values corresponding to each fault phenomenon evaluation data.

4. The method according to claim 1, characterized in that, Determining the problem entropy value of each system module according to the total phenomenon entropy value of the corresponding problem type sub-module in each system module includes: Based on the problem entropy value statistical algorithm, calculate according to the total phenomenon entropy value of the corresponding problem type sub-module in each system module and the fault problem type weight value of the corresponding problem type sub-module to obtain the fault problem entropy value of each system module.

5. The method according to claim 1, characterized in that The fault warning information includes the summarized appearance information of system fault problems, warning problem information, and information of files to be backed up corresponding to the system modules; the method further includes: Sending the fault warning information of the corresponding system module to the operating system corresponding to each system module; Automatically backing up files according to the information of files to be backed up in each fault warning information.

6. The method according to claim 5, characterized in that The method further includes: Querying in a fault solution database according to the warning problem information in each fault warning information to obtain the fault solutions for each fault warning information; Sending the fault solutions of the corresponding system module to the operating system corresponding to each system module; In response to receiving the confirmation information of the fault solution of the target system module, repairing the fault problems of the target system module according to the fault solution of the target system module; wherein, the target system module is any one of the system modules.

7. The method according to any one of claims 1 to 6, characterized in that The method further includes: In response to the arrival of the monitoring period, clearing the monitoring period and returning to the step of starting the monitoring period timing.

8. A multi-system fault warning device, characterized in that, The device includes: A timing start module, configured to start monitoring period timing in response to the configuration completion of each system module and the problem type sub-module corresponding to the system module; the system module is used to represent the corresponding operating system; the problem type sub-module is used to represent the types of fault problems of the corresponding system module; A data acquisition module, configured to obtain the fault phenomenon evaluation data of each problem type sub-module in response to the monitoring period not arriving, and obtain the total phenomenon entropy value of the problem type sub-module corresponding to the corresponding fault phenomenon evaluation data after performing phenomenon entropy value evaluation on each fault phenomenon evaluation data; An entropy value determination module, configured to determine the problem entropy value of each system module according to the total phenomenon entropy value of the problem type sub-module corresponding to each system module; A warning generation module, configured to query in a system fault warning problem query table according to each problem entropy value to obtain the fault warning information of the corresponding system module.

9. An electronic device, characterized in that, Including: A memory, configured to store a computer program; A processor, configured to implement the steps of the multi-system fault warning method according to any one of claims 1 to 7 when executing the computer program.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, The computer program, when executed by the processor, implements the steps of the method according to any one of claims 1 to 7.

Images