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

Abstract

The present application discloses a multi-system fault warning method, apparatus, computer equipment and storage medium, which relate to the technical field of system fault warning. The method comprises the following steps: in response to the completion of configuration of each system module and the problem type submodule of the corresponding system module, starting a monitoring cycle timing; in response to the failure of the monitoring cycle to arrive, obtaining fault phenomenon evaluation data of each problem type submodule, performing phenomenon entropy value evaluation based on each fault phenomenon evaluation data to obtain the phenomenon total entropy value of the problem type submodule corresponding to the corresponding fault phenomenon evaluation data; determining the problem entropy value of each system module based on the phenomenon total entropy value of the corresponding problem type submodule in each system module; and querying a system fault warning problem query table based on each problem entropy value to obtain fault warning information of the corresponding system module. The method solves technical problems such as low efficiency or low timeliness, thereby improving the efficiency, timeliness and accuracy of system fault warning and accurately locating the faulty system.

Description

Technical Field

[0001] The present application relates to the technical field of system failure warning, and in particular to a multi-system failure warning method, apparatus, computer equipment, and storage medium. Background Art

[0002] Many customer production environments currently run a vast array of business software, encompassing a wide range of applications, from basic management and data storage to external services. While servers come in both physical and virtual form factors, they all have operating systems installed. Business topologies encompass all operating systems. Business problems can lead to financial and credit losses. To prevent losses for customers, operating system failure warnings are essential.

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

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

[0005] In a first aspect, the present application provides a multi-system fault early warning method, the method comprising:

[0006] In response to the completion of configuration of each system module and the corresponding system module problem type submodule, the monitoring cycle timing is started; the system module is used to characterize the corresponding operating system; the problem type submodule is used to characterize the fault problem type of the corresponding system module;

[0007] In response to the monitoring period not being reached, obtaining fault phenomenon evaluation data of each problem type submodule, and performing phenomenon entropy value evaluation based on each fault phenomenon evaluation data to obtain a phenomenon total entropy value of the problem type submodule corresponding to the corresponding fault phenomenon evaluation data;

[0008] Determine the problem entropy value of each system module according to the total entropy value of the phenomenon of the corresponding problem type submodule in each system module;

[0009] According to the entropy value of each problem, the system fault warning problem query table is queried to obtain the fault warning information of the corresponding system module.

[0010] In one embodiment, the method further includes: dividing the modules according to the operating systems in the server cluster to obtain corresponding system modules; dividing the submodules according to the corresponding fault problem types in each system module to obtain the problem type submodules corresponding to each system module, and determining that the configuration of each system module and the corresponding problem type submodule of the system module is completed.

[0011] In one embodiment, fault phenomenon evaluation data of each problem type submodule is obtained, and a phenomenon entropy value is evaluated according to each fault phenomenon evaluation data to obtain a total phenomenon entropy value of the problem type submodule corresponding to the corresponding fault phenomenon evaluation data, including: obtaining fault phenomenon evaluation data of each problem type submodule; the fault phenomenon evaluation data includes each fault phenomenon evaluation index value; the fault phenomenon evaluation index is an index value used to evaluate the fault phenomenon of the corresponding problem type submodule; judging whether there is a fault phenomenon corresponding to the corresponding fault phenomenon evaluation index value according to each fault phenomenon evaluation index value and a threshold condition of the corresponding fault phenomenon evaluation index value; in response to the existence of a first target fault phenomenon evaluation index value, performing a phenomenon entropy value query in a fault phenomenon entropy value evaluation table according to the fault phenomenon corresponding to the first target fault phenomenon evaluation index value to obtain a phenomenon entropy value of the first target fault phenomenon evaluation index value; wherein the first target fault phenomenon evaluation index value is an evaluation index value for the existence of the corresponding fault phenomenon; and determining the total phenomenon entropy value of the problem type submodule 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.

[0012] In one embodiment, the problem entropy value of each system module is determined based on the total entropy value of the phenomenon of the corresponding problem type sub-module in each system module, including: based on the problem entropy value statistical algorithm, calculating according to the total entropy value of the phenomenon of the corresponding problem type sub-module in each system module and the fault problem type weight of the corresponding problem type sub-module to obtain the fault problem entropy value of each system module.

[0013] In one embodiment, the fault warning information includes the system fault problem summary information, warning problem information and file information to be backed up of the corresponding system module; the method also includes: sending the fault warning information of the corresponding system module to the operating system corresponding to each system module; and automatically backing up files according to the file information to be backed up in each fault warning information.

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

[0015] In one embodiment, the method further comprises:

[0016] In response to the monitoring period arriving, the monitoring period is cleared to zero, and the process returns to the step of starting the monitoring period timing.

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

[0018] Among them, the timing start module is used to start the monitoring cycle timing in response to the completion of configuration of each system module and the corresponding system module problem type submodule; the system module is used to characterize the corresponding operating system; the problem type submodule is used to characterize the type of fault problem of the corresponding system module;

[0019] A data acquisition module is used to obtain the fault phenomenon evaluation data of each problem type submodule in response to the monitoring period not being reached, and to evaluate the phenomenon entropy value of each fault phenomenon evaluation data to obtain the total phenomenon entropy value of the problem type submodule corresponding to the corresponding fault phenomenon evaluation data;

[0020] An entropy value determination module is used to determine the problem entropy value of each system module based on the total entropy value of the phenomenon of the corresponding problem type submodule in each system module;

[0021] The early warning generation module is used to query the system fault early warning problem query table according to the entropy value of each problem to obtain the fault early warning information of the corresponding system module.

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

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

[0024] Through the present application, the above-mentioned multi-system fault warning method, device, computer equipment and storage medium start the monitoring cycle timing in response to the completion of configuration of each system module and the problem type submodule of the corresponding system module; the system module is used to characterize the corresponding operating system; the problem type submodule is used to characterize the fault problem type of the corresponding system module; then, in response to the monitoring cycle not being arrived, the fault phenomenon evaluation data of each problem type submodule is obtained, and the phenomenon entropy value of the corresponding problem type submodule corresponding to the corresponding fault phenomenon evaluation data is evaluated after the phenomenon entropy value is evaluated; then, the problem entropy value of each system module is determined according to the phenomenon total entropy value of the corresponding problem type submodule in each system module; finally, according to the entropy value of each problem, the system fault warning problem query table is queried 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 fault problem dimension of system fault warning is broadened, the efficiency, timeliness and accuracy of system fault warning are improved, and the faulty system is accurately located. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] In order to more clearly illustrate the embodiments of the present application, the following is a brief introduction to the drawings required for use in the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0026] Figure 1 This is an application environment diagram of a multi-system fault early warning method in one embodiment;

[0027] Figure 2 1 is a schematic diagram of a first flow chart of a multi-system fault early warning method in one embodiment;

[0028] Figure 3 A second flow chart of a multi-system fault early warning method according to an embodiment;

[0029] Figure 4 A schematic diagram of a process for obtaining fault phenomenon evaluation data of each problem type submodule and performing phenomenon entropy value evaluation based on each fault phenomenon evaluation data to obtain the total phenomenon entropy value of the problem type submodule corresponding to the corresponding fault phenomenon evaluation data in one embodiment;

[0030] Figure 5 A third flow chart of a multi-system fault early warning method in one embodiment;

[0031] Figure 6 FIG. 4 is a structural block diagram of a multi-system fault warning device in one embodiment. DETAILED DESCRIPTION

[0032] The following will be combined with the accompanying drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0033] It should be noted that, in the description of this application, the terms "comprises," "includes," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or device. The terms "first," "second," etc., in this application are used to distinguish similar objects, and are not used to describe a particular order or sequence.

[0034] In order to enable those skilled in the art to better understand the present application, the present application is further described in detail below with reference to the accompanying drawings and specific implementation methods.

[0035] The multi-system fault warning method provided in this application can be applied to Figure 1 In the application environment shown, the terminal 102 communicates with the server 104 via a network. The terminal 102 may be, but is not limited to, various personal computers, laptops, smart phones, tablet computers, and portable wearable devices, and the server 104 may be implemented as an independent server or a server cluster consisting of multiple servers.

[0036] First, as Figure 2 As shown, a multi-system fault early warning method is provided, which is applied to Figure 1 The server 104 in the example is used for explanation, including the following steps 201 to 204.

[0037] Step 201 : In response to the completion of configuration of each system module and the corresponding problem type submodule of the system module, start the monitoring cycle timing.

[0038] The system module is used to represent the corresponding operating system; the problem type submodule is used to represent the fault problem type of the corresponding system module. Specifically, the server 104 starts the monitoring cycle timer in response to the completion of the configuration of each system module and the corresponding system module problem type submodule.

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

[0040] In one embodiment, Figure 3 As shown, the method further includes step 301 and step 302.

[0041] Step 301 : performing module division according to each operating system in the server cluster to obtain corresponding system modules.

[0042] Step 302 : After dividing the submodules according to the corresponding fault problem types in each system module, obtain the problem type submodules corresponding to each system module, and determine that the configuration of each system module and the corresponding problem type submodule of the system module is completed.

[0043] Specifically, the server 104 divides the modules according to the operating systems in the server cluster to obtain corresponding system modules; then, the server 104 divides the submodules according to the corresponding fault problem types in each system module to obtain the problem type submodules corresponding to each system module, and determines that the configuration of each system module and the corresponding system module problem type submodule is completed, thereby facilitating the realization of multi-system and multi-dimensional fault warning.

[0044] In this embodiment, the corresponding system modules are obtained after module division according to each operating system in the server cluster; then, the problem type sub-modules corresponding to each system module are obtained after sub-module division according to the corresponding fault problem type in each system module, and the configuration of each system module and the corresponding system module problem type sub-module is completed, thereby facilitating the realization of multi-system and multi-dimensional fault warning.

[0045] Step 202 : in response to the monitoring period not being reached, obtaining fault phenomenon evaluation data of each problem type submodule, and evaluating the phenomenon entropy value of each fault phenomenon evaluation data to obtain the total phenomenon entropy value of the problem type submodule corresponding to the corresponding fault phenomenon evaluation data.

[0046] The fault phenomenon assessment data is assessment data of the corresponding fault phenomenon occurring in the corresponding problem type submodule. Specifically, in response to the monitoring period not being reached, the server 104 obtains the fault phenomenon assessment data of each problem type submodule, and performs a phenomenon entropy value assessment based on each fault phenomenon assessment data to obtain a total phenomenon entropy value of the problem type submodule corresponding to the corresponding fault phenomenon assessment data.

[0047] In one embodiment, Figure 4 As shown, the fault phenomenon evaluation data of each problem type submodule is obtained, and the phenomenon entropy value of the corresponding problem type submodule corresponding to the corresponding fault phenomenon evaluation data is evaluated according to the phenomenon entropy value, including steps 401 to 404.

[0048] Step 401: Obtain fault phenomenon evaluation data for each problem type submodule.

[0049] The fault phenomenon evaluation data includes each fault phenomenon evaluation index value. The fault phenomenon evaluation index is an index value used to evaluate the fault phenomenon of the corresponding problem type submodule. Specifically, the server 104 obtains the fault phenomenon evaluation data of each problem type submodule.

[0050] Step 402 : judging whether a fault phenomenon corresponding to a corresponding fault phenomenon evaluation index value exists based on each fault phenomenon evaluation index value and a threshold condition corresponding to the fault phenomenon evaluation index value.

[0051] The server 104 determines whether the fault phenomenon corresponding to the corresponding fault phenomenon evaluation index value exists based on each fault phenomenon evaluation index value and a threshold condition of the corresponding fault phenomenon evaluation index value.

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

[0053] The first target fault phenomenon evaluation index value is an evaluation index value of a corresponding fault phenomenon. The fault phenomenon entropy value evaluation table includes a correspondence between the fault phenomenon corresponding to the fault phenomenon evaluation index value corresponding to each problem type submodule and the phenomenon entropy value of the corresponding fault phenomenon.

[0054] Specifically, in response to the existence of the first target fault phenomenon evaluation index value, the server 104 performs a 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 obtains the phenomenon entropy value of the first target fault phenomenon evaluation index value.

[0055] Step 404 : determining the total phenomenon entropy value of the problem type submodule 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 the respective fault phenomenon evaluation data.

[0056] Specifically, the server 104 determines the total phenomenon entropy value of the problem type sub-module corresponding to the corresponding fault phenomenon evaluation data based on the sum of the phenomenon entropy values ​​of the first target fault phenomenon evaluation index values ​​corresponding to each fault phenomenon evaluation data, thereby facilitating the determination of the problem entropy value of each system module based on the total phenomenon entropy value of the corresponding problem type sub-module in each system module, thereby broadening the fault problem dimension of the system fault warning.

[0057] In a specific example, the fault phenomenon evaluation data of each problem type submodule is obtained, and the phenomenon entropy value is evaluated according to each fault phenomenon evaluation data to obtain the total phenomenon entropy value of the problem type submodule corresponding to the corresponding fault phenomenon evaluation data, further comprising:

[0058] In response to the presence of a second target fault phenomenon evaluation index value, the phenomenon entropy value of the second target fault phenomenon evaluation index value is set to 0; wherein the second target fault phenomenon evaluation index value is the fault phenomenon evaluation index value when the corresponding fault phenomenon does not exist. The above is only a specific example, and in actual application, it can be flexibly set according to user needs and is not limited here.

[0059] In a specific example, after determining the phenomenon total entropy value of the problem type submodule 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, the method further includes:

[0060] Determine whether the monitoring period has been reached;

[0061] In response to the monitoring period not being reached, returning to the step of obtaining fault phenomenon assessment data of each problem type submodule;

[0062] In response to the monitoring cycle arriving, the monitoring cycle is reset and the process returns to the step of starting the monitoring cycle, thereby achieving real-time dynamic warning of system failure. The above is only a specific example, and in actual application, it can be flexibly set according to user needs and is not limited here.

[0063] In a specific example, the problem type submodule includes a hardware-level problem submodule, a system-level problem submodule, and an application-level problem submodule. The fault phenomenon evaluation index values ​​of the hardware-level problem submodule include memory usage, CPU usage, and disk usage. The fault phenomena corresponding to the fault phenomenon evaluation index values ​​in the hardware-level problem submodule include memory suddenly increasing to 80%, CPU suddenly occupying 80%, and disk usage exceeding 90%. The fault phenomena corresponding to the fault phenomenon evaluation index values ​​in the system-level problem submodule include network card slowdown, file opening slowdown, and process or service inability to start or stop. The fault phenomena corresponding to the fault phenomenon evaluation index values ​​in the application-level problem submodule include software errors, abnormal software resource usage, and software no response.

[0064] The fault phenomenon entropy value evaluation table is as follows:

[0065]

[0066] The above are only specific examples, which can be flexibly configured according to user needs in actual applications and are not limited here.

[0067] In this embodiment, fault phenomenon evaluation data of each problem type sub-module is obtained; then, based on each fault phenomenon evaluation index value and the threshold condition of the corresponding fault phenomenon evaluation index value, it is determined whether there is a fault phenomenon corresponding to the corresponding fault phenomenon evaluation index value; then, in response to the existence of the first target fault phenomenon evaluation index value, a phenomenon entropy value query is performed in the fault phenomenon entropy value evaluation table according to the fault phenomenon corresponding to the first target fault phenomenon evaluation index value to obtain the phenomenon entropy value of the first target fault phenomenon evaluation index value; finally, based on the sum of the phenomenon entropy values ​​of the first target fault phenomenon evaluation index value corresponding to each fault phenomenon evaluation data, the phenomenon total entropy value of the problem type sub-module corresponding to the corresponding fault phenomenon evaluation data is determined, thereby facilitating the determination of the problem entropy value of each system module and broadening the fault problem dimension of the system fault warning.

[0068] Step 203 : determining the problem entropy value of each system module according to the total entropy value of the phenomena of the corresponding problem type submodule in each system module.

[0069] Specifically, the server 104 determines the problem entropy value of each system module according to the total entropy value of the phenomenon of the corresponding problem type submodule in each system module, thereby facilitating accurate and rapid query of corresponding fault warning information according to the problem entropy value of each system module.

[0070] In one embodiment, determining the problem entropy value of each system module according to the total entropy value of the phenomenon of the corresponding problem type submodule in each system module includes:

[0071] Based on the problem entropy statistical algorithm, the fault problem entropy value of each system module is obtained by calculating the total entropy value of the fault phenomenon of the corresponding problem type submodule in each system module and the fault problem type weight of the corresponding problem type submodule.

[0072] Specifically, based on the problem entropy statistical algorithm, server 104 calculates the total entropy value of the phenomenon of the corresponding problem type sub-module in each system module and the fault problem type weight of the corresponding problem type sub-module to obtain the fault problem entropy value of each system module, thereby facilitating accurate and rapid query of the corresponding fault warning information based on the problem entropy value of each system module.

[0073] In a specific example, the problem type submodule includes a hardware level problem submodule, a system level problem submodule, and an application level problem submodule. The fault problem entropy value of the system module is calculated based on the following expression:

[0074] Value(n) = hand1 × Value(hard) + hand2 × Value(sys) + hand3 × Value(app) ;

[0075] in, Value(n) For the n The entropy value of the fault problem of each system module; hand1 For the n The fault problem type weight of the hardware level problem submodule of each system module; Value(hard) For the n The total entropy of the phenomena of the hardware-level problem submodules of each system module; hand2 For the n The fault problem type weight of the system-level problem submodule of each system module; Value(sys) For the n The total entropy of the phenomena of the system-level problem submodules of each system module; hand3 For the n The weight of the fault problem type of the application level problem submodule of each system module; Value(app) For the n The total entropy value of the phenomenon of the application-level problem sub-module of each system module; the above is only a specific example, and in actual application it is flexibly set according to user needs and is not limited here.

[0076] In this embodiment, based on the problem entropy statistical algorithm, the fault problem entropy value of each system module is obtained according to the total entropy value of the phenomenon of the corresponding problem type sub-module in each system module and the fault problem type weight of the corresponding problem type sub-module, so as to facilitate the accurate and rapid query of the corresponding fault warning information according to the problem entropy value of each system module.

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

[0078] Specifically, server 104 queries the system fault warning problem query table according to the entropy value of each problem to obtain the fault warning information of the corresponding system module, realizes real-time dynamic fault warning of multiple systems, broadens the fault problem dimension of system fault warning, improves the efficiency, timeliness and accuracy of system fault warning, and accurately locates the faulty system.

[0079] 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. According to the entropy value of each problem, the system fault warning problem query table is queried to obtain the fault warning information of the corresponding system module, including:

[0080] Determine the entropy value interval to which the corresponding entropy value belongs according to the entropy value of each question;

[0081] According to the problem entropy value interval to which each problem entropy value belongs, the system fault warning problem query table is queried to obtain the fault warning information of the corresponding system module.

[0082] The query table for system fault warning problems is as follows:

[0083]

[0084] The above are only specific examples, which can be flexibly configured according to user needs in actual applications and are not limited here.

[0085] Based on this, the above-mentioned multi-system fault warning method starts the monitoring cycle timing in response to the completion of configuration of each system module and the problem type submodule of the corresponding system module; the system module is used to characterize the corresponding operating system; the problem type submodule is used to characterize the fault problem type of the corresponding system module; then, in response to the monitoring cycle not being arrived, the fault phenomenon evaluation data of each problem type submodule is obtained, and the phenomenon entropy value of the corresponding problem type submodule corresponding to the corresponding fault phenomenon evaluation data is evaluated after the phenomenon entropy value is evaluated; then, the problem entropy value of each system module is determined according to the phenomenon total entropy value of the corresponding problem type submodule in each system module; finally, according to the entropy value of each problem, the system fault warning problem query table is queried to obtain the fault warning information of the corresponding system module, thereby realizing real-time dynamic fault warning of multiple systems, broadening the fault problem dimension of the system fault warning, improving the efficiency, timeliness and accuracy of the system fault warning, and accurately locating the faulty system.

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

[0087] Step 501: Send fault warning information of the corresponding system module to the operating system corresponding to each system module.

[0088] Step 502: Automatically back up files according to the information of files to be backed up in each fault warning information.

[0089] Specifically, the server 104 sends the fault warning information of the corresponding system module to the operating system corresponding to each system module; then, the file is automatically backed up according to the file information to be backed up in each fault warning information, which is convenient for real-time storage of the file information to be backed up in each fault warning information, and can facilitate fault tracing based on the file information to be backed up, thereby improving the convenience of multi-system fault warning.

[0090] In this embodiment, the fault warning information of the corresponding system module is sent to the operating system corresponding to each system module; then, the files are automatically backed up according to the to-be-backed-up file information in each fault warning information, so as to facilitate the real-time storage of the to-be-backed-up file information in each fault warning information, facilitate the fault tracing according to the to-be-backed-up file information, and improve the convenience of multi-system fault warning.

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

[0092] Step 503: query the fault solution database based on the warning problem information in each fault warning information to obtain the fault solution of each fault warning information;

[0093] Step 504: Send the fault solution of the corresponding system module to the operating system corresponding to each system module;

[0094] Step 505 : In response to receiving 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.

[0095] The target system module is any system module. Specifically, the server 104 searches the fault solution database based on the warning problem information in each fault warning information to obtain the fault solution for each fault warning information; then, the server 104 sends the fault solution for the corresponding system module to the operating system corresponding to each system module; then, in response to receiving confirmation information of the fault solution for the target system module, the server 104 repairs the fault problem in the target system module based on the fault solution for the target system module, thereby facilitating timely repair of the fault problem and improving the convenience of multi-system fault warning.

[0096] In this embodiment, a query is performed in the fault solution database based on the warning problem information in each fault warning information to obtain a fault solution for each fault warning information; then, the fault solution of the corresponding system module is sent to the operating system corresponding to each system module; then, in response to the confirmation information of the fault solution received for the target system module, the fault problem of the target system module is repaired 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.

[0097] In one embodiment, the method further comprises:

[0098] In response to the monitoring period arriving, the monitoring period is cleared to zero, and the process returns to the step of starting the monitoring period timing.

[0099] Specifically, in response to the monitoring period arriving, the server 104 resets the monitoring period and returns to the step of starting the monitoring period timing, so as to facilitate cyclic multi-system fault warning.

[0100] In this embodiment, in response to the monitoring period arriving, the monitoring period is reset to zero, and the process returns to the step of starting the monitoring period timing, so as to facilitate cyclic multi-system fault warning.

[0101] Through the description of the above embodiments, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, or by hardware, but in many cases the former is a better implementation method. Figure 2-Figure 5 The steps in the flowchart are shown in sequence as indicated by the arrows, but these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified in this document, there is no strict order restriction for the execution of these steps, and these steps can be executed in other orders. In addition, Figure 2-Figure 5 At least part of the steps may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily executed 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 in turn or alternately with other steps or at least part of the sub-steps or stages of other steps.

[0102] Second, as Figure 6 As shown, a multi-system fault warning device is provided, which includes a timing start module 610, a data acquisition module 620, an entropy value determination module 630 and a warning generation module 640.

[0103] Among them, the timing start module 610 is used to start the monitoring cycle timing in response to the completion of the configuration of each system module and the corresponding system module's problem type submodule; the system module is used to characterize the corresponding operating system; the problem type submodule is used to characterize the type of fault problem of the corresponding system module; the data acquisition module 620 is used to obtain the fault phenomenon evaluation data of each problem type submodule in response to the monitoring cycle not being arrived, and obtain the total phenomenon entropy value of the problem type submodule corresponding to the corresponding fault phenomenon evaluation data after evaluating the phenomenon entropy value of each fault phenomenon evaluation data; the entropy value determination module 630 is used to determine the problem entropy value of each system module based on the total phenomenon entropy value of the corresponding problem type submodule in each system module; the warning generation module 640 is used to query the system fault warning problem query table based on the entropy value of each problem to obtain the fault warning information of the corresponding system module.

[0104] In one embodiment, the apparatus further includes a module configuration module.

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

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

[0107] 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 each fault phenomenon evaluation index value; the fault phenomenon evaluation index is an index value used to evaluate the fault phenomenon of the corresponding problem type sub-module; the phenomenon entropy value evaluation unit is used to determine whether there is a fault phenomenon corresponding to the corresponding fault phenomenon evaluation index value based on each fault phenomenon evaluation index value and the threshold condition of the corresponding fault phenomenon evaluation index value; the phenomenon entropy value evaluation unit is used to respond to the existence of a first target fault phenomenon evaluation index value, and perform a 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 to 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 evaluation index value of the corresponding fault phenomenon; the phenomenon entropy value evaluation unit is used to determine the phenomenon total entropy value of the problem type sub-module corresponding to the corresponding fault phenomenon evaluation data based on the sum of the phenomenon entropy values ​​of the first target fault phenomenon evaluation index values ​​corresponding to each fault phenomenon evaluation data.

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

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

[0110] In one embodiment, the fault warning information includes system fault problem summary information, warning problem information and file information to be backed up of the corresponding system module; the device also includes a file backup module.

[0111] 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 information of the files to be backed up in each fault warning information.

[0112] In one embodiment, the device further includes a fault recovery module.

[0113] Among them, the fault repair module is used to query the fault solution database according to the warning problem information in each fault warning information, and obtain the fault solution of each fault warning information; the fault repair module is used to send the fault solution of the corresponding system module to the operating system corresponding to each system module; the fault repair module is used to respond to the confirmation information of the fault solution of the target system module, and repair the fault problem of the target system module according to the fault solution of the target system module; wherein the target system module is any system module.

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

[0115] The specific definitions of the multi-system fault warning device can be found in the definitions of the multi-system fault warning method above and will not be further elaborated here. Each module in the aforementioned SATA storage device information transmission multi-system fault warning device can be implemented in whole or in part through software, hardware, or a combination thereof. Each of these modules can be embedded in or independent of a processor in a computer device in hardware form, or stored in a computer device memory in software form, allowing the processor to call and execute the corresponding operations of each module.

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

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

[0118] In an exemplary embodiment, the computer-readable storage medium may include, but is not limited to, various media that can store computer programs, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk, or an optical disk.

[0119] In a fifth aspect, an embodiment of the present application further provides a computer program product, which includes a computer program. When the computer program is executed by a processor, it implements the steps in any of the above-mentioned multi-system fault warning method embodiments.

[0120] An embodiment of the present application also provides another computer program product, including a non-volatile computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, it implements the steps of any of the above-mentioned multi-system fault warning method embodiments.

[0121] Professionals may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the above description has generally described the components and steps of each example according to their functions. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0122] The above is a detailed introduction to a multi-system fault warning method, device, computer equipment and storage medium provided by the present application. Specific examples are used herein to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method and core ideas of the present application. It should be pointed out that for ordinary technicians in this technical field, without departing from the principles of the present application, several improvements and modifications can be made to the present application, and these improvements and modifications also fall within the scope of protection of the present application.

Claims

1. A multi-system fault early warning method, characterized in that: The method comprises: In response to the completion of configuration of each system module and the corresponding problem type submodule of the system module, starting the monitoring cycle timing; the system module is used to characterize the corresponding operating system; the problem type submodule is used to characterize the fault problem type of the corresponding system module; In response to the monitoring period not being reached, acquiring fault phenomenon evaluation data of each of the problem type submodules, and performing phenomenon entropy value evaluation based on each of the fault phenomenon evaluation data to obtain a phenomenon total entropy value of the problem type submodule corresponding to the corresponding fault phenomenon evaluation data; the fault phenomenon evaluation data is evaluation data of the corresponding fault phenomenon occurring in the corresponding problem type submodule; The problem entropy value of each system module is determined according to the phenomenon total entropy value of the corresponding problem type submodule in each system module; wherein, the fault phenomenon evaluation data of each problem type submodule is obtained, and the phenomenon entropy value is evaluated according to each fault phenomenon evaluation data to obtain the phenomenon total entropy value of the problem type submodule corresponding to the corresponding fault phenomenon evaluation data, including: obtaining the fault phenomenon evaluation data of each problem type submodule; the fault phenomenon evaluation data includes each fault phenomenon evaluation index value; the fault phenomenon evaluation index is used to evaluate the fault phenomenon of the corresponding problem type submodule; according to each fault phenomenon evaluation index value and the corresponding fault phenomenon evaluation index The threshold condition of the value determines whether there is the fault phenomenon corresponding to the corresponding fault phenomenon evaluation index value; in response to the existence of the first target fault phenomenon evaluation index value, a phenomenon entropy value query is performed in the fault phenomenon entropy value evaluation table according to the fault phenomenon corresponding to the first target fault phenomenon evaluation index value to 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 the corresponding fault phenomenon exists; the phenomenon total entropy value of the problem type submodule corresponding to the corresponding fault phenomenon evaluation data is determined 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; According to each of the problem entropy values, querying the system fault warning problem query table obtains the fault warning information of the corresponding system module; wherein, 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 the system fault warning problem query table according to each of the problem entropy values ​​obtains the fault warning information of the corresponding system module, including: determining the problem entropy value interval to which the corresponding problem entropy value belongs according to each of the problem entropy values; querying the system fault warning problem query table according to the problem entropy value interval to which each of the problem entropy values ​​belongs obtains the fault warning information of the corresponding system module.

2. The method according to claim 1, characterized in that The method further comprises: After performing module division according to each of the operating systems in the server cluster, the corresponding system modules are obtained; After dividing the submodules according to the corresponding fault problem types in each system module, the problem type submodules corresponding to each system module are obtained, and it is determined that the configuration of each system module and the corresponding problem type submodule of the system module is completed.

3. The method according to claim 1, characterized in that The acquiring of the fault phenomenon evaluation data of each of the problem type submodules, and performing phenomenon entropy value evaluation based on each of the fault phenomenon evaluation data to obtain the phenomenon total entropy value of the problem type submodule corresponding to the corresponding fault phenomenon evaluation data, includes: In response to the existence of a second target fault phenomenon evaluation index value, setting the phenomenon entropy value of the second target fault phenomenon evaluation index value to 0; wherein the second target fault phenomenon evaluation index value is the fault phenomenon evaluation index value when the corresponding fault phenomenon does not exist.

4. The method according to claim 1, wherein Determining the problem entropy value of each system module according to the total entropy value of the phenomenon of the corresponding problem type submodule in each system module includes: Based on the problem entropy statistical algorithm, the fault problem entropy value of each system module is obtained by calculating the total entropy value of the phenomenon of the corresponding problem type submodule in each system module and the fault problem type weight of the corresponding problem type submodule.

5. The method according to claim 1, wherein The fault warning information includes the system fault problem summary information, warning problem information and file information to be backed up of the corresponding system module; the method further includes: Sending the fault warning information of the corresponding system module to the operating system corresponding to each system module; Automatically back up files according to the to-be-backed-up file information in each of the fault warning messages.

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

7. The method according to any one of claims 1 to 6, characterized in that The method further comprises: In response to the monitoring period arriving, the monitoring period is cleared to zero, and the process returns to the step of starting the monitoring period timing.

8. A multi-system fault warning device, characterized in that: The device comprises: a timing start module for starting a monitoring cycle timer in response to completion of configuration of each system module and the corresponding problem type submodule of the system module; the system module is used to characterize the corresponding operating system; the problem type submodule is used to characterize the type of fault problem of the corresponding system module; a data acquisition module, configured to acquire, in response to the monitoring period not being reached, fault phenomenon evaluation data of each of the problem type submodules, and to evaluate the phenomenon entropy value of each of the fault phenomenon evaluation data to obtain a total phenomenon entropy value of the problem type submodule corresponding to the corresponding fault phenomenon evaluation data; the fault phenomenon evaluation data being evaluation data of the corresponding fault phenomenon occurring in the corresponding problem type submodule; An entropy value determination module 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 submodule in each system module; wherein the data acquisition module includes a phenomenon entropy value evaluation unit; the phenomenon entropy value evaluation unit is used to obtain the fault phenomenon evaluation data of each problem type submodule; the fault phenomenon evaluation data includes each fault phenomenon evaluation index value; the fault phenomenon evaluation index is used to evaluate the index value of the fault phenomenon of the corresponding problem type submodule; the phenomenon entropy value evaluation unit is used to judge whether there is a corresponding fault phenomenon evaluation index value according to each fault phenomenon evaluation index value and the threshold condition corresponding to the fault phenomenon evaluation index value. the fault phenomenon corresponding to the first target fault phenomenon evaluation index value; the phenomenon entropy value evaluation unit is used to, in response to the existence of a first target fault phenomenon evaluation index value, perform a phenomenon entropy value query in a fault phenomenon entropy value evaluation table according to the fault phenomenon corresponding to the first target fault phenomenon evaluation index value, and obtain a 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 of the corresponding fault phenomenon; the phenomenon entropy value evaluation unit is used to determine the phenomenon total entropy value of the problem type submodule 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; An early warning generation module is used to query the system fault early warning problem query table according to each of the problem entropy values ​​to obtain the corresponding fault early warning information of the system module; wherein the system fault early warning problem query table includes the correspondence between each problem entropy value interval and the fault early warning information of the corresponding problem entropy value interval; querying the system fault early warning problem query table according to each of the problem entropy values ​​to obtain the corresponding fault early warning information of the system module includes: determining the problem entropy value interval to which the corresponding problem entropy value belongs according to each of the problem entropy values; querying the system fault early warning problem query table according to the problem entropy value interval to which each of the problem entropy values ​​belongs to obtain the corresponding fault early warning information of the system module.

9. An electronic device, characterized in that: include: Memory for storing computer programs; A processor is configured to implement the steps of the multi-system fault early 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: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

Images