Warning marking method, device, electronic device and storage medium
By obtaining the preset change scene information of the data center computer room, automatically filtering and marking the alarms caused by the change operation, the problem of inefficient manual verification is solved and efficient alarm processing is achieved.
Patent Information
- Application Number
- CN202211399910.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-11-09
- Publication Date
- 2025-08-26
- Estimated Expiration
- 2042-11-09
AI Technical Summary
In data center operation and maintenance, alarms caused by change operations cannot be automatically identified, resulting in inefficient manual verification and consumes a lot of manpower and time.
By detecting the alarms in the target computer room and obtaining preset change scene information, automatically filtering and marking the alarms generated by the change operation, reducing manual verification work.
It improves the efficiency of alarm processing, reduces the workload of personnel verification, and improves the efficiency of processing.
Smart Images

Figure CN115811459B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of operation and maintenance technology, and specifically to an alarm marking method, device, electronic device and storage medium. Background Art
[0002] In the field of data center operation and maintenance, it is usually necessary to perform some change operations such as shutdown inspection, maintenance, switching, etc. on the equipment in the data center computer room. In the centralized center, these change operations will trigger a large number of alarms, and these alarms are caused by the change operations and do not need to be processed.
[0003] In the related art, the alarms notified by the center are manually checked one by one to confirm whether there are any alarms caused by sudden failures. This requires a lot of manpower and time to process, and the processing efficiency is relatively low. Summary of the Invention
[0004] The purpose of this application is to propose an alarm marking method, device, electronic device and storage medium to address the deficiencies of the above-mentioned existing technologies, and this purpose is achieved through the following technical solutions.
[0005] A first aspect of the present application provides an alarm marking method, the method comprising:
[0006] Detecting an alarm for a target computer room, and obtaining preset change scenario information corresponding to the target computer room;
[0007] Based on the preset change scenario information, determining whether the alarm is generated by a change operation;
[0008] If yes, then add a flag to the alarm.
[0009] In some embodiments of the present application, obtaining preset change scenario information corresponding to the target computer room includes:
[0010] From the recorded change operations, obtain the change operations belonging to the target computer room; among the obtained change operations, obtain the target change operations whose start time is before the trigger time of the alarm and have not ended; and use the first device corresponding to the target change operation and the pre-set first alarm list as the preset change scenario information.
[0011] In some embodiments of the present application, determining whether the alarm is generated by a change operation based on the preset change scenario information includes:
[0012] Match the alarm with the preset alarms in the first alarm list; when there is no preset alarm matching the alarm, determine whether the alarm is generated by a change operation based on the first device; when there is a preset alarm matching the alarm, determine that the alarm is not generated by a change operation in the target computer room.
[0013] In some embodiments of the present application, determining, according to the first device, whether the alarm is generated by a change operation includes:
[0014] Determine the second device targeted by the alarm; based on the fact that the first device and the second device are the same device, determine that the alarm is generated by a change operation in the target computer room; based on the fact that the first device and the second device are not the same device, determine whether the alarm is generated by a change operation based on the dependency relationship between the first device and the second device.
[0015] In some embodiments of the present application, determining whether the alarm is generated by a change operation based on the dependency relationship between the first device and the second device includes:
[0016] Obtain a list of downstream devices associated with the first device; based on the fact that the second device belongs to the downstream device list, determine that the alarm is generated by a change operation in the target computer room; based on the fact that the second device does not belong to the downstream device list, determine that the alarm is not generated by a change operation in the target computer room.
[0017] In some embodiments of the present application, obtaining a list of downstream devices associated with the first device includes:
[0018] Determine the topological relationship to which the first device belongs, the topological relationship including multiple levels, each level recording at least one device; determine the level to which the first device belongs in the topological relationship; from the topological relationship, obtain the devices located in the subordinate levels of the level to which it belongs and associated with the first device as the downstream device list.
[0019] In some embodiments of the present application, obtaining preset change scenario information corresponding to the target computer room includes:
[0020] Acquire a second alarm list pre-set for a target device in the target computer room; and determine the target device and the second alarm list as preset change scenario information.
[0021] In some embodiments of the present application, determining whether the alarm is generated by a change operation based on the preset change scenario information includes:
[0022] Determine whether the second device targeted by the alarm is the target device; if so, determine that the alarm is generated by a change operation in the target computer room based on the presence of a preset alarm matching the alarm in the second alarm list.
[0023] In some embodiments of the present application, obtaining preset change scenario information corresponding to the target computer room includes:
[0024] Determine pre-set first and second type alarms, where a trigger association relationship exists between the first and second type alarms; and determine the first and second type alarms as preset change scenario information corresponding to the target computer room.
[0025] In some embodiments of the present application, determining whether the alarm is generated by a change operation based on the preset change scenario information includes:
[0026] According to the fact that the alarm belongs to the first type of alarm, based on the trigger timestamp of the alarm and the second type of alarm, determine whether the alarm is generated by a change operation; according to the fact that the alarm belongs to the second type of alarm, determine that the alarm is not generated by a change operation of the target computer room.
[0027] In some embodiments of the present application, determining whether the alarm is generated by a change operation based on the trigger timestamp of the alarm and the second type of alarm includes:
[0028] Use the trigger timestamp of the alarm to determine the query time range; obtain the triggered alarms that are within the query time range and belong to the second device targeted by the alarm; determine that the alarm is generated by a change operation in the target computer room based on the absence of triggered alarms belonging to the second category of alarms; determine that the alarm is not generated by a change operation in the target computer room based on the existence of triggered alarms belonging to the second category of alarms.
[0029] A second aspect of the present application provides a warning marking device, the device comprising:
[0030] An acquisition module, configured to detect an alarm for a target computer room and acquire preset change scenario information corresponding to the target computer room;
[0031] A determination module, configured to determine whether the alarm is generated by a change operation based on the preset change scenario information;
[0032] The marking module is used to add a mark to the alarm when it is determined that the alarm is generated by a change operation of the target computer room.
[0033] The third aspect of the present application proposes an electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the steps of the method described in the first aspect above.
[0034] The fourth aspect of the present application proposes a computer-readable storage medium having a computer program stored thereon, wherein the program is executed by a processor to implement the steps of the method described in the first aspect above.
[0035] Based on the warning marking method and device described in the first and second aspects above, this application has at least the following beneficial effects or advantages:
[0036] When an alarm is triggered, since the alarm is triggered by the abnormal status of a device in the computer room, the preset change scenario information corresponding to the target computer room targeted by the alarm can be obtained for filtering the alarm. Then, based on the preset change scenario information, when it is determined that the currently triggered alarm is caused by a change operation in the target computer room, the alarm is automatically marked to indicate that the alarm is caused by a change operation. This can reduce personnel verification work and improve alarm processing efficiency. BRIEF DESCRIPTION OF THE DRAWINGS
[0037] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:
[0038] Figure 1 This is a flowchart of an embodiment of a warning marking method according to an exemplary embodiment of the present application;
[0039] Figure 2 This is a flowchart of an alarm determination in a preset change scenario according to an exemplary embodiment of the present application;
[0040] Figure 3 A schematic diagram of a topological relationship shown in this application;
[0041] Figure 4 This is a flowchart of an alarm determination in another preset change scenario according to an exemplary embodiment of the present application;
[0042] Figure 5 This is a flowchart of an alarm determination in another preset change scenario according to an exemplary embodiment of the present application;
[0043] Figure 6 This application is based on Figure 1 The embodiment shown is a schematic diagram of an alarm screening marking process;
[0044] Figure 7 This is a structural diagram of a warning marking device according to an exemplary embodiment of the present application;
[0045] Figure 8 This is a schematic diagram of the hardware structure of an electronic device according to an exemplary embodiment of the present application;
[0046] Figure 9 This is a schematic structural diagram of a storage medium according to an exemplary embodiment of the present application. DETAILED DESCRIPTION
[0047] Exemplary embodiments will be described in detail herein, with examples illustrated in the accompanying drawings. In the following description, when referring to the drawings, identical numerals in different figures represent identical or similar elements, unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.
[0048] The terms used in this application are for the purpose of describing specific embodiments only and are not intended to limit this application. As used in this application and the appended claims, the singular forms "a," "an," "the," and "the" are intended to include the plural forms, unless the context clearly indicates otherwise. It should also be understood that the term "and / or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.
[0049] It should be understood that although the terms first, second, third, etc. may be used in this application to describe various information, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from each other. For example, without departing from the scope of this application, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining".
[0050] In order to reduce the workload of personnel in checking alarms, this application proposes an alarm marking method, which performs preliminary screening of the triggered alarms at the center to screen out alarms generated by change operations, and automatically marks these alarms to indicate that these alarms are generated by change operations, so that the checking personnel no longer need to process them, thereby improving the efficiency of alarm processing.
[0051] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiment of the present application will be clearly and completely described below in conjunction with the drawings in the embodiment of the present application.
[0052] Figure 1 This is a flowchart of an embodiment of an alarm marking method according to an exemplary embodiment of the present application. The method can be applied to a computer room system and includes the following steps:
[0053] Step 101: Detect an alarm for a target computer room and obtain preset change scenario information corresponding to the target computer room.
[0054] In this embodiment, the computer room system will monitor the equipment status in each computer room in real time. When an abnormality is found in the equipment status of a certain computer room, an alarm will be triggered immediately for the equipment in that computer room. There are two reasons for the abnormal equipment status: one is caused by the operation and maintenance personnel making changes to the computer room. In this case, the alarm generated can be considered as an expected alarm and no processing is required; the other is caused by an on-site failure. In this case, the alarm generated can be considered as an unexpected alarm and needs to be processed in a timely manner.
[0055] Based on this, before executing step 101, in order to automatically filter out the expected alarms, it is necessary to set some change scenario information in the computer room system in advance, so that when an alarm is triggered, these change scenario information can be used to determine whether the triggered alarm is caused by a change operation.
[0056] The preset change scenario information includes some information related to the specified change scenario.
[0057] In one example, consider a complex change scenario involving a series of changes to equipment in a computer room. Each change requires pre-setting the device information, computer room information, and start time, and then setting the end time after the change is complete. Of course, for alarms that aren't triggered by the change, or unexpected alarms, these can be blacklisted, placing them in a separate alarm list.
[0058] Based on this, in the process of obtaining the preset change scenario information corresponding to the target computer room, the change operations belonging to the target computer room are obtained from the recorded change operations, and then the target change operations whose start time is before the trigger time of the alarm and have not ended are obtained from the obtained change operations, so that the first device corresponding to the target change operation and the pre-set first alarm list are used as the preset change scenario information corresponding to the target computer room.
[0059] The first device corresponding to the target change operation is the device in the target computer room undergoing the change operation. The first alarm list contains unexpected alarms that are not caused by the change operation. In other words, even if these alarms target the device undergoing the change operation, they are not caused by the change operation and require manual verification.
[0060] In another example, assuming the specified change scenario is a simple one, i.e., a temporary, simple change operation in the equipment room, you can pre-set the device information for the temporary change, the alarms that may be triggered by the change, and the reason for the change. This way, you can bind the alarms to the devices and use them as smart tag templates. Of course, these settings are deleted after the change is completed.
[0061] Based on this, in the process of obtaining the preset change scenario information corresponding to the target computer room, the second alarm list pre-set for the target device in the target computer room is obtained, so that the target device and the second alarm list are determined as the preset change scenario information.
[0062] The second alarm list of the target device is a list of possible alarms that may be generated by temporarily changing the device in a simple scenario set up in the target computer room, in which the expected alarms are recorded.
[0063] In another example, assume that the specified change scenario is a fixed scenario, that is, when a fault occurs, there will be a series of alarms, for example, alarm 1, alarm 2, alarm 3 and alarm 4 are triggered in series. If alarm 2, alarm 3, and alarm 4 occur first, the last alarm 1 is an unexpected alarm. However, if alarm 2, alarm 3, and alarm 4 do not occur, but alarm 1 occurs, it can be considered that it is not a fault, but personnel maintenance in a fixed scenario. Alarm 1 is an expected alarm. Therefore, two types of alarms can be set in advance: the first type of alarm and the second type of alarm. There is a trigger association relationship between these two types of alarms. For example, alarm 1 is set as the first type of alarm, and alarm 2, alarm 3, and alarm 4 are set as the second type of alarm.
[0064] The first type of alarm is a later-triggered alarm, while the second type of alarm is a first-triggered alarm. It is worth noting that in this specific scenario, the second type of alarm that is triggered first can be directly identified as an unexpected alarm.
[0065] Based on this, in the process of obtaining the preset change scenario information corresponding to the target computer room, the pre-set first-class alarm and second-class alarm are determined, and there is a trigger association relationship between the first-class alarm and the second-class alarm. Then, the first-class alarm and the second-class alarm are determined as the preset change scenario information corresponding to the target computer room.
[0066] Those skilled in the art will appreciate that the three change scenarios given above are merely exemplary. Other specified change scenario information may be set according to actual usage requirements for use in alarm screening.
[0067] Step 102: Based on the preset change scenario information, determine whether the alarm is generated by a change operation.
[0068] In some embodiments, for the complex scenario described in step 101 above, the preset change scenario information includes the first device and the first alarm list corresponding to the ongoing change operation. For the process of determining whether the alarm is generated by the change operation, see Figure 2 As shown, the process includes the following:
[0069] Step 201: Match the alarm with the preset alarms in the first alarm list.
[0070] Optionally, since each alarm triggered by the computer room system will carry a unique alarm code, the alarm code carried by the alarm can be compared with the alarm code of each preset alarm in the first alarm list. If there is a consistent match, it means that there is a preset alarm that matches the alarm. If there is no consistent match, it means that there is no preset alarm that matches the alarm.
[0071] Step 202: When there is no preset alarm matching the alarm, determine whether the alarm is generated by a change operation according to the first device included in the preset change scenario information.
[0072] Optionally, the second device targeted by the alarm is determined. If the first and second devices are the same device, the alarm can be directly determined to be caused by a change operation. However, if the first and second devices are different devices, it is necessary to further determine whether the alarm was caused by a change operation based on the dependency relationship between the first and second devices. In this way, by comparing the first and second devices, alarms related to devices undergoing changes can be preliminarily screened out.
[0073] Among them, for two devices with a dependent relationship, when one device is changed, it will affect the status of the other device that depends on it, causing the computer room system to trigger an alarm for the other device. Therefore, it is necessary to further determine based on the dependency relationship between the first device and the second device.
[0074] In one specific embodiment, based on the dependency relationship between a first device and a second device, determining whether an alarm was generated by a change operation is performed by obtaining a list of downstream devices associated with the first device. If the second device is included in the list, the alarm is determined to be generated by a change operation. If the second device is not included in the list, the alarm is determined not to be generated by a change operation. This retrieval from upstream to downstream devices can improve the precision of alarm screening.
[0075] The dependency relationship between the downstream devices in the downstream device list and the first device is that the downstream devices are dependent on the first device. This means that during a change operation on the first device, the computer room system may generate alarms for these downstream devices. Therefore, if the second device targeted by the alarm is in the downstream device list, the alarm was generated by the change operation.
[0076] It is worth noting that the process of obtaining the list of downstream devices associated with the first device can be either active acquisition when setting the change steps of the first device, or passive acquisition when it is necessary to determine whether the alarm is generated by a change operation based on the dependency relationship between the first device and the second device. This application does not specifically limit the timing of obtaining the list of downstream devices associated with the first device.
[0077] Optionally, for the process of obtaining the list of downstream devices associated with the first device, the topological relationship to which the first device belongs is determined, and then the level to which the first device belongs in the topological relationship is determined, and from the topological relationship, the devices located in the subordinate levels of the level to which they belong and associated with the first device are obtained as the downstream device list.
[0078] The topology relationship includes multiple levels, each level records at least one device, and a device in the previous level has at least one device associated with it recorded in the next level. Exemplarily, the topology relationship may be a power supply topology relationship.
[0079] It is worth noting that the subordinate levels of the level to which the first device belongs include the next level of the level to which it belongs, and the next level, until the last level, so the devices associated with the first device include directly associated devices and indirectly associated devices.
[0080] For example, see Figure 3 The topology diagram shown includes three levels: the first level, the second level, and the third level. Device 1 in the first level is associated with devices 2, 3, and 4 in the next level (the second level). Device 2 in the second level is associated with devices 5, 6, and 7 in the next level (the third level). The first level's subordinate levels include the second and third levels, and the second level's subordinate levels include the third level. Assuming the first device is device 2, the downstream devices associated with device 2 are devices 5, 6, and 7.
[0081] Step 203: When there is a preset alarm matching the alarm, it is determined that the alarm is not generated by a change operation.
[0082] When it is determined that the alarm is not generated by a change operation, it means that the alarm is an unexpected alarm and can be notified according to a fault alarm to facilitate personnel processing.
[0083] At this point, the above is completed Figure 2 The alarm screening process in a complex scenario is shown.
[0084] In another embodiment, for the simple scenario described in step 101 above, the preset change scenario information includes information about target devices in the target computer room that are temporarily undergoing a change operation and a second alarm list set for the target devices. For the process of determining whether an alarm is generated by a change operation, see Figure 4 As shown, the process includes the following:
[0085] Step 401: Determine whether the second device targeted by the alarm is the target device included in the preset change scenario information.
[0086] Step 402: During the determination, based on the presence of a preset alarm matching the alarm in the second alarm list, it is determined that the alarm is generated by a change operation.
[0087] So far, completed Figure 4 The alarm screening process in the simple scenario shown is to match the alarm and the second device it targets with the target device and the second alarm list in the preset change scenario information respectively. If both of these items match, it can be directly determined that the alarm is generated by a change operation, which is simple and convenient.
[0088] In another embodiment, for the fixed scenario described in step 101 above, the preset change scenario information includes the first type of alarm and the second type of alarm that have a trigger association relationship. For the process of determining whether the alarm is generated by the change operation, see Figure 5 As shown, the process includes the following:
[0089] Step 501: According to the alarm belonging to the first type of alarm, based on the triggering timestamp of the alarm and the second type of alarm, determine whether the alarm is generated by a change operation.
[0090] Among them, since the first type of alarm is the alarm that is triggered later in the trigger association relationship, if the alarm belongs to the first type of alarm, it is necessary to further use the triggering timestamp of the alarm and the second type of alarm to further determine.
[0091] In a specific implementation, the query time range can be determined first using the trigger timestamp of the alarm, and then the triggered alarm that is within the query time range and belongs to the second device targeted by the alarm is obtained, and the triggered alarm is compared with the second type of alarm. If there is no triggered alarm belonging to the second type of alarm, it is determined that the alarm is generated by a change operation. If there is a triggered alarm belonging to the second type of alarm, it is determined that the alarm is not generated by a change operation.
[0092] The query time range is a period of time defined by the trigger timestamp, extending back a specified period. If a triggered alarm in the second category is present, it indicates an unexpected fault. If no triggered alarm in the second category is present, it indicates no unexpected fault but rather an alarm caused by maintenance personnel in a specific scenario, which is an expected alarm.
[0093] Step 502: According to the alarm belonging to the second type of alarm, it is determined that the alarm is not generated by a change operation.
[0094] So far, completed Figure 5 The alarm screening process in a fixed scenario shown automatically determines the currently triggered alarm by using the first and second category alarms that have a trigger association relationship in the fixed scenario, so as to screen the expected alarms in the fixed scenario.
[0095] Based on the above Figure 2 、 Figure 4 、 Figure 5 The alarm screening process under the three scenarios shown is understandable. In the process of determining whether the alarm is generated by a change operation, the screening processes of these three scenarios can also be combined, such as a combination of fixed scenarios and complex scenarios. That is, if the triggered alarm does not belong to the two types of alarms set in the fixed scenario, the scenario information set in the complex scenario is used for judgment.
[0096] Step 103: If yes, add a mark to the alarm.
[0097] When it is determined that the alarm is generated by a change operation, a mark can be added to the alarm to distinguish it from unexpected alarms, which makes it easier for personnel to distinguish and view them.
[0098] It is understandable that the added mark can be an expected alarm prompt or a cause description information, and this application does not specifically limit this.
[0099] For the alarm marking scheme of steps 101 to 103 above, see Figure 6 The alarm processing flow shown, for the alarms in Building A of Computer Room A, are: Alarm 1 to Alarm 9. After using the processing flow shown in Steps 101 to 103 above, Alarm 1 to Alarm 4 are determined to be expected alarms, that is, alarms generated by change operations, and Alarm 5 to Alarm 9 are determined to be unexpected alarms, that is, alarms not generated by change operations. Therefore, since Alarm 1 to Alarm 4 are all marked, personnel do not need to check and process Alarm 1 to Alarm 4 again.
[0100] At this point, the above is completed Figure 1The alarm marking process shown is that when an alarm is triggered, since the alarm is triggered by the abnormal status of a device in the computer room, the preset change scenario information corresponding to the target computer room targeted by the alarm can be obtained for filtering the alarm. Then, based on the preset change scenario information, when it is determined that the currently triggered alarm is caused by a change operation in the target computer room, the alarm is automatically marked to indicate that the alarm is caused by a change operation. This can reduce personnel verification work and improve alarm processing efficiency.
[0101] Corresponding to the above-mentioned embodiment of the warning marking method, the present application also provides an embodiment of the warning marking device.
[0102] Figure 7 This is a schematic structural diagram of a warning marking device according to an exemplary embodiment of the present application, which is used to execute the warning marking method provided in any of the above embodiments, such as Figure 7 As shown, the warning marking device includes:
[0103] An acquisition module 710 is configured to detect an alarm for a target computer room and acquire preset change scenario information corresponding to the target computer room;
[0104] A determination module 720 is configured to determine whether the alarm is generated by a change operation based on the preset change scenario information;
[0105] The marking module 730 is configured to add a mark to the alarm when it is determined that the alarm is generated by a change operation in the target computer room.
[0106] The implementation process of the functions and effects of each unit in the above-mentioned device is specifically described in the implementation process of the corresponding steps in the above-mentioned method, and will not be repeated here.
[0107] For the device embodiments, since they basically correspond to the method embodiments, the relevant parts can be referred to the partial description of the method embodiments. The device embodiments described above are merely schematic, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the present application scheme. A person of ordinary skill in the art can understand and implement it without paying any creative work.
[0108] The embodiment of the present application further provides an electronic device corresponding to the alarm marking method provided in the above embodiment, so as to execute the above alarm marking method.
[0109] Figure 8This is a hardware structure diagram of an electronic device according to an exemplary embodiment of the present application. The electronic device includes: a communication interface 601, a processor 602, a memory 603, and a bus 604. The communication interface 601, the processor 602, and the memory 603 communicate with each other via the bus 604. The processor 602 can execute the alarm marking method described above by reading and executing machine-executable instructions corresponding to the control logic of the alarm marking method in the memory 603. The specific content of the method is described in the above embodiment and will not be repeated here.
[0110] The memory 603 mentioned in this application can be any electronic, magnetic, optical or other physical storage device, which can contain stored information, such as executable instructions, data, etc. Specifically, the memory 603 can be RAM (Random Access Memory), flash memory, a storage drive (such as a hard disk drive), any type of storage disk (such as an optical disk, DVD, etc.), or a similar storage medium, or a combination thereof. The communication connection between the system network element and at least one other network element is realized through at least one communication interface 601 (which can be wired or wireless), and the Internet, wide area network, local area network, metropolitan area network, etc. can be used.
[0111] The bus 604 may be an ISA bus, a PCI bus, or an EISA bus, etc. The bus may be divided into an address bus, a data bus, a control bus, etc. The memory 603 is used to store programs, and the processor 602 executes the programs after receiving an execution instruction.
[0112] The processor 602 may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method can be completed by an integrated logic circuit of the hardware in the processor 602 or an instruction in the form of software. The above-mentioned processor 602 can be a general-purpose processor, including a network processor (NP), a digital signal processor (DSP), an application-specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. The various methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc. The steps of the method disclosed in conjunction with the embodiments of the present application can be directly embodied as a hardware decoding processor for execution, or can be completed by a combination of hardware and software modules in the decoding processor.
[0113] The electronic device provided in the embodiment of the present application and the alarm marking method provided in the embodiment of the present application are based on the same inventive concept and have the same beneficial effects as the methods adopted, operated or implemented by them.
[0114] The present application also provides a computer-readable storage medium corresponding to the alarm marking method provided in the above embodiment. Figure 9 As shown, the computer-readable storage medium is a CD 30 on which a computer program (ie, a program product) is stored. When the computer program is run by a processor, the alarm marking method provided by any of the aforementioned embodiments is executed.
[0115] It should be noted that examples of the computer-readable storage medium may also include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other optical or magnetic storage media, which are not listed here one by one.
[0116] The computer-readable storage medium provided in the above-mentioned embodiment of the present application and the alarm marking method provided in the embodiment of the present application are based on the same inventive concept and have the same beneficial effects as the method adopted, run or implemented by the application program stored therein.
[0117] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the present application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The description and examples are to be considered as exemplary only, and the true scope and spirit of the present application are indicated by the following claims.
[0118] It should also be noted that the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, commodity, or apparatus that includes a series of elements includes not only those elements but also other elements not explicitly listed, or includes elements inherent to such process, method, commodity, or apparatus. In the absence of further limitations, an element defined by the phrase "comprises a ..." does not exclude the presence of other identical elements in the process, method, commodity, or apparatus that includes the element.
[0119] The above description is only a preferred embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application shall be included in the scope of protection of the present application.
Claims
1. A warning marking method, characterized in that: The method comprises: Detecting an alarm for a target computer room, and obtaining preset change scenario information corresponding to the target computer room; Based on the preset change scenario information, determining whether the alarm is generated by a change operation; If yes, add a mark to the alarm; The determining, based on the preset change scenario information, whether the alarm is generated by a change operation includes: Matching the alarm with the preset alarms in the first alarm list; When there is no preset alarm matching the alarm, determining, according to the first device, whether the alarm is generated by a change operation, wherein determining, according to the first device, whether the alarm is generated by a change operation includes: Determining a second device for which the alarm is directed; If the first device and the second device are the same device, determine whether the alarm is generated by a change operation; if the first device and the second device are not the same device, determine whether the alarm is generated by a change operation based on the dependency relationship between the first device and the second device.
2. The method according to claim 1, characterized in that The obtaining of preset change scenario information corresponding to the target computer room includes: Obtaining the change operations belonging to the target computer room from the recorded change operations; Among the acquired change operations, acquire the target change operations whose start time is before the trigger time of the alarm and which have not yet ended; The first device corresponding to the target change operation and the preset first alarm list are used as the preset change scenario information.
3. The method according to claim 1, characterized in that The determining, based on the preset change scenario information, whether the alarm is generated by a change operation further includes: When there is a preset alarm matching the alarm, it is determined that the alarm is not generated by a change operation.
4. The method according to claim 1, wherein The determining, based on the dependency relationship between the first device and the second device, whether the alarm is generated by a change operation includes: Obtaining a list of downstream devices associated with the first device; determining, based on the second device belonging to the downstream device list, that the alarm is generated by a change operation; According to the fact that the second device does not belong to the downstream device list, it is determined that the alarm is not generated by a change operation.
5. The method according to claim 4, characterized in that The acquiring a list of downstream devices associated with the first device includes: Determine a topological relationship to which the first device belongs, where the topological relationship includes multiple levels, and each level records at least one device; Determining a level to which the first device belongs in the topological relationship; From the topological relationship, devices located in a subordinate layer of the layer to which it belongs and associated with the first device are acquired as the downstream device list.
6. The method according to any one of claims 1 to 5, characterized in that The obtaining of preset change scenario information corresponding to the target computer room includes: Obtaining a second alarm list pre-set for the target device in the target computer room; The target device and the second alarm list are determined as preset change scenario information.
7. The method according to claim 6, characterized in that Determining whether the alarm is generated by a change operation based on the preset change scenario information includes: Determining whether the second device targeted by the alarm is the target device; If so, based on the presence of a preset alarm matching the alarm in the second alarm list, it is determined that the alarm is generated by a change operation.
8. The method according to any one of claims 1 to 5, characterized in that The obtaining of preset change scenario information corresponding to the target computer room includes: Determining a pre-set first-category alarm and a second-category alarm, where a trigger association relationship exists between the first-category alarm and the second-category alarm; The first type of alarm and the second type of alarm are determined as the preset change scenario information corresponding to the target computer room.
9. The method according to claim 8, characterized in that Determining whether the alarm is generated by a change operation based on the preset change scenario information includes: According to the alarm belonging to the first category of alarms, based on the triggering timestamp of the alarm and the second category of alarms, determining whether the alarm is generated by a change operation; According to the alarm belonging to the second type of alarm, it is determined that the alarm is not generated by a change operation of the target computer room.
10. The method according to claim 9, characterized in that The determining, based on the trigger timestamp of the alarm and the second type of alarm, whether the alarm is generated by a change operation includes: Determine the query time range using the trigger timestamp of the alarm; Obtaining a triggered alarm that is within the query time range and belongs to the second device targeted by the alarm; determining that the alarm is generated by a change operation based on the absence of a triggered alarm belonging to the second category of alarms; According to the existence of the triggered alarm belonging to the second category of alarms, it is determined that the alarm is not generated by a change operation.
11. A warning marking device, characterized in that: The device comprises: An acquisition module, configured to detect an alarm for a target computer room and acquire preset change scenario information corresponding to the target computer room; A determination module, configured to determine whether the alarm is generated by a change operation based on the preset change scenario information; a marking module, configured to add a mark to the alarm when determining that the alarm is generated by a change operation of the target computer room; The determining, based on the preset change scenario information, whether the alarm is generated by a change operation includes: Matching the alarm with the preset alarms in the first alarm list; When there is no preset alarm matching the alarm, determining, according to the first device, whether the alarm is generated by a change operation, wherein determining, according to the first device, whether the alarm is generated by a change operation includes: Determining a second device for which the alarm is directed; If the first device and the second device are the same device, determine whether the alarm is generated by a change operation; if the first device and the second device are not the same device, determine whether the alarm is generated by a change operation based on the dependency relationship between the first device and the second device.
12. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: The processor executes the program to implement the steps of the method according to any one of claims 1 to 10.
13. A computer-readable storage medium having a computer program stored thereon, characterized in that: The program is executed by a processor to implement the steps of the method according to any one of claims 1 to 10.
Citation Information
Patent Citations
Method and system for processing alarm caused by change in IT operation and maintenance
CN105589793A