Distributed monitoring system

Abstract

This application provides a distributed monitoring system, which relates to the field of distributed systems, including: a status acquisition module, a Kafka cluster module, a core processing server module, and a monitoring and display module; this application can improve the throughput and processing efficiency of the operation and maintenance system, and can achieve high fault tolerance, low latency, and scalable non-functional requirements.

Description

Technical Field

[0001] This application relates to the field of distributed systems, specifically to a distributed monitoring system. Background Technology

[0002] In a centralized architecture, the way IT personnel conduct operation and maintenance monitoring by logging into the terminal bastion host is no longer sufficient to meet the operation and maintenance needs of large-scale cluster deployments in a distributed architecture. Monitoring is difficult to carry out, and production problems are hard to trace and locate.

[0003] In existing distributed systems, most use Prometheus to monitor the status of physical machines. In this approach, Prometheus performs storage and computation based on memory. Therefore, when the deployed machine fails, the operation and maintenance monitoring tools will lose all data, making it impossible to track and locate the problem, resulting in operation and maintenance failure, low system reliability, and high operation and maintenance costs. Summary of the Invention

[0004] To address the problems in the existing technology, this application provides a distributed monitoring system that can improve the throughput and processing efficiency of the operation and maintenance system, and can achieve high fault tolerance, low latency, and scalable non-functional requirements.

[0005] To solve at least one of the above problems, this application provides the following technical solution:

[0006] Firstly, this application provides a distributed monitoring system, including:

[0007] A status acquisition module is used to collect client log files and send them to the Kafka cluster module.

[0008] The Kafka cluster module includes a load balancer node and a message middleware server node. The Kafka cluster module is used to receive log files sent by the status acquisition module and perform message distribution processing through the load balancer node and the message middleware server node.

[0009] The core processing server module is used to receive log files sent by the Kafka cluster module and process and consume them.

[0010] The monitoring and display module is connected to the core processing server module. The monitoring and display module is used to receive the feedback report information, operation status data and system indicator summary sent by the core processing server module and perform visualization display.

[0011] Furthermore, the core processing server module includes a unified access component, which is connected to the Kafka cluster module. The unified access component is used to allocate threads and distribute messages and pending tasks sent by the Kafka cluster module.

[0012] Furthermore, the core processing server module also includes a thread pool component, which is connected to the unified access component and is used to preprocess the messages distributed by the unified access component.

[0013] Furthermore, the core processing server module also includes a high-performance queue component, which is connected to the thread pool component and is used to receive messages distributed by the thread pool component.

[0014] Furthermore, the core processing server module also includes a central processing unit (CPU) component, which is used to process and consume the received messages.

[0015] Furthermore, the central processing unit component includes at least one of a sampling processor, a problem processor, a heartbeat processor, a message tree processor, and a business processor.

[0016] Furthermore, it also includes a shared component remote library module, which is connected to the status acquisition module and is used to host the source code of the log files collected by the status acquisition module.

[0017] Furthermore, it also includes a database storage module, which is connected to the core processing server module and is used to persistently store messages received by the core processing server.

[0018] Furthermore, it also includes a source code version hosting module, which includes an offline central repository for version management of the source code.

[0019] Secondly, this application provides an electronic device, including 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 distributed monitoring system.

[0020] Thirdly, this application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the distributed monitoring system described above.

[0021] Fourthly, this application provides a computer program product, including a computer program / instructions that, when executed by a processor, implement the distributed monitoring system described above.

[0022] As can be seen from the above technical solution, this application provides a distributed monitoring system. By setting up a status acquisition module, a Kafka cluster module, a core processing server module, and a monitoring and display module, the system can improve the throughput and processing efficiency of the operation and maintenance system, and achieve high fault tolerance, low latency, and scalable non-functional requirements. Attached Figure Description

[0023] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0024] Figure 1 This is a schematic diagram of the overall structure of the distributed monitoring system in the embodiments of this application;

[0025] Figure 2 This is a simplified structural diagram of the distributed monitoring system in the embodiments of this application;

[0026] Figure 3 This is a schematic diagram of the core processing server module in the embodiments of this application;

[0027] Figure 4 This is a schematic diagram of the structure of the electronic device in the embodiments of this application. Detailed Implementation

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

[0029] The acquisition, storage, use, and processing of data in this application all comply with the relevant provisions of national laws and regulations.

[0030] Considering that most existing distributed systems use Prometheus to monitor the status of physical machines, and that Prometheus performs memory-based storage and computation in this approach, when a deployment machine fails, the operation and maintenance monitoring tools will lose all data, making it impossible to trace and locate the problem, resulting in operational failure, low system reliability, and high operation and maintenance costs. This application provides a distributed monitoring system that, by setting up a status acquisition module, a Kafka cluster module, a core processing server module, and a monitoring and display module, can improve the throughput and processing efficiency of the operation and maintenance system, and achieve high fault tolerance, low latency, and scalable non-functional requirements.

[0031] To improve the throughput and processing efficiency of the operation and maintenance system, and to achieve high fault tolerance, low latency, and scalable non-functional requirements, this application provides an embodiment of a distributed monitoring system, see [link to relevant documentation]. Figure 1 and Figure 2 The distributed monitoring system specifically includes the following components:

[0032] Status acquisition module 10 is used to collect client log files and send them to Kafka cluster module 20.

[0033] Optionally, the status collection module 10 of this application is hosted in a central Maven repository and pulled to the local machine by the application server for building and deployment. It is mainly responsible for collecting various types of logs from the client and sending them to the Kafka cluster module 20 gateway load balancer for distribution processing in real time.

[0034] Kafka cluster module 20, which includes a load balancer node and a message middleware server node, is used to receive log files sent by the status acquisition module 10 and perform message distribution processing through the load balancer node and the message middleware server node.

[0035] Optionally, the Kafka cluster module 20 of this application can deploy load balancers and Kafka server nodes, receive log files sent by the status collection module 10, and use high-performance computing processing node capabilities to complete tasks such as message classification and aggregation, message tree construction, topic type labeling, and forward messages to the core processing module.

[0036] The core processing server module 30 is used to receive log files sent by the Kafka cluster module and process and consume them.

[0037] Optionally, the core processing server module 30 of this application may have four components: a unified access component 31, a thread pool component 32, a high-performance queue component 33, and a central processing unit component 34, thereby receiving and processing log files sent by the Kafka cluster module.

[0038] The monitoring and display module 40 is connected to the core processing server module 30. The monitoring and display module 40 is used to receive the feedback report information, operation status data and system indicator summary sent by the core processing server module 30 and perform visualization display.

[0039] Optionally, the monitoring and display module 40 of this application can connect to the report information, running status data, and system indicator summary returned by the core processing server module 30, perform UI drawing, and provide functions such as conditional filtering, fuzzy search, operation and maintenance monitoring statistics, customized report display, and view display.

[0040] As can be seen from the above description, the distributed monitoring system provided in this application embodiment can improve the throughput and processing efficiency of the operation and maintenance system by setting up a status acquisition module 10, a Kafka cluster module 20, a core processing server module 30, and a monitoring and display module 40, thereby achieving high fault tolerance, low latency, and scalable non-functional requirements.

[0041] In one embodiment of the distributed monitoring system of this application, see Figure 3 The core processing server module 30 includes a unified access component 31, which is connected to the Kafka cluster module 20. The unified access component 31 is used to allocate threads and distribute messages and tasks to be processed sent by the Kafka cluster module 20.

[0042] Specifically, the unified access component 31, in conjunction with the thread pool module, allocates threads for each message sent by the Kafka cluster and the tasks to be processed, and maintains the connection establishment status and the task distribution status monitoring.

[0043] The core processing server module 30 also includes a thread pool component 32, which is connected to the unified access component 31 and is used to preprocess the messages distributed by the unified access component 31.

[0044] Specifically, the thread pool component 32 provides configurable parameter maintenance functions. Based on the blocking and working status of each thread, it preprocesses the messages distributed by the access component and puts them into the corresponding message queues according to the topic and type labels, and binds them through the bind() method. It receives the wake-up callback of the queue pointer and forwards the messages to be processed to the processor component for consumption.

[0045] The core processing server module 30 also includes a high-performance queue component 33, which is connected to the thread pool component 32 and is used to receive messages distributed by the thread pool component 32.

[0046] Specifically, the high-performance queue component 33 maintains a Disruptor queue, receives messages distributed by the thread pool, and maintains independent pointers for each queue. Messages are put in and taken out by shifting the pointers forward and backward. The worker thread is called back through the bind() and awake() methods, and messages are sent back to the processor component for actual consumption.

[0047] The core processing server module 30 also includes a central processing unit 34, which is used to process and consume received messages.

[0048] Specifically, the central processing unit component 34 is designed with five types of processors: a sampling processor, a problem processor, a heartbeat processor, a message tree processor, and a business processor. These processors handle and consume messages of different topic types. Before processing, the messages are persisted to the database module to achieve high efficiency and reliability for non-functional requirements. For example, in the deposit system, if a transfer transaction occurs and a balance change message is generated afterward, when the message information is retrieved from the message queue component and the message is identified as 'businessType', the access layer will activate an interceptor and forward the message to the business processor. The business processor will then consume the message and store it in the database for use in processing fixed business monitoring reports within the system.

[0049] In one embodiment of the distributed monitoring system of this application, the central processing unit component 34 includes at least one of a sampling processor, a problem processor, a heartbeat processor, a message tree processor, and a business processor.

[0050] In one embodiment of the distributed monitoring system of this application, a shared component remote library module is also included. The shared component remote library module is connected to the status acquisition module 10 and is used to host the source code of the log files collected by the status acquisition module 10.

[0051] Optionally, the shared component remote library module of this application can be established based on a Maven remote repository, mainly hosting the source code of the status collection module 10, and working with the pom.xml file configured in the development state under the Spring Boot technology stack, which is deployed along with the application system during development.

[0052] In one embodiment of the distributed monitoring system of this application, a database storage module is further included. The database storage module is connected to the core processing server module 30 and is used to persistently store the messages received by the core processing server.

[0053] Optionally, the database storage module of this application can be built based on Cassandra and Clickhouse to achieve persistent message storage. It adopts a columnar storage mode and can achieve real-time data aggregation function.

[0054] In one embodiment of the distributed monitoring system of this application, a source code version hosting module is also included, which includes an offline central repository for version management of the source code.

[0055] Optionally, the source code version hosting module of this application can establish an offline central repository for GitLab, which is responsible for version management of all source code in this system; it should have a version management strategy and support multi-branch parallel management; the shared component remote library module, Kafka cluster module 20, core processing server module 30, and database module should all be managed uniformly through this module.

[0056] As can be seen from the above, this application, by adopting the Kafka Cluster + Lambda architecture to design the system, truly realizes automated monitoring and operation of distributed architecture, and provides high-quality operation and maintenance report analysis and display, overcoming the drawbacks of low efficiency, slow location, and difficult operation caused by manual operation and maintenance under centralized architecture.

[0057] This application effectively decouples the entire process of distributed operation and maintenance and report analysis into seven systems: remote component library, source code hosting, Kafka cluster, core processing, database storage, status collection, and front-end display.

[0058] The source code hosting module manages all system source code versions through a centralized offline central repository on GitHub, enabling centralized control and effective management of parallel branch development.

[0059] The component remote library module provides development-state source code retrieval and management functions. Together with Spring and pom.xml files, it enables automated build and deployment, allowing the collector to be embedded seamlessly.

[0060] The Kafka cluster module maximizes the utilization of physical resources and completes tasks such as log processing and topic tagging by making full use of computing resources. It has high availability and high parallelism, and significantly improves processing efficiency.

[0061] The core processing module, through a thread pool and high-performance queue, combined with a topic-based processor mounting processing mode, enables automatic and efficient processing of messages across all topics, providing basic data for operation and maintenance decisions and report analysis generation.

[0062] The database storage module, through a columnar storage database scheme, achieves high-performance and highly reliable data aggregation processing functions and improves the overall reliability of the system;

[0063] The status acquisition module effectively addresses the challenges of data acquisition in distributed architectures through automatic tracking technology and multiple implementations using Java agent and client JAR packages, significantly reducing development complexity and improving the comprehensiveness of status acquisition.

[0064] The front-end display module provides real-time UI rendering and offers features such as conditional filtering, fuzzy search, operation and maintenance monitoring statistics, customized report display, and view display. It effectively reduces the difficulty of analysis and monitoring for operation and maintenance personnel, improves the quality of operation and maintenance, and truly realizes end-to-end configurable distributed operation and maintenance monitoring and report analysis. It provides a very user-friendly experience and greatly improves development and operation and maintenance efficiency.

[0065] From a hardware perspective, in order to improve the throughput and processing efficiency of the operation and maintenance system and achieve high fault tolerance, low latency, and scalable non-functional requirements, this application provides an embodiment of an electronic device for implementing all or part of the functions of the distributed monitoring system. The electronic device specifically includes the following components:

[0066] The system comprises a processor, memory, a communications interface, and a bus; wherein the processor, memory, and communications interface communicate with each other via the bus; the communications interface is used to realize information transmission between the distributed monitoring system and core business systems, user terminals, and related databases and other related devices; the logic controller can be a desktop computer, tablet computer, or mobile terminal, etc., and this embodiment is not limited to these. In this embodiment, the logic controller can be implemented with reference to the embodiments of the distributed monitoring system in the present embodiment, and the contents of the embodiments of the distributed monitoring system are incorporated herein, and repeated parts will not be described again.

[0067] It is understood that the user terminal may include smartphones, tablet computers, network set-top boxes, portable computers, desktop computers, personal digital assistants (PDAs), in-vehicle devices, smart wearable devices, etc. Among these, the smart wearable devices may include smart glasses, smartwatches, smart bracelets, etc.

[0068] In practical applications, a portion of the distributed monitoring system can be executed on the electronic device side as described above, or all operations can be completed on the client device. The choice can be made based on the processing power of the client device and the limitations of the user's usage scenario. This application does not impose any limitations on this. If all operations are completed on the client device, the client device may further include a processor.

[0069] The aforementioned client device may have a communication module (i.e., a communication unit) that can communicate with a remote server to achieve data transmission. The server may include a server on the task scheduling center side; in other implementation scenarios, it may also include a server on an intermediate platform, such as a server on a third-party server platform that has a communication link with the task scheduling center server. The server may include a single computer device, a server cluster consisting of multiple servers, or a distributed server structure.

[0070] Figure 4 This is a schematic block diagram illustrating the system configuration of the electronic device 9600 according to an embodiment of this application. Figure 4 As shown, the electronic device 9600 may include a central processing unit 9100 and a memory 9140; the memory 9140 is coupled to the central processing unit 9100. It is worth noting that... Figure 4 This is an example; other types of structures can also be used to supplement or replace this structure to achieve telecommunications functions or other functions.

[0071] In one embodiment, the distributed monitoring system functionality can be integrated into the central processing unit 9100.

[0072] As can be seen from the above description, the electronic device provided in this application embodiment, by setting up a status acquisition module, a Kafka cluster module, a core processing server module, and a monitoring and display module, can improve the throughput and processing efficiency of the operation and maintenance system, and can achieve high fault tolerance, low latency, and scalable non-functional requirements.

[0073] In another implementation, the distributed monitoring system can be configured separately from the central processing unit 9100. For example, the distributed monitoring system can be configured as a chip connected to the central processing unit 9100, and the functions of the distributed monitoring system can be implemented through the control of the central processing unit.

[0074] like Figure 4 As shown, the electronic device 9600 may further include: a communication module 9110, an input unit 9120, an audio processor 9130, a display 9160, and a power supply 9170. It is worth noting that the electronic device 9600 does not necessarily need to include these components. Figure 4All components shown; in addition, the electronic device 9600 may also include Figure 4 For components not shown, please refer to existing technologies.

[0075] like Figure 4 As shown, the central processing unit 9100, sometimes also referred to as a controller or operating control, may include a microprocessor or other processor device and / or logic device, which receives inputs and controls the operation of various components of the electronic device 9600.

[0076] The memory 9140 may be, for example, one or more of a cache, flash memory, hard drive, removable media, volatile memory, non-volatile memory, or other suitable devices. It may store the aforementioned failure-related information, and also store a program for executing that information. The central processing unit 9100 may execute the program stored in the memory 9140 to perform information storage or processing, etc.

[0077] Input unit 9120 provides input to central processing unit 9100. Input unit 9120 may be, for example, a keypad or touch input device. Power supply 9170 provides power to electronic device 9600. Display 9160 displays images and text. Display may be, for example, an LCD display, but is not limited thereto.

[0078] The memory 9140 can be a solid-state memory, such as a read-only memory (ROM), random access memory (RAM), a SIM card, etc. It can also be a memory that retains information even when power is off, can be selectively erased, and contains more data; examples of this type of memory are sometimes referred to as EPROMs. The memory 9140 can also be some other type of device. The memory 9140 includes a buffer memory 9141 (sometimes referred to as a buffer). The memory 9140 may include an application / function storage unit 9142 for storing application programs and function programs or processes for executing the operation of the electronic device 9600 via the central processing unit 9100.

[0079] The memory 9140 may also include a data storage unit 9143 for storing data, such as contacts, digital data, pictures, sounds, and / or any other data used by the electronic device. The driver storage unit 9144 of the memory 9140 may include various drivers for the electronic device's communication functions and / or for performing other functions of the electronic device (such as messaging applications, address book applications, etc.).

[0080] The communication module 9110 is a transmitter / receiver 9110 that transmits and receives signals via the antenna 9111. The communication module (transmitter / receiver) 9110 is coupled to the central processing unit 9100 to provide input signals and receive output signals, which can be the same as in a conventional mobile communication terminal.

[0081] Based on different communication technologies, multiple communication modules 9110 can be configured in the same electronic device, such as cellular network modules, Bluetooth modules, and / or wireless LAN modules. The communication module (transmitter / receiver) 9110 is also coupled to a speaker 9131 and a microphone 9132 via an audio processor 9130 to provide audio output via the speaker 9131 and receive audio input from the microphone 9132, thereby realizing typical telecommunications functions. The audio processor 9130 may include any suitable buffer, decoder, amplifier, etc. Additionally, the audio processor 9130 is coupled to a central processing unit 9100, enabling on-device recording via the microphone 9132 and on-device playback of stored sound via the speaker 9131.

[0082] Embodiments of this application also provide a computer-readable storage medium capable of implementing all steps of the distributed monitoring system in the above embodiments where the execution subject is a server or client. The computer-readable storage medium stores a computer program that, when executed by a processor, implements all steps of the distributed monitoring system in the above embodiments where the execution subject is a server or client.

[0083] As can be seen from the above description, the computer-readable storage medium provided in this application embodiment, by setting up a status acquisition module, a Kafka cluster module, a core processing server module, and a monitoring and display module, can improve the throughput and processing efficiency of the operation and maintenance system, and can achieve high fault tolerance, low latency, and scalable non-functional requirements.

[0084] Embodiments of this application also provide a computer program product capable of implementing all steps in the distributed monitoring system in the above embodiments, where the execution subject is a server or a client. When the computer program / instruction is executed by a processor, it implements the distributed monitoring system.

[0085] As can be seen from the above description, the computer program product provided in this application embodiment, by setting up a status acquisition module, a Kafka cluster module, a core processing server module, and a monitoring and display module, can improve the throughput and processing efficiency of the operation and maintenance system, and can achieve high fault tolerance, low latency, and scalable non-functional requirements.

[0086] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, apparatus, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0087] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (devices), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0088] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0089] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0090] Specific embodiments have been used to illustrate the principles and implementation methods of this invention. The descriptions of the embodiments above are only for the purpose of helping to understand the method and core ideas of this invention. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this invention. Therefore, the content of this specification should not be construed as a limitation of this invention.

Claims

1. A distributed monitoring system, characterized in that, include: A status acquisition module is used to collect client log files and send them to the Kafka cluster module. The Kafka cluster module includes a load balancer node and a message middleware server node. The Kafka cluster module is used to receive log files sent by the status acquisition module and perform message distribution processing through the load balancer node and the message middleware server node. The core processing server module is used to receive log files sent by the Kafka cluster module and process and consume them. The monitoring and display module is connected to the core processing server module. The monitoring and display module is used to receive the feedback report information, running status data and system indicator summary sent by the core processing server module and perform visualization display. The core processing server module includes a unified access component, a thread pool component, and a high-performance queue component. The unified access component is connected to the Kafka cluster module and is used to allocate threads and distribute messages and tasks to be processed sent by the Kafka cluster module. The thread pool component is connected to the unified access component. The thread pool component is used to provide configurable parameter maintenance functions. Based on the blocking and working status of each thread, it preprocesses the messages distributed by the access component and puts them into the corresponding message queues according to the topic and type labels. The messages are then bound using the bind() method. The thread pool component receives the wake-up callback of the queue pointer and forwards the messages to be processed to the processor component for consumption. The high-performance queue component is connected to the thread pool component. The high-performance queue component is used to maintain the Disruptor queue, receive messages distributed by the thread pool component, maintain independent pointers for each queue, and realize message insertion and retrieval by shifting the pointers forward and backward. The bind() and awake() methods are used to call back the worker thread and send the message back to the processor component for actual consumption.

2. The distributed monitoring system according to claim 1, characterized in that, The core processing server module also includes a central processing unit (CPU) component, which is used to process and consume received messages.

3. The distributed monitoring system according to claim 2, characterized in that, The central processing unit component includes at least one of a sampling processor, a problem processor, a heartbeat processor, a message tree processor, and a business processor.

4. The distributed monitoring system according to claim 1, characterized in that, It also includes a shared component remote library module, which is connected to the status acquisition module and is used to host the source code of the log files collected by the status acquisition module.

5. The distributed monitoring system according to claim 1, characterized in that, It also includes a database storage module, which is connected to the core processing server module and is used to persistently store messages received by the core processing server.

6. The distributed monitoring system according to claim 1, characterized in that, It also includes a source code version hosting module, which includes an offline central repository for version management of source code.

7. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the distributed monitoring system according to any one of claims 1 to 6.

8. A computer-readable storage medium having a computer program stored thereon, characterized in that, When executed by a processor, the computer program implements the distributed monitoring system according to any one of claims 1 to 6.

9. A computer program product comprising a computer program / instructions, characterized in that, When the computer program / instructions are executed by the processor, they implement the distributed monitoring system according to any one of claims 1 to 6.

Images