Platform alarm method, device, electronic device, storage medium and program product

Abstract

The present application discloses a platform alarm method, device, electronic device, storage medium and program product, the method comprising: using the collectors corresponding to the different types of resource devices managed by the target platform to collect the equipment performance indicators of all resource devices; generating resource alarm information based on the collected equipment performance indicators and the stored resource alarm strategy; and pushing resource alarm notifications to the target platform according to the resource alarm information. In the platform alarm device, multiple collectors are integrated, each collector collects the equipment performance indicators of a resource device, and the resource devices can be quickly connected through the collectors, so that the collection of various types of resource devices managed by the target platform is integrated, which is conducive to calculating resource alarm information, and pushing alarm notifications to the target platform according to the resource alarm information to realize platform alarm, without the need to maintain data collection work of different devices on the target platform and calculate alarms, thereby reducing the error rate of the target platform.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a platform alarm method, device, electronic device, storage medium and program product. Background Art

[0002] With the application of cloud computing, big data, and mobile Internet, data traffic is increasing day by day. It is becoming increasingly important for platforms that manage more and more devices to monitor the operating status of devices.

[0003] Currently, on the platform, device status data is collected according to the device's external interface, and then a customized alarm strategy and the collected data are used to calculate whether an alarm is generated.

[0004] However, due to the inconsistency of external interfaces of different devices, the platform's subsequent maintenance workload is relatively large, and the platform's use of its own designed calculation logic combined with alarm strategies and collected data for alarm calculation is relatively complex, which leads to a relatively high error rate of the platform. Summary of the invention

[0005] The purpose of this application is to propose a platform alarm method, device, electronic device, storage medium and program product to address the deficiencies of the above-mentioned prior art, and this purpose is achieved through the following technical solutions.

[0006] The first aspect of the present application proposes a platform alarm method, which is applied to a platform alarm device, wherein the device is configured with collectors corresponding to various types of resource devices managed by a target platform, and the method comprises:

[0007] Using collectors corresponding to the multiple types of resource devices, respectively, to collect device performance indicators of all resource devices managed by the target platform;

[0008] Generate resource alarm information based on the collected equipment performance indicators and stored resource alarm policies;

[0009] A resource alarm notification is pushed to the target platform according to the resource alarm information.

[0010] A second aspect of the present application provides a platform alarm device, the device comprising: a monitoring component and an alarm processing component, the monitoring component being configured with collectors corresponding to various types of resource devices managed by the target platform;

[0011] The monitoring component is used to collect device performance indicators of all resource devices managed by the target platform using collectors corresponding to the various types of resource devices; and generate resource alarm information based on the collected device performance indicators and the stored resource alarm strategy;

[0012] The alarm processing component is used to push resource alarm notifications to the target platform according to the resource alarm information.

[0013] The third aspect of the present application proposes an electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the method described in the first aspect above.

[0014] A fourth aspect of the present application provides a computer-readable storage medium having a computer program stored thereon, wherein the program is executed by a processor to implement the method described in the first aspect above.

[0015] An embodiment of the fifth aspect of the present application provides a computer program product, including a computer program, wherein the computer program is executed by a processor to implement the method described in the first aspect above.

[0016] Based on the platform alarm method, device, electronic device, storage medium and program product described above, the present application has at least the following beneficial effects or advantages:

[0017] By connecting multiple collectors to the platform alarm device, each collector is responsible for collecting the equipment performance indicators of one type of resource equipment. The collector can quickly connect to the resource equipment managed by the target platform and collect data, so as to integrate the collection of various types of resource equipment managed on the target platform. It is beneficial to use the collected equipment performance indicators and resource alarm strategies to calculate resource alarm information, and push resource alarm notifications to the target platform based on the resource alarm information to realize platform alarm, without the need to maintain data collection work for different devices on the target platform and calculate alarms, thereby reducing the error rate of the target platform.

[0018] The above description is only an overview of the technical solution of the present application. In order to more clearly understand the technical means of the present application, it can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the present application more obvious and easy to understand, the specific implementation methods of the present application are listed below. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0020] Figure 1 It is a structural schematic diagram of a platform alarm device according to an exemplary embodiment;

[0021] Figure 2 The present invention is a flow chart of an embodiment of a platform alarm method according to an exemplary embodiment;

[0022] Figure 3 A resource alarm workflow diagram according to an exemplary embodiment is shown;

[0023] Figure 4 A business alarm workflow diagram according to an exemplary embodiment is shown;

[0024] Figure 5 is a schematic diagram of a hardware structure of an electronic device according to an exemplary embodiment;

[0025] Figure 6 The figure is a schematic diagram of the structure of a storage medium according to an exemplary embodiment. DETAILED DESCRIPTION

[0026] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of systems and methods consistent with some aspects of the present application as detailed in the appended claims.

[0027] The terms used in this application are for the purpose of describing specific embodiments only and are not intended to limit this application. The singular forms of "a", "said" and "the" used in this application and the appended claims are also intended to include plural forms unless the context clearly indicates other meanings. It should also be understood that the term "and / or" used herein refers to and includes any or all possible combinations of one or more associated listed items.

[0028] It should be understood that although the terms first, second, third, etc. may be used in the present application to describe various information, these information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of the present application, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining".

[0029] In addition, it should be noted that the user 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, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0030] The existing solution is to collect device status data on the platform according to the interface provided by the device, and calculate alarms through alarm strategies and collected data. As the platform manages more and more devices, and the interfaces of each device series or each manufacturer's equipment are inconsistent, this leads to a large workload for later maintenance of the platform. In addition, the platform uses its own designed calculation logic for alarm calculation, which is more complicated, resulting in a relatively high error rate of the platform.

[0031] In order to solve the above technical problems, the present application proposes a platform alarm solution, which implements platform alarms based on a platform alarm device, avoids the use of complex logical operations and data collection work on the platform, and connects the platform alarm device to multiple collectors. Each collector is responsible for collecting equipment performance indicators of a type of resource equipment managed by the platform. The collector can quickly connect to the resource equipment and collect data, so that the platform alarm device integrates the collection of various types of resource equipment managed on the platform into one, which is beneficial for the platform alarm device to use the collected equipment performance indicators and resource alarm strategies to calculate resource alarm information, and push resource alarm notifications to the platform based on the resource alarm information to realize platform alarms, without the need to maintain data collection work for different devices on the platform and calculate alarms, thereby reducing the error rate of the platform.

[0032] The technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems are described in detail below with specific embodiments. The several specific embodiments listed can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described in detail below with reference to the accompanying drawings.

[0033] See also Figure 1 , Figure 1 The present invention is a schematic diagram of a structure of a platform alarm device according to an exemplary embodiment, wherein the platform alarm device comprises: a monitoring component and an alarm processing component, wherein collectors corresponding to various types of resource devices managed by a target platform are configured on the monitoring component;

[0034] The monitoring component is used to collect device performance indicators of all resource devices managed by the target platform using collectors corresponding to the multiple types of resource devices, and generate resource alarm information based on the collected device performance indicators and the stored resource alarm strategy;

[0035] The alarm processing component is used to push resource alarm notifications to the target platform according to the resource alarm information.

[0036] The above-mentioned target platform can be understood as a device that needs to be monitored. On the target platform, users can define resource alarm strategies in combination with different resource devices to be managed, thereby pushing resource alarm strategies to monitoring components and receiving resource alarm notifications pushed by alarm processing components for users to view.

[0037] The above monitoring component can be understood as an open source service monitoring device, which is responsible for collecting data and generating resource alarm information in combination with resource alarm strategies. In addition to the collector, the monitoring component can also be configured with some other basic information, including the resource alarm strategy loading directory, data acquisition time interval, and alarm generation push target (i.e., alarm processing component information).

[0038] The above-mentioned alarm processing component can be understood as an alarm management tool, which is used to process the alarm information from the monitoring component to push alarm notifications to the target platform.

[0039] The collector can be understood as an open source indicator collector. The available collectors are determined based on the types of resource devices managed on the target platform, and these collectors are configured on the monitoring component. Each collector is responsible for collecting device performance indicators of one type of resource devices, without considering the external interfaces provided by different resource devices.

[0040] In an embodiment of the present application, multiple collectors are connected to the monitoring component, each collector is responsible for collecting the equipment performance indicators of one type of resource equipment. The collector can quickly connect to the resource equipment and perform data collection, so that the monitoring component integrates the collection of various types of resource equipment managed on the target platform into one, which is beneficial for the monitoring component to use the collected equipment performance indicators and resource alarm strategies to calculate resource alarm information, and push resource alarm notifications to the target platform based on the resource alarm information to realize platform alarms, without the need to maintain data collection work for different devices on the target platform and calculate alarms, thereby reducing the error rate of the target platform.

[0041] In some optional embodiments of the present application, the collector configured on the monitoring component may include: at least one of: SNMPExporter (Simple Network Management Protocol Exporter), Blackbox Exporter (Blackbox Exporter) and NodeExporter (Node Exporter).

[0042] like Figure 1As shown in the figure, the types of resource devices managed by the target platform can be divided into three categories: network device class, site server class and host class. Among them, resource devices belonging to the network device class can be regarded as devices used for data transmission and network management, which are mainly responsible for connecting, forwarding data, managing network traffic, etc. For example, switches, routers, firewalls, gateways, etc. all belong to the network device class. Resource devices belonging to the site server class can be regarded as servers that provide specific services in the network, usually used to carry services such as websites and applications. For example, application servers, Web servers, mail servers, etc. all belong to the site server class. Resource devices belonging to the host class can be regarded as physical devices used for virtualization platforms, which are mainly used to run virtual machines or easy to provide computing and storage resources. For example, physical servers, storage servers, etc. all belong to the host class.

[0043] Accordingly, SNMP Exporter queries the management information base on the device through the SNMP protocol to extract the performance indicators and status information of the device. Since network devices usually have SNMP services, SNMP Exporter is suitable for querying network device classes.

[0044] Blackbox Exporter is mainly used to monitor the accessibility of external services or network sites. It supports multiple protocols such as HTTP (Hypertext Transfer Protocol), HTTPS (Hypertext TransferProtocol Secure), TCP (Transmission Control Protocol), ICMP (Internet Control Message Protocol), etc. It can detect the availability of services and express the results in the form of indicators. Therefore, Blackbox Exporter is suitable for querying site servers.

[0045] Node Exporter obtains the running information of the host node by accessing system files, calling system commands or using certain libraries. Node Exporter is mainly used to collect system information and hardware information on the host node and export it in the form of indicators, such as memory usage, disk usage, system load, etc. Therefore, Node Exporter is suitable for querying the host class.

[0046] In this embodiment, collectors such as SNMP Exporter, Blackbox Exporter and Node Exporter are configured on the monitoring component to respectively implement data collection of resource devices of network device type, site server type and host machine type without considering the interface of each resource device, thereby simplifying the data collection work.

[0047] In some optional embodiments of the present application, such as Figure 1 As shown, the platform alarm device may also include:

[0048] The intermediate component is used to obtain the service performance indicators of the configured services on the target platform from the target platform, and convert the service performance indicators according to a preset format;

[0049] and, the monitoring component is further used to obtain the converted business performance indicators from the intermediate component, and generate business alarm information based on the obtained business performance indicators and the stored business alarm policies;

[0050] The alarm processing component is also used to push business alarm notifications to the target platform based on the business alarm information.

[0051] The above-mentioned intermediate component can be understood as a transfer station for business performance indicators, which is used to solve the problem that the monitoring component cannot directly obtain certain monitoring indicators. Exemplarily, by creating a scheduled task on the target platform, the task extracts business performance indicators according to the configured business at a specified interval period, and sends the business performance indicators to the intermediate component according to the interface format of the intermediate component. The intermediate component converts the business performance indicators pushed by the target platform according to a preset format and stores them. The preset format is a format recognizable by the monitoring component.

[0052] Furthermore, the monitoring component is configured with a business alarm policy loading directory, the location of the intermediate component, etc., so that the monitoring component can fetch the business performance indicators of the configured business on the target platform from the intermediate component according to the location of the intermediate component for alarm calculation.

[0053] In this embodiment, an intermediate component is used as a transfer station between the target platform and the monitoring component to push the business performance indicators of the business on the target platform to the monitoring component in a form that the monitoring component can understand, thereby realizing business alarms on the target platform.

[0054] In some optional embodiments of the present application, such as Figure 1 As shown, the platform alarm device may also include:

[0055] Visualization component, used to display the collected device performance indicators and collection time.

[0056] In this embodiment, the monitoring component is connected to an open source visualization component to display the device performance indicators collected by the monitoring component at different time points for users to view and understand.

[0057] It can be understood that the platform alarm device described in the embodiment of the present application is for more clearly illustrating the technical solution of the embodiment of the present application, and does not constitute a limitation on the technical solution provided in the embodiment of the present application. Ordinary technicians in this field can know that with the evolution of the device architecture and the emergence of new business scenarios, the technical solution provided in the embodiment of the present application is also applicable to similar technical problems.

[0058] Figure 2 is a flow chart of an embodiment of a platform alarm method according to an exemplary embodiment. Figure 1 The platform alarm device shown is an execution subject to illustrate the platform alarm method, such as Figure 2 As shown, the following steps are included:

[0059] Step 201: using collectors corresponding to various types of resource devices managed by the target platform, collect device performance indicators of all resource devices managed by the target platform;

[0060] Step 202: Generate resource alarm information based on the collected device performance indicators and the stored resource alarm strategy;

[0061] Step 203: Push a resource alarm notification to the target platform according to the resource alarm information.

[0062] According to the above description, the device performance indicators collected by the collector include device performance indicators belonging to the network device class, device performance indicators belonging to the site server class, and device performance indicators belonging to the host class. Different collectors can collect different data information.

[0063] For example, the device performance indicators collected by the collector belonging to the network device class may include various indicators such as memory usage, interface status, network traffic, CPU (Central Processing Unit) utilization, etc. The device performance indicators collected by the collector belonging to the site server class may include various indicators such as network delay, service availability, certificate validity, etc. The device performance indicators collected by the collector belonging to the host class may include various indicators such as memory usage, disk usage, system load, etc.

[0064] Resource alarm policy refers to the customized alarm policy for resource devices managed by the target platform. It may include policy name, device performance indicator rules, severity level, resource device name, etc. Different resource devices use different resource alarm policies for different device performance indicators. Users can set different resource alarm policies according to actual needs.

[0065] Taking a firewall as an example, the corresponding resource alarm policies may include policies for memory usage, policies for interface status, and policies for network traffic.

[0066] It can be seen from this that when generating resource alarm information based on the collected equipment performance indicators and the stored resource alarm policies, for each equipment performance indicator, the resource alarm policy corresponding to the resource equipment to which the equipment performance indicator belongs is used to calculate whether resource alarm information is generated for the equipment performance indicator.

[0067] Resource alarm information refers to the specific alarm content generated by calculation, which may include the alarm subject, alarm description, severity level, etc.

[0068] Resource alarm notifications can be understood as alarm notifications generated after unified processing of original resource alarm information and ultimately pushed to the target platform. The number of resource alarm notifications is usually less than or equal to the number of resource alarm information, which can ensure the reliability and stability of the target platform.

[0069] At this point, the above Figure 2 The platform alarm process shown integrates multiple collectors, each of which is responsible for collecting the equipment performance indicators of one type of resource equipment. The collector can quickly connect to the resource equipment and collect data, so as to integrate the collection of various types of resource equipment managed on the target platform into one, which is conducive to using the collected equipment performance indicators and resource alarm strategies to calculate resource alarm information, and push resource alarm notifications to the target platform based on the resource alarm information to realize platform alarms, without the need to maintain data collection work for different devices on the target platform and calculate alarms, thereby reducing the error rate of the target platform.

[0070] In an optional embodiment of the present application, before executing step 201, a configuration process of the collector may also be included:

[0071] Obtain a first configuration file for the collector corresponding to each type of resource device, and obtain a second configuration file for each resource device managed by the target platform. For the collector corresponding to each type of resource device, generate a collector configuration file based on the first configuration file and the second configuration file. The collector configuration file includes at least the access address of the collector corresponding to the current type of resource device and the access addresses of all resource devices of the current type managed by the target platform.

[0072] Based on the above description, the first configuration file can be understood as a configuration file for configuring the collector to the monitoring component, and the file format can be yalm. The first configuration file at least includes the access address of the collector, and of course can also include the file directory location of the target to be collected.

[0073] The second configuration file is a file that configures the resource device as the collection target of the collector. The file format can be the format required by the collector, such as json format. The second configuration file includes at least the access address of the resource device. In addition, it can also include the resource ID of the resource device. According to the resource ID, the detailed information of the resource device can be reversed to enrich the alarms pushed to the user.

[0074] When generating a collector configuration file, the second configuration file of the resource device can be placed in the file directory location recorded in the first configuration file of the collector corresponding to the type of the resource device, thereby obtaining the collector configuration file. It is worth noting here that the file directory location recorded in the first configuration file of the collector contains the second configuration files of multiple resource devices, and these resource devices all belong to the resource device type corresponding to the collector. Therefore, when collecting data, the collector is used to execute each second configuration file in turn to collect the device performance indicators of each resource device respectively.

[0075] Exemplarily, the collectors may include SNMP Exporter, Blackbox Exporter and NodeExporter. The first configuration file of each collector needs to be configured on the monitoring component. According to the types of resource devices managed on the target platform, the adoptable collectors are determined, and the second configuration files of each resource device are placed in the file directory location indicated by the corresponding collector. For example, the collector used for resource devices belonging to the network device category is SNMP Exporter, and the second configuration files of resource devices such as routers, firewalls, and switches are placed in the file directory location indicated by SNMPExporter.

[0076] In this embodiment, by pre-configuring the collector to be used and placing the configuration files of each resource device into the file directory location of the corresponding collector according to the type of the resource device, it is possible to flexibly manage the data collection work of different resource devices and simplify configuration management and monitoring expansion.

[0077] In an optional embodiment of the present application, the process of step 203 may include:

[0078] Deduplication is performed on the resource alarm information, and based on the deduplication-processed resource alarm information, resource alarm notifications are pushed to the target platform.

[0079] The deduplication process is to retain the resource alarm information with the highest severity level among multiple resource alarm information of the same alarm type belonging to the same resource device.

[0080] In this embodiment, resource alarm information is deduplicated so that the most serious of the same resource alarm information is pushed to the target platform in the form of an alarm notification, thereby avoiding multiple notifications of the same alarm problem and ensuring the stability and reliability of the target platform.

[0081] In another optional embodiment of the present application, the process of step 203 may include:

[0082] The resource alarm information is grouped according to the type of resource equipment, and the alarm notification is pushed to the target platform according to the grouping result; and / or, the resource alarm information is grouped according to the alarm type, and the alarm notification is pushed to the target platform according to the grouping result.

[0083] Exemplarily, resource alarm information is divided into network device groups, site server groups, host groups, etc. according to the types of resource devices. Resource alarm information of the network device group is pushed to the target platform as a resource alarm notification, and so on.

[0084] Alternatively, the resource alarm information is divided into a memory usage group, a disk usage group, etc. according to the alarm type. The resource alarm information of the memory usage group is pushed to the target platform as a resource alarm notification, and so on.

[0085] In this embodiment, by aggregating resource alarm information into groups according to resource device dimensions and / or alarm type dimensions, and pushing resource alarm notifications according to the grouping results, a large amount of alarm information can be effectively managed.

[0086] In an optional embodiment of the present application, the following service alarm process may also be included:

[0087] Receive the business performance indicators of the configured business on the target platform sent by the target platform, convert the business performance indicators according to the preset format, generate business alarm information based on the converted business performance indicators and the stored business alarm strategy, and then push business alarm notifications to the target platform according to the business alarm information.

[0088] The service performance indicator can be understood as data described in the form of indicators of the configured services on the target platform, such as the remaining bandwidth of the load balancer of the WAF (Web Application Firewall) cluster service configured on the target platform.

[0089] As mentioned above, considering that the monitoring component cannot directly obtain the monitoring indicators on the target platform, the target platform pushes the business performance indicators of its own configured services to the intermediate component, and the intermediate component converts the business performance indicators pushed by the target platform according to a preset format to obtain business performance indicators in a format recognizable by the monitoring component, so that the monitoring component can obtain the equipment performance indicators of the configured services on the target platform from the intermediate component.

[0090] A business alarm policy refers to a customized alarm policy for a business configured on the target platform. The business alarm policy is similar to the resource alarm policy described above. It may include policy names, business performance indicator rules, severity levels, business names, etc. Different business performance indicators of different businesses use different business alarm policies. Users can set different business alarm policies according to actual needs.

[0091] The explanations about business alarm information and business alarm notifications are similar to those about the above-mentioned resource alarm information and resource alarm notifications and will not be repeated here.

[0092] In this embodiment, by acquiring the service performance indicators of the configured services on the target platform and generating service alarm information in combination with the service alarm strategy, the service alarm notification is pushed to the target platform according to the service alarm information, thereby enriching the alarm types of the platform.

[0093] Based on the above embodiments, the resource alarm process and the business alarm process in the platform alarm method are described in detail by taking Prometheus as an example for the monitoring component. Accordingly, the alarm processing component can use AlertManage, and the intermediate component can use Push Gateway.

[0094] Figure 3 FIG. 1 is a flowchart of a resource alarm workflow according to an exemplary embodiment. Figure 3 As shown, the workflow includes:

[0095] Configure Prometheus: connect each collector to Prometheus, for example, configure the collectors on Prometheus: SNMP Exporter, Blackbox Exporter, and Node Exporter, then determine the collectors that can be used according to the types of resource devices managed by the target platform, write the information of each resource device into a file and put it into the file directory indicated by the collector configured on Prometheus, in addition, configure the resource alarm strategy loading directory, data acquisition time interval, Alert Manage location, etc. on Prometheus. Furthermore, after the user creates a resource alarm strategy on the target platform, push the resource alarm strategy to Prometheus.

[0096] Generate resource alarms: Prometheus collects device performance indicators of network devices through SNMP Exporter, device performance indicators of site servers through Blackbox Exporter, and device performance indicators of hosts through Node Exporter, and generates resource alarm information through resource alarm policies and device performance indicators of various resource devices.

[0097] Push alerts: After Alert Manage processes the resource alert information generated by Prometheus, it pushes resource alert notifications to the target platform.

[0098] Figure 4 FIG. 1 is a flowchart of a service alarm workflow according to an exemplary embodiment. Figure 4 As shown, the workflow includes:

[0099] Configure Prometheus: Configure the location of the Push Gateway and the directory for loading business alarm policies on Prometheus. Furthermore, after the user creates a business alarm policy on the target platform, the business alarm policy is pushed to Prometheus.

[0100] Generate business alarms: After the user configures the business on the target platform, the target platform extracts business performance indicators based on the configured business at a specified interval, pushes the business performance indicators to the Push Gateway for format conversion and storage. Prometheus periodically captures business performance indicators from the Push Gateway and generates business alarm information based on the business alarm strategy and the captured business performance indicators.

[0101] Push alerts: After Alert Manage processes the business alert information generated by Prometheus, it pushes business alert notifications to the target platform.

[0102] Resource alarm workflow and business alarm workflow are similar to the above Figure 1 to Figure 2 The illustrated embodiments are based on the same inventive concept, and the specific implementation of each process therein can refer to the relevant description in the above embodiments, which will not be repeated here.

[0103] The embodiment of the present application also provides an electronic device corresponding to the platform alarm method provided in the above embodiment, so as to execute the above platform alarm method.

[0104] Figure 5 The hardware structure diagram of an electronic device according to an exemplary embodiment is shown, and the electronic device includes: a communication interface 601, a processor 602, a memory 603 and a bus 604; wherein the communication interface 601, the processor 602 and the memory 603 complete mutual communication through the bus 604. The processor 602 can execute the platform alarm method described above by reading and executing the machine executable instructions corresponding to the control logic of the platform alarm method in the memory 603. The specific content of the method is referred to the above embodiment, and will not be repeated here.

[0105] The memory 603 mentioned in this application can be any electronic, magnetic, optical or other physical storage system, and can contain storage information, such as executable instructions, data, etc. Specifically, the memory 603 can be RAM (Random Access Memory), flash memory, storage drive (such as hard disk drive), any type of storage disk (such as optical disk, DVD, etc.), or similar storage medium, or a combination thereof. The communication connection between the system network element and at least one other network element is realized through at least one communication interface 601 (which can be wired or wireless), and the Internet, wide area network, local area network, metropolitan area network, etc. can be used.

[0106] The bus 604 may be an ISA bus, a PCI bus or an EISA bus, etc. The bus may be divided into an address bus, a data bus, a control bus, etc. The memory 603 is used to store programs, and the processor 602 executes the programs after receiving execution instructions.

[0107] Processor 602 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by an integrated logic circuit of hardware in processor 602 or an instruction in software form. The above-mentioned processor 602 can be a general-purpose processor, including a network processor (Network Processor, referred to as NP), a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a readily available programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. The disclosed methods, steps and logic block diagrams in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc. The steps of the method disclosed in conjunction with the embodiments of the present application can be directly embodied as a hardware decoding processor to execute, or the hardware and software modules in the decoding processor are combined to execute.

[0108] The electronic device provided in the embodiment of the present application and the platform alarm method provided in the embodiment of the present application are based on the same inventive concept and have the same beneficial effects as the methods adopted, run or implemented therein.

[0109] The present application also provides a computer-readable storage medium corresponding to the platform alarm method provided in the above embodiment. Figure 6 As shown, the computer-readable storage medium shown is a CD 30 on which a computer program (ie, a program product) is stored. When the computer program is run by a processor, the platform alarm method provided by any of the aforementioned embodiments will be executed.

[0110] It should be noted that examples of the computer-readable storage medium may also include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other optical or magnetic storage media, which are not listed here one by one.

[0111] The computer-readable storage medium provided in the above-mentioned embodiments of the present application and the platform alarm method provided in the embodiments of the present application are based on the same inventive concept and have the same beneficial effects as the methods adopted, run or implemented by the application programs stored therein.

[0112] An embodiment of the present application also provides a computer program product corresponding to the platform alarm method provided in the aforementioned embodiment. The computer program product includes a computer program, and the computer program is executed by a processor to implement the platform alarm method provided in the aforementioned embodiment.

[0113] The computer program product provided by the above-mentioned embodiments of the present application and the platform alarm method provided by the embodiments of the present application are based on the same inventive concept and have the same beneficial effects as the methods adopted, run or implemented by the application programs stored therein.

[0114] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the invention disclosed herein. The present application is intended to cover any modification, use or adaptation of the present application, which follows the general principles of the present application and includes common knowledge or customary techniques in the art that are not disclosed in the present application. The specification and examples are intended to be exemplary only, and the true scope and spirit of the present application are indicated by the following claims.

[0115] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0116] The above description is only a preferred embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application shall be included in the scope of protection of the present application.

Claims

1. A platform alarm method, characterized in that: Applied to a platform alarm device, the platform alarm device is configured with collectors corresponding to various types of resource devices managed by the target platform, and the method includes: Using collectors corresponding to the multiple types of resource devices, respectively, to collect device performance indicators of all resource devices managed by the target platform; Generate resource alarm information based on the collected equipment performance indicators and stored resource alarm policies; A resource alarm notification is pushed to the target platform according to the resource alarm information.

2. The method according to claim 1, characterized in that: Before collecting device performance indicators of all resource devices managed by the target platform using collectors corresponding to the multiple types of resource devices, the method further includes: Obtaining a first configuration file of a collector corresponding to each type of resource device, wherein the first configuration file at least includes an access address of the collector; Obtaining a second configuration file of each resource device managed by the target platform, wherein the second configuration file at least includes an access address of the resource device; For the collector corresponding to each type of resource device, a collector configuration file is generated based on the first configuration file and the second configuration file. The collector configuration file includes at least the access address of the collector corresponding to the current type of resource device and the access addresses of all resource devices of the current type managed by the target platform.

3. The method according to claim 1, characterized in that The pushing a resource alarm notification to the target platform according to the resource alarm information includes: Deduplication processing is performed on the resource alarm information; the deduplication processing is to retain the resource alarm information with the highest severity level among multiple resource alarm information of the same alarm type belonging to the same resource device; According to the resource alarm information after deduplication processing, a resource alarm notification is pushed to the target platform.

4. The method according to claim 1, characterized in that: The pushing a resource alarm notification to the target platform according to the resource alarm information includes: Grouping the resource alarm information according to the type of resource equipment, and pushing resource alarm notifications to the target platform according to the grouping results; and / or, The resource alarm information is grouped according to the alarm type, and the resource alarm notification is pushed to the target platform according to the grouping result.

5. The method according to any one of claims 1 to 4, characterized in that: The method further comprises: Acquire, from the target platform, a service performance indicator of a service configured on the target platform; Converting the service performance indicator according to a preset format; Generate business alarm information based on the converted business performance indicators and the stored business alarm strategy; Push a service alarm notification to the target platform according to the service alarm information.

6. A platform alarm device, characterized in that: The device comprises: a monitoring component and an alarm processing component, wherein the monitoring component is configured with collectors corresponding to various types of resource devices managed by the target platform; The monitoring component is used to collect device performance indicators of all resource devices managed by the target platform using collectors corresponding to the multiple types of resource devices; and generate resource alarm information based on the collected device performance indicators and the stored resource alarm strategy; The alarm processing component is used to push resource alarm notifications to the target platform according to the resource alarm information.

7. The device according to claim 6, characterized in that The collector includes at least one of the following: a simple network management protocol exporter SNMP Exporter, a black box exporter Blackbox Exporter and a node exporter NodeExporter.

8. The device according to claim 7, characterized in that The device also includes: An intermediate component is used to obtain the service performance indicators of the configured services on the target platform from the target platform, and convert the service performance indicators according to a preset format; The monitoring component is further used to obtain the converted service performance indicators from the intermediate component, and generate service alarm information based on the obtained service performance indicators and the stored service alarm strategy; The alarm processing component is also used to push a service alarm notification to the target platform according to the service alarm information.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: The processor executes the program to implement the method according to any one of claims 1 to 5.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: The program is executed by a processor to implement the method according to any one of claims 1 to 5.

11. A computer program product, comprising a computer program, characterized in that The computer program is executed by a processor to implement the method according to any one of claims 1 to 5.

Images