Monitoring system method and system under multi-activity architecture

By designing system monitoring, data display analysis, alarm and switching decision matrix modules under a multi-active architecture, the problem of the inability to effectively monitor and switch faults in the existing technology is solved, and the health monitoring and business continuity guarantee of service instances are achieved.

CN118945076AInactive Publication Date: 2024-11-12RURAL CREDIT BANKS FUNDS CLEARING CENT CO LTD
View PDF 6 Cites 0 Cited by

Patent Information

Application Number
CN202410992209.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-23
Publication Date
2024-11-12
Estimated Expiration
Not applicable · inactive patent

AI Technical Summary

Technical Problem

The existing technology is difficult to effectively monitor the health status of service instances and respond quickly to failures under a multi-active architecture, and cannot support complex monitoring switching scenarios, especially in commercial software monitoring with high costs and limited custom expansion, which cannot meet the high business. Availability and continuity requirements.

Method used

A monitoring system system under a multi-active architecture is designed, including system monitoring module, monitoring data display analysis module, alarm module and switching decision matrix module. Through probes, indicators are collected, health status is analyzed, alarm threshold is defined, faults are automatically judged and Perform switching decisions to achieve intelligent analysis and automatic switching.

Benefits of technology

Real-time health monitoring and rapid response to service instances is realized, business continuity is ensured, and rapid positioning problems are ensured through transaction link tracking and node detection, ensuring stable operation of the system.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118945076A_ABST
    Figure CN118945076A_ABST
Patent Text Reader

Abstract

The invention is suitable for the technical field of system monitoring, and provides a method and a system for monitoring a system under a multi-activity architecture. The method comprises the following steps: monitoring a system; displaying and analyzing the monitoring data; alarming; and switching the decision matrix. According to the invention, the service continuity is guaranteed by monitoring the health degree of the service instance in real time, analyzing the alarm frequency and the health threshold value of the service instance in the cluster, matching the fault scene and performing intelligent decision, and triggering the switching of the unit level or the IDC level. And meanwhile, the resource use condition of the system and the transaction success rate of the business are monitored in real time, and the system and business conditions are monitored and alarmed in time. In addition, through transaction link tracking and node detection functions, operation and maintenance personnel are helped to quickly position and solve problems, and stable operation of the system is ensured.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention belongs to the technical field of system monitoring, and in particular, relates to a monitoring system method and system under a multi-active architecture. Background Art

[0002] With the rapid development of information technology, enterprise business has increasingly higher requirements for system stability and continuity. In a distributed system architecture, especially in a multi-active architecture, how to ensure the health of service instances and how to quickly respond and switch when a failure occurs has become an urgent problem to be solved in the industry.

[0003] Currently, the more popular monitoring methods are mainly divided into open source tool monitoring, commercial software monitoring, etc. Open source tool monitoring is relatively simple to implement and low in cost, suitable for simple monitoring scenarios. The disadvantage is that the monitoring indicators are single and the functions are relatively limited. It is difficult to track the transaction links within the application and cannot support complex monitoring switching scenarios. Commercial software monitoring is provided by manufacturers, which is powerful and stable, with perfect after-sales service and technical support. The disadvantage is that the cost is high, and because it is closed source software, customization and expansion are limited, it is difficult to support fault intelligent switching under the multi-active architecture, and cannot meet the high availability and continuity of the business well. From the above, it can be seen that there is still a lack of effective, commonly used, and intelligent monitoring system methods and systems under the multi-active architecture on the market. Research on monitoring system methods and systems that support intelligent analysis and matching switching under the multi-active architecture is urgent. To this end, the present invention proposes a monitoring system method and system under the multi-active architecture. Summary of the invention

[0004] The purpose of the present invention is to provide a monitoring system method and system under a multi-active architecture, aiming to solve the problems raised in the above background technology.

[0005] To achieve the above object, the present invention provides the following technical solutions:

[0006] A monitoring system under a multi-active architecture includes:

[0007] System monitoring module, which is used to deploy probes in distributed systems under multi-active architecture, and use probes to collect and monitor indicators of the access layer, application layer, middleware, and infrastructure;

[0008] The monitoring data display and analysis module is used to collect, summarize, and count multi-center monitoring indicators, and display them after processing; through comprehensive analysis of various monitoring indicators, the health status of application service instances is evaluated;

[0009] The alarm module defines reasonable alarm thresholds and conditions based on business requirements and system characteristics, and issues warnings in a timely manner when indicators exceed the normal range;

[0010] The switching decision matrix module is used to group the alarm information to determine the fault type, and to determine whether it is a fault based on the set fault rules; if the fault threshold is reached, it is determined to be a fault, and the decision matrix will automatically match the fault scenario to determine whether center switching is required; if necessary, the corresponding switching information will be sent to the relevant application operation and maintenance execution center switching or automatic switching will be performed with the help of the dependent switching platform.

[0011] A monitoring system method under a multi-active architecture includes the following steps:

[0012] Step 1: System monitoring: Deploy probes in the distributed system under the multi-active architecture, and use the probes to collect and monitor indicators at the access layer, application layer, middleware, and infrastructure.

[0013] Step 2: Monitoring data display and analysis: Collect, summarize, and count multi-center monitoring indicators, and display them after processing; evaluate the health status of application service instances by comprehensively analyzing various monitoring indicators;

[0014] Step 3: Alarm: Define reasonable alarm thresholds and conditions based on business requirements and system characteristics, and issue warnings in a timely manner when indicators exceed the normal range;

[0015] Step 4, switching decision matrix: When the system under the multi-active architecture monitors a node abnormality, it will send an alarm message to the switching decision matrix. The switching decision matrix will automatically group the alarm information to determine the fault type, and comprehensively determine whether it is a fault based on the set fault rules; if the fault threshold is reached, it is determined to be a fault, and the decision matrix will automatically match the fault scenario to determine whether center switching is required; if necessary, the corresponding switching information will be sent to the relevant application operation and maintenance to execute the center switching or perform automatic switching with the help of the dependent switching platform.

[0016] Furthermore, in step 1, the specific monitoring includes:

[0017] a. Real-time monitoring of basic resources, including hosts, basic middleware indicators and application throughput;

[0018] b. Use bypass links to monitor and collect Internet traffic from multiple centers and monitor dedicated line ingress traffic;

[0019] c. Monitor each application node deployed in multiple centers and collect statistics on the total number of transactions, success rate, failure rate, and timeout rate;

[0020] d. Use probe detection to detect the connectivity of internal nodes, middleware, and dependent external system services of multi-center deployed systems;

[0021] e. Through distributed link tracking, monitor the flow of multi-center transactions and conduct full link tracking of the application node processing process.

[0022] Furthermore, the probe obtains indicators in two ways:

[0023] One type is to calculate and expose the status of the hardware and operating system of the monitored node by reading files under the proc file system, collect detailed information about system performance, and convert the information data into a unified monitoring data specification, which is summarized, analyzed and displayed by the monitoring system;

[0024] The other type is to send query requests to middleware through the TCP protocol to obtain corresponding monitoring indicators; at the same time, the probe detects the availability and response time indicators of external services or network endpoints, that is, to provide health checks and performance monitoring for various network services inside and outside the cluster and container.

[0025] Furthermore, the specific process of step 3 is as follows:

[0026] The probes deployed at each node collect various indicators of the system under the multi-active architecture in real time and summarize them into the monitoring system. The monitoring system periodically checks and calculates whether the collected data meets the alarm trigger conditions at the set frequency. If some indicators are found to be abnormal and meet the alarm trigger conditions, the alarm information is pushed to the alarm platform. The alarm platform further processes the received alarm information and finally sends the processed alarm information to the switching decision matrix and relevant recipients.

[0027] Furthermore, the switching decision matrix supports the definition of fault types and fault rules. The fault types are used to classify and group faults. The fault rules are used to define fault trigger modes, including instance quantity threshold trigger mode and alarm number trigger mode, which are whether the current number of surviving instances is less than a preset threshold and whether the number of alarms received is greater than a preset alarm number threshold.

[0028] Furthermore, in step 4, for the peripheral system node failure scenario, imperceptible automatic switching is achieved by domaining the peripheral system.

[0029] Compared with the prior art, the present invention has the following beneficial effects:

[0030] The present invention monitors the health of service instances in real time, analyzes the alarm frequency and the health threshold of service instances in the cluster, matches fault scenarios and makes intelligent decisions, triggers unit-level or IDC-level switching, and ensures business continuity. At the same time, it monitors the resource usage of the system and the transaction success rate of the business in real time to achieve timely monitoring and alarm of the system and line status. In addition, through the transaction link tracking and node detection functions, it helps operation and maintenance personnel to quickly locate and solve problems and ensure the stable operation of the system. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] Figure 1 It is a flow chart of the present invention. DETAILED DESCRIPTION

[0032] In order to make the purpose, technical solution and advantages of the present invention more clearly understood, the present invention is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not used to limit the present invention.

[0033] The specific implementation of the present invention is described in detail below in conjunction with specific embodiments.

[0034] An embodiment of the present invention provides a monitoring system under a multi-active architecture, including:

[0035] System monitoring module, which is used to deploy probes in distributed systems under multi-active architecture, and use probes to collect and monitor indicators of the access layer, application layer, middleware, and infrastructure;

[0036] The monitoring data display and analysis module is used to collect, summarize, and count multi-center monitoring indicators, and display them after processing; through comprehensive analysis of various monitoring indicators, the health status of application service instances is evaluated;

[0037] The alarm module defines reasonable alarm thresholds and conditions based on business requirements and system characteristics, and issues warnings in a timely manner when indicators exceed the normal range;

[0038] The switching decision matrix module is used to group the alarm information to determine the fault type, and to determine whether it is a fault based on the set fault rules; if the fault threshold is reached, it is determined to be a fault, and the decision matrix will automatically match the fault scenario to determine whether center switching is required; if necessary, the corresponding switching information will be sent to the relevant application operation and maintenance execution center switching or automatic switching will be performed with the help of the dependent switching platform.

[0039] like Figure 1 As shown, an embodiment of the present invention provides a monitoring system method under a multi-active architecture, comprising the following steps:

[0040] Step 1, system monitoring: At present, the distributed system under the multi-active architecture mainly adopts container technology, and the monitored objects and indicators have also undergone subtle changes. From the original host as the main body, it has become the container and service as the main body. The requirements for monitoring have gradually changed from "seeing indicators" to "observability" of the monitored objects. The present invention collects and monitors indicators of the access layer, application layer, middleware, infrastructure, etc. of the distributed system under the multi-active architecture by deploying probes. The way in which the probe obtains indicators can be roughly divided into two categories: one is to calculate and expose the status of the hardware and operating system of the monitored node by reading the files under the proc file system, collect detailed information about the system performance, and convert the information data into a unified monitoring data specification, which is summarized, analyzed and displayed by the monitoring system. The other is to send a query request to the middleware, etc. through the TCP protocol to obtain the corresponding monitoring indicators; at the same time, the probe can detect indicators such as the availability and response time of external services or network endpoints, that is, to provide health checks and performance monitoring for various network services inside and outside the cluster and container.

[0041] Specific monitoring includes:

[0042] a. Real-time monitoring of basic resources, including basic indicators such as hosts and middleware, application throughput, etc.

[0043] b. Use bypass links to monitor and collect Internet traffic from multiple centers and monitor dedicated line ingress traffic.

[0044] c. Monitor each application node deployed in multiple centers and collect statistics on total transactions, success rate, failure rate, timeout rate, etc.

[0045] d. Use probe detection to detect the connectivity of internal nodes, middleware, and dependent external system services of the multi-center deployed system.

[0046] e. Through distributed link tracking, monitor the flow of multi-center transactions and conduct full link tracking of the application node processing process.

[0047] Step 2: Monitoring data display and analysis: Collect, summarize, and count multi-center monitoring indicators, and display them after processing. Support multiple data sources and custom data sources. Through comprehensive analysis of various monitoring indicators, accurately evaluate the health status of application service instances.

[0048] Step 3, Alarm: The monitoring system supports user-defined alarm strategies. Based on business requirements and system characteristics, users can define reasonable alarm thresholds and conditions. For example, for response time, it can be set to be considered abnormal if it exceeds a certain threshold; for node status, it can be set to be considered abnormal if the node is down, etc. The probes deployed at each node collect various indicators of the system under the multi-active architecture in real time and summarize them to the monitoring system. The monitoring system periodically checks and calculates whether the collected data meets the alarm trigger conditions according to the set frequency. If some indicators are found to be abnormal and meet the alarm trigger conditions, the alarm information is pushed to the alarm platform. The alarm platform further processes the received alarm information, such as grouping, noise reduction, routing, notification, etc., and finally sends the processed alarm information to the switching decision matrix and relevant recipients.

[0049] Step 4, Switching Decision Matrix: The switching decision matrix is ​​used to support intelligent switching after monitoring faults in a multi-active architecture. It can respond and switch quickly when a fault occurs to ensure business continuity. The switching decision matrix supports the definition of fault types and fault rules. Fault types are used to classify and group faults; fault rules are used to define fault trigger modes, including instance quantity threshold trigger mode and alarm number trigger mode, which are whether the current number of surviving instances is less than the preset threshold, and whether the number of alarms received is greater than the preset alarm number threshold.

[0050] When the system under the multi-active architecture monitors a node abnormality, it will send an alarm message to the switching decision matrix. The switching decision matrix will automatically group the alarm information to determine the fault type and determine whether it is a fault based on the set fault rules. If the fault threshold is reached, it is determined to be a fault. The decision matrix will automatically match the fault scenario to determine whether a central switch is required. If necessary, the corresponding switching information will be sent to the relevant application operation and maintenance to perform the central switch or perform automatic switching with the help of the dependent switching platform. For the peripheral system node failure scenario, non-perceived automatic switching is achieved through the domain name of the peripheral system.

[0051] The above are only preferred embodiments of the present invention. It should be pointed out that, for those skilled in the art, several modifications and improvements can be made without departing from the concept of the present invention. These should also be regarded as the protection scope of the present invention. These will not affect the effect of the implementation of the present invention and the practicality of the patent.

Claims

1. A monitoring system under a multi-active architecture, It is characterized in that include: System monitoring module, which is used to deploy probes in distributed systems under multi-active architecture, and use probes to collect and monitor indicators of the access layer, application layer, middleware, and infrastructure; The monitoring data display and analysis module is used to collect, summarize, and count multi-center monitoring indicators, and display them after processing; through comprehensive analysis of various monitoring indicators, the health status of application service instances is evaluated; The alarm module defines reasonable alarm thresholds and conditions based on business requirements and system characteristics, and issues warnings in a timely manner when indicators exceed the normal range; Switching decision matrix module is used to group alarm information to determine the fault type and determine whether it is a fault based on the set fault rules; If the fault threshold is reached, it is judged as a fault, and the decision matrix will automatically match the fault scenario to determine whether center switching is required; if necessary, the corresponding switching information will be sent to the relevant application operation and maintenance execution center switching or automatic switching will be performed with the help of the dependent switching platform.

2. A monitoring system method under a multi-active architecture, It is characterized in that The following steps are involved: Step 1: System monitoring: Deploy probes in the distributed system under the multi-active architecture, and use the probes to collect and monitor indicators at the access layer, application layer, middleware, and infrastructure. Step 2: Monitoring data display and analysis: Collect, summarize, and count multi-center monitoring indicators, and display them after processing; evaluate the health status of application service instances by comprehensively analyzing various monitoring indicators; Step 3: Alarm: Define reasonable alarm thresholds and conditions based on business requirements and system characteristics, and issue warnings in a timely manner when indicators exceed the normal range; Step 4, switch decision matrix: When the system under the multi-active architecture monitors a node abnormality, it will send an alarm message to the switch decision matrix. The switch decision matrix will automatically group the alarm information to determine the fault type and determine whether it is a fault based on the set fault rules; If the fault threshold is reached, it is judged as a fault, and the decision matrix will automatically match the fault scenario to determine whether center switching is required; if necessary, the corresponding switching information will be sent to the relevant application operation and maintenance execution center switching or automatic switching will be performed with the help of the dependent switching platform.

3. The monitoring system method under the multi-active architecture according to claim 2, It is characterized in that In step 1, the specific monitoring includes: a. Real-time monitoring of basic resources, including hosts, basic middleware indicators and application throughput; b. Use bypass links to monitor and collect Internet traffic from multiple centers and monitor dedicated line ingress traffic; c. Monitor each application node deployed in multiple centers and collect statistics on the total number of transactions, success rate, failure rate, and timeout rate; d. Use probe detection to detect the connectivity of internal nodes, middleware, and dependent external system services of multi-center deployed systems; e. Through distributed link tracking, monitor the flow of multi-center transactions and conduct full link tracking of the application node processing process.

4. The monitoring system method under the multi-active architecture according to claim 2, It is characterized in that The probe obtains indicators in two ways: One type is to calculate and expose the status of the hardware and operating system of the monitored node by reading files under the proc file system, collect detailed information about system performance, and convert the information data into a unified monitoring data specification, which is summarized, analyzed and displayed by the monitoring system; The other type is to send query requests to middleware through the TCP protocol to obtain corresponding monitoring indicators; at the same time, the probe detects the availability and response time indicators of external services or network endpoints, that is, to provide health checks and performance monitoring for various network services inside and outside the cluster and container.

5. The monitoring system method under the multi-active architecture according to claim 2, It is characterized in that The specific process of step 3 is as follows: The probes deployed at each node collect various indicators of the system under the multi-active architecture in real time and summarize them into the monitoring system. The monitoring system periodically checks and calculates whether the collected data meets the alarm trigger conditions at the set frequency. If some indicators are found to be abnormal and meet the alarm trigger conditions, the alarm information is pushed to the alarm platform. The alarm platform further processes the received alarm information and finally sends the processed alarm information to the switching decision matrix and relevant recipients.

6. The monitoring system method under the multi-active architecture according to claim 2, It is characterized in that The switching decision matrix supports the definition of fault types and fault rules. The fault types are used to classify and group faults. The fault rules are used to define fault trigger modes, including instance quantity threshold trigger mode and alarm number trigger mode, which are respectively whether the current number of surviving instances is less than a preset threshold and whether the number of alarms received is greater than a preset alarm number threshold.

7. The monitoring system method under the multi-active architecture according to claim 2, It is characterized in that In step 4, for the peripheral system node failure scenario, imperceptible automatic switching is achieved by domaining the peripheral system.

Citation Information

Patent Citations

  • Methods and systems for deploying multi-active data centers

    CN109819004A

  • Method, server and equipment based on zabbix monitoring alarm and storage medium

    CN110048888A

  • Equipment operation and maintenance management method and device

    CN113821412A

  • Annular two-place three-center fault diagnosis method, system and device

    CN114338369A

  • Distributed cloud disaster recovery method and system

    CN116069556A