Monitoring method, device and computer program product for middleware

Abstract

The present application discloses a monitoring method, device, electronic device, storage medium and computer program product for middleware, and relates to the technical field of cloud services and distributed services. A specific implementation of the method includes: determining at least one middleware to be monitored, and the monitoring items of each of the at least one middleware; for each of the at least one middleware, collecting the operation data corresponding to the monitoring items of the middleware generated during the operation of the middleware; monitoring the at least one middleware according to the operation data corresponding to the monitoring items of the at least one middleware and the preset alarm rules. The present application provides a unified alarm method for middleware, which improves the convenience of monitoring different middleware.

Description

Technical Field

[0001] The present application relates to the field of computer technology, specifically to the field of cloud services and distributed service technologies, and in particular to monitoring methods, devices, electronic devices, storage media, and computer program products for middleware. Background Art

[0002] In the process of business system development, various middleware resources are introduced according to technical needs, such as etcd (a highly available key-value storage system), kafka (a distributed log system), redis (Remote DictionaryServer, remote dictionary service), elasticsearch (an open source search engine), zookeeper (an open source distributed application coordination service), etc. While introducing middleware resources to solve technical problems, we must also consider the adverse effects that middleware may bring to the business system, such as reducing system reliability and stability, affecting business, etc. In order to avoid such adverse effects, each time a middleware resource is connected, a monitoring and alarm system for the middleware resource needs to be customized and developed. Summary of the invention

[0003] The present application provides a method, apparatus, electronic device, storage medium and computer program product for monitoring middleware.

[0004] According to a first aspect, a monitoring method for middleware is provided, comprising: determining at least one middleware to be monitored, and monitoring items of each of the at least one middleware; for each of the at least one middleware, collecting operation data corresponding to the monitoring items of the middleware generated during the operation of the middleware; and monitoring the at least one middleware according to the operation data corresponding to the monitoring items of the at least one middleware and preset alarm rules.

[0005] According to a second aspect, a monitoring device for middleware is provided, comprising: a determination unit, configured to determine at least one middleware to be monitored, and monitoring items of each of the at least one middleware; a collection unit, configured to collect, for each of the at least one middleware, operation data corresponding to the monitoring items of the middleware, generated during the operation of the middleware; and a monitoring unit, configured to monitor the at least one middleware according to the operation data corresponding to the monitoring items of the at least one middleware and preset alarm rules.

[0006] According to a third aspect, an electronic device is provided, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute a method described in any implementation manner of the first aspect.

[0007] According to a fourth aspect, a non-transitory computer-readable storage medium storing computer instructions is provided, where the computer instructions are used to cause a computer to execute the method described in any implementation of the first aspect.

[0008] According to a fifth aspect, a computer program product is provided, comprising: a computer program, which implements the method described in any implementation manner of the first aspect when executed by a processor.

[0009] According to the technology of the present application, a unified alarm method for middleware is provided, which improves the convenience of monitoring different middleware.

[0010] It should be understood that the content described in this section is not intended to identify the key or important features of the embodiments of the present disclosure, nor is it intended to limit the scope of the present disclosure. Other features of the present disclosure will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] The accompanying drawings are used to better understand the present solution and do not constitute a limitation of the present application.

[0012] Figure 1 is an exemplary system architecture diagram in which an embodiment of the present application may be applied;

[0013] Figure 2 is a flow chart of an embodiment of a monitoring method for middleware according to the present application;

[0014] Figure 3 is a schematic diagram of an application scenario of the monitoring method for middleware according to this embodiment;

[0015] Figure 4 is a flow chart of another embodiment of a monitoring method for middleware according to the present application;

[0016] Figure 5 is a schematic diagram of an embodiment of a monitoring system for middleware according to the present application;

[0017] Figure 6 is a structural diagram of an embodiment of a monitoring device for middleware according to the present application;

[0018] Figure 7It is a structural diagram of a computer system suitable for implementing the embodiments of the present application. DETAILED DESCRIPTION

[0019] The following is a description of exemplary embodiments of the present application in conjunction with the accompanying drawings, including various details of the embodiments of the present application to facilitate understanding, which should be considered as merely exemplary. Therefore, it should be recognized by those of ordinary skill in the art that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the present application. Similarly, for the sake of clarity and conciseness, the description of well-known functions and structures is omitted in the following description.

[0020] Figure 1 An exemplary architecture 100 is shown to which the monitoring method and apparatus for middleware of the present application can be applied.

[0021] like Figure 1 As shown, the system architecture 100 may include terminal devices 101, 102, 103, a network 104 and a server 105. The communication connection between the terminal devices 101, 102, 103 constitutes a topological network, and the network 104 is used to provide a medium for the communication link between the terminal devices 101, 102, 103 and the server 105. The network 104 may include various connection types, such as wired, wireless communication links or optical fiber cables, etc.

[0022] Terminal devices 101, 102, 103 may be hardware devices or software that support network connection for data interaction and data processing. When terminal devices 101, 102, 103 are hardware, they may be various electronic devices that support network connection, information acquisition, interaction, display, processing and other functions, including but not limited to smart phones, tablet computers, e-book readers, laptop computers and desktop computers, etc. When terminal devices 101, 102, 103 are software, they may be installed in the electronic devices listed above. They may be implemented as multiple software or software modules for providing distributed services, or they may be implemented as a single software or software module. No specific limitation is made here.

[0023] Server 105 can be a server that provides various services, such as a background processing server that obtains request information sent by users through terminal devices 101, 102, and 103 and processes the request information. In the business system deployed in the background processing server, various middlewares are introduced according to technical needs, such as etcd, kafka, redis, elasticsearch, zookeeper, etc. During the operation of the business system combined with the middleware, the background processing server can monitor each middleware. As an example, server 105 can be a cloud server.

[0024] It should be noted that the server can be hardware or software. When the server is hardware, it can be implemented as a distributed server cluster consisting of multiple servers, or it can be implemented as a single server. When the server is software, it can be implemented as multiple software or software modules (for example, software or software modules used to provide distributed services), or it can be implemented as a single software or software module. No specific limitation is made here.

[0025] It should also be noted that the monitoring method for middleware provided in the embodiments of the present application can be executed by a server, or by a terminal device, or by a server and a terminal device in cooperation with each other. Accordingly, the various parts (e.g., various units) included in the monitoring device for middleware can be all set in the server, or all set in the terminal device, or can be set in the server and the terminal device respectively.

[0026] It should be understood that Figure 1 The number of terminal devices, networks, and servers in the system architecture is only illustrative. Depending on the implementation requirements, there may be any number of terminal devices, networks, and servers. When the electronic device on which the monitoring method for the middleware is running does not need to transmit data with other electronic devices, the system architecture may only include the electronic device (e.g., server or terminal device) on which the monitoring method for the middleware is running.

[0027] Please refer to Figure 2 , Figure 2 A flowchart of a monitoring method for middleware provided in an embodiment of the present application, wherein process 200 includes the following steps:

[0028] Step 201: determine at least one middleware to be monitored and monitoring items of each middleware in the at least one middleware.

[0029] In this embodiment, the execution subject of the monitoring method for the middleware (for example, Figure 1 The server in the system can determine at least one middleware to be monitored and the monitoring items of each middleware in the at least one middleware.

[0030] The execution subject may be deployed with a business system that implements various functions. The business system is based on middleware to assist in implementing the corresponding functions. At this time, the execution subject may determine locally at least one middleware that needs to be monitored, and the monitoring items of each of the at least one middleware. The execution subject may also determine at least one middleware that needs to be monitored, and the monitoring items of each of the at least one middleware, from a remote device based on a wired connection or a wireless connection. At this time, the device that deploys the business system and the middleware is a device independent of the execution subject.

[0031] Middleware can be any middleware that assists the business system to implement corresponding functions, including but not limited to etcd, kafka, redis, elasticsearch, zookeeper, etc. According to technical requirements, the same business system may introduce multiple middleware. At least one middleware to be monitored can be multiple middleware involved in the same business system.

[0032] Each middleware can be implemented as a middleware cluster. For each middleware, the monitoring items of the middleware can be pre-set according to actual needs. Each monitoring item can correspond to an operating indicator of the middleware. Taking the middleware Kafka as an example, the monitoring items include the overall health of brokers, the number of unsynchronized partitions of the topic, the message accumulation of each topic in the consumerGroup, the number of consumers in the consumerGroup, etc.

[0033] Step 202: For each of the at least one middleware, operation data corresponding to the monitoring items of the middleware generated during the operation of the middleware is collected.

[0034] In this embodiment, the execution subject may collect, for each of the at least one middleware, operation data corresponding to the monitoring items of the middleware, which is generated during the operation of the middleware.

[0035] As an example, the middleware to be monitored includes kafka and etcd. The monitoring items of kafka include 4 items, and the monitoring items of etcd include 3 items. Then, a corresponding data collection thread is set for each of the 7 monitoring items, and each data collection thread collects the running data of the corresponding monitoring item.

[0036] Step 203: monitor at least one middleware according to the operation data corresponding to the monitoring items of at least one middleware and the preset alarm rules.

[0037] In this embodiment, the execution subject may monitor at least one middleware according to the operation data corresponding to the monitoring item of at least one middleware and the preset alarm rules.

[0038] Corresponding to each monitoring item, a corresponding preset alarm rule is set according to the actual situation. The preset alarm rule is used to determine whether the operation data corresponding to the monitoring item meets the alarm condition, so as to monitor the operation of at least one middleware by means of an alarm. The preset alarm rule corresponding to the monitoring item can be a multi-level alarm rule divided according to the severity of the alarm.

[0039] As an example, corresponding to each monitoring item, set corresponding alarm rules corresponding to light, medium and severe. When the operation data of the monitoring item triggers an alarm rule of one level among multiple levels, an alarm is issued through the corresponding alarm method. Among them, each level of alarm rule corresponds to a different alarm method.

[0040] In order to solve the problem of long development cycle and waste of manpower caused by the need to customize the development of a monitoring and alarm system for each middleware connected, this application provides a unified monitoring method for middleware, which improves the convenience of monitoring different middleware.

[0041] Continue to see Figure 3 , Figure 3 FIG. 3 is a schematic diagram 300 of an application scenario of the monitoring method for middleware according to this embodiment. Figure 3 In the application scenario, the middleware introduced by the business system includes etcd 301, kafka 302, and redis 303. Corresponding to the middleware etcd 301, kafka 302, and redis 303, the monitoring items are monitoring items 3011, 3012, monitoring items 3021, 3022, 3023, and monitoring items 3031, 3032. The monitoring server first determines the above three middlewares to be monitored, as well as the monitoring items of each middleware. Then, for each of at least one middleware, the monitoring server collects the operation data corresponding to the monitoring items of the middleware generated during the operation of the middleware. Finally, the monitoring server monitors at least one middleware according to the operation data corresponding to the monitoring items of at least one middleware and the preset alarm rules.

[0042] In some optional implementations of this embodiment, the execution subject may perform step 202 in the following manner:

[0043] First, for each middleware in the at least one middleware, the data collection service corresponding to the middleware is determined from the data collection service cluster by the task scheduler.

[0044] This implementation is mainly aimed at situations where the monitoring task is heavy. The data collection service cluster includes data collection services for each middleware to collect information. Each type of middleware can pre-set multiple data collection services. Using the task scheduler, according to the middleware type, the data collection service can be quickly and effectively assigned to the corresponding monitoring item.

[0045] Second, the operation data corresponding to the monitoring items of the middleware and generated during the operation of the middleware are collected through the data collection service corresponding to the middleware.

[0046] In this implementation, the task scheduler reasonably distributes the collection tasks of the data collection service, thereby improving the efficiency of data collection.

[0047] In some optional implementations of this embodiment, the execution subject may perform step 203 in the following manner:

[0048] First, the monitoring component is used to obtain the operation data corresponding to the monitoring item of at least one middleware from the data collection service cluster.

[0049] As an example, the monitoring component can be prometheus, which is an open source monitoring and alarm solution. Prometheus periodically pulls the operating data of all monitoring items of the middleware from the data collection service cluster.

[0050] Second, for each monitoring item of at least one middleware, determine whether to perform alarm processing on the monitoring item according to the operation data corresponding to the monitoring item and the preset alarm rule.

[0051] Third, in response to determining to perform alarm processing, the alarm information corresponding to the monitoring item is pushed to the receiver corresponding to the middleware to which the monitoring item belongs through the alarm policy corresponding to the monitoring item.

[0052] In this implementation, corresponding alarm rules can be set in advance for each monitoring item. The alarm rules include the recipient of the alarm information (system or person), the alarm method (such as email, SMS, voice), and the alarm record information (for example, the alarm time, alarm details, the time when the interface person manually closes the alarm, and the entire alarm cycle from the start to the end of the alarm).

[0053] In this implementation, monitoring components such as prometheus are used to obtain the operation data of the middleware from the data collection service cluster, make alarm judgments, push alarm information, and other operations, thereby improving the efficiency and convenience of information processing.

[0054] In some optional implementations of this embodiment, the execution subject may perform the third step in the following manner:

[0055] First, in response to determining to perform alarm processing, the alarm information corresponding to the monitoring item is pushed to the service grid corresponding to the middleware to which the monitoring item belongs through the alarm policy corresponding to the monitoring item; then, the alarm information is pushed to the sidecar corresponding to the monitoring item through the service grid.

[0056] In this implementation, for the situation where the recipient of the alarm information is a business system, when an alarm occurs, the above-mentioned execution entity can notify the service mesh control plane through various methods such as Kafka messages or callback addresses, and then the service mesh control plane sends it to the sidecar to quickly and effectively push the alarm to the business system.

[0057] In some optional implementations of this embodiment, the execution subject may also process the middleware to which the alarmed monitoring item belongs in response to the alarmed monitoring item determined according to the operation data and the preset alarm rules. As an example, corresponding processing methods may be pre-set for alarms of different monitoring items, so as to timely process the alarms of the monitoring items and reduce the operation loss of the business system caused by the middleware alarms.

[0058] In some optional implementations of this embodiment, the above-mentioned execution entity may also, in response to receiving a creation request or an update request for a monitoring item, perform a validity check on the monitoring item represented by the request; in response to determining that the check passes, create or update the monitoring item represented by the request.

[0059] The validity check is used to determine whether the parameters of the created or updated monitoring items are correct so that they can be executed to monitor the operating indicators of the middleware. When creating or updating a monitoring item, the above-mentioned execution subject accesses the middleware instance of the same type as the middleware to which the created or updated monitoring item belongs to perform a validity check; after the check passes, the prometheus alarm rule is modified to successfully create and update the monitoring item. Among them, each monitoring item corresponds to an alert configuration item in the prometheus alarm rule. In this implementation, the above-mentioned execution subject can flexibly create and update monitoring items to meet the ever-changing actual needs of the business system.

[0060] In some optional implementations of this embodiment, the above-mentioned execution entity may also perform a feasibility check on the middleware represented by the request in response to receiving a creation request or an update request for the middleware; and create or update the middleware represented by the request in response to determining that the check passes.

[0061] The feasibility check represents whether the created or updated middleware can run accurately. In response to determining that the feasibility check passes, the middleware represented by the creation or update request is created or updated to avoid the business system from introducing unavailable middleware. In this embodiment, the above-mentioned execution entity can introduce new middleware into the above-mentioned unified alarm method for middleware to improve the scalability of this application.

[0062] Continue to refer Figure 4, shows a schematic process 400 of an embodiment of a monitoring method for middleware according to the present application, including the following steps:

[0063] Step 401: determine at least one middleware to be monitored and monitoring items of each middleware in the at least one middleware.

[0064] Step 402: for each middleware in at least one middleware, determine the data collection service corresponding to the middleware from the data collection service cluster through the task scheduler.

[0065] Step 403: collect the operation data corresponding to the monitoring items of the middleware and generated during the operation of the middleware through the data collection service corresponding to the middleware.

[0066] Step 404: Obtain, through the monitoring component, the operation data corresponding to the monitoring item of at least one middleware from the data collection service cluster.

[0067] Step 405: for each monitoring item of at least one middleware, determine whether to perform alarm processing on the monitoring item according to the operation data corresponding to the monitoring item and the preset alarm rule.

[0068] Step 406, in response to determining to perform alarm processing, the alarm information corresponding to the monitoring item is pushed to the receiver corresponding to the middleware to which the monitoring item belongs through the alarm policy corresponding to the monitoring item.

[0069] It can be seen from this embodiment that Figure 2 Compared with the corresponding embodiments, the process 400 of the monitoring method for the middleware in this embodiment specifically describes the data collection process and the alarm process, thereby improving the efficiency of data collection and information processing.

[0070] To deepen understanding, the present application also provides a specific implementation scheme 500 in combination with a specific application scenario, such as Figure 5 As shown:

[0071] The monitoring system for the middleware includes a space management platform 501 , a task scheduler 502 , a data collection service cluster 503 , a prometheus monitoring component 504 , an alarm manager 505 , and an alarm service 506 .

[0072] 1. The task scheduler 502 pulls monitoring resource data from the monitoring management platform 501, including at least one middleware to be monitored and monitoring items of each middleware in the at least one middleware.

[0073] 2. The task scheduler 502 determines a data collection service from the data collection service cluster 503 that collects the running data of the monitoring items of each middleware in at least one middleware.

[0074] 3. According to the scheduling of the data collection services in the data collection service cluster 503 by the task scheduler 502, the scheduled data collection services collect the operation data of the monitoring items of the corresponding middleware.

[0075] 4. The prometheus monitoring component 504 periodically pulls the operating data of the monitoring items of each middleware in at least one middleware from the data collection service cluster 503, makes an alarm determination, and sends the alarm information to the alarm manager 505.

[0076] 5. The alarm manager 505 pushes the alarm information to the alarm service 506 through webhook (a lightweight event processing application). The alarm service 506 performs data analysis on the alarm information and then sends the alarm information to the recipient (user or business system) according to the alarm strategy of the monitoring item.

[0077] Continue to refer Figure 6 As an implementation of the methods shown in the above figures, the present application provides an embodiment of a monitoring device for middleware, and the device embodiment is similar to Figure 2 Corresponding to the method embodiment shown, the device can be specifically applied to various electronic devices.

[0078] like Figure 6 As shown, the monitoring device for the middleware includes: a determination unit 601, configured to determine at least one middleware to be monitored, and the monitoring items of each middleware in the at least one middleware; a collection unit 602, configured to collect, for each middleware in the at least one middleware, the operation data corresponding to the monitoring items of the middleware generated during the operation of the middleware; and a monitoring unit 603, configured to monitor the at least one middleware according to the operation data corresponding to the monitoring items of the at least one middleware and preset alarm rules.

[0079] In some optional implementations of this embodiment, the collection unit 602 is further configured to: for each middleware of at least one middleware, determine the data collection service corresponding to the middleware from the data collection service cluster through the task scheduler; and collect the operation data corresponding to the monitoring items of the middleware generated during the operation of the middleware through the data collection service corresponding to the middleware.

[0080] In some optional implementations of this embodiment, the monitoring unit 603 is further configured to: obtain, through the monitoring component, the operating data corresponding to the monitoring item of at least one middleware from the data acquisition service cluster; for each monitoring item of at least one middleware, determine whether to perform alarm processing on the monitoring item according to the operating data corresponding to the monitoring item and the preset alarm rules; in response to determining to perform alarm processing, push the alarm information corresponding to the monitoring item to the receiver corresponding to the middleware to which the monitoring item belongs through the alarm policy corresponding to the monitoring item.

[0081] In some optional implementations of this embodiment, the monitoring unit 603 is further configured to: in response to determining to perform alarm processing, push the alarm information corresponding to the monitoring item to the service grid corresponding to the middleware to which the monitoring item belongs through the alarm policy corresponding to the monitoring item; and push the alarm information to the sidecar corresponding to the monitoring item through the service grid.

[0082] In some optional implementations of this embodiment, the above-mentioned device also includes: a processing unit (not shown in the figure), which is configured to process the middleware to which the alarm monitoring item belongs in response to determining the alarm monitoring item based on operating data and preset alarm rules.

[0083] In some optional implementations of this embodiment, the above-mentioned device also includes: a first verification unit (not shown in the figure), which is configured to, in response to receiving a creation request or an update request for a monitoring item, perform validity verification on the monitoring item represented by the request; a first creation and update unit, which is configured to, in response to determining that the verification is passed, create or update the monitoring item represented by the request.

[0084] In some optional implementations of this embodiment, the above-mentioned device also includes: a second verification unit (not shown in the figure), which is configured to perform a feasibility verification on the middleware represented by the request in response to receiving a creation request or an update request for the middleware; and a second creation and update unit, which is configured to create or update the middleware represented by the request in response to determining that the verification passes.

[0085] This embodiment provides a unified alarm device for middleware, which improves the convenience of monitoring different middleware.

[0086] According to an embodiment of the present disclosure, the present disclosure also provides an electronic device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can implement the monitoring method for the middleware described in any of the above embodiments when executing.

[0087] According to an embodiment of the present disclosure, the present disclosure further provides a readable storage medium, which stores computer instructions, and the computer instructions are used to enable a computer to implement the monitoring method for middleware described in any of the above embodiments when executed.

[0088] The embodiments of the present disclosure provide a computer program product. When the computer program is executed by a processor, the monitoring method for the middleware described in any of the above embodiments can be implemented.

[0089] Figure 7 A schematic block diagram of an example electronic device 700 that can be used to implement an embodiment of the present disclosure is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present disclosure described and / or required herein.

[0090] like Figure 7 As shown, the device 700 includes a computing unit 701, which can perform various appropriate actions and processes according to a computer program stored in a read-only memory (ROM) 702 or a computer program loaded from a storage unit 708 into a random access memory (RAM) 703. In the RAM 703, various programs and data required for the operation of the device 700 can also be stored. The computing unit 701, the ROM 702, and the RAM 703 are connected to each other via a bus 704. An input / output (I / O) interface 705 is also connected to the bus 704.

[0091] A number of components in the device 700 are connected to the I / O interface 705, including: an input unit 706, such as a keyboard, a mouse, etc.; an output unit 707, such as various types of displays, speakers, etc.; a storage unit 708, such as a disk, an optical disk, etc.; and a communication unit 709, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 709 allows the device 700 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.

[0092] The computing unit 701 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the computing unit 701 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, digital signal processors (DSPs), and any appropriate processors, controllers, microcontrollers, etc. The computing unit 701 performs the various methods and processes described above, such as monitoring methods for middleware. For example, in some embodiments, the monitoring method for middleware may be implemented as a computer software program, which is tangibly contained in a machine-readable medium, such as a storage unit 708. In some embodiments, part or all of the computer program may be loaded and / or installed on the device 700 via ROM 702 and / or communication unit 709. When the computer program is loaded into RAM 703 and executed by the computing unit 701, one or more steps of the monitoring method for middleware described above may be performed. Alternatively, in other embodiments, the computing unit 701 may be configured to perform a monitoring method for middleware in any other appropriate manner (e.g., by means of firmware).

[0093] Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0094] The program code for implementing the method of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that the program code, when executed by the processor or controller, enables the functions / operations specified in the flow chart and / or block diagram to be implemented. The program code may be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.

[0095] In the context of the present disclosure, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, device, or equipment. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0096] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user can provide input to the computer. Other types of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including acoustic input, voice input, or tactile input).

[0097] The systems and techniques described herein may be implemented in a computing system that includes back-end components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes front-end components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such back-end components, middleware components, or front-end components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), and the Internet.

[0098] A computer system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The relationship between the client and the server is generated by computer programs running on the corresponding computers and having a client-server relationship with each other. The server may be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system to solve the defects of difficult management and weak business scalability in traditional physical hosts and virtual private servers (VPS) services.

[0099] According to the technical solution of the embodiment of the present disclosure, by determining at least one middleware to be monitored and the monitoring items of each of the at least one middleware; for each of the at least one middleware, collecting the operation data corresponding to the monitoring items of the middleware generated during the operation of the middleware; monitoring the at least one middleware according to the operation data corresponding to the monitoring items of the at least one middleware and the preset alarm rules, thereby providing a unified alarm method for the middleware and improving the convenience of monitoring different middleware.

[0100] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps recorded in this disclosure can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solutions disclosed in this disclosure can be achieved, and this document does not limit this.

[0101] The above specific implementations do not constitute a limitation on the protection scope of the present disclosure. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present disclosure shall be included in the protection scope of the present disclosure.

Claims

1. A monitoring method for middleware, characterized in that: include: Pull monitoring resource data from the monitoring management platform through the task scheduler to determine at least one middleware to be monitored and the monitoring items of each middleware in the at least one middleware, wherein a monitoring item of the middleware corresponds to an operating indicator of the middleware; For each of the at least one middleware, determine and schedule the data collection service corresponding to the middleware from the data collection service cluster through the task scheduler, and collect the operation data corresponding to the monitoring items of the middleware generated during the operation of the middleware; The at least one middleware is monitored by the monitoring component according to the operation data corresponding to the monitoring items of the at least one middleware and the preset alarm rules.

2. The method according to claim 1, wherein: The monitoring of the at least one middleware according to the operation data corresponding to the monitoring item of the at least one middleware and the preset alarm rule includes: Obtaining, through the monitoring component, the operation data corresponding to the monitoring item of the at least one middleware from the data acquisition service cluster; For each monitoring item of the at least one middleware, determining whether to perform alarm processing on the monitoring item according to the operation data corresponding to the monitoring item and the preset alarm rule; In response to determining to perform alarm processing, the alarm information corresponding to the monitoring item is pushed to the receiver corresponding to the middleware to which the monitoring item belongs through the alarm policy corresponding to the monitoring item.

3. The method according to claim 2, wherein: In response to determining to perform alarm processing, the alarm information corresponding to the monitoring item is pushed to the receiver corresponding to the middleware to which the monitoring item belongs through the alarm policy corresponding to the monitoring item, including: In response to determining to perform alarm processing, the alarm information corresponding to the monitoring item is pushed to the service grid corresponding to the middleware to which the monitoring item belongs through the alarm policy corresponding to the monitoring item; The alarm information is pushed to the sidecar corresponding to the monitoring item through the service grid.

4. The method according to claim 1, wherein: Also includes: In response to determining the monitoring item of the alarm according to the operation data and the preset alarm rule, the middleware to which the monitoring item of the alarm belongs is processed.

5. The method according to claim 1, wherein: Also includes: In response to receiving a creation request or an update request for a monitoring item, performing a validity check on the monitoring item represented by the request; In response to determining that the verification passes, a monitoring item represented by the request is created or updated.

6. The method according to claim 1, wherein: Also includes: In response to receiving a creation request or an update request of a middleware, performing a feasibility check on the middleware represented by the request; In response to determining that the verification passes, the middleware represented by the request is created or updated.

7. A monitoring device for middleware, characterized in that: include: A determination unit is configured to pull monitoring resource data from the monitoring management platform through a task scheduler, determine at least one middleware to be monitored, and a monitoring item of each middleware in the at least one middleware, wherein a monitoring item of the middleware corresponds to an operation indicator of the middleware; The collection unit is configured to determine and schedule the data collection service corresponding to each middleware in the at least one middleware from the data collection service cluster through the task scheduler, and collect the operation data corresponding to the monitoring items of the middleware generated during the operation of the middleware; The monitoring unit is configured to monitor the at least one middleware through a monitoring component according to the operation data corresponding to the monitoring items of the at least one middleware and preset alarm rules.

8. The device according to claim 7, wherein: The monitoring unit is further configured to: Obtaining, from the data collection service cluster, operation data corresponding to the monitoring items of the at least one middleware through the monitoring component; for each monitoring item of the at least one middleware, determining whether to perform alarm processing on the monitoring item according to the operation data corresponding to the monitoring item and the preset alarm rule; In response to determining to perform alarm processing, the alarm information corresponding to the monitoring item is pushed to the receiver corresponding to the middleware to which the monitoring item belongs through the alarm policy corresponding to the monitoring item.

9. The device according to claim 8, wherein: The monitoring unit is further configured to: In response to determining to perform alarm processing, the alarm information corresponding to the monitoring item is pushed to the service grid corresponding to the middleware to which the monitoring item belongs through the alarm policy corresponding to the monitoring item; The alarm information is pushed to the sidecar corresponding to the monitoring item through the service grid.

10. The device according to claim 7, wherein: Also includes: The processing unit is configured to process the middleware to which the alarmed monitoring item belongs in response to determining the alarmed monitoring item according to the operation data and the preset alarm rule.

11. The device according to claim 7, wherein: Also includes: A first verification unit is configured to, in response to receiving a creation request or an update request for a monitoring item, perform a validity verification on the monitoring item represented by the request; The first creation and update unit is configured to create or update the monitoring item represented by the request in response to determining that the verification passes.

12. The device according to claim 7, wherein: Also includes: A second verification unit is configured to, in response to receiving a creation request or an update request of the middleware, perform a feasibility verification on the middleware represented by the request; The second creation and update unit is configured to create or update the middleware represented by the request in response to determining that the verification passes.

13. An electronic device, characterized in that: include: at least one processor; as well as a memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the method according to any one of claims 1 to 6.

14. A non-transitory computer-readable storage medium storing computer instructions, characterized in that: The computer instructions are used to cause the computer to execute the method according to any one of claims 1 to 6.

15. A computer program product comprising: A computer program which, when executed by a processor, implements the method according to any one of claims 1 to 6.

Images