Alarm processing method, system, device, storage medium and program product

Abstract

The application discloses an alarm processing method, system, device, storage medium and program product, relates to the technical field of computers, and comprises the following steps: after receiving current attribute information set by a sensor alarm, a configuration file configured with an alarm filtering rule according to actual requirements is acquired; it is judged whether the current attribute information meets the alarm filtering rule; and in the case where the alarm filtering rule is met, the alarm of the sensor is removed. The application solves a series of problems caused by the failure to filter alarms, alarm filtering is performed through flexible and configurable alarm filtering rules, and the technical effects of reducing redundant log accumulation and improving log management efficiency are achieved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computers, and particularly relates to an alarm processing method, system, device, storage medium and program product. BACKGROUND

[0002] With the rapid development of cloud computing and big data, the scale of data centers is continuously expanding, and the number of server nodes is surging, which puts higher requirements on the stability and maintainability of infrastructure. As the core out-of-band management unit of a server, a baseboard management controller (BMC) undertakes the important responsibility of real-time monitoring of the hardware state of the server, and the collection and alarm processing of sensor data are key links to ensure the stable operation of the system.

[0003] However, during the startup and running of the BMC, the alarms of some sensors belong to normal initialization behavior, non-critical state changes or negligible unnecessary alarms. If all alarms are recorded without distinction, a large number of redundant logs will be generated, which will further lead to low log management efficiency. SUMMARY

[0004] The present application provides an alarm processing method, system, device, storage medium and program product to at least solve the problem of a large number of redundant alarms in the related art.

[0005] The present application provides an alarm processing method, comprising:

[0006] obtaining current attribute information and current state information of a target sensor;

[0007] in a case where the current state information is an alarm state, obtaining a pre-constructed configuration file, wherein the configuration file comprises an alarm filtering rule of the target sensor;

[0008] in a case where the current attribute information meets the alarm filtering rule, canceling the alarm state of the target sensor.

[0009] The present application also provides an alarm processing device, comprising:

[0010] a first obtaining module configured to obtain current attribute information and current state information of a target sensor;

[0011] a second obtaining module configured to, in a case where the current state information is an alarm state, obtain a pre-constructed configuration file, wherein the configuration file comprises an alarm filtering rule of the target sensor;

[0012] a filtering module configured to, in a case where the current attribute information meets the alarm filtering rule, cancel the alarm state of the target sensor.

[0013] The application further provides an alarm processing system, comprising an alarm processing module, an alarm filtering module and a fault updating module, wherein:

[0014] The alarm processing module is configured to acquire current attribute information and current state information of the target sensor.

[0015] The alarm filtering module is configured to receive the current attribute information and the current state information transmitted by the alarm processing module, acquire a pre-constructed configuration file in the case that the current state information is an alarm state, wherein the configuration file comprises alarm filtering rules of the target sensor, and determine whether the current attribute information meets the alarm filtering rules, and in the case that the current attribute information meets the alarm filtering rules, release the alarm state of the target sensor.

[0016] The fault updating module is configured to receive an alarm processing result fed back by the alarm filtering module, and update a fault log of the target sensor based on the alarm processing result.

[0017] The application further provides an electronic device, comprising a memory configured to store a computer program, and a processor configured to execute the computer program to implement the steps of any of the alarm processing methods.

[0018] The application further provides a computer readable storage medium, wherein the computer readable storage medium stores a computer program, and the computer program is executed by a processor to implement the steps of any of the alarm processing methods.

[0019] The application further provides a computer program product, comprising a computer program, and the computer program is executed by a processor to implement the steps of any of the alarm processing methods.

[0020] According to the application, after receiving current attribute information set by a sensor alarm, a configuration file dynamically configured with alarm filtering rules according to actual requirements is acquired, it is determined whether the current attribute information meets the alarm filtering rules, and in the case that the current attribute information meets the alarm filtering rules, the alarm of the sensor is released, thus, the application solves the problem of accumulation of redundant alarm logs caused by the failure to filter alarms, alarm filtering is performed through flexible and configurable alarm filtering rules, and the technical effects of reducing the accumulation of redundant logs and improving log management efficiency are achieved. BRIEF DESCRIPTION OF DRAWINGS

[0021] In order to more clearly illustrate the embodiments of the application, the drawings required in the embodiments will be briefly introduced. Obviously, the drawings in the following description are only some embodiments of the application, and other drawings can be obtained by those skilled in the art without creative labor.

[0022] Figure 1A flowchart of an alarm processing method provided by an embodiment of the present application is shown in FIG. 1.

[0023] Figure 2 A sensor state code and event description diagram provided by an embodiment of the present application is shown in FIG. 2.

[0024] Figure 3 An alarm processing and event description diagram provided by an embodiment of the present application is shown in FIG. 3.

[0025] Figure 4 A flowchart of an alarm processing method provided by an embodiment of the present application is shown in FIG. 1.

[0026] Figure 5 A flowchart of an alarm processing device provided by an embodiment of the present application is shown in FIG. 4.

[0027] Figure 6 A structure diagram of an alarm processing system provided by an embodiment of the present application is shown in FIG. 5. DETAILED DESCRIPTION

[0028] The technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present application, but not all the embodiments of the present application. Based on the embodiments in the present application, any other embodiments obtained by those skilled in the art without creative work fall within the protection scope of the present application.

[0029] It should be noted that, in the description of the present application, the terms “include”, “contain” 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 explicitly listed or inherent to such process, method, article or device. The terms “first”, “second” and the like in the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence.

[0030] In order for those skilled in the art to better understand the present application, the present application will be further described in detail below with reference to the drawings and specific embodiments.

[0031] In combination with the specific application environment architecture or specific hardware architecture on which the alarm processing method is executed, the specific application environment architecture or specific hardware architecture is described here.

[0032] With the rapid development of information technology such as cloud computing and big data, the scale and complexity of data centers, as the key infrastructure supporting modern information society, continue to expand. To ensure the stable operation of data centers, the hardware health status monitoring of server nodes becomes particularly important. In this context, BMC (Baseboard Management Controller) as the core out-of-band management unit of the server bears the important responsibility of remote monitoring and management of hardware resources.

[0033] BMC collects various types of hardware status information through sensors and generates alarm logs based on the set threshold or state change, which is used to timely discover potential faults and assist in operation and maintenance decisions. Among them, sensors are mainly divided into threshold type sensors and discrete type sensors. Threshold type sensors are used to monitor continuous changing physical quantities such as temperature, voltage, current, and power. Discrete type sensors reflect the existence or non-existence of a device or whether a specific event has occurred in the form of binary or status code, such as power on state, fan speed anomaly, AC input loss, etc.

[0034] However, in actual application, it is found that during the startup and normal operation of BMC, some sensor alarms belong to the normal behavior of the system initialization stage, such as the on-site state alarm of memory and fan. At the same time, although some threshold type alarms exceed the preset range, they do not affect the overall performance of the server, and users do not want to record them in the alarm log, nor do they want such alarms to affect the overall health status evaluation of the server. Due to the lack of effective dynamic alarm filtering mechanism in the existing BMC, all sensor alarms are uniformly processed and recorded in the system event log (SEL), resulting in a large amount of redundant logs. Such redundant logs not only waste storage space, but also increase the difficulty of log analysis and troubleshooting, reducing the operation and maintenance efficiency. Especially in large-scale data center environment, this problem is particularly prominent, which seriously restricts the further development of intelligent operation and maintenance system.

[0035] In the current BMC-based server hardware monitoring system, there are several key defects in the sensor alarm mechanism, which affect the flexibility, maintainability and intelligent management level of the system.

[0036] Firstly, threshold type sensors rely on fixed thresholds to determine alarm status, lacking dynamic adaptability. For example, although the outlet temperature exceeds the preset CriticalHigh threshold, users believe that this abnormal value does not affect the overall performance of the server, and do not want to record it as an effective alarm. However, the existing system cannot dynamically adjust the filtering strategy according to the actual running environment or user demand, and can only avoid the problem by modifying the original threshold, which will destroy the original sensor logic rules and does not meet the requirements of engineering practice.

[0037] Secondly, the discrete sensor has a rigid processing mode for the Offset in the EventData (state code), which is difficult to meet the flexible filtering requirements. For example, the PSU (Power Supply Unit) bit event is a normal initialization behavior in the BMC startup stage, but the system still generates redundant log records. The existing scheme only supports shielding the alarm information corresponding to a specific Offset by manually modifying the json file, lacks an application layer interface for configuration management, and the modified content cannot be persisted.

[0038] Further, the static alarm filtering rules seriously restrict the flexibility of the system. Whether it is a threshold type or a discrete type sensor, the alarm rules are fixed in the system in a static way, and specific alarm items cannot be enabled or disabled on demand at runtime. If a user needs to change the sensor behavior, they can only modify the underlying file, which lacks a unified and standardized application layer control interface, reducing the efficiency and automation level of operation and maintenance.

[0039] Finally, the related art lacks a perfect persistence storage and recovery mechanism. When a user modifies the json file through the BMC console to achieve alarm filtering, since the path of the json file is located in the system read-only file system, it will be erased and reset to the default configuration when performing BMC recovery factory settings or firmware upgrade operations, resulting in the loss of user-defined sensor alarm rules, the system state is restored to the initial state, which seriously affects the configuration consistency and long-term availability.

[0040] In summary, the existing BMC sensor alarm mechanism has obvious deficiencies in flexibility, configurability, and persistence, which makes it difficult to meet the needs of modern data centers for fine and intelligent hardware management.

[0041] To solve the above technical problems, the present application provides a dynamic alarm processing method, which provides a flexible and configurable alarm filtering mechanism, which can effectively shield unnecessary alarms, reduce redundant logs, improve log quality and system management efficiency, and realize persistent storage of configuration files without affecting the reporting of key alarms.

[0042] Before the present application is described in detail, the technical terms involved are explained first.

[0043] The Baseboard Management Controller (BMC) is a special microcontroller embedded on the server motherboard, used for remote monitoring and management of the hardware status of the server.

[0044] The System Event Log (SEL) is an important component in the BMC that records the server hardware status and events, mainly collecting and storing data and alarm information from various sensors through the IPMI protocol.

[0045] The Intelligent Platform Management Interface (IPMI) is a standardized hardware management interface protocol used to monitor and manage the hardware status of servers, allowing remote monitoring, alarm recording, power control, and other operations through out-of-band methods even if the operating system crashes or the system shuts down.

[0046] The Desktop Bus (D-Bus) is an inter-process communication mechanism in Linux systems, used to efficiently and securely transfer messages between different applications or services.

[0047] Redfish is an open standard hardware management interface specification developed by DMTF, aiming to provide a unified, secure, and scalable way to remotely manage IT infrastructure such as servers, storage devices, and network devices.

[0048] The Distributed Management Task Force (DMTF) is a global industry organization dedicated to promoting the standardization of IT system management.

[0049] The Power Supply Unit (PSU) is an important component in electronic equipment, mainly used to convert input alternating current (AC) into stable direct current (DC) for use by various components within the device.

[0050] The Intelligent Platform Management Interface (IPMI) is an open standard hardware management interface specification, commonly used in servers and workstations.

[0051] Embodiments of the present application provide an alarm processing method, which is described in detail in combination with the execution process of the alarm processing method.

[0052] Figure 1 A flowchart of an alarm processing method provided by embodiments of the present application is shown in detail, which specifically includes the following steps as shown in Figure 1 .

[0053] S101, obtain the current attribute information and current state information of the target sensor.

[0054] The current attribute information is used to represent the current alarm state of the target sensor.

[0055] It can be understood that the current state information reflects whether the target sensor currently triggers an alarm condition to cause it to be in an alarm state, that is, whether the sensor is in an alarm state. The current attribute information is the current configuration or characteristic information of the target sensor. The current attribute information includes sensor-related basic information, attribute name, attribute type, and attribute value, and the like. The basic information includes bus name, object path, and interface name, and the like. The current attribute information can be understood as information stored on the Dbus. The fault states of all sensors are updated to the Dbus in real time. The core of the Dbus is to realize cross-process communication through bus message routing and standardized interfaces. Therefore, the basic information includes bus name, object path, and interface name, and the like. In addition, the alarm attribute information such as attribute name, attribute type, and attribute value in the current attribute information represents the current alarm state of the target sensor. That is, based on the current state information, it is determined whether the sensor is in an alarm state. Based on the current attribute information, it is determined the type of alarm state in which the sensor is currently in, for example, the current alarm state is a temperature too high alarm, a power in place alarm, or a power failure alarm, and the like.

[0056] Optionally, the current attribute information of the target sensor is obtained, including:

[0057] In the case where the target sensor is a threshold type sensor, an interface signal of the target sensor is received; the interface signal is compared with a safety threshold value of the target sensor which is pre-configured statically, wherein the safety threshold value has a corresponding alarm state identifier; in the case where a current value in the interface signal is inconsistent with the safety threshold value, an alarm is triggered, and the current attribute information is set based on the alarm state identifier.

[0058] It can be understood that the threshold sensor is a sensor for monitoring a physical quantity (such as temperature, voltage, current, etc.), and the acquisition process of the current attribute information of the threshold sensor is as follows: all values of the threshold sensor are collected in real time by listening to the PropertiesChanged signal of the DBus to obtain an interface signal, wherein the PropertiesChanged signal is a standard signal in the D-Bus, and is used to notify a listener that the attribute value of an object has changed, that is, the interface signal includes an actual value that can reflect the current alarm state of the sensor. Then, the actual value in the interface signal is compared with a safety threshold to obtain a comparison result, wherein the safety threshold is a normal value or a limit value that is statically configured in advance based on a threshold rule, for example, the normal temperature of the air outlet is 38 degrees, and the CriticalHigh (severe limit high) is 65 degrees, if the current air outlet temperature has an abnormal value of 70 degrees (actual value), 65 degrees is set as the safety threshold, and the actual value 70 is greater than the safety threshold 65, at this time, the CriticalHigh alarm is triggered, the comparison result is that the actual value is greater than the safety threshold, that is, the actual value and the safety threshold are inconsistent, and the CriticalHigh refers to an alarm state identifier. Then, the current attribute information is set based on the alarm state identifier, for example, the attribute name can be directly set as CriticalHigh, or set as CriticalHigh corresponding to CriticalAlarmHigh, and the attribute value of CriticalAlarmHigh is set as true, indicating that the alarm is to be generated. Subsequently, according to the attribute value of CriticalAlarmHigh in the current attribute information, it can be determined that the sensor is in a severe alarm state, that is, the current alarm state is a severe alarm state.

[0059] In an embodiment, the severe high threshold (CriticalHigh) of the air outlet temperature corresponds to the attribute name (CriticalAlarmHigh) of the severe alarm state, when the actual value is greater than the severe threshold (that is, the safety threshold), the alarm module will actively update the attribute value of CriticalAlarmHigh in the DBus from false to true, that is, the alarm is generated. On the contrary, if the actual value is less than the severe threshold, the alarm module will actively update the attribute value of CriticalAlarmHigh in the DBus from true to false, that is, the alarm is removed.

[0060] Optionally, the current attribute information of the target sensor is acquired, including:

[0061] In the case that the target sensor is a discrete sensor, the state change information after the discrete sensor generates an alarm is read; and the current attribute information is set based on the state change information.

[0062] It can be understood that the discrete sensor is divided into Host end sensor and BMC end sensor, wherein the Host end sensor is the change information passively received by the monitoring module, and can also be understood as the Host end sensor passively received by the monitoring module, held and updated by the monitoring module, and the Host end updates the EventData attribute of the monitoring module through the IPMI protocol. The BMC end sensor is divided into the BMC end sensor maintained by the monitoring module and the BMC end sensor listened to by the monitoring module, wherein the BMC end sensor maintained by the monitoring module is held by the monitoring module, and other processes are responsible for updating the EventData attribute thereof. The BMC end sensor listened to by the monitoring module is held and updated by other processes, and the attribute information of the sensor includes EventData. It can be understood that the discrete sensor maintains the Event Data and alarm description information / alarm state information of all discrete sensors by loading the / usr / share / sel-config.json file.

[0063] It can be understood that the acquisition process of the current attribute information of the discrete BMC-side sensor is as follows: the hardware state change (such as the PSU on-state) is monitored. Specifically, the object path of the discrete BMC-side sensor is created and managed by the monitoring module, for example, / com / otrd / system / chassis / motherboard / PSU0_Status (the storage path of the state information of the power supply unit 0), the PSU monitoring process reads the high and low states of the GPIO (General Purpose Input / Output) of PSU0 at regular intervals, if the GPIO changes, the EventData is updated synchronously through the Sensor.Status interface, and the alarm processing module is notified to update the EventData. Wherein, the EventData is a 16-bit unsigned integer (uint16), each bit (bit) corresponds to the offset of the SEL log (Offset), for example, the PSU off-state (power off) event is mapped to Offset1, corresponding to the binary bit 0000 0000 0000 0001. The object path of the monitored BMC-side sensor is created and managed by other processes, and the monitoring module is responsible for listening to whether the EventData of Sensor.Status under the sensor object path changes. For example, / com / otrd / state / PSU0_Redundant (power redundancy), PSU0 refers to the power supply unit 0, and the PSU monitoring process reads the on-state and running state of all power supplies on the server at regular intervals. If all on-state changes or power loss failures occur, the EventData of PSU0_Redundant is updated synchronously, and the monitoring module receives the state change information and notifies the alarm processing module to update the EventData.

[0064] It can be understood that the acquisition process of the current attribute information of the discrete Host-side sensor is as follows: the fault code sent by the operating system through the IPMI protocol is received, and then the Notify method of the Dbus is called to pass the fault event to the alarm processing module for subsequent processing. Specifically, the passive received Host-side sensor is created and managed by the monitoring module, and the operating system sends the sensor fault to the ipmid process through the IPMI protocol, and the ipmid process calls the Notify method of the monitoring module after preliminary parsing of the EventData attribute, and updates the EventData of Sensor.Status after parsing the event data1, event data2 and event data3 of the sensor alarm.

[0065] For example, see Figure 2 , Figure 2A sensor state code and event description schematic diagram provided for an embodiment of the present application, Figure 2 EventData in the above formula is 0000 0000 0000 0000, bit0 represents the 0th bit, Offset represents the attribute value of the 0th bit, Offset=0 represents DeAssert, and if Offset=1, it represents Assert.

[0066] S102, in the case that the current state information is the alarm state, a pre-constructed configuration file is acquired.

[0067] The configuration file includes an alarm filtering rule of the target sensor.

[0068] It can be understood that, on the basis of S101, in the case that the current state information is the alarm state, that is, the target sensor is in the alarm state at this time, a configuration file pre-configured according to the alarm filtering demand of a user is acquired, the configuration file includes an alarm filtering rule of at least one sensor, the at least one sensor includes the target sensor, and the alarm filtering rule is used to determine whether to shield, release or ignore the alarm state. The configuration file is recorded as an update-mask file.

[0069] Optionally, before the pre-constructed configuration file is acquired, the method further includes:

[0070] acquiring an alarm filtering demand of a user about the at least one sensor, wherein the alarm filtering demand is used to represent that the at least one sensor does not perform alarm processing when in a preset alarm state; determining a preset character identifier corresponding to the at least one sensor in the preset alarm state; setting a preset attribute identifier, wherein the preset attribute identifier is used to represent the preset alarm state of the at least one sensor; establishing a mapping relationship between the preset attribute identifier and the preset character identifier for the at least one sensor, to obtain preset attribute information, wherein the configuration file includes the preset attribute information.

[0071] It can be understood that the configuration file is constructed as follows: obtaining the alarm filtering requirements of the user for different types of sensors, wherein the alarm filtering requirements represent that a specific sensor does not alarm in a specific alarm state, and the specific alarm state is a preset alarm state, for example, the alarm filtering requirements are to filter out the transient temperature fluctuations of sensor a in a short period of time (such as a temporary temperature rise caused by load change), that is, the temperature rise of sensor a in a short period of time does not alarm, and for example, during system startup or power switching, the voltage alarm of sensor b is automatically shielded, that is, the voltage rise of sensor b does not alarm during system startup or power switching. Subsequently, the preset character identifier corresponding to the specific alarm state when at least one sensor involved in the alarm filtering requirements is in the specific alarm state is determined, and the preset character identifier is an object path, which can be understood as a string, for example, " / com / otrd / system / chassis / motherboard / PSU0_Status", the storage path of the status information of the power supply unit 0, and the object paths corresponding to different sensors are different. A preset attribute identifier capable of representing that a specific sensor is in a specific alarm state is set, and the preset attribute identifier has a plurality of attribute values, the plurality of attribute values including a first type of attribute value indicating that the alarm is cancelled and a second type of attribute value indicating the preset alarm state, for example, the first type of attribute value of sensor a in the CriticalAlarmHigh alarm state is set to false, indicating that the temperature rise alarm is cancelled, and correspondingly, the second type of attribute value is set to true, indicating that sensor a is in CriticalAlarmHigh, CriticalAlarmHigh is also a preset alarm state, or, the attribute value of CriticalAlarmHigh can also be set to a specific numerical value, for example, the first type of attribute value is set to 0, indicating that the temperature rise alarm is cancelled, and correspondingly, the second type of attribute value is set to 1, indicating that sensor a is in CriticalAlarmHigh, and the specific setting method is not limited. Subsequently, a mapping relationship between the preset attribute identifier and the preset character identifier is established to obtain preset attribute information, and the preset attribute information of a plurality of sensors constitutes the configuration file, that is, a mapping relationship between the attribute value and the object path is established, for example, a mapping relationship between " / com / otrd / system / chassis / motherboard / PSU0_Status" and Offset is established.

[0072] It can be understood that the BMC loads the / var / lib / update-mask file into the memory when starting, constructs a hash mapping table of the sensor object path and the Offset mask, and realizes the retrieval of the nanosecond-level alarm filtering rule. For example, if a user needs to filter the in-place alarm status code of the PSU, the Offset corresponding to the PSU0_Status (such as Offset = 1) can be written into the configuration file through the doPatch method of Redfish, the system updates the configuration file in the memory in real time, and the data consistency in the multi-threaded environment is guaranteed through atomic operation. When the in-place alarm of PSU0_Status occurs again, whether the current Offset matches the alarm filtering rule is determined according to the sensor object path, that is, whether the Offset in the configuration file and the Offset in the current attribute information are consistent. If the Offset is 1, it means that the alarm states represented by the two are the same, and the alarm state has been marked as filterable. In fact, the alarm state recorded in the configuration file is ignorable / filterable. In this case, the Offset in the EventData is ignored and is modified to 0. Offset = 1 represents alarm, and Offset = 0 represents no alarm. The alarm can trigger SEL recording and fault lamp prompting operations. It can be understood that the Offset = 1 (1 is the second attribute value) recorded in the current attribute information also indicates that the target sensor is in an alarm state. The updated current attribute information has Offset = 0 (0 is the first attribute value), and the attribute information indicates no alarm, so the alarm state is filtered out.

[0073] Optionally, a mapping relationship between the preset attribute identifier and the preset character identifier is established to obtain preset attribute information. After the configuration file includes the preset attribute information, the method further includes:

[0074] The configuration file is stored in the non-volatile storage medium in a binary storage mode; and when the firmware upgrade and / or factory reset processing is performed, the configuration file is not processed.

[0075] It can be understood that the configuration file is encoded into a compact key-value structure, that is, a preset character identifier-attribute value structure or an object path-attribute value structure, using the binary storage format of the Cereal serialization library, and the data is efficiently stored in binary form through the serialization mechanism, avoiding redundant characters and structured tags, significantly improving read-write performance and saving storage space. Among them, the Key refers to the object path of the sensor, that is, the preset character identifier, and the object path is used to uniquely identify the sensor object, and the Value refers to the Offset mask, that is, the attribute value, for example, "key": " / com / otrd / system / chassis / motherboard / PSU0_Status", "value": 1 (0000 0000 00000001), wherein "0000 0000 0000 0001" is a binary bit EventData attribute. This storage method can reduce data storage and reading resource consumption, improve processing speed, enhance data security, and improve data center operation efficiency.

[0076] It can be understood that the modified sensor alarm code is stored in the configuration file. If the actual requirement of the user is that the BMC does not reset all modified sensor alarm status codes to the state before factory setting when performing factory setting recovery or firmware upgrade, but needs to persist the updated sensor alarm status code, in this case, the application proposes a persistence mechanism. Specifically, when the BMC performs factory setting recovery or firmware upgrade, the Flash is dynamically erased and the rw partition content is used to remount the file system, so before erasing, the configuration file can be temporarily stored in / tmp or other directories, and after the file system is mounted, the configuration file can be restored.

[0077] It can be understood that the configuration file can be created under the / var / lib directory, and the configuration file can be added to the whitelist to ensure that the file is persisted and retained during firmware upgrade and factory setting recovery. When the BMC abnormally restarts, the configuration file can be quickly loaded to avoid repeated configuration. After the configuration file is stored in the Binary storage format of Cereal, the configuration file is encrypted by a high-strength encryption algorithm. Compared with the json file involved in the related art, the Binary format configuration file effectively reduces the storage space occupied by redundant characters, significantly improves the key cracking complexity, has stronger anti-force cracking and password analysis capability, and comprehensively guarantees the safety and confidentiality of data in the whole life cycle, providing reliable protection for the storage and transmission of sensitive information in the data center.

[0078] S103, in the case of the current attribute information meeting the alarm filtering rule, cancel the alarm state of the target sensor.

[0079] It can be understood that, on the basis of S102, if the current attribute information meets the alarm filtering rule, the alarm state of the target sensor is automatically canceled, that is, the fault does not need to be alarmed, the alarm filtering is completed, and invalid alarm reporting and log recording are avoided.

[0080] Optionally, in the case of the current attribute information meeting the alarm filtering rule, the alarm state of the target sensor is canceled, which can be realized by the following steps:

[0081] In the process of processing the current attribute information, the next attribute information of the target sensor is obtained, wherein the next attribute information is used to represent the next alarm state of the target sensor, the next alarm state is different from the current alarm state represented by the current attribute information; the target attribute information is calculated according to the current attribute information and the next attribute information, wherein the target attribute information is used to represent the next alarm state and / or the current alarm state represented by the current attribute information; in the case that the target attribute information meets the alarm filtering rule, the next alarm state of the target sensor and / or the current alarm state represented by the current attribute information is canceled.

[0082] It can be understood that in the process of alarm filtering of the current attribute information, if the next attribute information of the target sensor is obtained, that is, the target sensor generates two alarms at this time, wherein the next attribute information represents the next alarm state of the target sensor. In one possible case, the next alarm state is different from the current alarm state, for example, the next alarm state is a power failure alarm, and the current alarm state is a power on alarm. The power failure alarm and the power on alarm belong to different alarm types. In another possible case, the next alarm state is the same as the current alarm state, which is a repeated alarm, for example, both alarms are power failure alarms. In this case, the target attribute information is obtained by calculating the current attribute information and the next attribute information. The target attribute information represents the next alarm state and / or the current alarm state represented by the current attribute information. For example, if it is a repeated alarm, the attribute value or alarm state code of one alarm state is retained in the target attribute information. If it is two alarms, the alarm state codes of the next alarm state and the current alarm state are retained in the target attribute information. Subsequently, it is judged whether the target attribute information meets the alarm filtering rule. In the case that the alarm state codes of the next alarm state and the current alarm state are retained in the target attribute information, that is, in the case of two alarms, it is determined whether the next alarm state and / or the current alarm state represented by the current attribute information is filterable according to whether the next alarm state is recorded in the configuration file. That is, in the case of multiple alarms, the specific alarm state meeting the alarm filtering rule is removed, and other alarms except the specific alarm state in the multiple alarms are generated.

[0083] For example, referring to Figure 3 , Figure 3 An alarm processing and event description schematic diagram provided by the embodiment of the application, Figure 3 The initial state of the EventData in the embodiment is 0000 0000 0000 0000. By default, PSU0 is on, a Presencedetected alarm is generated, that is, a power on alarm is generated. The current alarm state is the power on alarm, that is Figure 3Offset1 in the current attribute information produces an alarm, and EventData1 (the identification code in the current attribute information) is 0000 0000 0000 0001. At this time, a power failure alarm is detected, and Offset2 produces an alarm, and EventData2 (the identification code in the next attribute information) is 0000 0000 0000 0010. The identification code of the target attribute information calculated according to the current attribute information and the next attribute information is 0000 0000 0000 0011. In this case, it is determined whether the target attribute information meets the alarm filtering rule. If the power presence alarm is filtered out by the alarm filtering rule, and the power failure alarm is not filtered out, the updated EventData is 0000 0000 0000 0010, that is, Offset1 is de-asserted (Presence detected-DeAsserted), and Offset2 triggers an alarm (Failure detected-Asserted).

[0084] Optionally, the method further comprises:

[0085] obtaining adjustment information of the alarm filtering rule; and updating the configuration file based on the adjustment information.

[0086] Understandably, the adjustment information (such as adding, modifying or deleting a filtering item) of the alarm filtering rule of the user or the system is obtained. Subsequently, the corresponding configuration file is updated according to the adjustment information, so as to keep the latest state of the alarm filtering rule.

[0087] The alarm processing method provided in the application supports the user to dynamically modify the configuration file to realize secondary filtering of the threshold type sensor alarm, and does not need to modify the original threshold. The false alarm problem of the fixed threshold in the related art which is prone to occur when the scene is switched is solved. In addition, the user can also adjust the alarm filtering rule at any time according to the actual demand, without the need to modify the system bottom rule, thereby effectively reducing the false alarm rate of the key component sensor in the over-limit scene. At the same time, for the discrete sensor alarms of multiple sources of the BMC end and the Host end, the cross-protocol alarm filtering is realized through the unified state code identification (such as the mapping relationship between the object path and the attribute value recorded in the attribute information), thereby significantly improving the accuracy of the alarm classification. Further, the operation and maintenance personnel do not need to frequently adjust the firmware configuration or manually intervene the alarm strategy, thereby reducing the maintenance cost, enhancing the autonomy and convenience of data management, and further widening the application range of the BMC system. In addition, in the firmware upgrading process, the alarm filtering rule also does not need to be re-adapted, thereby reducing the frequency of manual intervention and guaranteeing the continuity of the server management.

[0088] On the basis of the above-mentioned embodiments, refer to Figure 4 , Figure 4A flowchart of an alarm processing method provided by an embodiment of the present application is shown. Optionally, in the case that the current attribute information meets the alarm filtering rule, the alarm state of the target sensor is released, and the method includes the following steps as shown in Figure 4

[0089] S401, compare the current attribute information with preset attribute information.

[0090] It can be understood that the current attribute information and the preset attribute information are compared, specifically, the object path and the attribute value representing the alarm state are compared to generate a comparison result, and the comparison result includes whether the object path and / or the attribute value are consistent.

[0091] In one embodiment, the storage mode of the high threshold alarm of the outlet temperature (Outlet_Temp) of the discrete sensor on the DBus is as follows:

[0092] Bus name: com.otrd.HwmonTempSensor

[0093] Object path: / com / otrd / sensors / temperature / Outlet_Temp

[0094] Interface name: com.otrd.Sensor.Threshold.Critical

[0095] Attribute name: CriticalAlarmHigh

[0096] Attribute type: bool

[0097] Attribute value: true

[0098] In another embodiment, the storage mode of the in-place alarm of the power supply state (PSU0_Status) of the discrete sensor on the DBus is as follows:

[0099] Bus name: com.otrd.Sensor.Monitor

[0100] Object path: / com / otrd / sensors / chassis / motherboard / PSU0_Status

[0101] Interface name: com.otrd.Sensor.Status

[0102] Attribute name: EventData

[0103] Attribute type: map<uint8,map<uint8, vector <uint8>>>

[0104] Attribute Value: 0

[0105] The obtained attribute information of the sensor can be the storage manner of different alarm states on the DBus. The attribute information represents a specific alarm state, i.e., an actual alarm state, such as the power in-place alarm and the temperature high threshold alarm.

[0106] It can be understood that the object path and the attribute value are recorded in the preset attribute information and the current attribute information, and therefore, whether the object path and the attribute value are consistent can be compared.

[0107] S402, if the character identifier recorded in the current attribute information and the preset attribute information is consistent, and the current alarm state and the preset alarm state are consistent, the current attribute information is updated to release the alarm state of the target sensor.

[0108] It can be understood that, on the basis of S401, if the character identifier recorded in the current attribute information and the preset attribute information is consistent (i.e., the object path is consistent), and the current alarm state and the preset alarm state are consistent (i.e., the same alarm event is targeted), or the character identifier is consistent and the current attribute value in the current attribute information and the preset attribute value in the preset attribute information are consistent (i.e., the offset is the same, both are 1 or both are true), it is confirmed that the alarm state can be released, the alarm event does not need to be alarmed, and the current attribute information is updated to release the alarm state of the target sensor.

[0109] Optionally, the current attribute information is updated, which can be achieved through the following steps:

[0110] A first attribute value representing release of the alarm corresponding to the preset attribute identifier is determined, and a second attribute value corresponding to the current attribute identifier set for the current alarm state in the current attribute information is updated to the first attribute value, wherein the second attribute value represents generation of the alarm, and the first attribute value and the second attribute value are different.

[0111] It can be understood that the preset attribute identifier is used to identify that the alarm state can be ignored, and the preset attribute identifier can also be understood as a cancel alarm identifier, and specifically corresponds to a plurality of attribute values, for example, a first attribute value is set as a, indicating canceling the alarm, and a second attribute value is set as b, indicating generating the alarm. The current attribute information is generated when the target sensor is in the alarm state, and therefore, the current attribute identifier in the current attribute information represents generating the alarm, for example, the attribute value corresponding to the current attribute identifier is the second attribute value b. If the current alarm state can be filtered, the attribute value corresponding to the current attribute identifier is changed from b to a, that is, the alarm is canceled. In the embodiment of the severe alarm state of the air outlet temperature, false can be understood as the first attribute value of canceling the alarm, and true can be understood as the second attribute value of triggering / generating the alarm.

[0112] Optionally, the current attribute information is updated, and the updating can be specifically implemented through the following steps:

[0113] In a case where the current attribute information is set based on the previous attribute information, the current attribute information is updated as the previous attribute information, wherein the previous attribute information is used to represent a previous alarm state of the target sensor, the previous alarm state is different from the current alarm state, and the previous alarm state does not conform to the alarm filtering rule.

[0114] It can be understood that, before the current attribute information is generated, the target sensor has generated the previous attribute information, and the current attribute information is generated based on the previous attribute information. In this case, the previous alarm state represented by the previous attribute information is maintained or retriggered, wherein the current alarm state is a filterable specific alarm state, and the previous alarm state is a non-filterable alarm state.

[0115] It can be understood that the EventData (identifier code in the previous attribute information) of the PSU0_Status alarm is 00000000 0000 0010, and the previous alarm state is the power failure alarm. If the power present alarm is generated in the PSU, the EventData (identifier code in the current attribute information) is 0000 0000 0000 0001, and the updated EventData (identifier code in the target attribute information) obtained by calculating the current attribute information and the previous attribute information is 0000 00000000 0011. However, since the power present alarm is marked as an ignored state in the configuration file, that is, the current alarm state is a filterable specific alarm state, and after the secondary filtering of the configuration file, the new EventData is still 0000 00000000 0010, and therefore, the power present alarm will not be generated, and the power failure alarm will be generated or maintained.

[0116] Optionally, after the alarm state of the target sensor is canceled, the method further comprises:

[0117] generating the alarm cancellation log according to the preset character identifier of the target sensor, the updated current attribute information, and / or the alarm level of the current alarm state.

[0118] Understandably, in the case of triggering the SEL log record and the corresponding hardware operation, the alarm state needs to be updated, the sensor object path, the EventData, and the alarm level are sorted into the SEL structure, and the corresponding SEL log entry is generated, for example, the alarm log or the alarm cancellation log, and the corresponding action is driven by the fault light according to the current alarm state, such as constant light, off, or flickering.

[0119] The alarm processing method provided in the application avoids modification of the original sensor configuration file (such as a json file) and the default threshold value through the created configuration file. When performing alarm filtering processing, the alarm filtering rule is automatically applied, and the alarm state marked as ignored is shielded, for example, the alarm state of the air outlet temperature temporarily exceeding the threshold value, the power module in place, and the like, so that the marked sensor fault state code can be ignored without restarting the BMC service or reloading the firmware.

[0120] 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 realized by means of software and the necessary general hardware platform, of course, it can also be realized by hardware, but in many cases the former is a better embodiment.

[0121] The embodiment of the application further provides an alarm processing device, and the alarm processing device 500 comprises a first acquisition module 501, a second acquisition module 502, and a filtering module 503, wherein:

[0122] The first acquisition module 501 is configured to acquire the current attribute information and the current state information of the target sensor.

[0123] The second acquisition module 502 is configured to acquire the pre-constructed configuration file in the case that the current state information is the alarm state, wherein the configuration file comprises the alarm filtering rule of the target sensor.

[0124] The filtering module 503 is configured to cancel the alarm state of the target sensor in the case that the current attribute information meets the alarm filtering rule.

[0125] Optionally, the alarm processing device 500 is further configured to:

[0126] acquire the alarm filtering demand of the user about at least one sensor, wherein the alarm filtering demand is used to represent that at least one sensor does not perform alarm processing when in a preset alarm state.

[0127] determining a preset character identifier corresponding to the preset alarm state of the at least one sensor when the at least one sensor is in the preset alarm state;

[0128] setting a preset attribute identifier, wherein the preset attribute identifier is used to represent the preset alarm state of the at least one sensor;

[0129] establishing a mapping relationship between the preset attribute identifier and the preset character identifier for the at least one sensor, to obtain preset attribute information, wherein the configuration file comprises the preset attribute information.

[0130] wherein the current attribute information is used to represent the current alarm state of the target sensor.

[0131] Optionally, the filtering module 503 is configured to:

[0132] compare the current attribute information with the preset attribute information;

[0133] if the character identifier recorded in the current attribute information and the preset attribute information is consistent, and the current alarm state and the preset alarm state are consistent, then update the current attribute information to cancel the alarm state of the target sensor.

[0134] Optionally, the filtering module 503 is configured to:

[0135] determining a preset attribute identifier set for the preset alarm state in the preset attribute information, wherein the preset attribute identifier is a first attribute value representing cancellation of the alarm;

[0136] determining a first attribute value corresponding to the preset attribute identifier representing cancellation of the alarm;

[0137] updating a second attribute value corresponding to a current attribute identifier set for the current alarm state in the current attribute information to the first attribute value, wherein the second attribute value represents generation of the alarm, and the first attribute value and the second attribute value are different.

[0138] Optionally, the filtering module 503 is configured to:

[0139] if the current attribute information is set based on previous attribute information, updating the current attribute information to the previous attribute information, wherein the previous attribute information is used to represent a previous alarm state of the target sensor, the previous alarm state and the current alarm state are different, and the previous alarm state does not meet the alarm filtering rule.

[0140] Optionally, the alarm processing apparatus 500 is further configured to:

[0141] generating a cancellation alarm log according to the preset character identifier of the target sensor, the updated current attribute information, and / or the alarm level of the current alarm state.

[0142] Optionally, the filtering module 503 is configured to:

[0143] In the process of processing the current attribute information, the next attribute information of the target sensor is acquired, wherein the next attribute information is used to represent the next alarm state of the target sensor, and the next alarm state is different from the current alarm state represented by the current attribute information;

[0144] According to the current attribute information and the next attribute information, the target attribute information is calculated, wherein the target attribute information is used to represent the next alarm state and / or the current alarm state represented by the current attribute information;

[0145] In the case that the target attribute information meets the alarm filtering rule, the next alarm state of the target sensor and / or the current alarm state represented by the current attribute information is removed.

[0146] Optionally, the filtering module 503 is configured to:

[0147] The configuration file is stored in the non-volatile storage medium in a binary storage mode;

[0148] When the firmware upgrade and / or factory reset processing is performed, the configuration file is not processed.

[0149] Optionally, the first acquisition module 501 is configured to:

[0150] In the case that the target sensor is a threshold type sensor, the interface signal of the target sensor is received;

[0151] The interface signal is compared with the safety threshold value pre-configured by the target sensor statically, wherein the safety threshold value has a corresponding alarm state identifier;

[0152] In the case that the current value in the interface signal is inconsistent with the safety threshold value, an alarm is triggered, and the current attribute information is set based on the alarm state identifier.

[0153] Optionally, the first acquisition module 501 is configured to:

[0154] In the case that the target sensor is a discrete type sensor, the state change information after the discrete type sensor generates an alarm is read;

[0155] The current attribute information is set based on the state change information.

[0156] Optionally, the alarm processing apparatus 500 is further configured to:

[0157] Acquire adjustment information for the alarm filtering rule;

[0158] Update the configuration file based on the adjustment information.

[0159] The features of the embodiments of the alarm processing device can be referred to the related descriptions of the embodiments of the alarm processing method, which will not be repeated here.

[0160] Figure 6 A structural schematic diagram of an alarm processing system provided by the embodiments of the present application is shown in FIG. 1. The alarm processing system comprises an alarm processing module, an alarm filtering module and a fault updating module.

[0161] The alarm processing module is configured to acquire the current attribute information and the current state information of the target sensor.

[0162] It can be understood that the current EventData and the previous EventData of the sensor are calculated to generate the latest EventData, and the fault generated by the sensor and the released fault are notified to the fault updating module.

[0163] The alarm filtering module is configured to receive the current attribute information and the current state information transmitted by the alarm processing module, acquire a pre-constructed configuration file in the case that the current state information is an alarm state, wherein the configuration file comprises an alarm filtering rule of the target sensor, and determine whether the current attribute information conforms to the alarm filtering rule, and release the alarm state of the target sensor in the case that the current attribute information conforms to the alarm filtering rule.

[0164] It can be understood that the alarm filtering module is a core middleware between the alarm processing module and the fault updating module, and is a dynamic rule engine and an alarm state arbitrator. The dynamic rule engine is configured to acquire the pre-constructed configuration file, and the alarm state arbitrator is configured to determine whether the current attribute information conforms to the alarm filtering rule, and release the alarm state of the target sensor in the case that the current attribute information conforms to the alarm filtering rule.

[0165] The fault updating module is configured to receive the alarm processing result fed back by the alarm filtering module, and update the fault log of the target sensor based on the alarm processing result.

[0166] It can be understood that the fault updating module is configured to determine whether the fault needs to trigger the SEL log recording and the hardware action through the result fed back by the previous alarm filtering module.

[0167] The alarm processing system further comprises a sensor monitoring module, and the sensor monitoring module is configured to monitor the value change of all sensors and update the alarm attribute value.

[0168] It can be understood that the specific implementation steps of the alarm processing system are described above, and will not be repeated here.

[0169] The embodiment of the present application further provides an electronic device, comprising a memory and a processor, the memory stores a computer program, and the processor is configured to run the computer program to perform the steps in any of the above alarm processing method embodiments.

[0170] The embodiment of the present application further provides a computer readable storage medium, which stores a computer program, wherein the computer program is configured to perform the steps in any of the above alarm processing method embodiments when running.

[0171] In an example embodiment, the above computer readable storage medium can include, but is not limited to, a U disk, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk, and various media that can store computer programs.

[0172] The embodiment of the present application further provides a computer program product, which comprises a computer program, and the computer program is executed by a processor to implement the steps in any of the above alarm processing method embodiments.

[0173] The embodiment of the present application further provides another computer program product, which comprises a non-volatile computer readable storage medium, and the non-volatile computer readable storage medium stores a computer program, and the computer program is executed by a processor to implement the steps in any of the above alarm processing method embodiments.

[0174] The skilled person can further realize that the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein can be realized by electronic hardware, computer software or a combination of both. In order to clearly illustrate the interchangeability of hardware and software, the components and steps of the examples have been described in general terms in the above description. Whether the functions are realized in hardware or software depends on the specific application and design constraints of the technical solution. The skilled person can use different methods to realize the described functions for each specific application, but such implementation should not be considered beyond the scope of the present application.

[0175] The above describes in detail the alarm processing provided by the present application. The principles and implementation manners of the present application are described by using specific examples, and the above example descriptions are only used to help understand the method and core idea of the present application. It should be pointed out that, for the person skilled in the art, without departing from the principles of the present application, the present application can be improved and modified in several ways, and these improvements and modifications also fall within the protection scope of the claims of the present application. ​

Claims

1. An alarm processing method, characterized in that: include: Acquire current attribute information and current state information of the target sensor, wherein the current attribute information is used to characterize the type of alarm state the target sensor is currently in; When the current state information is an alarm state, obtaining a pre-built configuration file, wherein the configuration file includes an alarm filtering rule of the target sensor, and the configuration file is used to represent a mapping relationship between an attribute value and an object path; If the current attribute information meets the alarm filtering rule, releasing the alarm state of the target sensor, including: comparing the current attribute information with preset attribute information included in the configuration file; if the object paths recorded in the current attribute information and the preset attribute information are consistent and are for the same alarm event, updating the current attribute information to release the alarm state of the target sensor; Wherein, updating the current attribute information includes: In a case where the target sensor is in a previous alarm state, updated attribute information is calculated based on the current attribute information and the previous attribute information, wherein the previous attribute information is used to represent the previous alarm state, the previous alarm state and the current alarm state represented by the current attribute information are different, and the previous alarm state does not comply with the alarm filtering rule; comparing the updated attribute information with the preset attribute information, and setting the updated attribute information to the previous attribute information to release the current alarm state and maintain the previous alarm state; Wherein, updating the current attribute information includes: The second attribute value corresponding to the current attribute identifier in the current attribute information is modified to the first attribute value corresponding to the preset attribute identifier in the preset attribute information, wherein the second attribute value indicates generating an alarm, the first attribute value indicates canceling the warning, and the first attribute value and the second attribute value are different.

2. The method according to claim 1, characterized in that Before obtaining the pre-built configuration file, the method further includes: Obtaining a user's alarm filtering requirement for at least one sensor, wherein the alarm filtering requirement is used to indicate that the at least one sensor does not perform alarm processing when in a preset alarm state; Determining a preset character identifier corresponding to when the at least one sensor is in the preset alarm state; Setting a preset attribute identifier, wherein the preset attribute identifier is used to represent a preset alarm state of the at least one sensor; For the at least one sensor, a mapping relationship between the preset attribute identifier and the preset character identifier is established to obtain preset attribute information.

3. The method according to claim 2, characterized in that The same alarm event refers to that the current alarm state is consistent with the preset alarm state.

4. The method according to claim 3, characterized in that The updating of the current attribute information includes: In a case where the current attribute information is set based on the previous attribute information, the current attribute information is updated to the previous attribute information, wherein the previous attribute information is used to characterize the previous alarm state of the target sensor, the previous alarm state is different from the current alarm state, and the previous alarm state does not comply with the alarm filtering rule.

5. The method according to claim 3, characterized in that After releasing the alarm state of the target sensor, the method further includes: An alarm cancellation log is generated according to the preset character identifier of the target sensor, the updated current attribute information and / or the alarm level of the current alarm state.

6. The method according to claim 1, characterized in that When the current attribute information meets the alarm filtering rule, releasing the alarm state of the target sensor includes: In the process of processing the current attribute information, next attribute information of the target sensor is obtained, wherein the next attribute information is used to represent a next alarm state of the target sensor; Calculating target attribute information according to the current attribute information and the next attribute information, wherein the target attribute information is used to characterize the next alarm state and / or the current alarm state; In a case where the target attribute information meets the alarm filtering rule, the next alarm state of the target sensor and / or the current alarm state represented by the current attribute information are released.

7. The method according to claim 2, characterized in that After establishing the mapping relationship between the preset attribute identifier and the preset character identifier to obtain the preset attribute information, the method further includes: Storing the configuration file in a non-volatile storage medium in a binary storage manner; When performing a firmware upgrade and / or restoring factory settings process, the configuration file is not processed.

8. The method according to claim 1, characterized in that Get the current attribute information of the target sensor, including: In the case where the target sensor is a threshold type sensor, receiving an interface signal of the target sensor; Comparing the interface signal with a pre-statically configured safety threshold of the target sensor, wherein the safety threshold has a corresponding alarm status indicator; When the current value in the interface signal is inconsistent with the safety threshold, an alarm is triggered, and current attribute information is set based on the alarm status identifier.

9. The method according to claim 1, characterized in that Get the current attribute information of the target sensor, including: In the case where the target sensor is a discrete sensor, reading state change information of the discrete sensor after an alarm is generated; Current attribute information is set based on the state change information.

10. The method according to claim 1, characterized in that The method further comprises: Obtaining adjustment information for the alarm filtering rule; The configuration file is updated based on the adjustment information.

11. An alarm processing system, characterized in that: The alarm processing system includes an alarm processing module, an alarm filtering module and a fault update module, wherein: The alarm processing module is used to obtain current attribute information and current state information of the target sensor, wherein the current attribute information is used to represent the type of alarm state the target sensor is currently in; The alarm filtering module is configured to receive the current attribute information and the current state information transmitted by the alarm processing module, and, if the current state information is an alarm state, obtain a pre-built configuration file, wherein the configuration file includes an alarm filtering rule for the target sensor, the configuration file is configured to characterize a mapping relationship between an attribute value and an object path, and determine whether the current attribute information complies with the alarm filtering rule. If the current attribute information complies with the alarm filtering rule, the alarm state of the target sensor is released; The fault updating module is used to receive the alarm processing result fed back by the alarm filtering module, and update the fault log of the target sensor based on the alarm processing result; The alarm filtering module is used to: Compare the current attribute information with the preset attribute information included in the configuration file; if the object path recorded in the current attribute information and the preset attribute information are consistent and are for the same alarm event, update the current attribute information to release the alarm state of the target sensor; wherein, updating the current attribute information includes: when the target sensor is in the previous alarm state, calculate the updated attribute information based on the current attribute information and the previous attribute information, wherein the previous attribute information is used to represent the previous alarm state, and the previous alarm state and the current attribute information represent the current alarm state. The alarm status is different, and the previous alarm status does not comply with the alarm filtering rules; compare the updated attribute information with the preset attribute information, set the updated attribute information to the previous attribute information to release the current alarm status and maintain the previous alarm status; wherein, updating the current attribute information includes: modifying the second attribute value corresponding to the current attribute identifier in the current attribute information to the first attribute value corresponding to the preset attribute identifier in the preset attribute information, wherein the second attribute value indicates that an alarm is generated, the first attribute value indicates that the warning is released, and the first attribute value and the second attribute value are different.

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

13. 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 processing method according to any one of claims 1 to 10.

14. 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 processing method according to any one of claims 1 to 10 are implemented.

Images