Alarm event reporting method and device, electronic equipment and program product

Abstract

The invention discloses an alarm event reporting method and device, electronic equipment and a program product, and relates to the field of computers.The method comprises the steps that under the condition that a first alarm event of a first type triggered in a first client application is detected, the first alarm event is registered in an alarm register, the first type is used for indicating that the reporting priority of the first alarm event is smaller than a preset priority, and the alarm register is used for registering the first type of alarm event; when it is detected that the number of the first type of alarm events in the alarm register reaches a first preset number, compressing the first preset number of the first type of alarm events to obtain a target alarm event; and reporting the target alarm event.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of computer, in particular to a method and device for reporting alarm event, electronic equipment and program product. BACKGROUND

[0002] In a traditional monitoring alarm system, when low-priority alarm events are triggered frequently, these events will occupy a large amount of processing resources of the alarm system and attention of monitoring personnel, resulting in important high-priority alarm events being ignored or delayed. Especially for those alarm events that occur repeatedly in a short time, such as service thread exceptions, they can generate a large number of alarm signals, which are not important, but if not managed, they can seriously interfere with the response speed to the real key problems.

[0003] Therefore, how to effectively manage and compress low-priority frequent alarms to ensure that important alarms can be processed in time has become a problem to be solved. SUMMARY

[0004] Embodiments of the present application provide a method and device for reporting alarm event, electronic equipment and program product to at least solve the technical problem of how to effectively manage and compress low-priority frequent alarms.

[0005] In order to achieve the above-mentioned purpose, according to one aspect of the present application, a method for reporting alarm event is provided, comprising: in the case of detecting a first alarm event of a first type triggered in a first client application, registering the first alarm event to an alarm register, wherein the first type is used to indicate that the reporting priority of the first alarm event is less than a preset priority, and the alarm register is used to register alarm events of the first type; in the case of detecting that the number of alarm events of the first type in the alarm register reaches a first preset number, compressing the first preset number of alarm events of the first type to obtain a target alarm event; and reporting the target alarm event.

[0006] As an optional solution, registering the first alarm event to the alarm register comprises: registering the first alarm event to a first registration area of the alarm register, wherein the first registration area is used to register alarm events triggered in the first client application; the method further comprises: in the case of detecting a second alarm event of the first type triggered by a second client application, registering the second alarm event to a second registration area of the alarm register, wherein the second registration area is used to register alarm events triggered in the second client application, and the alarm register comprises a plurality of registration areas, and one registration area corresponds to one client application.

[0007] As an optional approach, before compressing the first preset number of alarm events of the first type, the method further includes: configuring a first preset number for the first storage area, wherein the first preset number is determined based on the first application type of the first client application; before storing the second alarm event in the second storage area of ​​the alarm storage area, the method further includes: configuring a second preset number for the second storage area, wherein the second preset number is determined based on the second application type of the second client application.

[0008] As an optional approach, before registering the first alarm event to the alarm register, the method further includes: registering the first application information of the first client application to a configuration table; and, upon completion of the registration of the first application information, configuring a component for the first client application based on the first application information, wherein the component is used to register the first alarm event triggered within the first client application to the alarm register.

[0009] As an optional solution, reporting target alarm events includes: forwarding the target alarm event from the alarm storage area to the first client application through a component; and reporting the target alarm event to the early warning center through the first client application, wherein the early warning center is used to receive alarm events reported by each client application.

[0010] As an optional approach, the method further includes: reporting the third alarm event when a first type of third alarm event triggered within a third client application is detected, wherein the third application information of the third client application is not registered in the configuration table.

[0011] As an optional approach, the method further includes: upon detecting a fourth alarm event of the second type triggered within the first client application, reporting the fourth alarm event, wherein the second type is used to indicate that the reporting priority of the fourth alarm event is greater than or equal to a preset priority.

[0012] According to another aspect of the present invention, an alarm event reporting device is also provided, comprising: a register unit, configured to register a first alarm event of a first type triggered within a first client application to an alarm register, wherein the first type is used to indicate that the reporting priority of the first alarm event is less than a preset priority, and the alarm register is used to register alarm events of the first type; a compression unit, configured to compress the first preset number of alarm events of the first type in the alarm register to obtain a target alarm event when the number of alarm events of the first type in the alarm register reaches a first preset number; and a reporting unit, configured to report the target alarm event.

[0013] As an optional solution, the register unit includes: a first register module for registering a first alarm event to a first register area of ​​an alarm register, wherein the first register area is used to register alarm events triggered within a first client application; the device further includes: a second register module for registering a second alarm event to a second register area of ​​an alarm register area when a second alarm event of the first type triggered by a second client application is detected, wherein the second register area is used to register alarm events triggered within a second client application, and the alarm register area includes multiple register areas, with one register area corresponding to one client application.

[0014] As an optional solution, the device further includes: a first configuration module, configured to configure a first preset quantity for the first storage area before compressing a first preset quantity of alarm events of the first type, wherein the first preset quantity is determined based on a first application type of the first client application; the device further includes: a second configuration module, configured to configure a second preset quantity for the second storage area before storing the second alarm event in the second storage area of ​​the alarm storage area, wherein the second preset quantity is determined based on a second application type of the second client application.

[0015] As an optional solution, the device further includes: a registration module, used to register the first application information of the first client application to a configuration table before storing the first alarm event to the alarm register; and a third configuration module, used to configure a component for the first client application according to the first application information after the first application information registration is completed, before storing the first alarm event to the alarm register, wherein the component is used to store the first alarm event triggered within the first client application to the alarm register.

[0016] As an optional solution, the reporting unit includes: a forwarding module, used to forward the target alarm event from the alarm register area to the first client application through a component; and a first reporting module, used to report the target alarm event to the early warning center through the first client application, wherein the early warning center is used to receive the alarm events reported by each client application.

[0017] As an optional solution, the device further includes: a second reporting module, used to report a third alarm event when a third alarm event of the first type triggered within a third client application is detected, wherein the third application information of the third client application is not registered in the configuration table.

[0018] As an optional solution, the device further includes: a third reporting module, used to report the fourth alarm event when a fourth alarm event of the second type triggered within the first client application is detected, wherein the second type is used to indicate that the reporting priority of the fourth alarm event is greater than or equal to a preset priority.

[0019] According to another aspect of the present invention, an electronic device is also provided, including one or more processors and a memory, wherein the memory is used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the alarm event reporting method of any of the above.

[0020] According to another aspect of the present invention, a computer program product is also provided, including a computer program that, when executed by a processor, implements the steps of the alarm event reporting method of any of the above-mentioned embodiments.

[0021] The embodiments provided in this application achieve configurable compression processing of frequent low-priority alarm events by introducing an alarm register. Specifically, when a first type (low priority) alarm event triggered within a first client application is detected, these events are not immediately reported but are instead stored in the alarm register. Then, when the number of events of this type in the alarm register reaches a preset first number, these events are compressed to generate a target alarm event, thereby reducing the repeated reporting of the same or similar low-priority events, avoiding waste of alarm system resources and distraction of monitoring personnel. The embodiments provided in this application allow for flexible configuration of the compression time period and quantity threshold, ensuring that compression and reporting are only performed when low-priority events accumulate to a certain level, while high-priority important alarm events remain unaffected and can be reported immediately. Even when a large number of low-priority alarm events occur, critical high-priority alarms can be quickly identified and responded to, greatly improving the overall efficiency and reliability of the alarm system. This achieves the technical effect of efficiently managing and compressing low-priority alarm events, ensuring that important alarms are processed in a timely manner, and effectively solving the problem of important alarm overload. Attached Figure Description

[0022] The accompanying drawings, which are included to provide a further understanding of the invention and form part of this application, illustrate exemplary embodiments of the invention and, together with their description, serve to explain the invention and do not constitute an undue limitation thereof. In the drawings:

[0023] Figure 1 A hardware block diagram of a computer terminal (or mobile device) for implementing a method for reporting alarm events is shown.

[0024] Figure 2 This is a flowchart of an optional alarm event reporting method according to an embodiment of the present invention.

[0025] Figure 3 This is an optional distributed system architecture interaction diagram according to an embodiment of the present invention.

[0026] Figure 4 This is a schematic diagram of an optional alarm event reporting device according to an embodiment of the present invention.

[0027] Figure 5 This is a structural block diagram of an electronic device according to an embodiment of this application. Detailed Implementation

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

[0029] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0030] It should be noted that the alarm event reporting method and device in this disclosure can be used in the computer field, or in any field other than the computer field. This disclosure does not limit the application field of the alarm event reporting method and device.

[0031] It should be noted that the information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, and displayed data) collected in this public disclosure are information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, storage, use, processing, transmission, provision, disclosure, and application of related data all comply with the relevant laws, regulations, and standards of the relevant regions, necessary confidentiality measures have been taken, and they do not violate public order and good morals. Corresponding operation entry points are provided for users to choose to authorize or refuse. For example, this system has interfaces with relevant users or organizations. Before obtaining relevant information, a request to obtain the information needs to be sent to the aforementioned user or organization through the interface, and the relevant information is obtained only after receiving consent from the aforementioned user or organization.

[0032] It should be noted that in this disclosure, customer information is collected and analyzed, and users are provided with corresponding operation entry points to choose whether to agree to or reject the automated decision results; if the user chooses to reject, the process will proceed to the expert decision-making process.

[0033] The present invention will now be described in detail with reference to various embodiments.

[0034] Example 1

[0035] According to an embodiment of the present invention, an embodiment of a method for reporting alarm events 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.

[0036] The alarm event reporting method embodiment provided in Embodiment 1 of this application can be executed on a mobile terminal, computer terminal or similar computing device. Figure 1 A hardware block diagram of a computer terminal (or mobile device) for implementing a method for reporting alarm events is shown. Figure 1 As shown, computer terminal 10 (or mobile device) may include one or more ( Figure 1 The processor 102 (which may include, but is not limited to, a microprocessor MCU (Microcontroller Unit) or a programmable gate array (FPGA)) is shown as 102a, 102b, ..., 102n. It also includes a memory 104 for storing data and a transmission device 106 for communication functions. In addition, it may include: a display, an input / output interface (I / O interface), a Universal Serial Bus (USB) port (which may be included as one of the ports of a BUS bus), a network interface, a power supply, and / or a camera. Those skilled in the art will understand that... Figure 1 The structure shown is for illustrative purposes only and does not limit the structure of the aforementioned electronic device. For example, computer terminal 10 may also include... Figure 1 The more or fewer components shown, or having the same Figure 1 The different configurations shown.

[0037] It should be noted that the aforementioned one or more processors 102 and / or other data processing circuits are generally referred to herein as "data processing circuits". These data processing circuits may be embodied, in whole or in part, in software, hardware, firmware, or any other combination thereof. Furthermore, the data processing circuits may be a single, independent processing module, or may be integrated, in whole or in part, into any other element within the computer terminal 10 (or mobile device). As involved in the embodiments of this application, the data processing circuits serve as a processor control mechanism (e.g., selection of a variable resistor termination path connected to an interface).

[0038] The memory 104 can be used to store software programs and modules of application software, such as the program instructions / data storage device corresponding to the alarm event reporting method in the embodiments of this application. The processor 102 executes various functional applications and data processing by running the software programs and modules stored in the memory 104, thereby realizing the alarm event reporting method described above. The memory 104 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include memory remotely located relative to the processor 102, and these remote memories can be connected to the computer terminal 10 via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0039] The transmission device 106 is used to receive or send data via a network. Specific examples of the network described above may include a wireless network provided by the communication provider of the computer terminal 10. In one example, the transmission device 106 includes a Network Interface Controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In another example, the transmission device 106 may be a Radio Frequency (RF) module, used for wireless communication with the Internet.

[0040] The display can be, for example, a touchscreen liquid crystal display (LCD), which allows the user to interact with the user interface of the computer terminal 10 (or mobile device).

[0041] Under the aforementioned operating environment, this application provides the following: Figure 2 The method for reporting alarm events is shown. Figure 2 This is a flowchart of an optional alarm event reporting method according to an embodiment of the present invention, such as... Figure 2 As shown, the method includes the following steps:

[0042] S202, when a first alarm event of the first type triggered within the first client application is detected, the first alarm event is registered in the alarm register, wherein the first type is used to indicate that the reporting priority of the first alarm event is less than the preset priority, and the alarm register is used to register the alarm event of the first type.

[0043] S204, when the number of alarm events of the first type in the alarm register reaches a first preset number, the first preset number of alarm events of the first type are compressed to obtain the target alarm event;

[0044] S206, Report target alarm events.

[0045] Optionally, in this embodiment, the first client application refers to an application used by internal or external users of the enterprise. It can be any application that needs to monitor performance and service status, such as a bank transaction processing system or an e-commerce platform back-end management system.

[0046] Optionally, in this embodiment, the first type refers to a specific category of alarm events. These events have a lower reporting priority and are usually associated with minor anomalies in service threads or other non-critical issues. The first alarm event is a single alarm instance belonging to this category.

[0047] Optionally, in this embodiment, the alarm register is an intermediate storage structure used to receive and temporarily store all alarm events of the first type from the first client application. This can be a data structure or a specially designed software component, with the function of filtering and managing frequent but not urgent alarm information.

[0048] Optionally, in this embodiment, the preset priority is the lowest processing level of alarm events set according to the needs of the enterprise or system. Alarm events at a higher level are considered more urgent and important events that require immediate response and processing.

[0049] Optionally, in this embodiment, the first preset quantity is a pre-set threshold used to determine whether the accumulated first-type alarm events in the register are sufficient to warrant compression and generation of a target alarm event. The target alarm event is a compressed alarm event that includes a summary of information from multiple original first-type alarm events, reducing the load on the alarm system while ensuring that monitoring personnel can focus on the overall picture rather than trivial details.

[0050] Optionally, in this embodiment, when a service thread of the first client application triggers a first type of first alarm event due to an execution error or performance problem, the event will not be directly reported to the monitoring system or alarm platform, but will first be sent to the alarm register. This operation aims to reduce the immediate response of the monitoring system to low-priority alarms and prevent its resources from being consumed by unnecessary alarms.

[0051] The alarm register continuously collects first alarm events of the same type until the number of these events reaches a first preset number. When this condition is met, the system compresses the accumulated events, that is, merges them into a single target alarm event with more comprehensive information. This process may involve counting event frequency, summarizing event logs, or analyzing event patterns.

[0052] Once a target alarm event is generated, it will be reported to the monitoring system or the relevant technical support team will be notified. This reporting mechanism ensures that even low-priority events receive appropriate attention after accumulating a certain number, avoiding the omission of critical information or processing delays due to a large number of duplicate alarms.

[0053] It is understood that this embodiment proposes an intelligent management and compression mechanism for low-priority alarm events, especially when faced with a large number of repetitive and non-urgent events. By temporarily storing these events in an alarm register and compressing them after accumulating a certain number, a more valuable target alarm event is formed. This approach not only reduces the processing burden of low-priority events on the monitoring system but also ensures the visibility and response speed of high-priority alarms, thereby improving the overall efficiency of the alarm system and the user experience. Through the embodiment provided in this application, configurable compression processing of frequent low-priority alarm events is achieved by introducing an alarm register. Specifically, when a first type (low-priority) alarm event triggered within a first client application is detected, these events are not immediately reported but are instead stored in the alarm register. Then, when the number of events of this type in the alarm register reaches a preset first number, these events are compressed to generate a target alarm event, thereby reducing the repeated reporting of the same or similar low-priority events and avoiding waste of alarm system resources and distraction of monitoring personnel. The embodiments provided in this application allow for flexible configuration of the compression time period and quantity threshold, ensuring that low-priority events are compressed and reported only when they accumulate to a certain level, while high-priority important alarm events remain unaffected and can be reported immediately. Even when a large number of low-priority alarm events occur, critical high-priority alarms can be quickly identified and responded to, greatly improving the overall efficiency and reliability of the alarm system. This achieves the technical effect of efficiently managing and compressing low-priority alarm events, ensuring that important alarms are processed in a timely manner and effectively solving the problem of important alarm overload.

[0054] As an optional solution, the first alarm event is registered in the alarm register, including:

[0055] The first alarm event is registered to the first register area of ​​the alarm register, wherein the first register area is used to register alarm events triggered within the first client application;

[0056] The method also includes:

[0057] Upon detecting a second alarm event of the first type triggered by a second client application, the second alarm event is registered in a second registration area of ​​the alarm registration area. The second registration area is used to register alarm events triggered within the second client application. The alarm registration area includes multiple registration areas, with one registration area corresponding to one client application.

[0058] Optionally, in this embodiment, the first register area is part of an alarm register, specifically used to store low-priority, first-type alarm events generated by a first client application. Each register area corresponds to a specific client application, ensuring that alarm events from different applications are clearly classified and managed.

[0059] Optionally, in this embodiment, the second register area is similar to the first register area, but is used to store the same type of events from the second client application. This also reflects the regional storage characteristic of the alarm register in this invention, so as to more effectively process and identify alarm information from different sources.

[0060] Optionally, in this embodiment, the alarm register is designed to include a structure with multiple register areas, each corresponding to a different client application. This ensures more granular management of alarm events and avoids interference between alarm information from different applications.

[0061] Optionally, in this embodiment, when a service thread or component within the first client application triggers a low-priority first alarm event of the first type, the event will be registered in the first register area within the alarm register. This employs an application-specific registration strategy to ensure that alarm events for each application can be managed independently, unaffected by events from other applications.

[0062] Similarly, if a second client application also triggers the same type of first alarm event (i.e., the second alarm event), that event will be registered in the second register area. This operation demonstrates the flexibility and scalability of the alarm register, enabling it to adapt to the alarm processing needs of multiple client applications while maintaining the clarity and independence of alarm information.

[0063] The alarm register's alarm storage area is designed with an architecture containing multiple independent storage areas, each corresponding to a different client application. This allows the system to effectively distinguish, manage, and compress events from different applications, even in complex scenarios where multiple applications generate alarm events simultaneously, ensuring the accuracy and timeliness of alarm information.

[0064] The embodiments provided in this application enable the classification and processing of a series of first-type alarm events generated by different client applications by establishing multiple independent register areas in the alarm register. Specifically, each application has its own dedicated register area. When an application triggers an alarm, the system registers the event in the corresponding area, preventing it from being mixed with alarm events from other applications. When the number of events in a certain area reaches a preset threshold, the events in that area are compressed to generate the target alarm event, ensuring the accuracy of alarm information and the relevance of the response. This area-based registering and compression mechanism not only improves the processing efficiency of the alarm system but also makes alarm management more refined, helping to quickly locate problems, reduce invalid responses, and ensure that critical alarm events receive timely attention and processing.

[0065] As an optional approach, before compressing the first preset number of alarm events of the first type, the method further includes:

[0066] Configure a first preset quantity for the first storage area, wherein the first preset quantity is determined based on the first application type of the first client application;

[0067] Before registering the second alarm event to the second register area of ​​the alarm register area, the method further includes:

[0068] Configure a second preset quantity for the second storage area, wherein the second preset quantity is determined based on the second application type of the second client application.

[0069] Optionally, in this embodiment, the first application type refers to the category or nature of the first client application, such as a transaction processing system, a database server, etc. Different application types may have different processing requirements and priority settings for alarm events based on their business characteristics and system architecture differences.

[0070] Optionally, in this embodiment, the first preset quantity is a threshold number of alarm events preset according to the specific situation of the first client application. When this threshold is reached or exceeded, the system will trigger compression processing of these events.

[0071] Optionally, in this embodiment, the second application type is similar to the first application type, but each application type has its own unique business scenario and alarm processing requirements, corresponding to the second client application. The second preset quantity is an alarm event quantity threshold designed specifically for the second client application, used to determine when to compress events of the same type and generate target alarm events for reporting.

[0072] Optionally, in this embodiment, before compressing alarm events of the first type from the first client application, the system needs to configure a specific first preset quantity based on the characteristics of the first application type of the application. The principle for setting this quantity threshold usually considers factors such as the application's business impact, system architecture, alarm frequency, and resource consumption to ensure that alarm compression is effective without missing important monitoring signals.

[0073] Similarly, when processing similar alarm events generated by a second client application, the system also needs to independently configure a second preset quantity based on the characteristics of the second application type. This step demonstrates the flexibility and customizability of the method of the present invention. Different applications or services can set different compression trigger conditions according to their specific needs, thereby managing alarm information more accurately and avoiding resource waste.

[0074] The embodiments provided in this application achieve refined management of low-priority alarm events by configuring independent preset quantities for different client applications. Specifically, each application's storage area has its own exclusive event quantity threshold. These thresholds are determined based on the characteristics of the application type; for example, the alarm threshold for a transaction system may be higher than that for a database server, reflecting its different requirements for real-time performance and fault tolerance. When the number of first-type alarm events in a certain storage area reaches the preset threshold, the system automatically compresses them, generates a target alarm event, and reports it. This mechanism ensures that the compression strategy can adapt to various application scenarios and effectively avoids the problem of important alarms being overwhelmed.

[0075] As an optional approach, the method further includes the following steps before registering the first alarm event to the alarm register:

[0076] Register the first application information of the first client application into the configuration table;

[0077] Once the first application information registration is completed, a component is configured for the first client application based on the first application information. The component is used to register the first alarm event triggered within the first client application to the alarm register.

[0078] Optionally, in this embodiment, the first application information includes the identifier, type, key configuration parameters, etc. of the first client application. This information is crucial for the system to understand application characteristics, set alarm compression strategies, and configure specific components.

[0079] Optionally, in this embodiment, the configuration table is a system-level database or data structure used to store the registration information of all client applications, including but not limited to application type, alarm priority configuration, and related component parameters. The configuration table is a key component for realizing personalized alarm management.

[0080] Optionally, in this embodiment, a component refers to a software component or module designed to interact with the monitoring system and alarm registers to capture, process, and store specific types of alarm events. The configuration and use of components ensure the standardized and efficient management of alarm events.

[0081] Optionally, in this embodiment, when the first client application starts running or is identified in the system, its first application information needs to be registered in the configuration table. This process includes inputting basic information such as the application's identifier and type, as well as a series of monitoring and alarm parameters set according to the application's characteristics, such as the priority of alarm events and the preset number of compression strategies.

[0082] Once the first application information is registered in the configuration table, the system will configure a dedicated component for the first client application based on this information. This component is designed to monitor and capture low-priority alarm events of the first type triggered within the application, and to store these events in the alarm register instead of reporting them directly. The component configuration ensures that the capture and processing of alarm events follow preset rules and parameters, achieving preliminary screening and management of alarm information.

[0083] In accordance with the embodiments provided in this application, to effectively compress and manage frequent low-priority alarm events, it is first necessary to register key information of the first client application, including application type and alarm processing parameters. This information will be entered into a configuration table, becoming the basis for subsequent component configuration and alarm compression strategy settings. Subsequently, the system automatically configures a dedicated component based on the first application information. This component runs within the application and is responsible for identifying and capturing the first type of first alarm events, temporarily storing these events in an alarm register instead of reporting them immediately. This preprocessing mechanism combines the categorized storage of alarm events with on-demand compression, ensuring that important alarms are not overwhelmed, while reducing the processing load on the monitoring system and alarm platform, and improving the efficiency and accuracy of the entire alarm management process.

[0084] As an optional solution, target alarm events are reported, including:

[0085] The component forwards the target alarm event from the alarm register to the first client application.

[0086] The target alarm event is reported to the early warning center through the first client application, and the early warning center is used to receive alarm events reported by each client application.

[0087] Optionally, in this embodiment, the early warning center is an integrated monitoring platform or system designed to receive, analyze, and respond to alarm events from various client applications. The early warning center acts as a centralized processing center for alarm events, ensuring that all reported events are handled promptly and appropriately.

[0088] Optionally, in this embodiment, forwarding refers to the transmission process of the target alarm event from the register area of ​​the alarm register to the first client application. During this process, the information of the target alarm event is updated and prepared to meet the requirements and format of the early warning center, ensuring that the alarm event can be correctly understood and responded to.

[0089] Optionally, in this embodiment, after compressing the first type of alarm event and generating the target alarm event, the target alarm event is retrieved from the alarm register using a component previously configured in the first client application. This target event is then formatted, supplemented with necessary information, and forwarded to the first client application. This operation ensures that the target alarm event carries sufficient information and context for accurate analysis and response by the early warning center.

[0090] Once a target alarm event is processed by the component and reaches the first client application, the application will report it to the early warning center. As the central hub for receiving and analyzing alarm events, the early warning center can immediately activate corresponding early warning and response mechanisms based on the nature and severity of the event, ensuring that critical issues are addressed and resolved in a timely manner.

[0091] The embodiments provided in this application first compress low-priority frequent alarm events within the alarm register to generate target alarm events. This process is executed by a dedicated component, ensuring that the filtering and organization of events conforms to the preset alarm management strategy. Subsequently, the component forwards the target alarm event back to the first client application. After confirming the completeness of the event information, the application reports it to the early warning center. As the core of the entire monitoring system, the early warning center can quickly respond to and prioritize the processing of these compressed important alarms, avoiding interference and resource waste caused by a large number of duplicate alarm events, and ensuring that genuine emergencies can be quickly detected and handled. This phased alarm management and early warning mechanism not only optimizes the response efficiency of the monitoring system but also enhances its intelligence and adaptability, significantly improving the operation and maintenance and troubleshooting of large-scale distributed systems.

[0092] As an alternative approach, the method also includes:

[0093] If a third alarm event of the first type is detected within a third client application, the third alarm event is reported. The third application information of the third client application is not registered in the configuration table.

[0094] Optionally, in this embodiment, the third client application refers to a client application that has not yet completed information registration in the system. It may fail to register its application information, including alarm handling strategies, in the configuration table for various reasons (such as new deployment, temporary access, etc.).

[0095] Optionally, in this embodiment, the third application information is similar to the first and second application information, including the application's identifier, type, alarm priority configuration, etc., but due to the special nature of the third client application, its information has not yet been registered in the configuration table.

[0096] Optionally, in this embodiment, when a third client application triggers a third alarm event of the first type, namely a low-priority alarm event that has not been pre-configured with a compression strategy by the system, the monitoring system will immediately identify this event.

[0097] Since the third application information is not registered in the configuration table, the system determines that there is no need to compress the third alarm event. In this case, in order to ensure that all alarm events can be responded to and processed in a timely manner, this embodiment stipulates that the third alarm event is directly reported to the early warning center, that is, the alarm information is sent in its original state without temporary storage or compression.

[0098] According to the embodiments provided in this application, when a third-party client application that has not registered its information triggers a first-type alarm event, the system adopts a direct reporting strategy. That is, the event information is sent directly to the early warning center without going through the storage and compression of the alarm register. This mechanism aims to ensure that alarm events generated by applications that are not configured by the system can also receive a timely response, avoiding potential risks caused by delayed or missing information registration. Furthermore, the direct reporting strategy is applicable to all types of applications, ensuring that even in the absence of specific configurations, the early warning center can receive all alarm information for subsequent analysis and processing.

[0099] As an alternative approach, the method also includes:

[0100] If a fourth alarm event of the second type is detected within the first client application, the fourth alarm event is reported. The second type indicates that the reporting priority of the fourth alarm event is greater than or equal to the preset priority.

[0101] Optionally, in this embodiment, the second type is a classification of alarm events. The second type indicates that the priority of the event is higher than or equal to the preset priority set by the system, which means that such events need to be paid attention to and responded to immediately and cannot be delayed or compressed.

[0102] Optionally, in this embodiment, during the operation of the first client application, if the monitoring system detects a fourth alarm event of the second type, that is, a high-priority or urgent alarm, this event will not be compressed into the alarm register, but will be directly identified as a situation that needs immediate attention.

[0103] Unlike the low-priority Type 1 alarm events, the fourth alarm event, due to its high priority, skips the compression process and is reported directly from the first client application to the early warning center. This reporting method ensures that emergencies can be responded to in a timely manner, avoiding response delays that may be caused by compression waiting.

[0104] The embodiments provided in this application not only focus on the intelligent compression processing of low-priority alarm events, but also fully consider the urgency of high-priority events. For fourth alarm events of the second type triggered within the first client application, since the reporting priority of such events reaches or exceeds the preset priority, the system is designed with a direct reporting mechanism, which directly sends the event information to the early warning center without going through the storage and compression process of the alarm register.

[0105] As an optional approach, the aforementioned alarm reporting method can be applied to configurable monitoring alarm compression scenarios. In this scenario, with the development of technologies such as servers, clients, and PaaS cloud, traditional businesses are experiencing explosive growth online via internet platforms. Simultaneously, this places certain challenges on the performance and stability of backend programs. Many enterprises, in order to improve customer service experience, have simultaneously built multiple high-availability environments on the backend, providing services to the channel side through load balancing strategies. To ensure timely notification of technical personnel for repairs when an environment becomes unavailable, monitoring of backend services is essential, such as the availability status of the APP server, the database server, and whether certain threads deployed in the backend services are running normally.

[0106] In certain scenarios, abnormal execution of certain threads may frequently trigger alerts on the monitoring platform. For example, if a thread encounters an error during execution, it will frequently send alerts to the monitoring platform. When the monitoring platform receives such alerts frequently over a period of time, it can cause other important alert events to be overlooked, thus affecting the discovery of important alert events by technical personnel.

[0107] This embodiment proposes a configurable compression method that supports frequent monitoring alarms. It can perform configurable compression for various types of alarms, ensuring that important alarms are not buried and can be promptly addressed by application support and R&D personnel for emergency handling.

[0108] Optionally, in this embodiment, a distributed caching application based on the underlying storage engine is deployed, and a high-speed cache information access component is developed for its own architecture. When the service thread of the application executes abnormally and frequently alarms, it is stored in the distributed caching application through the access component, and the decision to send an alarm to the application monitoring platform is made according to the compression time period configured in the configuration file, thereby realizing the compression of backend thread monitoring alarms within the enterprise.

[0109] To further illustrate, an architectural interaction diagram of a distributed system is as follows: Figure 3 The diagram illustrates the collaboration logic between the configuration center, multiple applications, distributed cache, and alarm monitoring platform. The specific process is as follows:

[0110] Registration: Application 1, Application 2... Application N will all send a "registration" request to the configuration center to complete their own identity registration / registration in the system.

[0111] Component distribution: The configuration center distributes components (configuration files, functional components, and other resources) to all registered applications to ensure that each application obtains the corresponding runtime configuration.

[0112] Alarm information reporting: Taking application 1 as an example, application 1 stores alarm information in a distributed cache. When the number of alarm information of application 1 in the distributed cache reaches a certain number, it is compressed into one alarm information, which is then pulled by application 1 and sent to the alarm monitoring platform.

[0113] Example 2

[0114] The alarm event reporting device provided in this embodiment includes multiple implementation units, each of which corresponds to a specific implementation step in the above embodiment one. The specific implementation method and beneficial effects can be referred to the aforementioned method embodiment, and will not be repeated here.

[0115] Figure 4 This is a schematic diagram of an optional alarm event reporting device according to an embodiment of the present invention, such as... Figure 4 As shown, the alarm event reporting device may include:

[0116] The register unit 402 is used to register the first alarm event to the alarm register when a first alarm event of the first type triggered in the first client application is detected. The first type is used to indicate that the reporting priority of the first alarm event is less than the preset priority, and the alarm register is used to register the alarm event of the first type.

[0117] Compression unit 404 is used to compress the first preset number of first type alarm events to obtain the target alarm event when the number of first type alarm events detected in the alarm register reaches a first preset number.

[0118] Reporting unit 406 is used to report target alarm events.

[0119] As an optional solution, register unit 402 includes:

[0120] The first register module is used to register the first alarm event to the first register area of ​​the alarm register, wherein the first register area is used to register alarm events triggered within the first client application;

[0121] The device also includes:

[0122] The second register module is used to register the second alarm event to the second register area of ​​the alarm register area when a second alarm event of the first type triggered by the second client application is detected. The second register area is used to register alarm events triggered within the second client application. The alarm register area includes multiple register areas, and one register area corresponds to one client application.

[0123] As an optional solution, the device also includes:

[0124] The first configuration module is used to configure a first preset quantity for the first storage area before compressing a first preset quantity of alarm events of the first type, wherein the first preset quantity is determined based on the first application type of the first client application;

[0125] The device also includes:

[0126] The second configuration module is used to configure a second preset quantity for the second storage area before storing the second alarm event in the second storage area of ​​the alarm storage area, wherein the second preset quantity is determined based on the second application type of the second client application.

[0127] As an optional solution, the device also includes:

[0128] The registration module is used to register the first application information of the first client application in the configuration table before storing the first alarm event in the alarm register;

[0129] The third configuration module is used to configure a component for the first client application based on the first application information before the first alarm event is registered in the alarm register. The component is used to register the first alarm event triggered within the first client application in the alarm register.

[0130] As an optional solution, reporting unit 406 includes:

[0131] The forwarding module is used to forward target alarm events from the alarm register to the first client application via components;

[0132] The first reporting module is used to report target alarm events to the early warning center through the first client application. The early warning center is used to receive alarm events reported by each client application.

[0133] As an optional solution, the device also includes:

[0134] The second reporting module is used to report the third alarm event when a third alarm event of the first type is detected within the third client application. The third application information of the third client application is not registered in the configuration table.

[0135] As an optional solution, the device also includes:

[0136] The third reporting module is used to report the fourth alarm event when a fourth alarm event of the second type is detected within the first client application. The second type is used to indicate that the reporting priority of the fourth alarm event is greater than or equal to the preset priority.

[0137] The alarm event reporting device may also include a processor and a memory. The aforementioned register unit 402, compression unit 404, reporting determination unit 406, etc., are all stored in the memory as program units, and the processor executes the aforementioned program units stored in the memory to realize the corresponding functions.

[0138] The processor described above contains a kernel, which retrieves the corresponding program units from memory. One or more kernels can be configured, and alarm event reporting can be implemented by adjusting kernel parameters.

[0139] The aforementioned memory may include non-permanent memory in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM, and the memory includes at least one memory chip.

[0140] Example 3

[0141] Embodiments of this application may provide an electronic device. Figure 5 This is a structural block diagram of an electronic device for performing an alarm event reporting method according to an embodiment of this application. Figure 5 As shown, the electronic device may include: one or more ( Figure 5 (Only one is shown) processor 502, memory 504, memory controller, and peripheral interface, wherein the peripheral interface is connected to the radio frequency module, audio module and display.

[0142] The memory can be used to store software programs and modules, such as the program instructions / modules corresponding to the alarm event reporting method and device in this embodiment. The processor executes various functional applications and data processing by running the software programs and modules stored in the memory, thereby realizing the alarm event reporting method described above. The memory may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory may further include memory remotely located relative to the processor, and these remote memories can be connected to the terminal via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0143] The processor can invoke information and applications stored in the memory via the transmission device to perform the following steps: in response to a first backup request triggered by a first resource of a first shared client, verifying the resource type of the first resource; if the resource type of the first resource is a shared resource type, determining the target source resource corresponding to the first resource on the shared server associated with the first shared client, wherein the shared server is used to share at least one source resource with at least two clients, the at least one source resource includes the target source resource, and the at least two clients include the first shared client; and copying the target source resource from the shared server to the backup server.

[0144] Those skilled in the art will understand that Figure 5 The structure shown is for illustrative purposes only. Electronic devices can also be smartphones, tablets, handheld computers, mobile internet devices (MIDs), PADs, and other terminal devices. Figure 5 This does not limit the structure of the aforementioned electronic device. For example, electronic devices may also include components that are more... Figure 5 The more or fewer components shown (such as network interfaces, display devices, etc.), or having the same Figure 5 The different configurations shown.

[0145] Those skilled in the art will understand that all or part of the steps in the various alarm event reporting methods of the above embodiments can be implemented by a program instructing the hardware related to the terminal device. The program can be stored in a computer-readable storage medium, which may include: flash drive, read-only memory (ROM), random access memory (RAM), disk or optical disk, etc.

[0146] Example 4

[0147] Embodiments of this application also provide a storage medium. Optionally, in this embodiment, the storage medium can be used to store the program code executed by the alarm event reporting method provided in Embodiment 1.

[0148] According to another aspect of the present invention, a computer-readable storage medium is also provided, the computer-readable storage medium including a stored computer program, wherein, when the computer program is running, it controls the device where the computer-readable storage medium is located to execute the alarm event reporting method of any one of the above embodiments.

[0149] Optionally, in this embodiment, the storage medium may be located in any computer terminal in a group of computer terminals in a computer network, or in any mobile terminal in a group of mobile terminals.

[0150] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the alarm event reporting method in various embodiments of this application.

[0151] This application also provides a computer program product, including a non-volatile computer-readable storage medium storing a computer program. When the computer program is executed by a processor, it implements the steps of the alarm event reporting method in various embodiments of this application.

[0152] The sequence numbers of the above embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0153] In the above embodiments of the present invention, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0154] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units can be a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual couplings, direct couplings, or communication connections may be through some interfaces; indirect couplings or communication connections between units or modules may be electrical or other forms.

[0155] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0156] Furthermore, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0157] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, read-only memory (ROM), random access memory (RAM), portable hard drives, magnetic disks, or optical disks.

[0158] The above are merely preferred embodiments of the present invention. It should be noted that those skilled in the art can make various improvements and modifications without departing from the principle of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.

Claims

1. A method for reporting alarm events, characterized in that, include: Upon detecting a first alarm event of the first type triggered within the first client application, the first alarm event is registered in an alarm register, wherein the first type is used to indicate that the reporting priority of the first alarm event is less than a preset priority, and the alarm register is used to register alarm events of the first type. When the number of alarm events of the first type in the alarm register reaches a first preset number, the first preset number of alarm events of the first type are compressed to obtain the target alarm event. The target alarm event is reported.

2. The method according to claim 1, characterized in that, The step of registering the first alarm event to the alarm register includes: The first alarm event is registered to the first register area of ​​the alarm register, wherein the first register area is used to register alarm events triggered within the first client application; The method further includes: Upon detecting a second alarm event of the first type triggered by a second client application, the second alarm event is stored in a second storage area of ​​the alarm storage area. The second storage area is used to store alarm events triggered within the second client application. The alarm storage area includes multiple storage areas, with one storage area corresponding to one client application.

3. The method according to claim 2, characterized in that, Before compressing the first preset number of alarm events of the first type, the method further includes: Configure the first preset quantity for the first storage area, wherein the first preset quantity is determined based on the first application type of the first client application; Before registering the second alarm event to the second register area of ​​the alarm register area, the method further includes: Configure a second preset quantity for the second storage area, wherein the second preset quantity is determined based on the second application type of the second client application.

4. The method according to claim 1, characterized in that, Before registering the first alarm event to the alarm register, the method further includes: Register the first application information of the first client application into the configuration table; When the first application information registration is completed, a component is configured for the first client application according to the first application information, wherein the component is used to store the first alarm event triggered in the first client application to the alarm register.

5. The method according to claim 4, characterized in that, The reporting of the target alarm event includes: The component forwards the target alarm event from the alarm register to the first client application. The first client application reports the target alarm event to the early warning center, wherein the early warning center is used to receive alarm events reported by each client application.

6. The method according to claim 4, characterized in that, The method further includes: If a third alarm event of the first type is detected within a third client application, the third alarm event is reported, wherein the third application information of the third client application is not registered in the configuration table.

7. The method according to any one of claims 1 to 6, characterized in that, The method further includes: If a fourth alarm event of the second type is detected within the first client application, the fourth alarm event is reported, wherein the second type is used to indicate that the reporting priority of the fourth alarm event is greater than or equal to the preset priority.

8. A device for reporting alarm events, characterized in that, include: The register unit is used to register the first alarm event to the alarm register when a first alarm event of the first type is detected within the first client application, wherein the first type is used to indicate that the reporting priority of the first alarm event is less than the preset priority, and the alarm register is used to register the alarm event of the first type. The compression unit is used to compress the first preset number of alarm events of the first type in the alarm register to obtain the target alarm event when the number of alarm events of the first type in the alarm register reaches a first preset number. The reporting unit is used to report target alarm events.

9. An electronic device, characterized in that, The method includes one or more processors and a memory for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors cause the one or more processors to implement the method of any one of claims 1 to 7.

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the method described in any one of claims 1 to 7.

Images