A method, apparatus, computer device, and storage medium for device delay alarm.

Abstract

This invention relates to the field of process management technology and discloses a device, computer equipment, and storage medium for equipment delay alarms. This invention solves the problem that when calculating alarm triggering logic, it is impossible to be completely precise to a specified number of seconds as a constraint by converting the alarm delay period into a target count. Furthermore, a target count value is generated through a remote dictionary service, and a new alarm record is generated when the target count value equals the target count. This ensures that, under multi-process and multi-threaded conditions, when an alarm record for the same measurement point is triggered multiple times, only one alarm record is ultimately generated. Therefore, through this invention, when a device generates false alarms due to network jitter, its own busy status, or other issues, the alarm rule can be delayed to ensure that a correct alarm is generated.

Description

Technical Field

[0001] This invention relates to the field of process management technology, specifically to a method, apparatus, computer device, and storage medium for equipment delay alarm. Background Technology

[0002] In monitoring various sub-monitoring systems and infrastructure devices, DCIM (Data Center Infrastructure Management) platforms and environmental monitoring platforms need to monitor the operational status of devices and determine whether to generate alarms based on set thresholds. After configuring alarm rules, considering that network jitter, busy terminal devices, and other factors may occur during actual communication with devices, leading to problems with the data returned to the DCIM or environmental monitoring platforms (i.e., data cannot be collected), alarm rules such as device disconnection may be triggered, resulting in false alarms. This can cause maintenance personnel to misdirect their troubleshooting, wasting time and effort. Summary of the Invention

[0003] In view of this, the present invention provides a device, apparatus, computer equipment and storage medium for device delay alarm, in order to solve the problem that during the device detection process, DCIM platform and environmental monitoring platform cannot respond to data collection requests in a timely manner due to network jitter and device busyness, resulting in false alarms due to failure to collect data, which affects the operation and maintenance personnel's judgment and troubleshooting of real problems.

[0004] In a first aspect, the present invention provides a device delay alarm method for a data center infrastructure management platform, the data center infrastructure management platform being connected to a user terminal; the method includes:

[0005] The system utilizes a data center infrastructure management platform to acquire device datasets and determines alarm thresholds for device measurement points based on these datasets. It then checks whether alarm records have been generated at the device measurement points based on these thresholds. If no alarm records have been generated, it checks whether an alarm delay period has been configured for the device measurement point. If an alarm delay period has been configured, it converts the alarm delay period into a target count. Using a remote dictionary service, it increments the delayed alarm count for each device measurement point to obtain a target count value. The target count is then compared to the target count value. When the target count equals the target count value, the device measurement point generates a new alarm record and sends it to the user terminal.

[0006] The device delay alarm method provided by this invention solves the problem that it is impossible to be completely precise to a specified number of seconds as a constraint when calculating the alarm triggering logic. Furthermore, a target count value is generated through a remote dictionary service, and a new alarm record is generated when the target count value equals the target number of times. This ensures that, under multi-process and multi-threaded conditions, when an alarm record for the same measurement point is triggered multiple times, only one alarm record is ultimately generated. Therefore, through this invention, when a device generates false alarms due to network jitter, its own busy status, or other issues, the alarm rule can be delayed to ensure that a correct alarm is generated.

[0007] In one optional implementation, determining whether an alarm record has been generated at a device measurement point based on an alarm threshold includes:

[0008] Determine if the alarm threshold has been triggered; if the alarm threshold has been triggered, determine if the device measurement point has generated an alarm record.

[0009] This invention can further determine whether an alarm record has been generated at the device's measurement point by judging whether the alarm threshold has been triggered.

[0010] In one optional implementation, after determining whether the alarm threshold has been triggered, the method further includes:

[0011] If the alarm threshold is not triggered, determine whether the device measurement point has been configured with an alarm delay period; if the device measurement point has been configured with an alarm delay period, obtain the historical alarm delay count and historical alarm recovery delay count of the device measurement point, and clear the historical alarm delay count and historical alarm recovery delay count; if the device measurement point has not been configured with an alarm delay period, end the alarm.

[0012] When the device measurement point has been configured with an alarm delay period, the present invention promptly clears the alarm delay count and alarm recovery delay count of the delay period to zero, which can ensure that the alarm delay period can be correctly calculated in the next period, and thus correctly judge the alarm logic.

[0013] In one optional implementation, after determining whether an alarm record has been generated by a device measuring point based on an alarm threshold, the method further includes: if an alarm record has been generated by a device measuring point, ignoring the alarm record and ending the alarm process.

[0014] In one optional implementation, after determining whether an alarm delay period has been configured on the device measurement point when no alarm record is generated, the method further includes: when no alarm delay period is configured on the device measurement point, the device measurement point generates a new alarm record and sends the new alarm record to the user terminal.

[0015] In this invention, if the device measurement point does not generate an alarm record and no alarm delay period is configured, a new alarm record can be generated directly and sent to the corresponding user terminal.

[0016] In one optional implementation, after comparing the target number of times with the target count value, the method further includes: ignoring the alarm when the target count value is less than the target number of times; recording the target number of times and ending the alarm.

[0017] In one optional implementation, after comparing the target number of times with the target count value, the method further includes: ignoring the alarm and ending the alarm when the target count value is greater than the target number of times.

[0018] In a second aspect, the present invention provides a device delay alarm device for a data center infrastructure management platform, the data center infrastructure management platform being connected to a user terminal; the device includes:

[0019] The system comprises the following modules: an acquisition and determination module, used to acquire device datasets using the data center infrastructure management platform and determine alarm thresholds for device test points based on the datasets; a first judgment module, used to determine whether a device test point has generated an alarm record based on the alarm thresholds; a second judgment module, used to determine whether an alarm delay period has been configured for the device test point if no alarm record has been generated; a conversion module, used to convert the alarm delay period into a target count when the device test point has been configured with an alarm delay period; an addition module, used to add the delayed alarm count of the device test point using a remote dictionary service to obtain a target count value; a comparison module, used to compare the target count with the target count value; and a first generation and sending module, used to generate a new alarm record for the device test point and send the new alarm record to the user terminal when the target count equals the target count value.

[0020] Thirdly, the present invention provides a computer device, including: a memory and a processor, the memory and the processor being communicatively connected to each other, the memory storing computer instructions, and the processor executing the computer instructions to perform the device delay alarm method described in the first aspect or any corresponding embodiment thereof.

[0021] Fourthly, the present invention provides a computer-readable storage medium storing computer instructions for causing a computer to execute the device delay alarm method described in the first aspect or any corresponding embodiment thereof. Attached Figure Description

[0022] To more clearly illustrate the specific embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the specific embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0023] Figure 1 This is a flowchart illustrating a device delay alarm method according to an embodiment of the present invention;

[0024] Figure 2 This is a flowchart illustrating another device delay alarm method according to an embodiment of the present invention;

[0025] Figure 3 This is a flowchart illustrating another device delay alarm method according to an embodiment of the present invention;

[0026] Figure 4 This is a flowchart illustrating a device delay alarm scheme according to an embodiment of the present invention;

[0027] Figure 5 This is a structural block diagram of a device delay alarm device according to an embodiment of the present invention;

[0028] Figure 6 This is a schematic diagram of the hardware structure of a computer device according to an embodiment of the present invention. Detailed Implementation

[0029] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0030] This invention provides a device delay alarm method, which solves the problem that it is impossible to be completely accurate to a specified number of seconds as a constraint when calculating the alarm triggering logic by converting the alarm delay period into a target number.

[0031] According to an embodiment of the present invention, a device delay alarm method embodiment is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0032] This embodiment provides a device delay alarm method that can be used in a data center infrastructure management (DCIM) platform connected to a user terminal. Figure 1 This is a flowchart of a device delay alarm method according to an embodiment of the present invention, such as... Figure 1 As shown, the process includes the following steps:

[0033] Step S101: Obtain the device dataset using the data center infrastructure management platform, and determine the alarm threshold of the device measurement point based on the device dataset.

[0034] The equipment dataset can include equipment data from various subsystems and basic equipment within the DCIM platform and the environmental monitoring platform.

[0035] Furthermore, the environmental monitoring platform is part of the DCIM platform.

[0036] Specifically, the DCIM platform and the environmental monitoring platform collect corresponding data from various subsystems and infrastructure equipment and form equipment datasets.

[0037] Furthermore, based on the collected device dataset, the alarm thresholds for the corresponding device measurement points can be queried.

[0038] Step S102: Determine whether the device measurement point has generated an alarm record based on the alarm threshold.

[0039] Specifically, based on the alarm threshold obtained from the query, it can be further determined whether the device measurement point has generated a corresponding alarm record.

[0040] Step S103: When no alarm record is generated by the device measurement point, determine whether the device measurement point has been configured with an alarm delay period.

[0041] Specifically, after determining that no corresponding alarm record has been generated at the device measurement point, it is further determined whether the corresponding device measurement point has been configured with the corresponding alarm delay period.

[0042] Step S104: When the device measurement point has been configured with an alarm delay period, convert the alarm delay period into the target number.

[0043] Specifically, if the device measurement point has been configured with a corresponding alarm delay period, the alarm delay period is converted into the corresponding target number. For example, the DCIM platform and the environmental monitoring platform will perform an alarm logic judgment every 5 seconds by default. Therefore, the alarm delay period can be converted into the corresponding number, that is, a delay of 60 seconds is 60 / 5 = 12 times.

[0044] Step S105: Using the remote dictionary service, increase the number of delay alarms at the device measurement points to obtain the target count value.

[0045] The target count value represents the number of times the record is made in the Remote Dictionary Server (Redis).

[0046] Specifically, under multi-process and multi-threaded conditions, alarm records for the same test point will be triggered multiple times. Therefore, by utilizing the single-threaded nature of the remote dictionary service Redis, the delay alarm count for the current device test point is incremented by 1.

[0047] Step S106: Compare the target number of times with the target count value.

[0048] Specifically, the target number after the alarm delay period is converted is compared with the target count value recorded in the remote dictionary service Redis.

[0049] Step S107: When the target number of times equals the target count value, the device measurement point generates a new alarm record and sends the new alarm record to the user terminal.

[0050] Specifically, when the target count after the alarm delay period conversion is equal to the target count value recorded in the remote dictionary service Redis, the corresponding device test point will generate a new alarm record and notify the corresponding operation and maintenance personnel on the user end of the alarm record.

[0051] The device delay alarm method provided in this embodiment solves the problem that it is impossible to be completely accurate to a specified number of seconds as a constraint when calculating the alarm triggering logic. Furthermore, a target count value is generated through a remote dictionary service, and a new alarm record is generated when the target count value equals the target number of times. This ensures that, under multi-process and multi-threaded conditions, when an alarm record for the same measurement point is triggered multiple times, only one alarm record is ultimately generated. Therefore, through this invention, when a device generates false alarms due to network jitter, its own busy status, or other issues, the alarm rule can be delayed to ensure that a correct alarm is generated.

[0052] This embodiment provides a device delay alarm method that can be used in a data center infrastructure management (DCIM) platform connected to a user terminal. Figure 2 This is a flowchart of a device delay alarm method according to an embodiment of the present invention, such as... Figure 2 As shown, the process includes the following steps:

[0053] Step S201: Obtain the device dataset using the data center infrastructure management platform, and determine the alarm thresholds for the device measurement points based on the device dataset. For details, please refer to [link to relevant documentation]. Figure 1 Step S101 of the illustrated embodiment will not be described again here.

[0054] Step S202: Determine whether the device measurement point has generated an alarm record based on the alarm threshold.

[0055] Specifically, step S202 includes:

[0056] Step S2021: Determine whether the alarm threshold has been triggered.

[0057] Step S2022: When the alarm threshold is triggered, determine whether the device measurement point has generated an alarm record.

[0058] Each measuring point is configured with an alarm rule, which includes a threshold and a judgment symbol. For example, for a measuring point of a temperature and humidity device: temperature. The backend is configured to generate an alarm when the temperature > 27. After the DCIM collects data from the actual device, it compares the collected values ​​with the temperature and humidity thresholds and symbols. If the judgment condition is met (e.g., the currently collected temperature value is 28), the alarm threshold can be determined to be triggered.

[0059] Specifically, if it is determined that the alarm threshold has been triggered, then it is further determined whether the device measurement point has generated the corresponding alarm record.

[0060] In some optional implementations, after step S2021, step S202 further includes:

[0061] Step S2023: If the alarm threshold is not triggered, determine whether the device measurement point has been configured with an alarm delay period.

[0062] Specifically, if it is determined that the alarm threshold has not been triggered, the system will continue to determine whether the device measurement point has been configured with the corresponding alarm delay period.

[0063] Step S2024: When the device measurement point has been configured with an alarm delay period, obtain the historical alarm delay count and historical alarm recovery delay count of the device measurement point, and clear the historical alarm delay count and historical alarm recovery delay count.

[0064] Specifically, if it is determined that the current device measurement point has been configured with a corresponding alarm delay period, then the historical alarm delay count and historical alarm recovery delay count corresponding to the device measurement point are obtained.

[0065] Furthermore, promptly clearing the historical alarm delay count and historical alarm recovery delay count ensures that the alarm delay period can be correctly calculated in the next cycle, thereby correctly judging the alarm logic.

[0066] Step S2025: When the device measurement point is not configured with an alarm delay period, the alarm is terminated.

[0067] Specifically, if it is determined that the current device measurement point is not configured with a corresponding alarm delay period, then the alarm will be terminated.

[0068] Step S203: If no alarm record is generated by the device's measuring point, determine whether the device's measuring point has been configured with an alarm delay period. For details, please refer to [link to relevant documentation]. Figure 1 Step S103 of the illustrated embodiment will not be described again here.

[0069] Step S204: If the device measurement point has already been configured with an alarm delay period, convert the alarm delay period into the target number of times. For details, please refer to [link to relevant documentation]. Figure 1 Step S104 of the illustrated embodiment will not be described again here.

[0070] Step S205: Using the remote dictionary service, increase the delay alarm count at the device measurement points to obtain the target count value. For details, please refer to [link to relevant documentation]. Figure 1 Step S105 of the illustrated embodiment will not be described again here.

[0071] Step S206: Compare the target number of times with the target count value. For details, please refer to [link to relevant documentation]. Figure 1 Step S106 of the illustrated embodiment will not be described again here.

[0072] Step S207: When the target number of times equals the target count value, the device measurement point generates a new alarm record and sends the new alarm record to the user terminal. For details, please refer to [link to details]. Figure 1 Step S107 of the illustrated embodiment will not be described again here.

[0073] The device delay alarm method provided in this embodiment can further determine whether an alarm record has been generated by the device measurement point by judging whether the alarm threshold has been triggered. Furthermore, by converting the alarm delay period into a target count, the problem of not being able to be completely accurate to a specified number of seconds as a constraint condition when calculating the alarm triggering logic is solved. Furthermore, a target count value is generated through a remote dictionary service, and a new alarm record is generated when the target count value equals the target count. This ensures that only one alarm record is generated when multiple alarm records for the same measurement point are triggered multiple times under multi-process and multi-threaded conditions. Furthermore, when an alarm delay period has been configured for the device measurement point, the alarm delay count and alarm recovery delay count of the delay period are promptly cleared to zero, ensuring that the alarm delay period can be correctly calculated in the next period, thereby correctly judging the alarm logic. Therefore, through this invention, when a device generates false alarms due to network jitter, its own busy status, or other issues, the alarm rule can be delayed to ensure that a correct alarm is generated.

[0074] This embodiment provides a device delay alarm method that can be used in a data center infrastructure management (DCIM) platform connected to a user terminal. Figure 3 This is a flowchart of a device delay alarm method according to an embodiment of the present invention, such as... Figure 3 As shown, the process includes the following steps:

[0075] Step S301: Obtain the device dataset using the data center infrastructure management platform, and determine the alarm thresholds for the device measurement points based on the device dataset. For details, please refer to [link to relevant documentation]. Figure 1 Step S101 of the illustrated embodiment will not be described again here.

[0076] Step S302: Determine whether an alarm record has been generated at the device's measurement point based on the alarm threshold. For details, please refer to [link to relevant documentation]. Figure 2 Step S202 of the illustrated embodiment will not be described again here.

[0077] Step S303: When the device measurement point has generated an alarm record, ignore the alarm record and end the alarm process.

[0078] Specifically, if it is determined that the current device measurement point has already generated a corresponding alarm record, then the alarm record is ignored and the alarm is terminated.

[0079] Step S304: If no alarm record is generated by the device's measuring point, determine whether the device's measuring point has been configured with an alarm delay period. For details, please refer to [link to relevant documentation]. Figure 1 Step S103 of the illustrated embodiment will not be described again here.

[0080] Step S305: When the device measurement point is not configured with an alarm delay period, the device measurement point generates a new alarm record and sends the new alarm record to the user terminal.

[0081] Specifically, if it is determined that the current device measurement point is not configured with the corresponding alarm delay period, the device measurement point will generate a new alarm record and notify the corresponding operation and maintenance personnel on the user end of the alarm record.

[0082] Step S306: If the device measurement point has already been configured with an alarm delay period, convert the alarm delay period into the target number of times. For details, please refer to [link to relevant documentation]. Figure 1 Step S104 of the illustrated embodiment will not be described again here.

[0083] Step S307: Using the remote dictionary service, increase the delay alarm count at the device's measurement points to obtain the target count value. For details, please refer to [link to relevant documentation]. Figure 1 Step S105 of the illustrated embodiment will not be described again here.

[0084] Step S308: Compare the target number of times with the target count value. For details, please refer to [link to relevant documentation]. Figure 1 Step S106 of the illustrated embodiment will not be described again here.

[0085] Step S309: When the target number of times equals the target count value, the device measurement point generates a new alarm record and sends the new alarm record to the user terminal. For details, please refer to [link to relevant documentation]. Figure 1 Step S107 of the illustrated embodiment will not be described again here.

[0086] Step S3010: When the target count value is less than the target number of times, ignore the alarm and record the target number of times, and end the alarm.

[0087] Specifically, if the target count value recorded in the remote dictionary service Redis is less than the target number after the alarm delay period conversion, the alarm record is ignored and the alarm ends after the corresponding target number is recorded.

[0088] Step S3011: When the target count value is greater than the target number of times, ignore the alarm and end the alarm.

[0089] Specifically, if the target count value recorded in the remote dictionary service Redis is greater than the target number after the alarm delay period conversion, the alarm will be ignored and the alarm will be terminated.

[0090] The device delay alarm method provided in this embodiment solves the problem that it is impossible to be completely accurate to a specified number of seconds as a constraint when calculating the alarm triggering logic. Furthermore, a target count value is generated through a remote dictionary service, and a new alarm record is generated when the target count value equals the target number of times. This ensures that, under multi-process and multi-threaded conditions, when an alarm record for the same measurement point is triggered multiple times, only one alarm record is ultimately generated. Therefore, through this invention, when a device generates false alarms due to network jitter, its own busy status, or other issues, the alarm rule can be delayed to ensure that a correct alarm is generated.

[0091] In one example, a device delayed alarm solution is provided. The alarm process is designed such that a delay time (in seconds) is set when configuring alarm rules for each monitoring point. When the value of a monitored monitoring point triggers an alarm rule, the configured alarm delay time is first checked. If the delay time is 0 (no delay), an alarm rule is immediately generated and notified to the operations and maintenance personnel. If the delay time is not 0, the current alarm rule is processed. Utilizing the single-threaded nature of Redis, the count of pre-alarms for that monitoring point is incremented by 1 (the DCIM platform and the environmental monitoring platform perform alarm logic checks every 5 seconds by default, so the delay time can be converted into a corresponding number of times; a 60-second delay is 60 / 5 = 12 times). When the alarm count of the monitoring point is less than the number of times corresponding to the delay period, no alarm is generated; only the count is recorded. Only when the alarm count of the monitoring point equals the number of times corresponding to the delay period is an actual alarm record generated and notified to the operations and maintenance personnel. For situations where alarms are continuously generated—that is, alarm rules are triggered even after the delay period has elapsed—only one alarm will be generated under the aforementioned conditions, thus avoiding alarm bombardment. Simultaneously, considering that the device resumes normal communication during the delayed alarm period, the collected data is normal and will not trigger the alarm threshold for the measurement point; therefore, the existing alarm count for the measurement point will be reset to zero. This ensures that the alarm delay period can be correctly calculated in the next cycle.

[0092] like Figure 4 As shown, the device's delayed alarm scheme includes:

[0093] 1. The DCIM platform and the environmental monitoring platform collect data from various subsystems and infrastructure equipment into the system and begin alarm processing.

[0094] 2. Query the alarm threshold of the measurement points of the devices in the current dataset.

[0095] 3. Calculate whether the alarm threshold of the device is triggered based on the collected data. If it is not triggered, proceed to step 4; if it is triggered, proceed to step 5.

[0096] 4. Check if an alarm delay period is configured for this test point. If not, the alarm process ends. If it is configured, the recorded alarm delay counts and alarm recovery delay counts will be cleared, and the process ends.

[0097] 5. Check if an alarm record has been generated for this measurement point. If it has, ignore the alarm and the process ends. Otherwise, proceed to the next step.

[0098] 6. Check if an alarm delay period is configured for this measurement point. If not, generate an alarm record directly; otherwise, proceed to the next step.

[0099] 7. Convert the alarm delay period into the number of times (the DCIM platform and the environmental monitoring platform will perform an alarm logic judgment every 5 seconds by default, so the delay time can be converted into the corresponding number of times, that is, a delay of 60 seconds is 60 / 5 = 12 times).

[0100] 8. Utilize Redis's single-threaded nature to increment the latency alarm count for the current test point by 1.

[0101] 9. Calculate the number of delay cycle conversions at the measurement point and compare it with the number already recorded in Redis. If the number recorded in Redis is less than the number of delay cycle conversions, ignore the alarm and record the number, and the process ends; if the number recorded in Redis is greater than the number of delay cycle conversions, ignore the alarm and the process ends; if the two are equal, proceed to the next step.

[0102] 10. Generate a new alarm record and notify the operations and maintenance personnel.

[0103] 11. Process complete.

[0104] The device delay alarm solution provided in this example takes into account that it is impossible to be completely precise to a specified number of seconds when calculating the alarm triggering logic. Furthermore, under multi-process and multi-threaded conditions, alarm records for the same measurement point may be triggered multiple times. Therefore, it is necessary to ensure that only one alarm record is ultimately generated, which requires using the "equal to" condition for constraint. Additionally, if the alarm at the measurement point automatically recovers within the delay period, the record count for the delay period needs to be reset to zero promptly to ensure correct alarm logic judgment in the next instance.

[0105] Furthermore, the device delay alarm solution provided in this example has been running stably in a large data center for six months, detecting more than 1,520 devices and a total of 90,000+ test points. It can capture false alarms caused by network jitter or busy terminal devices that cannot respond in time, and issue delayed alarms to ensure accurate output of device alarms, helping operation and maintenance personnel to better understand the equipment operation status of the data center.

[0106] Therefore, the device delay alarm solution provided in this example can eliminate false alarms caused by network jitter, system switching, or busy terminal devices, and present key information and core alarms to maintenance personnel, thereby reducing unnecessary system troubleshooting and improving work efficiency.

[0107] This embodiment also provides a device delay alarm device, which is used to implement the above embodiments and preferred embodiments; details already described will not be repeated. As used below, the term "module" can be a combination of software and / or hardware that implements a predetermined function. Although the device described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.

[0108] This embodiment provides a device delay alarm for a data center infrastructure management platform, which is connected to a user terminal. Figure 5 As shown, it includes:

[0109] The acquisition and determination module 501 is used to acquire the device dataset using the data center infrastructure management platform and determine the alarm threshold of the device measurement points based on the device dataset.

[0110] The first judgment module 502 is used to determine whether the device measurement point has generated an alarm record based on the alarm threshold.

[0111] The second judgment module 503 is used to determine whether the device measurement point has been configured with an alarm delay period when no alarm record is generated.

[0112] The conversion module 504 is used to convert the alarm delay period into the target number when the device measurement point has been configured with an alarm delay period.

[0113] Add module 505 to increase the number of delay alarms at device measurement points using remote dictionary service, and obtain the target count value.

[0114] The comparison module 506 is used to compare the target number of times with the target count value.

[0115] The first generation and transmission module 507 is used to generate a new alarm record at the device measurement point when the target number equals the target count value, and send the new alarm record to the user terminal.

[0116] In some optional implementations, the first determination module 502 includes:

[0117] The first judgment unit is used to determine whether the alarm threshold has been triggered.

[0118] The second judgment unit is used to determine whether an alarm record has been generated at the device measurement point when the alarm threshold is triggered.

[0119] In some optional implementations, the first determination module 502 further includes:

[0120] The third judgment unit is used to determine whether the device measurement point has been configured with an alarm delay period when the alarm threshold is not triggered.

[0121] The acquisition and processing unit is used to acquire the historical alarm delay count and historical alarm recovery delay count of the device measurement point when the device measurement point has been configured with an alarm delay period, and to clear the historical alarm delay count and historical alarm recovery delay count.

[0122] The termination unit is used to terminate alarms when no alarm delay period is configured for the device's measurement points.

[0123] In some alternative embodiments, the device further includes:

[0124] The first processing module is used to ignore alarm records and end alarms when alarm records have been generated at the device's measurement points.

[0125] In some alternative embodiments, the device further includes:

[0126] The second generation and transmission module is used to generate new alarm records when the device measurement point is not configured with an alarm delay period, and then send the new alarm records to the user terminal.

[0127] In some alternative embodiments, the device further includes:

[0128] The second processing module is used to ignore the alarm and record the target count when the target count value is less than the target number of times, and to end the alarm.

[0129] In some alternative embodiments, the device further includes:

[0130] The third processing module is used to ignore the alarm and end the alarm when the target count value is greater than the target number of times.

[0131] Further functional descriptions of the above modules and units are the same as those in the corresponding embodiments described above, and will not be repeated here.

[0132] In this embodiment, the device delay alarm device is presented in the form of a functional unit. Here, a unit refers to an ASIC (Application Specific Integrated Circuit) circuit, a processor and memory that execute one or more software or fixed programs, and / or other devices that can provide the above functions.

[0133] This invention also provides a computer device having the above-described features. Figure 5 The device shown is a delay alarm device.

[0134] Please see Figure 6 , Figure 6 This is a schematic diagram of the structure of a computer device provided in an optional embodiment of the present invention, such as... Figure 6As shown, the computer device includes one or more processors 10, memory 20, and interfaces for connecting the components, including high-speed interfaces and low-speed interfaces. The components communicate with each other via different buses and can be mounted on a common motherboard or otherwise installed as needed. The processors can process instructions executed within the computer device, including instructions stored in or on memory to display graphical information of a GUI on external input / output devices (such as display devices coupled to the interfaces). In some alternative implementations, multiple processors and / or multiple buses can be used with multiple memories and multiple memory modules, if desired. Similarly, multiple computer devices can be connected, each providing some of the necessary operations (e.g., as a server array, a group of blade servers, or a multiprocessor system). Figure 6 Take a processor 10 as an example.

[0135] Processor 10 may be a central processing unit, a network processor, or a combination thereof. Processor 10 may further include a hardware chip. The hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The programmable logic device may be a complex programmable logic device (CAMP), a field-programmable gate array (FPGA), a general-purpose array logic (GDA), or any combination thereof.

[0136] The memory 20 stores instructions executable by at least one processor 10 to cause at least one processor 10 to perform the method shown in the above embodiments.

[0137] The memory 20 may include a program storage area and a data storage area. The program storage area may store the operating system and applications required for at least one function; the data storage area may store data created based on the use of the computer device. Furthermore, the memory 20 may include high-speed random access memory and may also include non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid-state storage device. In some alternative embodiments, the memory 20 may optionally include memory remotely located relative to the processor 10, and these remote memories may be connected to the computer device via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

[0138] The memory 20 may include volatile memory, such as random access memory; the memory may also include non-volatile memory, such as flash memory, hard disk or solid-state drive; the memory 20 may also include a combination of the above types of memory.

[0139] The computer device also includes a communication interface 30 for communicating with other devices or communication networks.

[0140] This invention also provides a computer-readable storage medium. The methods described above according to embodiments of the invention can be implemented in hardware or firmware, or implemented as computer code that can be recorded on a storage medium, or implemented as computer code downloaded via a network and originally stored on a remote storage medium or a non-transitory machine-readable storage medium and then stored on a local storage medium. Thus, the methods described herein can be processed by software stored on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. The storage medium can be a magnetic disk, optical disk, read-only memory, random access memory, flash memory, hard disk, or solid-state drive, etc.; further, the storage medium can also include combinations of the above types of memory. It is understood that computers, processors, microprocessor controllers, or programmable hardware include storage components capable of storing or receiving software or computer code, which, when accessed and executed by the computer, processor, or hardware, implements the methods shown in the above embodiments.

[0141] Although embodiments of the invention have been described in conjunction with the accompanying drawings, those skilled in the art can make various modifications and variations without departing from the spirit and scope of the invention, and all such modifications and variations fall within the scope defined by the appended claims.

Claims

1. A method for device delay alarm, characterized in that, For a data center infrastructure management platform, the data center infrastructure management platform is connected to a user terminal; the method includes: The data center infrastructure management platform is used to obtain device datasets, and alarm thresholds for device measurement points are determined based on the device datasets. Based on the alarm threshold, determine whether the device measurement point has generated an alarm record; If no alarm record is generated by the device measurement point, determine whether the device measurement point has been configured with an alarm delay period; When the alarm delay period has been configured at the device measurement point, convert the alarm delay period into the target number; Using a remote dictionary service, the number of delay alarms at the device measurement point is increased to obtain a target count value. The remote dictionary service is used to increment the number of delay alarms at the current device measurement point by 1 when the alarm record of the same measurement point is triggered multiple times under multi-process and multi-thread conditions. Compare the target number of times with the target count value; When the target number equals the target count value, the device measurement point generates a new alarm record and sends the new alarm record to the user terminal.

2. The method according to claim 1, characterized in that, Determining whether an alarm record has been generated at the device's measurement point based on the alarm threshold includes: Determine whether the alarm threshold has been triggered; When the alarm threshold is triggered, determine whether the device measurement point has generated the alarm record.

3. The method according to claim 2, characterized in that, After determining whether the alarm threshold has been triggered, the method further includes: If the alarm threshold is not triggered, determine whether the alarm delay period has been configured at the device measurement point; When the alarm delay period has been configured for the device measurement point, the historical alarm delay count and historical alarm recovery delay count of the device measurement point are obtained, and the historical alarm delay count and historical alarm recovery delay count are cleared. The alarm ends when the device measurement point is not configured with the alarm delay period.

4. The method according to claim 1, characterized in that, After determining whether an alarm record has been generated at the device measurement point based on the alarm threshold, the method further includes: When the device measurement point has generated the alarm record, ignore the alarm record and end the alarm process.

5. The method according to claim 1, characterized in that, When no alarm record is generated at the device measurement point, after determining whether the alarm delay period has been configured at the device measurement point, the method further includes: When the device measurement point is not configured with the alarm delay period, the device measurement point generates a new alarm record and sends the new alarm record to the user terminal.

6. The method according to claim 1, characterized in that, After comparing the target number of times with the target count value, the method further includes: When the target count value is less than the target number of times, ignore the alarm, record the target number of times, and end the alarm.

7. The method according to claim 1, characterized in that, After comparing the target number of times with the target count value, the method further includes: When the target count value is greater than the target number of times, the alarm is ignored and the alarm is terminated.

8. A device delay alarm device, characterized in that, For a data center infrastructure management platform, the data center infrastructure management platform is connected to a user terminal; the device includes: The acquisition and determination module is used to acquire device datasets using the data center infrastructure management platform and determine alarm thresholds for device measurement points based on the device datasets. The first judgment module is used to determine whether the device measurement point has generated an alarm record based on the alarm threshold. The second judgment module is used to determine whether the device measurement point has been configured with an alarm delay period when no alarm record is generated by the device measurement point. The conversion module is used to convert the alarm delay period into a target number when the device measurement point has been configured with the alarm delay period; An additional module is added to increase the number of delay alarms at the device measurement points using a remote dictionary service to obtain a target count value. The remote dictionary service is used to increment the number of delay alarms at the current device measurement point by 1 when the alarm record of the same measurement point is triggered multiple times under multi-process and multi-threaded conditions. The comparison module is used to compare the target number of times with the target count value; The first generation and transmission module is used to generate a new alarm record at the device measurement point when the target number equals the target count value, and send the new alarm record to the user terminal.

9. A computer device, characterized in that, include: A memory and a processor are communicatively connected, the memory stores computer instructions, and the processor executes the computer instructions to perform the device delay alarm method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions for causing a computer to execute the device delay alarm method according to any one of claims 1 to 7.

Images