Alarm method and device, electronic equipment, medium and product

Abstract

The invention discloses an alarm method and device, electronic equipment, a medium and a product, and relates to the technical field of equipment management, when to-be-detected equipment works abnormally, jitter removal detection processing is firstly carried out to determine whether the reason of the abnormal work is fault or jitter, so that the situation that the jitter which does not affect the work of the to-be-detected equipment is alarmed can be avoided, and the reliability of the to-be-detected equipment is improved. Therefore, the alarm accuracy is improved.

Description

Technical Field

[0001] This application relates to the technical field of device management, and particularly to an alarm method, device, electronic device, medium and product. Background Art

[0002] During the operation of a device, the device may malfunction due to various factors, such as changes in power supply status, device temperature, or working environment. Managing the device to promptly detect and resolve faults is of great significance for maintaining the normal operation of the device.

[0003] In the related art, the working parameters of the device are detected, and the working state of the device is determined according to the working parameters. If the working state is abnormal, alarm processing is directly performed to improve the ability of operation and maintenance personnel to handle faults. However, this method has the problem of low alarm accuracy. Summary of the Invention

[0004] This application provides an alarm method, device, electronic device, medium and product to at least solve the problem of low alarm accuracy in the related art.

[0005] This application provides an alarm method, including: receiving a detection request, where the detection request includes at least one device identifier to be detected; determining at least one device to be detected corresponding to the at least one device identifier to be detected according to the detection request; determining the working state of the device to be detected; if the working state is abnormal, performing a debounce detection process on the device to be detected to obtain a detection result, and performing alarm processing according to the detection result.

[0006] This application also provides an alarm device, including: a receiving module, configured to receive a detection request, where the detection request includes at least one device identifier to be detected; a determining module, configured to determine at least one device to be detected corresponding to the at least one device identifier to be detected according to the detection request; an obtaining module, configured to determine the working state of the device to be detected; a detection module, configured to, if the working state is abnormal, perform a debounce detection process on the device to be detected to obtain a detection result, and perform alarm processing according to the detection result.

[0007] This application also provides an electronic device, including: a memory, configured to store a computer program; a processor, configured to implement the steps of any of the above alarm methods when executing the computer program.

[0008] This application also provides a computer-readable storage medium, in which a computer program is stored, and the computer program, when executed by a processor, implements the steps of any of the above alarm methods.

[0009] This application also provides a computer program product, including a computer program, and the computer program, when executed by a processor, implements the steps of any of the above alarm methods.

[0010] Through the present application, when the device to be detected malfunctions, a debounce detection process is first performed to determine whether the cause of the malfunction is a fault or a jitter, which can avoid alarming for jitters that do not affect the operation of the device to be detected, thereby improving the accuracy of the alarm. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] To more clearly illustrate the embodiments of the present application, the drawings required for 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, other drawings can be obtained based on these drawings without creative efforts.

[0012] Figure 1 Schematic diagram of an application scenario of an alarm method provided by an embodiment of the present application;

[0013] Figure 2 Schematic diagram of a flow of an alarm method provided by an embodiment of the present application;

[0014] Figure 3 Schematic diagram of a flow of an alarm method provided by an embodiment of the present application;

[0015] Figure 4 Schematic diagram of issuing a working policy provided by an embodiment of the present application;

[0016] Figure 5 Schematic diagram of debounce detection provided by an embodiment of the present application;

[0017] Figure 6 Schematic diagram of a lighting policy provided by an embodiment of the present application;

[0018] Figure 7 Schematic diagram of controller alarm provided by an embodiment of the present application;

[0019] Figure 8 Schematic diagram of the structure of an alarm device provided by an embodiment of the present application;

[0020] Figure 9 Schematic diagram of the structure of an alarm device provided by an embodiment of the present application;

[0021] Figure 10 Schematic diagram of the structure of an electronic device provided by an embodiment of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS

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

[0023] 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 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 also 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.

[0024] Exemplarily, faults or jitters may occur during the operation of the device. A fault is a serious abnormality that will seriously affect the operation of the device. Faults should be processed in a timely manner, otherwise the device may not be able to achieve or fully achieve the corresponding functions, and may even affect other devices. Jitter can be an instantaneous fluctuation abnormality generated during the operation of the device. At this time, the device is in a transitional state, and the jitter is within the safe and controllable range and does not affect the normal operation of the device.

[0025] In practical applications, multiple devices can work together. For example, a large data center includes multiple devices, and the multiple devices work together to achieve the functions of the large data center. If some of the devices fail, it may cause the large data center to not work properly, and may even cause other devices to be damaged. Therefore, it is necessary to accurately alarm for faults to prompt the operation and maintenance personnel to process the faults in a timely manner and restore the normal functions of the large data center.

[0026] In the related art, both faults and jitters will cause abnormalities in the device. The difference lies in the degree and duration of the abnormality. Jitters do not need to be processed and correspondingly do not need to be alarmed. If faults and jitters are not distinguished and alarms are given for both, there will be a problem of false alarms, and the operation and maintenance personnel's handling of false alarms will affect the maintenance of the device. For example, when multiple devices generate alarms, the operation and maintenance personnel need to check one by one to determine whether the alarm is caused by jitter or fault. The operation and maintenance personnel's handling of the alarm caused by jitter will affect the efficiency of handling the alarm caused by fault, and the failure to process the fault in a timely manner will affect the normal operation of the device.

[0027] In order 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 accompanying drawings and specific embodiments.

[0028] In combination with the specific application environment architecture or specific hardware architecture on which the execution of the alarm method depends, the specific application environment architecture or specific hardware architecture is described herein. Refer to Figure 1 , Figure 1 FIG. Figure 1 is a schematic diagram of the application scenario of the alarm method. The device is detected and processed to obtain the working state of the device. The working state is normal or abnormal. If the working state is abnormal, alarm processing is performed.

[0029] In the related art, without distinguishing whether the abnormal working state is caused by a fault or a jitter and directly performing an alarm, there may be a problem of false alarms.

[0030] In this application, when it is determined that the working state of the device is abnormal, a judgment process is performed to determine whether the abnormal working state is caused by a fault or a jitter. Only the abnormal working state caused by a fault is alarmed, avoiding the problem of false alarms, thereby improving the accuracy of the alarm.

[0031] Figure 2 FIG. Figure 2 is a schematic flowchart of the alarm method provided by the embodiment of this application. As Figure 2 shown, the embodiment of this application provides an alarm method, and the method is described in detail as follows:

[0032] S201. Receive a detection request, where the detection request includes at least one device identifier to be detected.

[0033] Exemplarily, the device identifier to be detected is used to identify the device to be detected, and different devices to be detected can be accurately distinguished through the device identifier to be detected.

[0034] Optionally, the device identifier to be detected includes but is not limited to at least one of the following: the code of the device, the serial number of the device, or the identification code of the device, etc.

[0035] Exemplarily, the detection request is used to trigger alarm processing, and alarm processing starts according to the indication of the detection request.

[0036] Optionally, the detection request can be attached with a time limit, and the time limit is used to indicate the duration of the alarm processing. During the duration, real-time alarm processing is performed on the device to be detected, so as to continuously monitor whether the device to be detected is abnormal.

[0037] S202. According to the detection request, determine at least one device to be detected corresponding to at least one device identifier to be detected.

[0038] Exemplarily, there is a one-to-one correspondence between the device identifier to be detected and the device to be detected, and each device identifier to be detected corresponds to a device to be detected, so as to accurately determine the device to be detected.

[0039] Combined with a scenario example, the device to be detected is a device that is running or about to run. Warning the device to be detected is used to promptly handle the faults of the device to be detected, so that the device to be detected can continue to run.

[0040] Combined with a scenario example, the device to be detected includes but is not limited to at least one of the following: devices in switches, devices in servers, etc.

[0041] S203. Determine the working state of the device to be detected.

[0042] Exemplarily, normal operation indicates that the device to be detected works according to the preset state, and abnormal operation indicates that the device to be detected does not work according to the preset state. For example, the preset state can be a preset working parameter range. If the real-time working parameters of the device to be detected are not within the preset working parameter range, it indicates abnormal operation. The preset state can be a preset function. If the device to be detected fails to implement the preset function (for example: power supply stops, heat dissipation stops, calculation is not performed), it indicates abnormal operation.

[0043] Combined with a scenario example, both the faults of the device and the jitter of the device can cause the working state of the device to be abnormal. However, if the jitter of the device is within a controllable range, it has no impact on the operation of the device and does not require handling.

[0044] S204. If the working state is abnormal, perform debounce detection processing on the device to be detected to obtain a detection result, and perform warning processing according to the detection result.

[0045] Exemplarily, the debounce detection processing includes a debounce operation. Through the debounce operation, the abnormal operation caused by jitter can be filtered. The detection result obtained by the debounce detection processing is the detection result after filtering the jitter. If the detection result shows abnormality, it is the abnormality caused by a fault.

[0046] Exemplarily, if the abnormal operation is caused by jitter, it will recover by itself within a short period of time. If the abnormal operation is caused by a fault, it will last for a period of time. Through the debounce detection processing, the cause of the jitter can be accurately distinguished.

[0047] Exemplarily, if the working state is abnormal, further debounce detection is performed. According to the detection result, it is judged whether the abnormal operation is caused by a fault or jitter. Thus, warning for jitter can be avoided.

[0048] Combined with a scenario example, when the working state is abnormal, the debounce detection processing continues to be performed through the debounce detection processing to further judge the abnormal operation, so as to determine whether the abnormal operation is caused by a fault or jitter, thereby improving the accuracy of the warning processing.

[0049] The alarm method provided by the embodiment of the present application receives a detection request, where the detection request includes at least one device identifier to be detected; determines at least one device to be detected corresponding to the at least one device identifier to be detected according to the detection request; determines the working state of the device to be detected; if the working state is abnormal, performs a debounce detection process on the device to be detected to obtain a detection result, and performs an alarm process according to the detection result. In the above solution, when the device to be detected has an abnormal working state, a debounce detection process is first performed to determine whether the reason for the abnormal working state is a fault or a jitter, which can avoid alarming for jitters that do not affect the operation of the device to be detected, thereby improving the accuracy of the alarm.

[0050] Based on any one of the above embodiments, below, in combination with Figure 3 , the detailed process of the alarm will be described.

[0051] Figure 3 It is a schematic flowchart of an alarm method provided by an embodiment of the present application. As Figure 3 shown, the method includes:

[0052] S301. Receive a detection request, where the detection request includes at least one device identifier to be detected.

[0053] It should be noted that the execution process of S301 refers to S201, which will not be elaborated here.

[0054] S302. Determine at least one device to be detected corresponding to the at least one device identifier to be detected according to the detection request.

[0055] It should be noted that the execution process of S302 refers to S202, which will not be elaborated here.

[0056] S303. Obtain the working policy message of the device to be detected, where the working policy message includes the current working policy indicating the device to be detected to execute.

[0057] Exemplarily, the current working policy is used to indicate the working parameters that the device to be detected needs to execute currently.

[0058] Optionally, the working parameters include but are not limited to at least one of the following: voltage, current, rotational speed, or frequency, etc.

[0059] Optionally, encapsulate the current working policy into a message for transmission, and perform parsing processing on the message to obtain the current working policy.

[0060] Illustrated with a scenario example, taking the cooling fan installed in a switch as the device to be detected, the current rotation speed of the cooling fan is 500 rpm, and the current temperature of the switch is higher than the temperature threshold, indicating that the current rotation speed of the cooling fan is insufficient to dissipate heat from the switch. To achieve effective heat dissipation, the switch can send a working policy to the fan to increase the rotation speed of the fan, and the working policy corresponds to a working policy message. Conversely, if the current temperature of the switch is lower than the temperature threshold, for energy-saving considerations, the switch can send a working policy to the fan to reduce the rotation speed of the fan.

[0061] S304. Determine the historical working policy of the device to be detected.

[0062] Exemplarily, the historical working policy can be the working parameters executed by the device to be detected last time.

[0063] Optionally, maintain a policy record for each device. The policy record stores the working policy executed each time, and obtain the historical working policy through the policy record.

[0064] Optionally, obtain the historical working policy through a log file.

[0065] S305. If the current working policy is the same as the historical working policy, determine the working state of the device to be detected.

[0066] Exemplarily, if the current working policy is the same as the historical working policy, it indicates that the working policy of the device to be detected has not changed. At this time, the device to be detected will not jitter due to the change of the working policy, and then determine the working state of the device to be detected.

[0067] Exemplarily, if the current working policy is the same as the historical working policy, control the target indicator light to display the second light, and the second light indicates that the device to be detected is normal. If the current working policy is the same as the historical working policy, it indicates that the working policy of the device to be detected has changed. When the current working policy is executed, the device to be detected is working normally, and the working parameters of the device to be detected may be unstable. Forcing the target indicator light to display the second light can avoid false alarms, thereby realizing the debounce operation.

[0068] Exemplarily, update the historical working policy after executing the current working policy.

[0069] Next, in combination with Figure 4 describe the issuance of the working policy.

[0070] Figure 4 is a schematic diagram of the issuance of the working policy provided by the embodiment of the present application. As Figure 4As shown, determine whether the device to be detected has stopped working. If so, end the process. If the device to be detected is working, generate the current working strategy based on the real-time status (such as too low rotation speed of the cooling fan). Determine whether the current working strategy is different from the historical working strategy. If different, generate a change message; if the same, generate an unchanged message. The change message or the unchanged message is used to indicate whether to perform the debounce operation. Use the current working strategy as the historical working strategy to update the historical working strategy, and send down the current working strategy. The generation or end of the working strategy can be executed multiple times.

[0071] Taking the cooling fan as an example in combination with a scenario example, if the historical working strategy is a rotation speed of 500 rpm and the current working strategy is a rotation speed of 700 rpm, during the process of the cooling fan executing the current working strategy to adjust the rotation speed to 700 rpm, the rotation speed of the cooling fan is in an unstable state, and the duration of this process is relatively short, which belongs to jitter. At this time, forcing the control target indicator light to display the second light can effectively avoid false alarms.

[0072] A feasible implementation method can determine the working state of the device to be detected through the following methods, including: performing an in-place detection process on the device to be detected to obtain the in-place information of the device to be detected, and the in-place information is in-place normal or in-place abnormal; if the in-place information is in-place normal, determine the working state of the device to be detected.

[0073] Exemplarily, the in-place information indicates whether the device to be detected is correctly set in the corresponding position, and in-place normal means that the device to be detected is correctly set in the corresponding position. The in-place information being in-place normal is a prerequisite for the device to be detected to work normally, and the working state determined on this basis can be free from the interference of in-place abnormalities.

[0074] In this feasible implementation method, through the in-place detection process, the interference of in-place abnormalities on the working state can be avoided, thereby improving the accuracy of determining the working state, and further improving the accuracy of alarms.

[0075] A feasible implementation method, the alarm method further includes: if the in-place information is in-place abnormal, control the target indicator light not to display the light.

[0076] Exemplarily, in-place abnormal means that the device to be detected is not correctly installed, and the target indicator light not displaying the light is used to indicate in-place abnormality to prompt the operation and maintenance personnel to handle it in time. When in-place abnormal, the device to be detected cannot work normally, and the process of not performing the alarm processing can reduce operations.

[0077] Optionally, if in-place abnormal, send a prompt to the upper computer to promptly prompt the operation and maintenance personnel to handle it in time and eliminate the abnormality.

[0078] In this feasible implementation, by controlling the target indicator light not to display light, the operation and maintenance personnel can be prompted to handle the situation in a timely manner, thereby improving the reliability of the device to be detected.

[0079] S306. Determine the window stack corresponding to the device to be detected and the target window width. The window stack is used to temporarily store detection data, and the target window width is the upper limit of the number of detection data temporarily stored in the window stack.

[0080] Exemplarily, the debounce detection process of the present application includes multiple detections, and the detection result of the debounce detection is obtained based on the detection data of the multiple detections. The window stack is used to temporarily store detection data, and the detection result is obtained based on the detection data in the window stack. In the process of determining the detection result, the detection data in the window stack is used as the basis.

[0081] Combined with the scenario example, if the anomaly caused by the fault lasts for a long time or cannot recover by itself, and continuous detection data is stored in the window stack, if all the continuous detection data in the window stack is abnormal, it can be determined that the anomaly is caused by the fault.

[0082] Exemplarily, the target window width controls the number of detection data in the window stack, and the detection data in the window stack can be partially retrieved or cleared.

[0083] Exemplarily, the window stack is bound to the device to be detected, and the detection data of the device to be detected can only be temporarily stored in the window stack, and the window stack can only temporarily store the detection data of the bound device to be detected. It can be understood that through the binding process, the interference between the detection data of different devices is avoided, thereby improving the accuracy of the alarm.

[0084] A feasible implementation can determine the target window width through the following method, including: determining the historical alarm records and historical window width of the device to be detected; determining the window width mapping relationship table and the window width reference value; determining the window width offset value corresponding to the device to be detected according to the historical alarm records, historical window width, and window width mapping relationship table; determining the target window width according to the window width reference value and the window width offset value.

[0085] Exemplarily, the historical alarm records include multiple alarm records of the device to be detected, including the time corresponding to each alarm record. The historical window width is the width of the window stack used by the device to be detected historically.

[0086] Exemplarily, the window width offset value represents the offset degree of the target window width relative to the window width reference value.

[0087] Optionally, the window width mapping relationship table is used to map the matching window width offset value according to the historical alarm records and historical window width.

[0088] Combined with a scenario example, it can be determined from historical alarm records the frequency and / or severity of historical alarms. If historical alarms occur frequently or are relatively severe, strict alarm handling should be performed on the device to be detected, that is, a smaller target window width is set to avoid missing faults. The historical window width, which is the window width that has been used, can be used for reference. If the historical window width is 4, it indicates that a window width of 4 is suitable for the device to be detected, and the target window width can be determined around 4. The window width mapping relationship table is used to reflect the reference relationship between historical alarm records and historical window width for the target window width.

[0089] Exemplarily, the target window width is the sum of the window width reference value and the window width offset value.

[0090] Combined with a scenario example, if the window width reference value is 6 and the window width offset value is -1, then the determined target window width is , that is, 5.

[0091] In this feasible implementation manner, dynamically determining the target window width according to historical alarm records and historical window width can make the target window width more match the fault occurrence situation of the device to be detected, thereby improving the accuracy of alarms.

[0092] S307. Continuously detect and process the working state of the device to be detected, obtain multiple detection data, and add the multiple detection data to the window stack. The detection data is normal detection or abnormal detection.

[0093] Exemplarily, there is an order relationship among the multiple detection data. Add the multiple detection data to the window stack in sequence according to the order relationship, so that the detection data in the window stack can accurately reflect the abnormal change situation of the device to be detected.

[0094] Combined with a scenario example, if all the detection data in the window stack are abnormal, it indicates that the abnormality of the data to be detected appears continuously rather than as an instantaneous jitter, then it is considered that the device to be detected has a fault.

[0095] Optionally, determine the detection interval, and continuously detect and process the working state of the detection device at a fixed detection interval to obtain multiple detection data. It can be understood that using a fixed detection interval can accurately reflect the change situation of the multiple detection data, thereby improving the accuracy of alarms.

[0096] S308. Perform debounce detection processing based on the consistency of the multiple detection data in the window stack to obtain a detection result.

[0097] Exemplarily, the detection data includes normal or abnormal, and the consistency of multiple detection data indicates whether all the multiple detection data are normal or all abnormal. Through consistency judgment, the interference of instantaneous jitter on alarms can be eliminated, thereby improving the accuracy of alarms.

[0098] A feasible implementation method can perform debounce detection processing through the following method to obtain a detection result, including: if multiple detection data in the window stack are different, clear the window stack, and continuously detect the working state of the device to be detected again and add the detection data to the window stack until the multiple detection data in the window stack are the same; if multiple detection data in the window stack are the same, and all the multiple detection data in the window stack are in normal working condition, determine that the detection result is normal detection; if multiple detection data in the window stack are the same, and all the multiple detection data in the window stack are in abnormal working condition, determine that the detection result is abnormal detection.

[0099] Exemplarily, if multiple detection data in the window stack are different, that is, both normal and abnormal exist simultaneously among the multiple detection data, it indicates that the working state of the device to be detected is in a transitional state of jitter. At this time, debounce detection processing is performed, that is, no alarm is issued for the jitter until the jitter is eliminated, avoiding jitter interference with the alarm. Clear all the detection data in the window stack, and add new detection data in sequence until the detection data in the window stack are the same, indicating that the jitter has been eliminated. At this time, alarm processing can be performed.

[0100] Exemplarily, if multiple detection data in the window stack are the same, and all the multiple detection data in the window stack are in normal working condition. It indicates that the working state of the device to be detected has been stabilized and is stable in the normal working state. At this time, it can be determined that the detection result is normal detection.

[0101] Exemplarily, if multiple detection data in the window stack are the same, and all the multiple detection data in the window stack are in abnormal working condition. It indicates that the working state of the device to be detected is abnormal and no longer changes. At this time, it can be determined that the detection result is abnormal detection.

[0102] Next, in combination with Figure 5 the debounce detection will be described.

[0103] Figure 5 is a schematic diagram of the debounce detection provided by the embodiment of the present application. As Figure 5As shown, a window stack is set up for in-place detection. If the in-place condition is abnormal, multiple exception flags are added to the window stack to indicate that there is an abnormality currently. Then, the lighting strategy is executed without the need for debounce detection. If the in-place detection is normal, continuous detection processing is performed to obtain multiple detection data, and the detection data is added to the window stack. If the number of detection data in the window stack reaches the target window width, it is determined whether the data in the window stack is consistent. If it is inconsistent, the window stack is cleared and the detection data is added to the window stack again. If the data in the window stack is consistent, it is determined whether the latest detection data in the detection data is the same as the data in the window stack. If they are the same, the lighting strategy is executed; if they are different, the window stack is cleared and the detection data is added to the window stack again. If the window stack is not full, it is determined whether the data in the window stack is consistent. If it is inconsistent, the window stack is cleared and the detection data is added to the window stack again. If it is consistent, the lighting strategy is executed. In the lighting strategy, if the window stack is not full, it indicates that there is less detection data or the detection request only specifies a small number of detection times. To avoid false alarms, the second light indicating that the device is normal is displayed. If the window stack is full, it is determined whether the detection data in the window stack is normal or abnormal. If it is normal, the second light is displayed; if it is abnormal, the first light indicating that the device is abnormal is displayed.

[0104] In this feasible implementation, based on the consistency of multiple detection data, the stability of the detection data in the window stack can be determined. According to the stability, it can be judged whether the jitter is eliminated, thereby improving the accuracy of the detection result.

[0105] A feasible implementation, the warning method further includes: determining the first delay duration corresponding to the device to be detected; if multiple detection data in the window stack are the same and all the multiple detection data in the window stack are work abnormal, after the first delay duration, the working state of the device to be detected is detected and processed to obtain a detection result.

[0106] Exemplarily, the first delay duration is used for further verification processing of the fault to avoid misjudging jitter as a fault.

[0107] Combined with the scenario example, when the working state of the device to be detected is abnormal and does not change anymore, the detection result of the device to be detected is not temporarily determined as detection abnormal. After delaying for a period of time, that is, the first delay duration, the working state of the detection device is detected and processed once to obtain detection data. If the detection data at this time is still detection abnormal, it indicates that the abnormality cannot be automatically eliminated, and it can be determined that the device to be detected has a fault. If the detection data at this time becomes detection normal, it indicates that the abnormality of the device to be detected has been eliminated, and it can be determined that the abnormality of the device to be detected is caused by jitter.

[0108] In this feasible implementation, the anomaly is further verified and processed through the first delay duration, and jitter can be effectively identified based on the results of the further verification, thereby improving the accuracy of the alarm.

[0109] A feasible implementation can determine the first delay duration of the device to be detected through the following method, including: determining the historical jitter records and historical delay durations of the device to be detected; determining the delay duration mapping relationship table and the delay duration reference value; determining the delay duration offset value corresponding to the device to be detected according to the historical jitter records, historical delay durations, and the delay duration mapping relationship table; and determining the first delay duration according to the delay duration reference value and the delay duration offset value.

[0110] Exemplarily, the historical jitter records include multiple jitter records that have occurred in the history of the device to be detected, including the time corresponding to each jitter record.

[0111] Exemplarily, the delay duration offset value represents the offset degree of the first delay duration relative to the delay duration reference value.

[0112] Optionally, the delay duration mapping relationship table is used to map the matching delay duration offset value according to the historical jitter records and historical delay durations.

[0113] Combined with the scenario example, the frequency and / or regularity of historical jitter can be determined through historical jitter records. If historical jitter occurs frequently, it indicates that the device to be detected is prone to jitter, and then the detection results of the device to be detected should be strictly verified, that is, a longer first delay duration should be set to avoid misjudging jitter as a fault. If historical jitter occurs regularly, for example, jitter occurs frequently in a period or occurs less frequently in a period, and the periods alternate, then strict verification should be performed during the period when jitter occurs frequently, and loose verification should be performed during the period when jitter occurs less frequently. The historical delay duration is the delay duration that has been used and can be used for reference. The longer the historical delay duration, the more the device to be detected needs to be subjected to anti-jitter detection processing, and then the first delay duration can be increased. The window width mapping relationship table is used to reflect the reference relationship between historical jitter records and historical delay durations on the first delay duration.

[0114] Exemplarily, the first delay duration is the sum of the delay duration reference value and the delay duration offset value.

[0115] In this feasible implementation, dynamically determining the first delay duration according to historical jitter records and historical delay durations can make the first delay duration more matched with the jitter occurrence situation of the device to be detected, improve the recognition accuracy of jitter, and thus improve the accuracy of the alarm.

[0116] A feasible implementation method. Alarm processing can be performed through the following methods, including: if the detection result is normal detection and all detection data are in normal working condition, or if the working status is normal, alarm processing is performed according to the device type of the device to be detected; if the detection result is abnormal detection and all detection data are in abnormal working condition, the target indicator light corresponding to the device to be detected is determined, and the target indicator light is controlled to display the first light for alarm processing.

[0117] Optionally, during alarm processing, the device to be detected can be re-detected, and alarm processing is performed according to the detection result. If the result of the re-detection is normal detection and all detection data in the window stack are in normal working condition, it indicates that the device to be detected has jittered and the jitter has recovered. At this time, alarm processing is performed according to the device type to exclude abnormal device types.

[0118] Combined with a scenario example, an abnormal device type will not be reflected in the detection data, and the detection process cannot detect the abnormal device type. Separate alarm processing for the device type is required.

[0119] Exemplarily, if the detection result is abnormal detection and all detection data are in abnormal working condition, it indicates that the detection data in the window stack continuously shows abnormal working conditions, and the re-detection is still abnormal. Then it is considered that the abnormality is caused by a fault and cannot recover on its own. At this time, a clear alarm result is obtained, and the alarm result is reflected through the light.

[0120] Exemplarily, the first light indicates that the device to be detected has a fault.

[0121] Combined with a scenario example, corresponding indicator lights can be set for each device to be detected, or multiple devices to be detected share indicator lights. In the scenario where multiple devices to be detected share indicator lights, if at least one device to be detected is abnormal, the shared indicator light displays the first light. Taking the example of setting corresponding indicator lights for each device to be detected, the working status of the cooling fan is displayed through the indicator light corresponding to the cooling fan, the working status of the power supply is displayed through the indicator light corresponding to the power supply, whether the CPU is overheated or the temperature is lost is displayed through the indicator light corresponding to the CPU, whether the switching chip is overheated or the temperature is lost is displayed through the indicator light corresponding to the switching chip, whether the basic input / output system (Basic Input / Output System, abbreviated as BIOS) starts abnormally is displayed through the indicator light corresponding to the basic input / output system, and whether the controller starts abnormally is displayed through the indicator light corresponding to the controller.

[0122] In this feasible implementation method, by integrating the detection data in the window stack and the result of the re-detection, the error of fault judgment can be reduced, thereby improving the accuracy of alarm processing.

[0123] A feasible implementation method can perform alarm processing according to the device type of the device to be detected through the following steps: determining the current device type and the preset device type corresponding to the device to be detected; performing device type detection processing on the device to be detected according to the current device type and the preset device type to obtain a device type detection result, where the device type detection result is that the device type is normal or the device type is abnormal; if the device type detection result is that the device type is abnormal, controlling the target indicator light to display a first light for alarm processing; if the device type detection result is that the device type is normal, controlling the target indicator light to display a second light to indicate that the device to be detected is a normal device, and the second light is different from the first light.

[0124] Exemplarily, device type detection is used to detect whether the device to be detected is used according to the preset requirements. Device type detection can detect abnormalities that are not detected by the debounce detection process, and detect the device to be detected from another dimension through device type detection.

[0125] Exemplarily, different lights are displayed through the lighting strategy, and different device states are indicated to the operation and maintenance personnel through different lights.

[0126] Optionally, in-place detection can be repeated after the debounce detection process to exclude the situation where the in-place information changes from normal to abnormal, thereby improving the accuracy of the alarm.

[0127] Next, the lighting strategy will be described in conjunction with Figure 6 the following.

[0128] Figure 6 FIG. Figure 6 shows a schematic diagram of the lighting strategy provided by the embodiment of the present application. As shown, in-place detection is performed on the device to be detected. If the in-place is abnormal, no light is displayed. If the in-place is normal, the working state is further judged. If the working state is normal, device type detection is performed. If the working state is abnormal, debounce detection processing is performed. After performing the debounce detection processing, in-place detection is repeated. If the in-place detection is normal, alarm processing is performed according to the detection result of the debounce detection processing. If the detection result is abnormal, the first light is displayed. If the detection result is normal, type detection is performed. If the device type detection result is normal, the second light is displayed. If the device type detection result is abnormal, the first light is displayed.

[0129] In this feasible implementation method, alarm processing is combined with device type detection and debounce detection, which can comprehensively detect the device to be detected, thereby improving the accuracy of the alarm.

[0130] A feasible implementation method, where the current device type includes at least one of the following: device power supply type, device identifier, or device direction.

[0131] In the related art, after confirming that the device is in place, the device type is not detected. It may occur that the working parameters of the device are stable, but the abnormal device type causes the device to malfunction. If not detected, there will be a problem of missed alarms, which will affect the use of the device or other devices.

[0132] Combined with the scenario example, the device power supply type can be for the power supply, specifically including direct current, alternating current, the magnitude of the supply voltage, or the magnitude of the supply current, etc. The device identifier can be the model number, serial number, identification code, etc. of the device. The device direction can be for the cooling fan, specifically including the rotation direction of the fan blades (forward rotation or reverse rotation, etc.).

[0133] In this feasible implementation, by setting multiple current devices for detection, it is possible to judge whether the device to be detected is working properly from multiple dimensions, thereby reducing the problem of missed alarms and improving the accuracy of alarms.

[0134] A feasible implementation is to perform debounce detection processing on the device to be detected to obtain a detection result, and it further includes: determining a second delay duration corresponding to the device to be detected; after the second delay duration, performing debounce detection processing on the device to be detected to obtain a detection result.

[0135] Exemplarily, the second delay duration is used before performing debounce detection processing, and is used to filter the jitter situation of the device to be detected, providing a buffer period for the jitter situation. If the detection result obtained after the detection processing after the second delay duration is still abnormal, the possibility of jitter can be excluded.

[0136] In this feasible implementation, by setting the second delay duration, it is possible to further avoid misjudging jitter as a fault, thereby improving the accuracy of alarms.

[0137] A feasible implementation is that the device to be detected is a controller, and the alarm method further includes: performing debounce detection processing on the controller to determine whether the controller fails to start from both the primary and backup flash memories; if so, controlling the target indicator light to display a first light for alarm processing; if not, performing detection processing on the startup method of the controller to obtain a startup detection result, and performing alarm processing according to the startup detection result.

[0138] In the related art, for the controller, if the startup fails, it is directly alarmed as a fault. However, the startup process of the controller includes various situations, and there is a problem of low accuracy in direct alarming.

[0139] Optionally, the controller can be a baseboard management controller or a basic input / output system, etc., which is not limited in this application.

[0140] As shown in the scenario example, after the controller fails to start from the main flash memory, it will automatically attempt to start from the backup flash memory. If it still fails to start from the backup flash memory, the startup will stop and be determined as a failure, and an alarm will be processed through the first lamp tube. During the process of switching from starting from the main flash memory to starting from the backup flash memory, there are various situations. By detecting and processing to determine the specific situation and performing alarm processing, the corresponding situation can be accurately reflected, enabling the operation and maintenance personnel to quickly locate the problems of the device to be detected.

[0141] In this feasible implementation manner, specific detection and processing are performed on the startup method of the controller, which can make the alarm processing accurately reflect the corresponding startup situation, thereby improving the accuracy of the alarm.

[0142] A feasible implementation manner, the startup detection results include successful startup from the main flash memory, startup from the backup flash memory in progress, and successful startup from the backup flash memory; alarm processing is performed according to the startup detection results, including: if the startup detection result is successful startup from the main flash memory, then control the target indicator light to display the second light; if the startup detection result is startup from the backup flash memory in progress, then control the target indicator light to flash and display the third light, and the third light is different from the second light; if the startup detection result is successful startup from the backup flash memory, then control the target indicator light to display the third light.

[0143] Next, Figure 7 the controller alarm will be described.

[0144] Figure 7 The figure is a schematic diagram of the controller alarm provided by the embodiment of the present application. As Figure 7 shown, the device to be detected is subjected to debounce detection processing to eliminate jitter. If the detection result is that the startup fails from both the main flash memory and the backup flash memory, then the first light indicating device abnormality is displayed. If the startup fails from the main flash memory and the device to be detected is starting from the backup flash memory, then the third light is flashed to prompt the operation and maintenance personnel that the current is in the startup process. If the startup fails from the main flash memory and the startup from the backup flash memory is successful, and the device to be detected completes startup and can run normally, the third light is displayed to prompt the operation and maintenance personnel that there is a fault in the main flash memory to avoid alarm omission. If the startup from the main flash memory is successful, then the second light is displayed indicating that the device to be detected is normal.

[0145] In this feasible implementation manner, different startup states of the device to be detected are respectively displayed with corresponding lights for alarm processing, which can accurately reflect the startup state of the device to be detected, thereby improving the accuracy of the alarm.

[0146] A feasible implementation method, where the number of devices to be detected is multiple, and the warning method further includes: performing debounce detection processing on multiple devices to be detected respectively to obtain multiple detection results; if all the multiple detection results indicate that the devices are normal, controlling the whole-machine indicator light to display a second light; if at least one of the multiple detection results indicates that the device is abnormal, controlling the whole-machine indicator light to display a first light.

[0147] Exemplarily, if there are multiple devices to be detected and they share a single whole-machine indicator light, the whole-machine indicator light reflects the fault conditions of the multiple devices to be detected.

[0148] Illustrated with a scenario example, taking a heat dissipation fan group as an example, the heat dissipation fan group corresponds to a whole-machine indicator light. The heat dissipation fan group includes multiple heat dissipation fans. The devices to be detected are the multiple heat dissipation fans. If all the multiple heat dissipation fans are normal, the second light is displayed. If all the multiple heat dissipation fans are abnormal, the first light is displayed. If some of the multiple heat dissipation fans are abnormal, the second light is displayed.

[0149] Illustrated with a scenario example, taking the whole machine as an example, the whole machine includes multiple devices to be detected. The working status of the whole machine is displayed through the whole machine indicator light. First, it is detected whether the CPU is overheated or the CPU temperature is lost. If it is overheated or lost, a debounce detection process is performed to determine whether the CPU is overheated or the CPU temperature is lost. If it is overheated or lost, the whole machine indicator light is set to display the first light; otherwise, it is further detected whether the switch chip is overheated or the switch chip temperature is lost. If it is overheated or lost, a debounce detection process is performed to determine whether the switch chip is overheated or the switch chip temperature is lost. If it is overheated or lost, the whole machine indicator light is set to display the first light; otherwise, it is further detected whether the multiple cooling fans are all in an abnormal state. If they are all in an abnormal state, a debounce detection process is performed to determine whether the multiple cooling fans are all in an abnormal state. If they are all in an abnormal state, the whole machine indicator light is set to display the first light; otherwise, it is further detected whether the multiple installed power supplies are all in an abnormal state. If they are all in an abnormal state, a debounce detection process is performed to determine whether the multiple installed power supplies are all in an abnormal state. If they are all in an abnormal state, the whole machine indicator light is set to display the first light; otherwise, it is further detected whether the basic input / output system fails to start from both the primary and secondary flash memories. If so, the whole machine indicator light is set to display the first light. Otherwise, it is further detected that the basic input / output system fails to start from the primary flash memory and is starting from the secondary flash memory, then the whole machine indicator light is set to display the first light; otherwise, it is further detected that the basic input / output system fails to start from the primary flash memory but succeeds in starting from the secondary flash memory, then the whole machine indicator light is set to display the third light; otherwise, it is further detected whether the controller fails to start from both the primary and secondary flash memories. If so, the whole machine indicator light is set to display the first light. Otherwise, it is further detected that the controller fails to start from the primary flash memory and is starting from the secondary flash memory, then the whole machine indicator light blinks and displays the third light; otherwise, it is further detected that the controller fails to start from the primary flash memory but succeeds in starting from the secondary flash memory, then the whole machine indicator light is set to display the third light; otherwise, the whole machine indicator light is set to display the second light.

[0150] In this feasible implementation manner, for some of the multiple devices to be detected with abnormal display of corresponding lights for alarm processing, the abnormality of some of the devices to be detected can be accurately reflected through an indicator light, thereby improving the accuracy of the alarm.

[0151] 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. Of course, it can also be implemented by hardware, but in many cases the former is a better implementation manner.

[0152] Figure 8 It is a schematic structural diagram of the alarm device provided by the embodiment of the present application. As Figure 8As shown in the figure, an embodiment of the present application further provides an alarm device, and the alarm device 80 may include: a receiving module 81, a determining module 82, an obtaining module 83, and a detecting module 84, where,

[0153] The receiving module 81 is configured to receive a detection request, and the detection request includes at least one device identifier to be detected.

[0154] The determining module 82 is configured to determine at least one device to be detected corresponding to at least one device identifier to be detected according to the detection request.

[0155] The obtaining module 83 is configured to determine the working state of the device to be detected.

[0156] The detecting module 84 is configured to, if the working state is abnormal, perform a debounce detection process on the device to be detected to obtain a detection result, and perform an alarm process according to the detection result.

[0157] Optionally, the receiving module 81 may execute Figure 2 S201 in the embodiment.

[0158] Optionally, the determining module 82 may execute Figure 2 S202 in the embodiment.

[0159] Optionally, the obtaining module 83 may execute Figure 2 S203 in the embodiment.

[0160] Optionally, the detecting module 84 may execute Figure 2 S204 in the embodiment.

[0161] It should be noted that the alarm device shown in the embodiment of the present application may execute the technical solution shown in the above method embodiment, and its implementation principle and beneficial effects are similar, and will not be elaborated here.

[0162] In a possible implementation manner, the detecting module 84 is specifically configured to:

[0163] Determine the window stack corresponding to the device to be detected and the target window width, where the window stack is used to temporarily store detection data, and the target window width is the upper limit of the number of detection data temporarily stored in the window stack;

[0164] Perform a debounce detection process on the device to be detected according to the target window width to obtain a detection result.

[0165] In a possible implementation manner, the detecting module 84 is specifically configured to:

[0166] Determine the historical alarm record and the historical window width of the device to be detected;

[0167] Determine the window width mapping relationship table and the window width reference value;

[0168] Determine the window width offset value corresponding to the device to be detected according to the historical alarm record, the historical window width, and the window width mapping relationship table;

[0169] Determine the target window width according to the window width reference value and the window width offset value.

[0170] In a possible implementation manner, the detection module 84 is specifically configured to:

[0171] Continuously detect the working state of the device to be detected to obtain a plurality of detection data, and add the plurality of detection data to the window stack, where the detection data is normal detection or abnormal detection;

[0172] Perform debounce detection processing according to the consistency of the plurality of detection data in the window stack to obtain a detection result.

[0173] In a possible implementation manner, the detection module 84 is specifically configured to:

[0174] If the plurality of detection data in the window stack are different, clear the window stack, and continuously detect the working state of the device to be detected again and add the detection data to the window stack until the plurality of detection data in the window stack are the same;

[0175] If the plurality of detection data in the window stack are the same and all the plurality of detection data in the window stack are normal in work, determine that the detection result is normal detection;

[0176] If the plurality of detection data in the window stack are the same and all the plurality of detection data in the window stack are abnormal in work, determine that the detection result is abnormal detection.

[0177] Figure 9 This is a schematic structural diagram of an alarm device provided by an embodiment of the present application. On the basis of Figure 8 the shown embodiment, as Figure 9 shown, the alarm device 90 further includes: an execution module 85, a delay module 86, a judgment module 87, an in-position detection module 88, a start detection module 89, and an overall machine detection module 810, where

[0178] The execution module 85 is configured to:

[0179] Determine the first delay duration corresponding to the device to be detected;

[0180] If the plurality of detection data in the window stack are the same and all the plurality of detection data in the window stack are abnormal in work, after the first delay duration, detect the working state of the device to be detected to obtain a detection result.

[0181] In a possible implementation, the execution module 85 is specifically configured to:

[0182] Determine the historical jitter record and historical delay duration of the device to be detected;

[0183] Determine the delay duration mapping relation table and the delay duration reference value;

[0184] According to the historical jitter record, historical delay duration, and the delay duration mapping relation table, determine the delay duration offset value corresponding to the device to be detected;

[0185] According to the delay duration reference value and the delay duration offset value, determine the first delay duration.

[0186] In a possible implementation, the execution module 85 is specifically configured to:

[0187] If the detection result is normal detection and all detection data are normal in operation, or if the working state is normal in operation, perform alarm processing according to the device type of the device to be detected;

[0188] If the detection result is abnormal detection and all detection data are abnormal in operation, determine the target indicator light corresponding to the device to be detected, and control the target indicator light to display the first light for alarm processing.

[0189] In a possible implementation, the execution module 85 is specifically configured to:

[0190] Determine the current device type and the preset device type corresponding to the device to be detected;

[0191] The execution module is further specifically configured to perform device type detection processing on the device to be detected according to the current device type and the preset device type, and obtain a device type detection result, where the device type detection result is normal device type or abnormal device type;

[0192] The execution module is further specifically configured to, if the device type detection result is abnormal device type, control the target indicator light to display the first light for alarm processing;

[0193] The execution module is further specifically configured to, if the device type detection result is normal device type, control the target indicator light to display the second light to indicate that the device to be detected is a normal device, and the second light is different from the first light.

[0194] In a possible implementation, the current device type includes at least one of the following: device power supply type, device identifier, or device direction.

[0195] The delay module 86 is used to:

[0196] Determine the second delay duration corresponding to the device to be detected;

[0197] After the second delay duration, anti-shake detection processing is performed on the device to be detected to obtain a detection result.

[0198] A judgment module 87, configured to:

[0199] Obtain a working policy message of the device to be detected, where the working policy message includes a current working policy indicating the device to be detected to execute;

[0200] Determine the historical working policy of the device to be detected;

[0201] If the current working policy is the same as the historical working policy, determine the working state of the device to be detected.

[0202] In a possible implementation manner, the judgment module 87 is specifically configured to:

[0203] Perform in-position detection processing on the device to be detected to obtain in-position information of the device to be detected, where the in-position information is normal in position or abnormal in position;

[0204] If the in-position information is normal in position, determine the working state of the device to be detected.

[0205] An in-position detection module 88, configured to:

[0206] If the in-position information is abnormal in position, control the target indicator light not to display light.

[0207] The device to be detected is a controller, and a start detection module 89 is started, configured to:

[0208] Perform anti-shake detection processing on the controller to determine whether the controller fails to start from both the main and backup flash memories;

[0209] If so, control the target indicator light to display a first light for alarm processing;

[0210] If not, perform detection processing on the start mode of the controller to obtain a start detection result, and perform alarm processing according to the start detection result.

[0211] In a possible implementation manner, the start detection result includes successful start from the main flash memory, starting from the backup flash memory, and successful start from the backup flash memory; the start detection module 89 is specifically configured to:

[0212] If the start detection result is successful start from the main flash memory, control the target indicator light to display a second light;

[0213] If the start detection result is starting from the backup flash memory, control the target indicator light to flash and display a third light, where the third light is different from the second light;

[0214] If the start detection result is successful start from the backup flash memory, control the target indicator light to display the third light.

[0215] The number of devices to be detected is multiple. The whole-machine detection module 810 is used for:

[0216] Performing debounce detection processing on multiple devices to be detected respectively to obtain the detection result corresponding to each device to be detected;

[0217] If the detection result corresponding to each device to be detected is that the device is normal, then control the whole-machine indicator light to display the second light;

[0218] If the detection result corresponding to each device to be detected is that the device is abnormal, then control the whole-machine indicator light to display the first light;

[0219] If some of the detection results corresponding to each device to be detected are that the device is abnormal, then control the whole-machine indicator light to display the third light.

[0220] For the description of the features in the embodiments corresponding to the warning device, reference can be made to the relevant description of the embodiments corresponding to the warning method, which will not be elaborated here one by one.

[0221] Figure 10 This is a schematic structural diagram of the electronic device provided by the present application. As Figure 10 shown, the electronic device 100 provided in this embodiment includes: at least one processor 1001 and a memory 1002. Optionally, the electronic device 100 further includes a communication component 1003. Among them, the processor 1001, the memory 1002, and the communication component 1003 are connected through a bus.

[0222] In the specific implementation process, at least one processor 1001 executes the computer execution instructions stored in the memory 1002, so that at least one processor 1001 executes the above-mentioned warning method embodiment.

[0223] For the specific implementation process of the processor 1001, reference can be made to the above method embodiment. The implementation principle and technical effect are similar, and will not be elaborated here in this embodiment.

[0224] In the above embodiment, it should be understood that the processor may be a central processing unit (Central Processing Unit, abbreviated as: CPU), or other general-purpose processors, digital signal processors (Digital Signal Processor, abbreviated as: DSP), application-specific integrated circuits (Application Specific Integrated Circuit, abbreviated as: ASIC), etc. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc. The steps of the method disclosed in combination with the application can be directly embodied as being executed by a hardware processor, or executed by a combination of hardware and software modules in the processor.

[0225] The memory may include a random access memory (RAM), and may also include a non-volatile memory (NVM), such as at least one disk memory.

[0226] The bus may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, the buses in the drawings of this application are not limited to only one bus or one type of bus.

[0227] Embodiments of the present application also provide a computer-readable storage medium, in which a computer program is stored, and the computer program is configured to execute the steps in any one of the above-described warning method embodiments when running.

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

[0229] Embodiments of the present application also provide a computer program product, the above computer program product includes a computer program, and when the computer program is executed by a processor, the steps in any one of the above-described warning method embodiments are implemented.

[0230] Embodiments of the present application also provide another computer program product, including a non-volatile computer-readable storage medium, the non-volatile computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps in any one of the above-described warning method embodiments are implemented.

[0231] 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 composition 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.

[0232] The above has introduced in detail an alarm method, device, electronic device, medium, and product 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, 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 the claims of this application.

Claims

1. An alarm method, characterized in that: include: Receiving a detection request, wherein the detection request includes at least one identification of a device to be detected; Determine, according to the detection request, at least one device to be detected corresponding to the at least one device to be detected identifier; Determining the working status of the device to be detected; If the working state is abnormal, de-jitter detection processing is performed on the device to be detected to obtain a detection result, and alarm processing is performed according to the detection result.

2. The alarm method according to claim 1, characterized in that: Performing de-jitter detection processing on the device to be detected to obtain a detection result includes: Determine a window stack and a target window width corresponding to the device to be detected, wherein the window stack is used to temporarily store detection data, and the target window width is an upper limit of the amount of detection data temporarily stored in the window stack; According to the target window width, de-jitter detection processing is performed on the device to be detected to obtain the detection result.

3. The alarm method according to claim 2, characterized in that: Determining the target window width corresponding to the device to be detected includes: Determine the historical alarm records and historical window width of the device to be detected; Determine a window width mapping relationship table and a window width reference value; Determine the window width offset value corresponding to the device to be detected according to the historical alarm record, the historical window width, and the window width mapping relationship table; The target window width is determined according to the window width reference value and the window width offset value.

4. The alarm method according to claim 3, characterized in that: According to the target window width, performing de-jitter detection processing on the device to be detected to obtain the detection result includes: Continuously detecting the working state of the device to be detected to obtain a plurality of detection data, and adding the plurality of detection data to the window stack, wherein the detection data is a normal detection or an abnormal detection; De-jitter detection processing is performed according to the consistency of multiple detection data in the window stack to obtain the detection result.

5. The alarm method according to claim 4, characterized in that: Performing de-jitter detection processing according to the consistency of the multiple detection data in the window stack to obtain the detection result includes: If the multiple detection data in the window stack are not the same, the window stack is cleared, and the working state of the device to be detected is continuously detected again and the detection data is added to the window stack until the multiple detection data in the window stack are the same; If the plurality of detection data in the window stack are the same, and the plurality of detection data in the window stack are all working normally, then determining that the detection result is normal; If the plurality of detection data in the window stack are the same, and the plurality of detection data in the window stack are all abnormal in operation, then it is determined that the detection result is abnormal in detection.

6. The alarm method according to claim 5, characterized in that: The method further comprises: Determine a first delay duration corresponding to the device to be detected; If the multiple detection data in the window stack are the same, and the multiple detection data in the window stack are all working abnormalities, then after the first delay time, the working state of the device to be detected is detected and processed to obtain a detection result.

7. The alarm method according to claim 6, characterized in that: Determining a first delay duration corresponding to the device to be detected includes: Determine the historical jitter record and historical delay duration of the device to be detected; Determine a delay duration mapping relationship table and a delay duration reference value; Determine the delay duration offset value corresponding to the device to be detected according to the historical jitter record, the historical delay duration, and the delay duration mapping relationship table; The first delay duration is determined according to the delay duration reference value and the delay duration offset value.

8. The alarm method according to claim 6, characterized in that: Performing alarm processing according to the detection result includes: If the detection result is that the detection is normal and the detection data are all working normally, or if the working status is working normally, an alarm process is performed according to the device type of the device to be detected; If the detection result is a detection abnormality and the detection data are all working abnormalities, the target indicator light corresponding to the device to be detected is determined, and the target indicator light is controlled to display a first light for alarm processing.

9. The alarm method according to claim 8, characterized in that: Perform alarm processing according to the device type of the device to be detected, including: Determine the current device type and the preset device type corresponding to the device to be detected; Performing device type detection processing on the device to be detected according to the current device type and the preset device type to obtain a device type detection result, wherein the device type detection result is that the device type is normal or the device type is abnormal; If the device type detection result is that the device type is abnormal, controlling the target indicator light to display a first light for alarm processing; If the device type detection result is that the device type is normal, the target indicator light is controlled to display a second light to indicate that the device to be detected is a normal device, and the second light is different from the first light.

10. The alarm method according to claim 9, characterized in that: The current device type includes at least one of the following: device power supply type, device identification, or device direction.

11. The alarm method according to claim 1, characterized in that: Performing de-jitter detection processing on the device to be detected to obtain a detection result, further comprising: Determine a second delay time corresponding to the device to be detected; After the second delay time has elapsed, a de-jitter detection process is performed on the device to be detected to obtain the detection result.

12. The alarm method according to claim 1, characterized in that: Determining the working status of the device to be detected includes: Acquire a working strategy message of the device to be detected, wherein the working strategy message includes a current working strategy instructing the device to be detected to execute; Determining the historical working strategy of the device to be detected; If the current working strategy is the same as the historical working strategy, the working state of the device to be detected is determined.

13. The alarm method according to claim 12, characterized in that: Determining the working state of the device to be detected includes: Performing in-situ detection processing on the device to be detected to obtain in-situ information of the device to be detected, wherein the in-situ information is normal or abnormal; If the in-place information indicates that the device is in-place and normal, the working status of the device to be detected is determined.

14. The alarm method according to claim 13, characterized in that: The method further comprises: If the in-position information is in-position abnormality, the target indicator light is controlled not to display light.

15. The alarm method according to claim 1, characterized in that: The device to be detected is a controller, and the method further includes: Performing a debounce detection process on the controller to determine whether the controller fails to start from both the primary and standby flash memories; If yes, the target indicator light is controlled to display a first light for warning processing; If not, a detection process is performed on the startup mode of the controller to obtain a startup detection result, and an alarm process is performed according to the startup detection result.

16. The alarm method according to claim 15, characterized in that: The startup detection result includes successful startup from the main flash memory, startup from the backup flash memory, and successful startup from the backup flash memory; Performing alarm processing according to the startup detection result includes: If the startup detection result is that the startup from the main flash memory is successful, controlling the target indicator light to display a second light; If the startup detection result is that the system is starting from the backup flash memory, the target indicator light is controlled to flash and display a third light, which is different from the second light; If the startup detection result is that the startup from the backup flash memory is successful, the target indicator light is controlled to display the third light.

17. The alarm method according to claim 1, characterized in that: The number of the devices to be detected is multiple, and the method further includes: Perform de-jitter detection processing on multiple devices to be detected respectively to obtain a detection result corresponding to each device to be detected; If the detection results corresponding to each of the devices to be detected are all normal, the indicator light of the whole device is controlled to display a second light; If the detection results corresponding to each of the devices to be detected are all abnormal, the indicator light of the whole device is controlled to display a first light; If some of the detection results corresponding to each of the devices to be detected show that the device is abnormal, the whole device indicator light is controlled to display a third light.

18. An electronic device, characterized in that: include: Memory for storing computer programs; A processor, configured to implement the steps of the alarm method as claimed in any one of claims 1 to 17 when executing the computer program.

19. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, wherein the computer program, when executed by a processor, implements the steps of the alarm method according to any one of claims 1 to 17.

20. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the alarm method according to any one of claims 1 to 17 are implemented.

Images