An alarm convergence method, system, and computer-readable storage medium

Abstract

The application relates to an alarm convergence method, comprising the following steps: S1, receiving power failure alarm data of a monitored device; S2, searching for a root cause device of the power failure alarm data according to device connection data and device real-time state data; S3, judging whether convergence alarm event data of the root cause device has been generated, if yes, deleting the power failure alarm data and returning to step S1, otherwise, adding the convergence alarm event data of the root cause device and returning to step S1. The application also relates to an alarm convergence system and a computer readable storage medium. The application is simple in configuration, can rapidly locate and display power failure, and thus improves the practicability and reliability of a data center.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of commercial power, more particularly, to an alarm convergence method, system and computer readable storage medium. BACKGROUND

[0002] Data center is an important part of today's information age, widely used to deliver, accelerate, display, compute, store data information on the network infrastructure of Ethernet. In the future development, data center will also become the asset of enterprise competition, and the business model will also change accordingly. With the wide application of data center, artificial intelligence, network security, etc. also appeared in succession, more users are brought to the application of network and mobile phone. With the increase of computers and data volume, people can also improve their ability through continuous learning and accumulation. Therefore, the power monitoring system of data center is becoming more and more important, especially the power supply system monitoring of IT equipment. If not careful, it will cause a large number of business downtime and cause business interruption accidents. Therefore, major data center operators have proposed power failure alarm solutions to alarm when power supply failure (power failure or open phase) occurs in the commercial power system, so as to quickly locate the fault source. Therefore, due to the large number of devices included in the monitoring, when the fault occurs, nearly ten thousand alarms may be generated, and the on-duty personnel can hardly find the most fundamental reason from these alarms, and cannot accurately locate the fault device. If the power outage time is long, the data center business will face the risk of interruption. SUMMARY

[0003] The technical problem to be solved by the present application is to provide an alarm convergence method, system and computer readable storage medium with simple configuration, which can quickly locate and display power failure, thereby improving the practicability and reliability of data center, in view of the above defects of the prior art.

[0004] The technical scheme adopted by the present application to solve the technical problem is: an alarm convergence method is constructed, comprising:

[0005] S1, receiving commercial power failure alarm data of a monitored device;

[0006] S2, finding the root cause device of the commercial power failure alarm data according to device connection data and device real-time state data;

[0007] S3, determining whether the convergence alarm event data of the root cause device has been generated, if yes, deleting the commercial power failure alarm data and returning to step S1, otherwise, adding the convergence alarm event data of the root cause device and returning to step S1.

[0008] In the alarm convergence method of the present application, the step S1 further comprises:

[0009] S11, receiving alarm data from the monitored device, and filtering the alarm data based on alarm type and device type to obtain the power failure alarm data;

[0010] S12, putting the power failure alarm data into a power alarm cache and removing according to alarm state.

[0011] In the alarm convergence method, the alarm type includes power failure, and the device type includes high-voltage power distributor, low-voltage power distributor and transformer.

[0012] In the alarm convergence method, the step S2 further includes:

[0013] S21, extracting the power failure alarm data with duration exceeding a first set time from the power alarm cache;

[0014] S22, finding a connection path of the power failure alarm data according to the device connection data to obtain all devices from power supply to the monitored device;

[0015] S23, obtaining device real-time state data of the all devices, and finding the root cause device based on the device real-time state data.

[0016] In the alarm convergence method, the device connection data includes connection relationship ID, child device ID, parent device ID and connection path.

[0017] In the alarm convergence method, the step S3 further includes:

[0018] S31, finding convergence alarm event data of the root cause device according to device ID of the root cause device, if the convergence alarm event data of the root cause device is found, executing step S32, otherwise executing step S33;

[0019] S32, judging whether a convergence state in the convergence alarm event data is end, if yes, executing step S33, otherwise deleting the power failure alarm data and returning to step S1;

[0020] S33, adding the convergence alarm event data of the root cause device and returning to step S1.

[0021] In the alarm convergence method, the convergence alarm event data includes convergence event ID, convergence event name, convergence type, convergence rule, convergence trigger event, convergence alarm number, convergence state, convergence root cause, confirmation time and root cause device ID.

[0022] In the alarm convergence method, further including:

[0023] S4, reading the convergence alarm event data in time and updating the convergence alarm event data according to the device connection data, the alarm convergence configuration data and the device real-time state data

[0024] In the alarm convergence method, the step S4 further comprises:

[0025] S41, reading the convergence alarm event data whose convergence state is not ended, and updating the parent device ID of the monitored device which generates the power failure alarm data within the set time according to the device connection data and the alarm convergence configuration data, and returning the convergence alarm number;

[0026] S42, updating the convergence state and the convergence alarm number of the convergence alarm event data according to the device real-time state data.

[0027] In the alarm convergence method, in the step S42, when the device real-time state data comprises the device real-time state data of the power recovery device, the convergence alarm number is updated and the convergence state is updated to be ended, otherwise the convergence alarm number is updated.

[0028] In the alarm convergence method, the alarm rule data comprises a rule ID, a rule name, a convergence type, a device type, a start expression, a convergence alarm type, a convergence interval, a convergence start trigger number, a convergence end trigger number and a convergence root cause.

[0029] Another technical solution adopted by the present application to solve its technical problems is to construct a computer readable storage medium having a computer program stored thereon, the computer program being executed by a processor to implement the alarm convergence method.

[0030] Another technical solution adopted by the present application to solve its technical problems is to construct an alarm convergence system, comprising:

[0031] The receiving module is configured to receive power failure alarm data of a monitored device;

[0032] The root cause finding module is configured to find a root cause device of the power failure alarm data according to device connection data and device real-time state data;

[0033] The convergence module is configured to determine whether convergence alarm event data of the root cause device is generated, and if so, delete the power failure alarm data, otherwise, increase the convergence alarm event data of the root cause device.

[0034] The alarm convergence system further comprises a convergence updating module, which is configured to read the convergence alarm event data at a regular time interval and update the convergence alarm event data according to the device connection data, the alarm convergence configuration data and the real-time state data of the device.

[0035] The alarm convergence method, system and computer readable storage medium of the present application have simple configuration, can quickly locate and display power failure, and thus improve the practicability and reliability of the data center. BRIEF DESCRIPTION OF DRAWINGS

[0036] The present application will be further described below in conjunction with the accompanying drawings and embodiments, in which:

[0037] Figure 1 is a flow chart of the alarm convergence method of the preferred embodiment of the present application;

[0038] Figure 2 is a flow chart of the alarm filtering step of the preferred embodiment of the alarm convergence method of the present application;

[0039] Figure 3 shows the format of the preferred embodiment of the device connection data, the convergence alarm event data and the alarm rule data of the present application;

[0040] Figure 4 is a flow chart of the root cause device searching step of the preferred embodiment of the alarm convergence method of the present application;

[0041] Figure 5 is a flow chart of the convergence alarm event data generating step of the preferred embodiment of the alarm convergence method of the present application;

[0042] Figure 6 is a flow chart of the convergence alarm event data updating step of the preferred embodiment of the alarm convergence method of the present application;

[0043] Figure 7 shows the specific embodiment of the preferred embodiment of the device connection data, the convergence alarm event data and the alarm rule data of the present application;

[0044] Figure 8 is a schematic diagram of the power failure alarm data using the alarm convergence method of the present application;

[0045] Figure 9 is another schematic diagram of the power failure alarm data using the alarm convergence method of the present application;

[0046] Figure 10 is still another schematic diagram of the power failure alarm data using the alarm convergence method of the present application;

[0047] Figure 11is a principle block diagram of an alarm convergence system of a preferred embodiment of the present application. DETAILED DESCRIPTION

[0048] In order to make the objects, technical solutions and advantages of the present application clearer, the present application will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and do not limit the present application.

[0049] Figure 1 is a flow chart of an alarm convergence method of a preferred embodiment of the present application. As shown in Figure 1 Step S1, power failure alarm data of a monitored device is received. Since there are many monitored devices, a large amount of alarm data is received from the moving ring, and thus some irrelevant alarm data is filtered out according to alarm type and / or device type, so as to reduce the amount of alarm data to be processed.

[0050] Figure 2 a preferred alarm filtering step is shown. As shown in Figure 2 Step S11, alarm data is received from the monitored device, and the alarm data is filtered based on alarm type and device type to obtain the power failure alarm data. For example, it can be firstly judged whether the device type contained in the alarm data satisfies high-voltage power distributor, low-voltage power distributor or transformer, and if not, it is directly filtered out. Then it is judged whether the alarm type contained in the alarm data is power failure (such as power outage, phase loss). If not, it is also filtered out. For the alarm data whose device type and alarm type both satisfy the requirements, it can be taken as the power failure alarm data.

[0051] In other preferred embodiments of the present application, the judgment of alarm type can be performed first, and then the judgment of device type, or the judgment of device type and alarm type can be performed simultaneously. In further preferred embodiments of the present application, the requirements of the device type and alarm type can also be different. Herein, the present application is not limited by the specific types.

[0052] In Step S12, the power failure alarm data is put into the power supply alarm cache and removed according to alarm state. After the power failure alarm data is put into the power supply alarm cache, if its alarm state is alarm start, subsequent processing can be performed, and if its alarm state becomes alarm end, subsequent processing is not needed, and thus it is removed from the power supply alarm cache, so as to further reduce the amount of data to be processed and presented.

[0053] Returning to Figure 1In step S2, the root cause device of the mains power fault alarm data is located based on the device connection data and the device real-time status data. In a preferred embodiment of the present invention, the device connection data includes a connection relationship ID, a child device ID, a parent device ID, and a connection path. The device real-time status data can be real-time status information collected by the environmental monitoring system from the monitored device, particularly including power consumption status information. In a preferred embodiment of the present invention, the device connection data can be... Figure 3 The format shown. Figure 7 A specific embodiment of a preferred embodiment of the device connection data of the present invention is shown.

[0054] Figure 4 Preferred root cause device identification steps are shown. For example... Figure 4 As shown, in step S21, mains power failure alarm data with a duration exceeding a first set time is periodically extracted from the power supply alarm buffer. In a preferred embodiment of the present invention, mains power failure alarm data with a duration exceeding 10 seconds can be extracted from the power supply alarm buffer at set intervals, such as 20 seconds, 15 seconds, or 10 seconds. This is mainly to prevent time differences in the uploading of monitoring data from various power supply systems.

[0055] In step S22, the connection path of the mains power fault alarm data is found based on the device connection data to obtain all devices from the mains power to the monitored device.

[0056] For example, if a monitored device with device ID = 516001568 generates a mains power failure alarm, its connection path is 516002070.516002074.516001646.516001650.516001542.516001568. This connection path is a top-down connection from high voltage to transformer to low voltage, thus indicating that the power supply passes through six levels of equipment from the mains power source to the monitored device. Therefore, any of these six devices could be the root cause of the mains power failure alarm.

[0057] Therefore, in step S23, the device real-time state data of all the devices is acquired, and the root cause device is found based on the device real-time state data. Based on the above analysis, it is known that the six devices 516002070, 516002074, 516001646, 516001650, 516001542 and 516001568 are all possible root cause devices triggering the alarm, and therefore only the power consumption states of the six devices 516002070, 516002074, 516001646, 516001650, 516001542 and 516001568 need to be acquired from the top down from the dynamic ring. Since it is a strict power supply relationship connection, the first device with power consumption anomaly is acquired, which is the root cause device. For example, the processing result is that 516002070 is normal, 516002074 is power failure, and 516002074 is the root cause device. The following devices do not need to be continuously judged, and the processing flow ends.

[0058] The specific algorithm for finding the root cause device is as follows:

[0059]

[0060]

[0061] Return Figure 1 In step S3, it is determined whether the convergence alarm event data of the root cause device has been generated. If yes, step S4 of deleting the city power failure alarm data and returning to step S1 is performed. Otherwise, step S5 of adding the convergence alarm event data of the root cause device is performed. The convergence alarm event data includes: convergence event ID, convergence event name, convergence type, convergence rule, convergence trigger event, convergence alarm number, convergence state, convergence root cause, confirmation time and root cause device ID. In the preferred embodiment of the present application, if the convergence alarm event data of the root cause device has been generated, the city power failure alarm data does not need to generate convergence alarm event data again, and can be directly deleted and returned to step S1 to judge the next city power failure alarm data. If the convergence alarm event data of the current root cause device has not been generated, it is proved that it is newly generated, and a new convergence alarm event data is written into the database, and then step S1 is returned to judge the next city power failure alarm data.

[0062] Figure 5 The preferred embodiment of generating the convergence alarm event data is shown. As Figure 5As shown, in step S31, the convergence alarm event data of the root cause device is searched according to the device ID of the root cause device, if the convergence alarm event data of the root cause device is searched, step S32 is executed, otherwise step S33 is executed. In step S32, it is judged whether the convergence state in the convergence alarm event data is end, if yes, step S33 is executed, otherwise step S34 is executed. In step S33, the convergence alarm event data of the root cause device is added and the process returns to step S1. In step S34, the power failure alarm data is deleted and the process returns to step S1.

[0063] In the preferred embodiment of the present application, the convergence alarm event data comprises: convergence event ID, convergence event name, convergence type, convergence rule, convergence trigger event, convergence alarm number, convergence state, convergence root cause, confirmation time and root cause device ID. In the preferred embodiment of the present application, the convergence alarm event data can adopt the format as shown. Figure 3 Figure 7 The specific embodiment of the preferred embodiment of the convergence alarm event data of the present application is shown.

[0064] In the further preferred embodiment of the present application, the convergence alarm event data can be updated. The updating step can occur at any suitable time, and can be automatically performed or based on user instruction. Preferably, the convergence alarm event data can be read at regular intervals and updated according to the device connection data, alarm convergence configuration data and the device real-time state data.

[0065] Figure 6 The preferred embodiment of the convergence alarm event data updating is shown. As shown, Figure 6 As shown, in step S41, the convergence alarm event data with the convergence state not being end is read, and the parent device ID of the monitored device generating the power failure alarm data within the setting time is updated according to the device connection data and the alarm convergence configuration data, and the convergence alarm number is returned. In step S42, the convergence state and the convergence alarm number of the convergence alarm event data are updated according to the device real-time state data. In step S42, when the device real-time state data comprises the device real-time state data of the power recovery device being normal, the convergence alarm number is updated and the convergence state is updated to end. When the power state is still failure, for example, power failure or open phase, only the convergence alarm number is updated. Preferably, the alarm rule data comprises rule ID, rule name, convergence type, device type, start expression, convergence alarm type, convergence interval, convergence start trigger number, convergence end trigger number and convergence root cause. In the preferred embodiment of the present application, the format of the alarm rule data can refer to the format as shown. Figure 3 Figure 7 ​​The specific embodiment of the preferred embodiment of the alarm rule data of the present application is shown,

[0066] In order to better illustrate the present application, refer to Figures 8-10 Further explained as follows. Figure 8 The alarm rule data in the table 1 shows that the 12 types of devices above will generate alarms due to power supply failure, each type of device has a specific type of alarm which will be considered as a sub-alarm, and the rules of convergence configuration can be dynamically adjusted. Figure 8 The device connection data in the table 2 shows that each device is defined with a detailed connection path; according to the relationship, it can be clearly shown that how many power lines the data center has and the connection superior-inferior relationship of the devices. Figure 8 The convergence alarm event data in the table 3 reflects the triggering event, convergence number, triggering rule, convergence state, root cause device ID, etc. of each alarm.

[0067] As can be seen from the above Figure 9 It can be seen that the monitoring system unifies the power failure and related alarms into one alarm, sets the related alarms as its sub-alarm, and can prompt the alarm root device, while Figure 9 The alarm management page shown in the table 4 can still display the alarms in the current system which are not related to power failure. And Figure 10 The downstream power supply device affected by the power failure can be intuitively displayed, and the recovery of the power supply can be detected according to this, and the on-duty personnel can very calmly deal with the power failure.

[0068] By implementing the alarm convergence method of the present application, the power supply connection relationship of the root power distribution devices of several power lines in the current system can be quickly clarified through the imported connection data, there is no invasiveness to the existing dynamic system, and it does not affect its function, and it can be deployed as a value-added module. And the present application further adopts a fast root cause device searching algorithm, and when any non-root cause power distribution device fails, it can quickly trace back to the fault source device through the root cause searching algorithm, and the system can generally respond within 10 seconds. And through the efficient tree searching algorithm and the data structure of the connection path, the device hanging sub-device can be quickly found, and the associated search between devices can be realized. Further, the present application can increase the practicability and reliability of the whole system, when the power failure occurs, the on-duty personnel can quickly know the root cause, take measures to avoid the occurrence of the situation affecting the business, and the practicability is wide, and it can also be used for the monitoring of telecommunication machine rooms and base stations.

[0069] The further preferred embodiment of the present application can further include a computer readable storage medium having a computer program stored thereon, and the computer program is executed by a processor to realize the alarm convergence method.

[0070] Figure 11is a principle block diagram of the alarm convergence system which is a preferred embodiment of the present application. As shown in Figure 11 The alarm convergence system comprises a receiving module 100, a root cause finding module 200, a convergence module 300 and a convergence updating module 400. The receiving module 100 is configured to receive power failure alarm data of a monitored device. The root cause finding module 200 is configured to find a root cause device of the power failure alarm data according to device connection data and real-time state data of the device. The convergence module 300 is configured to determine whether convergence alarm event data of the root cause device is generated, and if yes, delete the power failure alarm data, otherwise, add the convergence alarm event data of the root cause device. The convergence updating module 400 is configured to read the convergence alarm event data at a regular time and update the convergence alarm event data according to the device connection data, alarm convergence configuration data and the real-time state data of the device.

[0071] Here, the receiving module 100, the root cause finding module 200, the convergence module 300 and the convergence updating module 400 can be configured as shown in the embodiment shown in Figures 1-10 Here, the receiving module 100, the root cause finding module 200, the convergence module 300 and the convergence updating module 400 can be configured as shown in the embodiment shown in

[0072] Therefore, the present application can be realized by hardware, software or a combination of software and hardware. The present application can be realized in a centralized manner in at least one computer system or in a decentralized manner by different parts distributed in several interconnected computer systems. Any computer system or other apparatus capable of implementing the method of the present application is suitable. Commonly used combinations of software and hardware can be a general-purpose computer system with a computer program installed, which controls the computer system such that it operates according to the method of the present application.

[0073] The present application can also be implemented by a computer program product, which comprises all features enabling the implementation of the method of the present application, which becomes reality when it is installed in a computer system. The computer program in the present document refers to any expression, in any language, code or notation, of a set of instructions intended to cause a system having information processing capability to perform a particular function either directly or after either a) conversion to another language, code or notation; b) reproduction in a different material form.

[0074] Although the present application has been described by way of specific embodiments, those skilled in the art will understand that various changes and modifications can be made to the present application without departing from the scope of the present application. In addition, various modifications can be made to the present application for specific situations or materials without departing from the scope of the present application. Therefore, the present application is not limited to the specific embodiments disclosed, but includes all embodiments falling within the scope of the claims of the present application.

[0075] The above description is only the preferred embodiment of the present application, and is not intended to limit the present application. Any modification, equivalent replacement and improvement made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. An alarm convergence method, characterized by, The method comprises the following steps: S1, receiving power failure alarm data of a monitored device; S2, finding a root cause device of the power failure alarm data according to device connection data and device real-time state data; S3, determining whether converged alarm event data of the root cause device has been generated, if yes, deleting the power failure alarm data and returning to step S1, otherwise, adding the converged alarm event data of the root cause device and returning to step S1; The step S1 further comprises: S11, receiving alarm data from the monitored device, and filtering the alarm data to obtain the power failure alarm data based on alarm types and device types; S12, putting the power failure alarm data into a power supply alarm cache and removing the power failure alarm data according to alarm states; The step S2 further comprises: S21, extracting the power failure alarm data with a duration exceeding a first set time from the power supply alarm cache at a time; S22, finding a connection path of the power failure alarm data according to the device connection data to obtain all devices between power supply and the monitored device; S23, obtaining device real-time state data of the all devices, and finding the root cause device based on the device real-time state data; The step S3 further comprises: S31, finding the converged alarm event data of the root cause device according to a device ID of the root cause device, if the converged alarm event data of the root cause device is found, step S32 is executed, otherwise, step S33 is executed; S32, judging whether a convergence state in the converged alarm event data is end, if yes, step S33 is executed, otherwise, the power failure alarm data is deleted and the step S1 is returned; S33, adding the converged alarm event data of the root cause device and returning to the step S1.

2. The method of claim 1, wherein, The alarm types comprise power failure, and the device types comprise high-voltage power distributor, low-voltage power distributor and transformer.

3. The method of claim 1, wherein the step of converging the alarms further comprises the step of: The device connection data comprises a connection relationship ID, a child device ID, a parent device ID and a connection path.

4. The method of claim 1, wherein the method further comprises: The converged alarm event data comprises a convergence event ID, a convergence event name, a convergence type, a convergence rule, a convergence trigger event, a convergence alarm number, a convergence state, a convergence root cause, a confirmation time and a root cause device ID.

5. The method of claim 1 or 2, wherein, The method further comprises: S4, reading the converged alarm event data at a time and updating the converged alarm event data according to the device connection data, alarm convergence configuration data and the device real-time state data.

6. The method of claim 5, wherein the step of converging the alarms further comprises the step of: The step S4 further comprises: S41, reading the converged alarm event data with a convergence state being not end, and updating a parent device ID of a monitored device generating the power failure alarm data within a set time according to the device connection data and the alarm convergence configuration data and returning a convergence alarm number; S42, updating the convergence state and the convergence alarm number of the converged alarm event data according to the device real-time state data.

7. The method of claim 5, wherein the step of converging the alarms further comprises the step of: In the step S42, when the device real-time state data includes the device real-time state data of the power recovery device, the convergence alarm number is updated and the convergence state is updated to end, otherwise the convergence alarm number is updated. ​ 8. The method of claim 7, wherein the step of converging the alarms further comprises the step of: The alarm rule data includes rule ID, rule name, convergence type, device type, start expression, convergence alarm type, convergence interval, convergence start trigger number, convergence end trigger number and convergence root cause.

9. A computer-readable storage medium having stored thereon a computer program, characterized in that, The computer program is executed by the processor to implement the alarm convergence method according to any one of claims 1-8.

10. An alarm convergence system, comprising: Comprise: The receiving module is used for receiving the power failure alarm data of the monitored device; The root cause finding module is used for finding the root cause device of the power failure alarm data according to the device connection data and the device real-time state data; The convergence module is used for judging whether the convergence alarm event data of the root cause device is generated, if yes, deleting the power failure alarm data, otherwise increasing the convergence alarm event data of the root cause device; The receiving module is further used for receiving alarm data from the monitored device, and filtering the alarm data based on alarm type and device type to obtain the power failure alarm data; putting the power failure alarm data into the power supply alarm cache and removing according to alarm state; The root cause finding module is further used for extracting the power failure alarm data with duration exceeding the first set time from the power supply alarm cache; According to the device connection data, the connection path of the power failure alarm data is found to obtain all devices between the power supply and the monitored device; the device real-time state data of all devices is obtained, and the root cause device is found based on the device real-time state data.

11. The alarm convergence system of claim 10, wherein, Further comprise: The convergence updating module is used for reading the convergence alarm event data and updating the convergence alarm event data according to the device connection data, alarm convergence configuration data and device real-time state data.

Images