A sensor fault state monitoring method and monitoring device
By capturing and storing sensor event status in SEL logs, the problem that the prior art cannot display all sensor failure status is solved, and comprehensive monitoring and analysis of sensor failures is achieved.
Patent Information
- Application Number
- CN202211579210.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-12-06
- Publication Date
- 2024-11-19
- Estimated Expiration
- 2042-12-06
AI Technical Summary
The prior art cannot display the fault status of all sensors at the same time, making it difficult for operation and maintenance personnel to locate and analyze sensor failures.
By capturing the sensor event status and event type values in the SEL log, determining whether it matches the sensor category in the set specification, storing the current and historical sensor event status, ensuring that operation and maintenance personnel can view all the fault status of the sensor.
It realizes the storage of all fault status of the sensor, which facilitates operation and maintenance personnel to comprehensively analyze and locate faults, and solves the problem of sensor fault status monitoring coverage.
Smart Images

Figure CN116225825B_ABST
Abstract
Description
Technical Field
[0001] The embodiments of the present invention relate to the field of computer technology, and in particular to a sensor fault status monitoring method and monitoring device. Background Art
[0002] The Baseboard Management Controller (BMC) is the basic core functional subsystem of the server, responsible for the server's hardware status management, operating system management, health status management, power consumption management and other core functions. BMC monitors many sensors and needs to report the event status of these sensors to the background in real time. At the same time, if a failure occurs, an alarm needs to be issued immediately.
[0003] Current technology can only monitor the current event status of all sensors. Historical sensor fault status will be overwritten, and all fault status of all sensors cannot be displayed at the same time, which is not conducive to operation and maintenance personnel to locate and analyze sensor faults. Summary of the invention
[0004] The present invention provides a sensor fault status monitoring method and a monitoring device, which can store all fault states of all sensors, making it convenient for subsequent operation and maintenance personnel to locate and analyze sensor faults.
[0005] In the first aspect, an embodiment of the present invention provides a sensor fault status monitoring method, including: capturing an SEL log, the SEL log records the current sensor event status and the event type value of the current sensor event; judging whether the event type value of the current sensor event matches the event type of the corresponding sensor category in the set specification. By judging whether the event type value of the current sensor event matches the event type of the corresponding sensor category in the set specification, event types that do not belong to the set specification can be removed, and event types that do not need to be judged can also be removed. By storing the current sensor event status and the historical sensor event status, all fault states of the sensor can be displayed, which is convenient for operation and maintenance personnel to comprehensively analyze and locate sensor faults.
[0006] Optionally, the SEL log also records the sensor type; before determining whether the current event type value of the sensor event matches the event type of the corresponding sensor category in the set specification, it also includes: parsing the event type value and sensor type of the current sensor event in the SEL log; determining the sensor category according to the sensor type; determining whether the sensor category belongs to the set sensor category; if so, continuing to determine whether the event type value of the current sensor event matches the event type of the corresponding sensor category in the set specification. By determining whether the sensor category belongs to the set sensor category, sensor events that do not need to be determined can be removed.
[0007] Optionally, setting sensor categories includes threshold sensors, discrete sensors and universal sensors; judging whether the sensor category belongs to the set sensor category, including: when the sensor category is any one of the threshold sensor, discrete sensor and universal sensor, determining that the sensor category belongs to the set sensor category; judging whether the event type value of the current sensor event matches the event type within a set range of the corresponding sensor category in the setting specification, including: when the event type value of the current sensor event matches any event type of the corresponding sensor category in the setting specification, determining that the event type value of the current sensor event matches the event type within a set range of the corresponding sensor category in the setting specification.
[0008] Optionally, the SEL log also records a current sensor event data group, the current sensor event data group includes first event data, the first event data includes an event type value of the current sensor event; wherein, before determining whether the event type value of the current sensor event matches the event type of the corresponding sensor category in the set specification, it also includes: obtaining the event type value of the current sensor event from the first event data.
[0009] Optionally, for a threshold sensor and a universal sensor, the event type value of the current sensor event includes a first offset parameter; for a discrete sensor, the event type value of the current sensor event includes a first offset parameter and / or a second offset parameter.
[0010] Optionally, for discrete sensors and universal sensors, the current sensor event data group also includes second event data, and the second event data includes a sensor serial number; if the sensor category belongs to a discrete sensor and a universal sensor, after obtaining the event type value of the current sensor event from the first event data, it also includes: obtaining the sensor serial number from the second event data.
[0011] Optionally, storing the current sensor event state in a corresponding sensor event state set includes: storing the current sensor event state in a storage space corresponding to the sensor event state set, wherein the storage space also stores a sensor type and a sensor category.
[0012] Optionally, before storing the current sensor event state in the storage space corresponding to the sensor event state set, it also includes: parsing the current sensor event state to determine the current event direction; storing the current sensor event state in the storage space corresponding to the sensor event state set, including: determining the offset storage address of the current event state in the corresponding storage space according to the event type value of the current sensor event; when the current event direction is occurrence, storing the first event parameter in the corresponding offset storage address; when the current event direction is disappearance or recovery, storing the second event parameter in the corresponding offset storage address. By determining the offset storage address of the current event state in the corresponding storage space according to the event type value of the current sensor event, all fault states of the sensor can be stored in the storage space corresponding to the sensor, which is convenient for operation and maintenance personnel to comprehensively analyze and locate sensor faults.
[0013] Optionally, after storing the current sensor event state in the corresponding sensor event state set, it also includes: determining the alarm level corresponding to the current sensor event state according to the event type value of the current sensor event, and recording the alarm level in the sensor alarm level set. By using the sensor type code to classify the alarm information, it complies with the IPMI2.0 standard specification and solves the problem that it is difficult to adapt to platform changes when classifying sensor event information according to the sensor name.
[0014] Optionally, before capturing the SEL log, the method further includes: initializing a SEL log monitoring module so that the SEL log can be captured when it is generated. By initializing the list of SEL logs, the SEL logs can be captured in time when they are generated.
[0015] In a second aspect, an embodiment of the present invention further provides a sensor fault state monitoring device, which includes: a capture module, used to capture an SEL log, the SEL log records the current sensor event state and the event type value of the current sensor event; a judgment module, used to judge whether the event type value of the current sensor event matches the event type of the corresponding sensor category in the set specification; a storage module, used to store the current sensor event state in a corresponding sensor event state set when the event type value of the current sensor event matches the event type of the corresponding sensor category in the set specification, the sensor event state set including the historical sensor event state and the current sensor event state.
[0016] The technical solution of the embodiment of the present invention can remove event types that do not belong to the set specifications, and can also remove event types that do not need to be judged, by capturing the current sensor event state and the event type value of the current sensor event in the SEL log, and then judging whether the event type value of the current sensor event matches the event type of the corresponding sensor category in the set specification. By storing the current sensor event state that meets the set specification in the corresponding sensor event state set, all fault states of the sensor can be stored, which is convenient for operation and maintenance personnel to comprehensively analyze and locate sensor faults. BRIEF DESCRIPTION OF THE DRAWINGS
[0017] Figure 1 is a flow chart of a sensor fault status monitoring method provided by Embodiment 1 of the present invention;
[0018] Figure 2 is a flow chart of a sensor fault status monitoring method provided by Embodiment 2 of the present invention;
[0019] Figure 3 is a flow chart of a sensor fault status monitoring method provided by Embodiment 3 of the present invention;
[0020] Figure 4 is a flow chart of a sensor fault status monitoring method provided by Embodiment 4 of the present invention;
[0021] Figure 5 It is a structural schematic diagram of a sensor fault status monitoring device provided in Embodiment 5 of the present invention. DETAILED DESCRIPTION
[0022] The present invention will be further described in detail below in conjunction with the accompanying drawings and embodiments. It is to be understood that the specific embodiments described herein are only used to explain the present invention, rather than to limit the present invention. It should also be noted that, for ease of description, only parts related to the present invention, rather than all structures, are shown in the accompanying drawings.
[0023] Figure 1 This is a flow chart of a sensor fault status monitoring method provided in Embodiment 1 of the present invention. This embodiment is applicable to the case where a BMC monitors a sensor fault status. The method of this embodiment can be executed by a sensor fault status monitoring device, which can be implemented in software and / or hardware and can be integrated on a BMC.
[0024] like Figure 1 As shown, the sensor fault status monitoring method disclosed in this embodiment may include:
[0025] S101 . Capture a SEL log. The SEL log records a current sensor event state and an event type value of a current sensor event.
[0026] Among them, the SEL log is the server system event log, which is one or more log files automatically created and maintained by the server, which contains a list of its performed activities. The sensors of the server can form events, which are recorded in the SEL log. The information recorded in the SEL log includes but is not limited to the current sensor event status, the event type value of the current sensor event, and the sensor type. For example, the occurrence of sensor A event B, the disappearance or recovery of sensor A event B, will all be recorded in the SEL log.
[0027] The current sensor event state includes the current event direction, which is used to indicate whether the sensor event disappears or recovers. For example, when sensor event A and sensor event B occur, event B has not disappeared, and the current sensor event state at this time can be represented by 1; when sensor event A and sensor event B disappear or recover, the current sensor event state at this time can be represented by 0.
[0028] The event type value of the current sensor event may be in code form, and each code corresponds to an event type of the sensor event. Exemplarily, the event type value of the current sensor event may be 00h, and the event type value of the current sensor event may also be 01h.
[0029] S102: Determine whether the event type value of the current sensor event matches the event type of the corresponding sensor category in the setting specification.
[0030] The setting specification may be an IPMI2.0 protocol, and the event type value of the current sensor event is determined to match the event type of the corresponding sensor category in IPMI2.0. The setting specification may include multiple sensor categories, and the event type of each sensor category includes multiple event type values, and each event type value is also represented in code form. The event type value of the current sensor event may be any event type value of the event type in the setting specification, and may also be an event type value not included in the setting specification.
[0031] Exemplarily, the event type of a sensor category in IPMI2.0 is 00h-0Bh. When the sensor belongs to the above sensor category and the event type value of the current sensor event obtained is 04h, the event type value of the current sensor event obtained belongs to the event type of the corresponding sensor category in IPMI2.0; when the sensor belongs to the above sensor category and the event type value of the current sensor event obtained is 0Ch, the event type value of the current sensor event obtained does not belong to the event type of the corresponding sensor category in IPMI2.0.
[0032] If the event type value of the current sensor event matches the event type of the corresponding sensor category in the setting specification, step S1031 is executed; if the event type value of the current sensor event does not match the event type of the corresponding sensor category in the setting specification, step S1032 is executed.
[0033] S1031. Store the current sensor event state into a corresponding sensor event state set, where the sensor event state set includes a historical sensor event state and a current sensor event state.
[0034] Specifically, the sensor event state set includes multiple current sensor event states and multiple historical sensor event states, and different sensor categories correspond to different sensor event state sets. In this step, when the current sensor event state is stored, the sensor event state before the current sensor event state (that is, the historical sensor event state) will not be overwritten, so that when the operating personnel comprehensively analyze the sensor failure, the historical sensor event state and the current sensor event state of each sensor can be obtained, providing data support for the operation and maintenance management personnel to comprehensively analyze the sensor failure.
[0035] S1032: Wait for the next sensor event to arrive.
[0036] The technical solution of the embodiment of the present invention can remove event types that do not belong to the set specifications, and can also remove event types that do not need to be judged, by capturing the current sensor event state and the event type value of the current sensor event in the SEL log, and then judging whether the event type value of the current sensor event matches the event type of the corresponding sensor category in the set specification. By storing the current sensor event state that meets the set specification in the corresponding sensor event state set, all fault states of the sensor can be stored, which is convenient for operation and maintenance personnel to comprehensively analyze and locate sensor faults.
[0037] Embodiment 2
[0038] Figure 2 is a flow chart of a sensor fault status monitoring method provided in the second embodiment of the present invention, which is further optimized and expanded based on the above embodiment and can be combined with various optional technical solutions in the above embodiment. Figure 2 As shown, the method may include:
[0039] S201 . Capture a SEL log. The SEL log records a current sensor event state and an event type value of a current sensor event.
[0040] Specifically, the SEL log also records the sensor type and the current sensor event data group, wherein the current sensor event data group includes the first event data, and the first event data includes the event type value of the current sensor event.
[0041] S202: Parse the event type value and sensor type of the current sensor event in the SEL log, and determine the sensor category according to the sensor type.
[0042] Sensor types include voltage, current, temperature, CPU status, memory status, and hard disk status sensors. Voltage sensors, current sensors, and temperature sensors are threshold sensors, while CPU status sensors, memory status sensors, and hard disk status sensors are discrete sensors.
[0043] S203: Determine whether the sensor category belongs to the set sensor category.
[0044] The set sensor category includes a threshold sensor, a discrete sensor and a universal sensor; when the sensor category is any one of the threshold sensor, the discrete sensor and the universal sensor, it is determined that the sensor category belongs to the set sensor category, and then step S2041 is executed.
[0045] S2041. Obtain an event type value of a current sensor event from first event data.
[0046] For threshold sensors and universal sensors, the event type value of the current sensor event includes a first offset parameter. For discrete sensors, the event type value of the current sensor event includes a first offset parameter and / or a second offset parameter. The first offset parameter may be the Generic Offset in IPMI2.0, and the second offset parameter may be the Sensor-specificOffset in IPMI2.0. For discrete sensors and universal sensors, the current sensor event data group also includes second event data, and the second event data includes a sensor serial number. If the sensor category belongs to a discrete sensor or a universal sensor, after obtaining the event type value of the current sensor event from the first event data, it is necessary to obtain the sensor serial number from the second event data.
[0047] Specifically, the threshold type sensor includes multiple sensor types, each sensor type has only one sensor, that is, the threshold type sensor includes multiple types of sensors, each sensor has only one. Discrete sensors and universal sensors include multiple sensor types, each sensor type includes multiple sensors, that is, discrete sensors and universal sensors include multiple types of sensors, each type of sensor may include multiple sensors. Exemplarily, when a C-type sensor is a discrete sensor or a universal sensor, the C-type sensors may exist as C1, C2...Cn. C1 represents the first sensor of type C, C2 represents the second sensor of type C, and Cn represents the nth sensor of type C. At this time, after obtaining the event type value of the current sensor event from the first event data, it is necessary to obtain the sensor serial number from the second event data to determine what type of sensor it is and which sensor of this type has failed.
[0048] S205: Determine whether the event type value of the current sensor event matches the event type of the corresponding sensor category in the setting specification.
[0049] When the event type value of the current sensor event matches any event type of the corresponding sensor category in the setting specification (where the corresponding sensor category in the setting specification is the sensor category to which the sensor type belongs in the setting specification), it is determined that the event type value of the current sensor event matches the event type of the setting range of the corresponding sensor category in the setting specification. Exemplarily, for the event type of the sensor type of the current sensor corresponding to the sensor category in the setting specification is 00h-0Bh, when the event type value of the current sensor event obtained is 04h, the event type value of the current sensor event obtained belongs to the event type of the corresponding sensor category in the setting specification; when the event type value of the current sensor event obtained is 0Ch, the event type value of the current sensor event obtained does not belong to the event type of the corresponding sensor category in the setting specification. If the event type value of the current sensor event matches the event type of the setting range of the corresponding sensor category in the setting specification, S206 is executed.
[0050] S206: Store the current sensor event state into a corresponding sensor event state set.
[0051] Specifically, the current sensor event state is stored in the storage space corresponding to the sensor event state set, wherein the storage space also stores the sensor type and sensor category. The sensor type and sensor category are both stored in the form of codes, and the sensor event information is classified by using the sensor type code, which complies with the IPMI2.0 standard specification and solves the problem that the sensor event information is difficult to adapt to platform changes when it is classified according to the sensor name.
[0052] Continue to refer Figure 2 The sensor fault status monitoring method also includes: if the sensor category does not belong to any of the threshold type sensor, discrete type sensor and universal type sensor, then execute S2042; and if the event type value of the current sensor event does not match the event type of the set range of the corresponding sensor category in the set specification, then execute S2042.
[0053] S2042: Wait for the next sensor event to arrive.
[0054] The technical solution of the embodiment of the present invention can remove sensor events that do not need to be judged by judging whether the sensor category belongs to the set sensor category; by judging whether the event type value of the current sensor event matches the event type of the corresponding sensor category in the set specification, the event type that does not belong to the set specification can be removed, and the event type that does not need to be judged can also be removed. By storing the current sensor event status and the historical sensor event status, all fault states of the sensor can be stored, which is convenient for operation and maintenance personnel to comprehensively analyze and locate sensor faults. By using sensor type codes to classify sensor event information, it complies with the IPMI2.0 standard specification and solves the problem that it is difficult to adapt to platform changes when classifying sensor event information according to sensor names.
[0055] Embodiment 3
[0056] Figure 3 is a flow chart of a sensor fault status monitoring method provided in the third embodiment of the present invention, which is further optimized and expanded based on the above implementation, and can be combined with various optional technical solutions in the above implementation. Figure 3 As shown, the method may include:
[0057] S301 . Capture a SEL log. The SEL log records the current sensor event state and the event type value of the current sensor event.
[0058] S302: Determine whether the event type value of the current sensor event matches the event type of the corresponding sensor category in the setting specification.
[0059] If the event type value of the current sensor event matches the event type of the corresponding sensor category in the setting specification, step S3031 is executed.
[0060] S3031. Analyze the current sensor event state to determine the current event direction.
[0061] S304. Determine the offset storage address of the current event state in the corresponding storage space according to the event type value of the current sensor event; when the current event direction is occurrence, store the first event parameter to the corresponding offset storage address; when the current event direction is disappearance or recovery, store the second event parameter to the corresponding offset storage address.
[0062] As an implementable solution, when the current event direction is occurrence, the corresponding first event parameter is 1, and when the current event direction is disappearance or recovery, the corresponding second event parameter is 0. If 8 bytes of storage space are provided for each sensor, and each bit records an event, 8 bytes is 64 bits, and 64 events occurring in the current sensor can be recorded. The offset storage address of the current event state in the corresponding storage space is equal to the event type value of the current sensor event. When the current event direction is occurrence, 1 is stored in the offset storage address corresponding to the event type value of the current sensor event; when the current event direction is disappearance or recovery, 0 is stored in the offset storage address corresponding to the event type value of the current sensor event.
[0063] S305 . Determine the alarm level corresponding to the current sensor event state according to the event type value of the current sensor event, and record the alarm level into a sensor alarm level set.
[0064] The alarm level includes, but is not limited to, a minor alarm, a major alarm, and an irrecoverable alarm. The event type value of a sensor event corresponds to an alarm level. For example, when the event type value of the current sensor event is 03h, the corresponding alarm level is a minor alarm. An alarm level is recorded every 3 bits in the storage space. For example, 000 indicates that the alarm disappears, 001 indicates a minor alarm, 010 indicates a major alarm, and 100 indicates an irrecoverable alarm.
[0065] Continue to refer Figure 3 , the sensor fault status monitoring method also includes: if the event type value of the current sensor event does not match the event type of the corresponding sensor category in the setting specification, executing S3032.
[0066] S3032: Wait for the next sensor event to arrive.
[0067] The technical solution of the embodiment of the present invention determines the offset storage address of the current event state in the corresponding storage space through the event type value of the current sensor event, and can store all fault states of the sensor in the storage space corresponding to the sensor, which is convenient for operation and maintenance personnel to comprehensively analyze and locate sensor faults. The present invention classifies alarm information by using sensor type codes, which complies with the IPMI2.0 standard specification and solves the problem that it is difficult to adapt to platform changes when classifying sensor event information according to sensor names.
[0068] Embodiment 4
[0069] Figure 4 4 is a flow chart of a sensor fault status monitoring method provided by the fourth embodiment of the present invention, which is further optimized and expanded based on the above implementation, and can be combined with various optional technical solutions in the above implementation. Figure 4 As shown, the method may include:
[0070] S401. Initialize the SEL log monitoring module so that the SEL log can be captured when it is generated.
[0071] S402: Capture the SEL log, where the SEL log records the current sensor event state and the event type value of the current sensor event.
[0072] S403: parse the event type value and sensor type of the current sensor event in the SEL log, and determine the sensor category according to the sensor type.
[0073] S404: Determine whether the sensor category belongs to the set sensor category.
[0074] If the sensor category belongs to the set sensor category, execute step S4051; if the sensor category does not belong to the set sensor category, execute S4052.
[0075] S4051. Obtain an event type value of a current sensor event from the first event data.
[0076] S406: Determine whether the event type value of the current sensor event matches the event type of the corresponding sensor category in the setting specification.
[0077] If the event type value of the current sensor event matches the event type of the corresponding sensor category in the setting specification, step S407 is executed.
[0078] S407: Analyze the current sensor event state to determine the current event direction.
[0079] S408. Determine the offset storage address of the current event state in the corresponding storage space according to the event type value of the current sensor event; when the current event direction is occurrence, store the first event parameter to the corresponding offset storage address; when the current event direction is disappearance or recovery, store the second event parameter to the corresponding offset storage address.
[0080] S409: Determine the alarm level corresponding to the current sensor event state according to the event type value of the current sensor event, and record the alarm level into the sensor alarm level set.
[0081] S410, display sensor event status collection on dbus.
[0082] S411. Turn on the fault lamp according to the sensor warning level.
[0083] Continue to refer Figure 4 , the sensor fault state monitoring method further includes: if the event type value of the current sensor event does not match the event type of the corresponding sensor category in the setting specification, executing step S4052.
[0084] S4052: Wait for the next sensor event to arrive.
[0085] The technical solution of the embodiment of the present invention can capture the SEL log in time when the SEL log is generated by initializing the list of SEL logs. By judging whether the sensor category belongs to the set sensor category, the sensor events that do not need to be judged can be removed; by judging whether the event type value of the current sensor event matches the event type of the corresponding sensor category in the set specification, the event type that does not belong to the set specification can be removed, and the event type that does not need to be judged can also be removed; by determining the offset storage address of the current event state in the corresponding storage space through the event type value of the current sensor event, all fault states of the sensor can be stored in the storage space corresponding to the sensor, which is convenient for operation and maintenance personnel to comprehensively analyze and locate sensor faults; by using sensor type codes to classify alarm information, it complies with the IPMI2.0 standard specification, and solves the problem that it is difficult to adapt to platform changes when classifying sensor event information according to sensor names; by displaying the sensor event state set on dbus, the sensor event state set can be conveniently called by functions provided by other processes.
[0086] Embodiment 5
[0087] Figure 5 It is a structural schematic diagram of a sensor fault status monitoring device provided in Embodiment 5 of the present invention.
[0088] like Figure 5 As shown, the sensor fault state monitoring device includes:
[0089] The capture module 501 is used to capture the SEL log. The SEL log records the current sensor event state and the event type value of the current sensor event.
[0090] The determination module 502 is used to determine whether the event type value of the current sensor event matches the event type of the corresponding sensor category in the setting specification.
[0091] The storage module 503 is used to store the current sensor event state into the corresponding sensor event state set when the event type value of the current sensor event matches the event type of the corresponding sensor category in the setting specification. The sensor event state set includes the historical sensor event state and the current sensor event state.
[0092] The sensor fault state monitoring device is used to execute the method of any of the above embodiments of the present invention, and the sensor fault state monitoring device has the beneficial effects of any of the above embodiments of the present invention.
[0093] Note that the above are only preferred embodiments of the present invention and the technical principles used. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein, and that various obvious changes, readjustments and substitutions can be made by those skilled in the art without departing from the scope of protection of the present invention. Therefore, although the present invention has been described in more detail through the above embodiments, the present invention is not limited to the above embodiments, and may include more other equivalent embodiments without departing from the concept of the present invention, and the scope of the present invention is determined by the scope of the appended claims.
Claims
1. A sensor fault status monitoring method, characterized in that: include: Capturing an SEL log, wherein the SEL log records a current sensor event state and an event type value of a current sensor event; Determine whether the event type value of the current sensor event matches the event type of the corresponding sensor category in the setting specification; If yes, the current sensor event state is stored in a corresponding sensor event state set, wherein the sensor event state set includes a historical sensor event state and a current sensor event state, wherein the current sensor event state includes a current event direction, and the current event direction is used to indicate whether the event occurring at the sensor disappears or is restored; The SEL log also records the sensor type; Before determining whether the event type value of the current sensor event matches the event type of the corresponding sensor category in the setting specification, the method further includes: Parsing the event type value of the current sensor event and the sensor type in the SEL log; determining a sensor category according to the sensor type; Determining whether the sensor category belongs to a set sensor category; If so, continue to determine whether the event type value of the current sensor event matches the event type of the corresponding sensor category in the setting specification.
2. The sensor fault status monitoring method according to claim 1, characterized in that: The set sensor categories include threshold sensors, discrete sensors and universal sensors; The determining whether the sensor category belongs to a set sensor category includes: when the sensor category is any one of a threshold sensor, a discrete sensor, and a universal sensor, determining that the sensor category belongs to a set sensor category; The determining whether the event type value of the current sensor event matches the event type of a setting range of the corresponding sensor category in the setting specification includes: When the event type value of the current sensor event matches any event type of the corresponding sensor category in the setting specification, it is determined that the event type value of the current sensor event matches an event type of a setting range of the corresponding sensor category in the setting specification.
3. The sensor fault status monitoring method according to claim 2, characterized in that: The SEL log also records a current sensor event data group, the current sensor event data group includes first event data, and the first event data includes an event type value of the current sensor event; Before determining whether the event type value of the current sensor event matches the event type of the corresponding sensor category in the setting specification, the method further includes: An event type value of the current sensor event is acquired from the first event data.
4. The sensor fault status monitoring method according to claim 2, characterized in that: For the threshold type sensor and the universal type sensor, the event type value of the current sensor event includes a first offset parameter. For the discrete type sensor, the event type value of the current sensor event includes a first offset parameter and / or a second offset parameter.
5. The sensor fault status monitoring method according to claim 3, characterized in that: For the discrete sensor and the universal sensor, the current sensor event data set further includes second event data, and the second event data includes a sensor serial number; If the sensor category belongs to the discrete sensor and the universal sensor, after acquiring the event type value of the current sensor event from the first event data, the method further includes: The sensor serial number is obtained from the second event data.
6. The sensor fault status monitoring method according to claim 1, characterized in that: Storing the current sensor event state into a corresponding sensor event state set includes: The current sensor event state is stored in a storage space corresponding to the sensor event state set, wherein the sensor type and the sensor category are also stored in the storage space.
7. The sensor fault status monitoring method according to claim 6, characterized in that: Before storing the current sensor event state into the storage space corresponding to the sensor event state set, the method further includes: Analyze the current sensor event status to determine the current event direction; The storing the current sensor event state into a storage space corresponding to the sensor event state set includes: Determine the offset storage address of the current event state in the corresponding storage space according to the event type value of the current sensor event; When the current event direction is occurrence, storing the first event parameter to the corresponding offset storage address; When the current event direction is disappearance or restoration, the second event parameter is stored in the corresponding offset storage address.
8. The sensor fault status monitoring method according to claim 1 or 7, characterized in that: After storing the current sensor event state into the corresponding sensor event state set, the method further includes: An alarm level corresponding to the current sensor event state is determined according to the event type value of the current sensor event, and the alarm level is recorded in a sensor alarm level set.
9. The sensor fault status monitoring method according to claim 1, characterized in that: Before capturing the SEL log, also include: Initialize the monitoring SEL log module so that the SEL log can be captured when it is generated.
10. A sensor fault status monitoring device, characterized in that: include: A capture module, used to capture a SEL log, wherein the SEL log records a current sensor event state and an event type value of a current sensor event; A judgment module, used to judge whether the event type value of the current sensor event matches the event type of the corresponding sensor category in the setting specification; and also used to parse the event type value and sensor type of the current sensor event in the SEL log; Determine the sensor category according to the sensor type; determine whether the sensor category belongs to the set sensor category; A storage module is used to store the current sensor event state into a corresponding sensor event state set when the event type value of the current sensor event matches the event type of the corresponding sensor category in the setting specification, wherein the sensor event state set includes historical sensor event states and current sensor event states, and the current sensor event state includes a current event direction, and the current event direction is used to indicate whether the event occurring at the sensor disappears or is restored.
