Nuclear power production monitoring alarm system and construction method thereof

Abstract

The invention belongs to the technical field of nuclear power, and particularly relates to a nuclear power production monitoring alarm system and a construction method thereof. According to the system disclosed by the invention, a set of monitoring system which is comprehensive in monitoring, rich in index and timely in response is built based on Kubernetes and docker containerization virtualization technology and in combination with Promise, the system is seamlessly fused and perfectly connected with cloud native, the system is uninterruptedly monitored in real time, the current state of the system is fed back in real time, the abnormality of the system can be timely checked, and the real-time monitoring of the system is realized. And continuous and stable operation of services is ensured. Besides, the system supports a clustering deployment mode, so that the monitoring service is more stable and robust, and a nuclear power service system can be better helped to master the system state and the abnormal condition in real time.

Description

Technical Field

[0001] This invention belongs to the field of nuclear power technology, specifically relating to a nuclear power production monitoring and alarm system and its construction method. Background Technology

[0002] Currently, informatization and intelligentization are crucial means to drive industrial progress in the nuclear power industry. Faced with increasingly complex system environments, higher demands are being placed on monitoring systems. These systems not only need to monitor various objects, including containers, distributed storage, networks, and various applications, but also need to be able to collect and store large amounts of monitoring data in a timely manner, promptly identify system problems, and perform intelligent analysis and decision support based on this data. Having a comprehensive real-time monitoring system is an urgent need for nuclear power systems and a vital guarantee for ensuring the safe and reliable informatization services of the nuclear power industry.

[0003] The development of cloud computing and the popularization and advancement of virtualization and containerization technologies have given rise to cloud-native technologies. By combining the flexible scheduling of cloud-native technologies with the advantages of containerization and virtualization, we can build real-time monitoring systems that are stable and reliable. Summary of the Invention

[0004] To overcome the problems existing in related technologies, a nuclear power production monitoring and alarm system and its construction method are provided.

[0005] According to one aspect of the present disclosure, a nuclear power production monitoring and alarm system is provided, the system comprising: The Prometheus Server, running on a Kubernetes cluster, is used to capture and store monitoring metrics and generate alerts based on rules. Alertmanager, running in a Kubernetes cluster, is independent of the Prometheus Server and is used to receive, route, and suppress alerts, and can be forwarded via Webhook; One or more exporters running on or accessible within a Kubernetes cluster are used to expose monitoring metrics for specific services or resources. The backend service is used to receive Webhook alerts from Alertmanager, and to parse, store, and make notification decisions. Multiple Kubernetes ConfigMaps are used to store the configuration files for Prometheus Server and Alertmanager, respectively, and are mounted into the corresponding containers.

[0006] According to one aspect of the present disclosure, a method for constructing a nuclear power production monitoring and alarm system is provided, the method comprising: Step 1: Send commands to the Kubernetes API server using the kubectl command-line tool to deploy the Prometheus Server based on a YAML configuration file or binary file; Step 2: Deploy the Alertmanager component independently in the Kubernetes cluster in the same manner; Step 3: Deploy one or more exporters in the Kubernetes cluster to collect monitoring metrics for the specified target and expose the interface; Step 4: Deploy the backend service and configure the crawling conditions of Prometheus Server, including statically specifying and dynamically discovering monitoring targets; configure the communication links between Prometheus Server and Alertmanager, and between Alertmanager and the backend service; wherein, the configuration files of Prometheus Server and Alertmanager are mounted to their respective containers through Kubernetes ConfigMap resources; Step 5: The monitoring target and alarm policy rules are issued through the backend service. The rules are added, deleted or modified by modifying the ConfigMap resource mounted by PrometheusServer, and PrometheusServer is triggered to reload the configuration. Step 6: Configure the recipient information, alarm template, and routing rules for alarm notifications in Alertmanager; Step 7: When a monitoring metric triggers an alarm rule, the Prometheus Server sends the alarm to the Alertmanager. The Alertmanager forwards the alarm to the backend service via a POST request using a Webhook. The backend service parses and persistently stores the alarm information, and decides whether to send a notification based on the policy. If a notification is required, it fills the template with the alarm content and sends it to the designated recipient.

[0007] In one possible implementation, in step 1, the YAML configuration file defines the corresponding Deployment, Service, and ConfigMap resources.

[0008] In one possible implementation, the exporter includes a nodeexporter for collecting basic operating system metrics and a Redis exporter for collecting Redis service metrics.

[0009] In one possible implementation, the Prometheus Server makes the updated monitoring targets and alarm rules effective by rereading the mounted ConfigMap.

[0010] In one possible implementation, the communication link between Alertmanager and the backend service is configured, specifically by setting the Webhook receiving address in the Alertmanager configuration to the endpoint of the backend service.

[0011] In one possible implementation, the backend service parses the received Webhook POST request, extracts the alarm content, and determines whether to trigger email, SMS, or instant message notifications based on predefined rules.

[0012] According to another aspect of the present disclosure, a non-volatile computer-readable storage medium is provided, on which computer program instructions are stored, which, when executed by a processor, implement the above-described method.

[0013] The beneficial effects of this disclosure are as follows: The system proposed here is based on Kubernetes and Docker containerized virtualization technologies, combined with Prometheus, to build a comprehensive monitoring system with rich metrics and timely responses. This system seamlessly integrates and perfectly connects with cloud-native technologies, providing uninterrupted real-time monitoring and feedback on the system's current status. This facilitates timely troubleshooting of system anomalies and ensures the continuous and stable operation of business. Furthermore, the system supports clustered deployment, making the monitoring service more stable and robust, and better enabling nuclear power business systems to grasp the system status and anomalies in real time. Attached Figure Description

[0014] Figure 1 This is a schematic diagram of a nuclear power production monitoring and alarm system shown in an embodiment of this disclosure. Detailed Implementation

[0015] The present disclosure will now be described in further detail with reference to the accompanying drawings and specific embodiments.

[0016] Unless otherwise defined, the technical and scientific terms used in this disclosure have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains; the terminology used in this disclosure is for the purpose of describing particular embodiments only and is not intended to be limiting of this disclosure; the term "comprising" and any variations thereof in this disclosure are intended to cover non-exclusive inclusion. Clearly, the embodiments described in this disclosure are only a part of the embodiments of this disclosure, and not all of them. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of this disclosure without inventive effort are within the scope of protection of this disclosure.

[0017] In this disclosure, the reference to "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this disclosure. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0018] Figure 1 This is a schematic diagram of a nuclear power production monitoring and alarm system according to an embodiment of this disclosure, such as... Figure 1 As shown, the system includes: The Prometheus Server, running on a Kubernetes cluster, is used to scrape and store monitoring metrics and generate alerts based on rules. As the core component of monitoring, the Prometheus Server is responsible for periodically scraping metric data from targets. Each target needs to expose an HTTP service interface. This pull-based approach enables automated upstream and horizontal monitoring, requires less configuration, is easier to scale, and the scraped targets are unaware of the monitoring system's existence, enhancing system controllability. Furthermore, the Prometheus Server also handles historical data storage and provides flexible query functionality. Storage can be local or written to remote storage, significantly expanding the capacity for historical data storage.

[0019] Running independently of the Prometheus Server in the Kubernetes cluster, Alertmanager receives, routes, and suppresses alerts, and can forward them via Webhook. After receiving alert information from the Prometheus Server, Alertmanager removes duplicate data, groups the alerts, routes them to the appropriate receiving method, and then issues the alert. Here, the alert information is sent to the backend service via Webhook. A Webhook is a POST request, and the request body contains important information such as the monitored object, trigger time and frequency, monitoring metrics, alert rules, and current alert value.

[0020] One or more exporters running on or accessible within a Kubernetes cluster are used to expose monitoring metrics for specific services or resources. The exporter provides metric data for the target object and delivers it to the Prometheus Server via an HTTP interface. Metrics can be collected as long as they conform to the interface format. Alternatively, custom exporter programs can be developed to expose metrics to the Prometheus Server for data collection.

[0021] The backend service receives Webhook alerts from Alertmanager, parses, stores, and makes notification decisions. Its functions include modifying alert configuration files and creating alert policies. Furthermore, upon receiving alert information, the backend service determines the alert level, selects recipients, edits the alert content according to a template, and promptly sends the alert information in various ways.

[0022] Multiple Kubernetes ConfigMaps are used to store the configuration files for Prometheus Server and Alertmanager, respectively, and are mounted into the corresponding containers.

[0023] In one possible implementation, a method for constructing a nuclear power production monitoring and alarm system is provided, the method comprising: Step 1: Send instructions to the Kubernetes API server using the kubectl command-line tool to deploy the Prometheus Server based on a YAML configuration file or binary file; the YAML configuration file defines the corresponding Deployment, Service, and ConfigMap resources.

[0024] Step 2: Deploy the Alertmanager component independently in the Kubernetes cluster in the same manner; Step 3: Deploy one or more exporters in the Kubernetes cluster to collect monitoring metrics for specified targets and expose interfaces; the exporters include a node exporter for collecting basic operating system metrics and a Redis exporter for collecting Redis service metrics.

[0025] Step 4: Deploy the backend service and configure the crawling conditions of the Prometheus Server, including statically specifying and dynamically discovering monitoring targets; configure the communication links between the Prometheus Server and Alertmanager, and between Alertmanager and the backend service; wherein, the configuration files of the Prometheus Server and Alertmanager are mounted to their respective containers through Kubernetes ConfigMap resources; the Prometheus Server makes the updated monitoring targets and alarm rules effective by rereading the mounted ConfigMap.

[0026] Step 5: The monitoring target and alarm policy rules are issued through the backend service. The rules are added, deleted or modified by modifying the ConfigMap resource mounted by PrometheusServer, and PrometheusServer is triggered to reload the configuration. Step 6: Configure the recipient information, alarm template, and routing rules for alarm notifications in Alertmanager; configure the communication link between Alertmanager and the backend service, specifically by setting the Webhook receiving address to the endpoint of the backend service in the Alertmanager configuration.

[0027] Step 7: When a monitoring metric triggers an alarm rule, the Prometheus Server sends the alarm to the Alertmanager. The Alertmanager forwards the alarm to the backend service via a POST request using a Webhook. The backend service parses and persistently stores the alarm information, and decides whether to send a notification based on the policy. If a notification is required, it fills the template with the alarm content and sends it to the designated recipient.

[0028] The backend service parses the received Webhook POST request, extracts the alarm content, and determines whether to trigger email, SMS, or instant message notifications based on predefined rules.

[0029] This disclosure can be a system, method, and / or computer program product. A computer program product may include a computer-readable storage medium having computer-readable program instructions loaded thereon for causing a processor to implement various aspects of this disclosure.

[0030] Computer-readable storage media can be tangible devices capable of holding and storing instructions for use by an instruction execution device. Computer-readable storage media can be, for example—but not limited to—electrical storage devices, magnetic storage devices, optical storage devices, electromagnetic storage devices, semiconductor storage devices, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of computer-readable storage media include: portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), static random access memory (SRAM), portable compact disc read-only memory (CD-ROM), digital multifunction disc (DVD), memory sticks, floppy disks, mechanical encoding devices, such as punch cards or recessed protrusions storing instructions thereon, and any suitable combination of the foregoing. The computer-readable storage media used herein are not to be construed as transient signals themselves, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through waveguides or other transmission media (e.g., light pulses through fiber optic cables), or electrical signals transmitted through wires.

[0031] The computer-readable program instructions described herein can be downloaded from computer-readable storage media to various computing / processing devices, or downloaded via a network, such as the Internet, local area network, wide area network, and / or wireless network, to an external computer or external storage device. The network may include copper transmission cables, fiber optic transmission, wireless transmission, routers, firewalls, switches, gateway computers, and / or edge servers. A network adapter card or network interface in each computing / processing device receives the computer-readable program instructions from the network and forwards them to the computer-readable storage media in the respective computing / processing device.

[0032] Computer program instructions used to perform the operations of this disclosure may be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, status setting data, or source code or object code written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Smalltalk, C++, etc., and conventional procedural programming languages ​​such as the "C" language or similar programming languages. The computer-readable program instructions may execute entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or may be connected to an external computer (e.g., via the Internet using an Internet service provider). In some embodiments, electronic circuitry, such as programmable logic circuitry, field-programmable gate arrays (FPGAs), or programmable logic arrays (PLAs), is personalized by utilizing the status information of the computer-readable program instructions to implement various aspects of this disclosure.

[0033] Various aspects of this disclosure are described herein with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this disclosure. It should 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-readable program instructions.

[0034] These computer-readable program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that, when executed by the processor of the computer or other programmable data processing apparatus, they create means for implementing the functions / actions specified in one or more blocks of the flowchart and / or block diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium that causes a computer, programmable data processing apparatus, and / or other device to operate in a particular manner; thus, the computer-readable medium storing the instructions comprises an article of manufacture that includes instructions for implementing aspects of the functions / actions specified in one or more blocks of the flowchart and / or block diagram.

[0035] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby causing the instructions executed on the computer, other programmable data processing apparatus, or other device to perform the functions / actions specified in one or more boxes of a flowchart and / or block diagram.

[0036] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of an instruction containing one or more executable instructions for implementing a specified logical function. In some alternative implementations, the functions marked in the blocks may occur in a different order than those shown in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.

[0037] The various embodiments of this disclosure have been described above. These descriptions are exemplary and not exhaustive, nor are they limited to the disclosed embodiments. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described embodiments. The terminology used herein is chosen to best explain the principles, practical application, or improvement of the technology in the market, or to enable others skilled in the art to understand the embodiments disclosed herein.

Claims

1. A nuclear power production monitoring and alarm system, characterized in that, The system includes: The Prometheus Server, running on a Kubernetes cluster, is used to capture and store monitoring metrics and generate alerts based on rules. Alertmanager, running in a Kubernetes cluster, is independent of the Prometheus Server and is used to receive, route, and suppress alerts, and can be forwarded via Webhook; One or more exporters running on or accessible within a Kubernetes cluster are used to expose monitoring metrics for specific services or resources. The backend service is used to receive Webhook alerts from Alertmanager, and to parse, store, and make notification decisions. Multiple Kubernetes ConfigMaps are used to store the configuration files for Prometheus Server and Alertmanager, respectively, and are mounted into the corresponding containers.

2. A method for constructing a nuclear power production monitoring and alarm system, characterized in that, The method includes: Step 1: Send commands to the Kubernetes API server using the kubectl command-line tool to deploy the Prometheus Server based on a YAML configuration file or binary file; Step 2: Deploy the Alertmanager component independently in the Kubernetes cluster in the same manner; Step 3: Deploy one or more exporters in the Kubernetes cluster to collect monitoring metrics for the specified target and expose the interface; Step 4: Deploy the backend service and configure the crawling conditions of Prometheus Server, including statically specifying and dynamically discovering monitoring targets; configure the communication links between Prometheus Server and Alertmanager, and between Alertmanager and the backend service; wherein, the configuration files of Prometheus Server and Alertmanager are mounted to their respective containers through KubernetesConfigMap resources. Step 5: The monitoring target and alarm policy rules are issued through the backend service. The rules are added, deleted or modified by modifying the ConfigMap resource mounted by PrometheusServer, and PrometheusServer is triggered to reload the configuration. Step 6: Configure the recipient information, alarm template, and routing rules for alarm notifications in Alertmanager; Step 7: When a monitoring metric triggers an alarm rule, the Prometheus Server sends the alarm to the Alertmanager. The Alertmanager forwards the alarm to the backend service via a POST request using a Webhook. The backend service parses and persistently stores the alarm information, and decides whether to send a notification based on the policy. If a notification is required, it fills the template with the alarm content and sends it to the designated recipient.

3. The method according to claim 1, characterized in that, In step 1, the YAML configuration file defines the corresponding Deployment, Service, and ConfigMap resources.

4. The method according to claim 1, characterized in that, The exporter includes a node exporter for collecting basic operating system metrics and a Redis exporter for collecting Redis service metrics.

5. The method according to claim 1, characterized in that, The Prometheus Server applies updated monitoring targets and alerting rules by rereading the mounted ConfigMap.

6. The method according to claim 1, characterized in that, Configure the communication link between Alertmanager and the backend service. Specifically, set the Webhook receiving address in the Alertmanager configuration to the endpoint of the backend service.

7. The method according to claim 1, characterized in that, The backend service parses the received Webhook POST request, extracts the alarm content, and determines whether to trigger email, SMS, or instant message notifications based on predefined rules.

8. A non-volatile computer-readable storage medium storing computer program instructions thereon, characterized in that, When the computer program instructions are executed by the processor, they implement the method described in any one of claims 2 to 7.

Images