A method and system for calculating the health of application systems based on edge probes
By using an edge probe-driven, end-to-end closed-loop architecture combined with multi-dimensional data processing technology, the problem of the disconnect between perception and computation in edge computing solutions under special environments is solved. This enables high-confidence application system health assessment and graded early warning, and is suitable for special scenarios such as mines and remote areas.
Patent Information
- Application Number
- CN202610825667.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-06-09
- Publication Date
- 2026-11-17
AI Technical Summary
Existing edge computing solutions can only perform simple inference calculations without relying on cloud-assisted modeling. They suffer from a significant defect of disconnect between perception and computation, and cannot complete the 'collection-computation-early warning' processing loop, resulting in low confidence of the calculation results.
Adopting an architecture of 'edge probe + deep node integration', the system achieves a closed-loop end-to-end data collection, preprocessing, computation, and early warning through the deep integration of embedded monitoring probes and edge computing node hardware. Combined with Z-Score standardization, isolated forest outlier removal, and SMOTE data balancing technology, it performs multi-dimensional data processing and builds a hierarchical early warning and operation and maintenance system.
It enables end-to-end local closed-loop computing without cloud dependency in special environments, provides high-confidence application system health assessment and graded early warning, ensures data security and computing accuracy, and is suitable for special scenarios such as mines and remote areas.
Smart Images

Figure CN123114880A_ABST
Abstract
Description
Technical Field
[0001] This invention belongs to the field of network and distributed computing technology, and in particular relates to a method and system for calculating the health of application systems based on edge probes. Background Technology
[0002] As application systems grow in scale and diversify in scenarios, health assessment has become a core aspect of operations and maintenance management, leading to two main architectures: centralized cloud-based and edge computing-based. In special equipment deployment environments such as mines and remote areas, data uploads to the cloud pose high security risks and are difficult to implement, making centralized cloud-based solutions impractical. Existing edge computing solutions, without cloud-assisted modeling, can only perform simple inference calculations, exhibiting a significant disconnect between perception and computation, failing to complete the "collection-computation-early warning" processing loop, and resulting in low confidence levels in the calculation results. Therefore, a standalone solution that deeply integrates edge probes and local computing is urgently needed for calculating system health in special scenarios. Summary of the Invention
[0003] This invention provides a method and system for calculating the health of application systems based on edge probes, which solves the problem that existing edge computing solutions can only perform simple inference calculations without relying on cloud-assisted modeling, resulting in a significant disconnect between perception and computation.
[0004] Firstly, a method for calculating the health status of an application system based on edge probes is provided, the method comprising: Step 1: Deploy edge nodes and, based on these, deploy monitoring probes to complete data collection; Step 2: Preprocess the collected data locally to obtain preprocessed data; Step 3: Obtain the application system health value based on the preprocessed data; Step 4: Visualize the health status of the application system, presenting an overall overview of system health indicators.
[0005] Secondly, a health calculation system for application systems based on edge probes is provided, the system comprising: The data acquisition module is used to deploy edge nodes and, based on these, deploy monitoring probes to complete data acquisition. The data preprocessing module is used to preprocess the collected data and perform local data processing to obtain preprocessed data. The health value acquisition module is used to acquire the application system's health value based on preprocessed data; The display module is used to visualize the health status of the application system, presenting an overall picture of the system's health indicators.
[0006] Beneficial effects: 1. A cloud-free closed-loop architecture combining edge probes and deep node integration. This technology is the first to deeply integrate embedded monitoring probes and edge computing node hardware. The monitoring probes collect data on the operating status and performance of application software and hardware, enabling local initial screening and filtering. The edge nodes integrate preprocessing, computing, storage, and early warning modules, achieving a complete local closed loop of "collection-processing-computation-early warning," suitable for special network environments and eliminating reliance on the cloud.
[0007] 2. Hierarchical early warning and operation and maintenance system based on special environments To address the challenge of delayed operation and maintenance in special environments, a closed-loop mechanism of "quantitative scoring - tiered early warning - local push - precise handling" is constructed. Based on a health score of 0-100, three-tiered early warning thresholds are set, and differentiated response priorities are configured. Anomaly details and handling suggestions are pushed in real time through local terminals, without cloud interaction, filling the technical gap in independent operation and maintenance in special environments.
[0008] 3. Local security processing mechanism for multi-dimensional data To address the data security and quality requirements of special environments, an innovative two-tier mechanism of "probe initial filtering + edge node deep preprocessing" is designed. It adopts Z-Score standardization, isolated forest outlier removal, and SMOTE data balancing technology to achieve local storage of data throughout the process, avoid the risk of data leakage, and ensure the accuracy of health calculation.
[0009] Other features and advantages of the invention will be set forth in the description which follows, and will be apparent in part from the description, or may be learned by practicing the invention. The objects and other advantages of the invention may be realized and obtained by means of the structures particularly pointed out in the written description, claims, and drawings. Attached Figure Description
[0010] The accompanying drawings, which are included to provide a further understanding of the invention and form part of this invention, illustrate exemplary embodiments of the invention and are used to explain the invention, but do not constitute an undue limitation of the invention. In the drawings: Figure 1 This is a schematic diagram illustrating the implementation process of an application system health calculation method based on edge probe driving according to an embodiment of the present invention; Figure 2 This is a schematic diagram illustrating an application health algorithm provided according to an embodiment of the present invention; Figure 3 This is a schematic diagram of the primary interface of an application health monitoring screen provided according to an embodiment of the present invention; Figure 4This is a schematic diagram of a two-level interface for an application health monitoring screen provided according to an embodiment of the present invention. Detailed Implementation
[0011] To make the objectives, technical solutions, and advantages of this specification clearer, the technical solutions of this specification will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this specification, and not all of them. Based on the embodiments in this specification, all other embodiments obtained by those skilled in the art without creative effort are within the protection scope of this specification.
[0012] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, apparatus, product, or device that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or devices.
[0013] The technical solutions provided in the various embodiments of this specification are described in detail below with reference to the accompanying drawings.
[0014] To improve the ability to monitor the health status of application systems in real time, this invention provides a method and system for calculating the health status of application systems based on edge probes.
[0015] Figure 1 This is a schematic diagram illustrating the implementation process of an application system health calculation method based on edge probe driving according to an embodiment of the present invention. (See attached diagram.) Figure 1 The method includes: Step 1: Deploy edge nodes and, based on these, deploy monitoring probes to complete data collection; Step 2: Preprocess the collected data locally to obtain preprocessed data; Step 3: Obtain the application system health value based on the preprocessed data; Step 4: Visualize the health status of the application system, presenting an overall overview of system health indicators.
[0016] In one specific implementation, step 1: deploying edge nodes and, based on these, deploying monitoring probes to complete data collection, specifically includes: Step 1.1 Hardware Integration Deploy edge nodes and mount edge probes directly on the edge nodes via general-purpose input / output (GPIO) interfaces. The edge probes establish a data transmission channel with the local storage module and preprocessing module of the edge nodes through an internal bus. Step 1.2 Deployment of Data Acquisition Software A lightweight data acquisition program is embedded in the edge probe, and the acquisition frequency is set, specifically once per second, to collect various indicator data of each application node.
[0017] The key monitoring indicators for the application are shown in Table 1.
[0018] Table 1 Key Indicators for Application Monitoring It should be noted that edge probes are lightweight acquisition or detection agents deployed at the edge, close to the data source / user. The difference between edge nodes and the cloud is: Edge nodes: computing, storage, and network devices located in the last mile from the data source or user, responsible for processing data locally; Cloud: Centralized / regional data centers provide massive, elastic resource pools, but with greater physical distances; In one specific implementation, step 2: preprocessing the collected data, performing local data processing to obtain preprocessed data, specifically includes: Step 2.1 Z-Score Standardization The collected data of various indicators are normalized and converted into the range of [-1,1] to eliminate differences in dimensions. Step 2.2 Outlier Removal in Isolated Forests Set an outlier detection threshold to remove extreme data that deviates from the normal distribution; Step 2.3 SMOTE Data Balancing Since fault data accounts for a small proportion, virtual fault data is generated through interpolation to ensure the model training effect.
[0019] It should be noted that Z-Score standardization is a method of transforming the original data into a distribution with a mean of 0 and a standard deviation of 1. ,in, The original value, The population (or sample) mean; This represents the population (or sample) standard deviation; it indicates how many standard deviations a value is above or below the mean; for example, z=1.5 means "1.5 standard deviations above the mean"; z=-0.8 means "0.8 standard deviations below the mean". Outlier removal in isolated forests involves randomly making a few cuts and seeing who gets isolated the fastest. SMOTE data balancing technique is an oversampling method that synthesizes new samples to solve the problem of the model ignoring the minority class when the classes are extremely imbalanced. It interpolates between minority class samples to artificially create reasonable new samples instead of simply copying them.
[0020] In one specific implementation, see Figure 2 Step 3: Obtaining the application system health value based on the preprocessed data, specifically includes: The preprocessed data of each indicator of each application node are compared with the corresponding preset thresholds, and the three-level alarm level and frequency of each application node are determined according to the preset rules; the score corresponding to the three-level alarm level can be set manually according to actual needs. The application uses a single server as a node, including database nodes, middleware nodes, and application component nodes. When metrics exceed certain thresholds, different levels of alerts are triggered. Node health is calculated as: Total Score - Critical Alerts * Critical Alert Score - Important Alerts * Important Alert Score - General Alerts * General Alert Score. Application health is calculated by combining the health of the node cluster and the health of application probing (simulating user network requests to the application), as detailed below: Step 3.1 Calculate the health of a single node. The health of a single node is calculated using the following formula: in, Indicates the first The health of each node N 紧急 This represents the number of times the application has issued emergency alerts. S 紧急 This represents the points that will be deducted for this emergency alarm. Similarly, N 重要 This represents the number of times the application has issued significant alerts. S 重要 This represents the points deducted for important warnings. N 一般 This represents the number of times the application has generated general alerts. S 一般 This represents the points deducted for a typical alarm. The minimum value is limited to 0; Step 3.2 Calculate the health of the node group Application deployment node clusters are divided into critical nodes and non-critical nodes. Critical nodes play a crucial role in application availability and have a greater impact on application health. The health score of the node cluster is calculated by dividing the critical node score by 100 and then multiplying it by the average health score of the non-critical nodes. The formula is as follows: ; wherein, represents the health degree of all node clusters of the application, represents the health degree of critical nodes , represents the health degree of non-critical nodes ; and respectively represent the total number of critical nodes and non-critical nodes; and have subscripts that are respectively the uppercase English initial of the Chinese character for critical "Guan" and the uppercase English initial of the Chinese character for non-critical "Fei"; Step 3.3 Calculate the health degree of dial testing Perform multiple types of dial testing on each application node and important functional modules, generate urgent, important, and general alarms according to the return code and delay of the dial testing, and the single dial testing health degree has a minimum value of 0, which follows the same algorithm as the node health degree, and is obtained by subtracting the alarm score from the specified total score, and the overall dial testing health degree is obtained by averaging the health degrees of all dial tests: ; wherein, represents the total number of dial tests; Step 3.4 Calculate the health degree of the application Taking the dial testing health degree as an influence factor, the health degree of the application is calculated in combination with the node cluster health degree : .
[0021] For example, if an urgent alarm is set to 30 points, an important alarm to 10 points, and a general alarm to 3 points, an application consists of one database node, two middleware nodes and one application component node. Since the database is deployed as a standalone unit, it is set as a critical node.
[0022] In a specific embodiment, the step 4: visually presenting the health status of the application system, and integrally presenting indicators related to system health degree, specifically includes: Step 4.1 Design the primary interface of the application health degree monitoring large screen The application health monitoring dashboard's primary interface focuses on displaying application system usage. Building upon basic network and resource monitoring, it takes a business-centric approach, organizing the ITI resources that make up the business system into a business logic model based on their relationships. This ends the traditional, fragmented resource monitoring and management, establishing a monitoring interface from a business perspective. The dashboard displays core application health, overall application monitoring rankings, application availability, abnormal application statistics, number of monitored devices, current alarm count, and alarm trend charts. (See [link to relevant documentation]). Figure 3 ; Step 4.2 Design the secondary interface of the application health monitoring screen. As an application details view, it displays application health values, application ledger information, application database, middleware, component node health and alarm values, application probing access trends, and alarm information. Device information can be drilled down to the device monitoring details page. See also... Figure 4 This interface provides a rich set of data visualization components, using more intuitive charts to display monitoring data, quickly locate faulty nodes in the application structure, effectively improve operational efficiency, and ensure the stability of application systems.
[0023] This invention provides a method for calculating the health of an application system based on edge probes. By monitoring probes to collect data on the operating status and performance of application software and hardware, an application system health value algorithm is designed, and combined with the application deployment architecture, the overall health status of the application system is comprehensively evaluated.
[0024] Based on the same inventive concept, the present invention also provides a health calculation system for application systems driven by edge probes, the system comprising: The data acquisition module is used to deploy edge nodes and, based on these, deploy monitoring probes to complete data acquisition. The data preprocessing module is used to preprocess the collected data and perform local data processing to obtain preprocessed data. The health value acquisition module is used to acquire the application system's health value based on preprocessed data; The display module is used to visualize the health status of the application system, presenting an overall picture of the system's health indicators.
[0025] In one specific implementation, the deployment acquisition module is specifically used for: Hardware integration Deploy edge nodes and mount edge probes directly on the edge nodes via general-purpose input / output (GPIO) interfaces. The edge probes establish a data transmission channel with the local storage module and preprocessing module of the edge nodes through an internal bus. Data collection software deployment A lightweight data acquisition program is embedded in the edge probe, and the acquisition frequency is set to collect various indicator data of each application node.
[0026] In one specific embodiment, the data preprocessing module is specifically used for: Z-Score Standardization The collected data of various indicators are normalized to eliminate differences in units; Outlier removal in isolated forests Set an outlier detection threshold to remove extreme data that deviates from the normal distribution; SMOTE Data Balancing Since fault data accounts for a small proportion, virtual fault data is generated through interpolation to ensure the model training effect.
[0027] In one specific embodiment, the health value acquisition module is specifically used for: The preprocessed data of each indicator of each application node are compared with the corresponding preset thresholds, and the three-level alarm level and frequency of each application node are determined according to the preset rules; the score corresponding to the three-level alarm level is set according to actual needs. The application uses a single server as a node, including database nodes, middleware nodes, and application component nodes. When a metric exceeds a certain threshold, different levels of alerts are triggered. Node health is calculated as: Total Score - Emergency Alerts * Emergency Alert Score - Important Alerts * Important Alert Score - General Alerts * General Alert Score. Application health is calculated by combining the health of the node cluster and the health of the application during probing, as detailed below: Calculate the health of a single node The health of a single node is calculated using the following formula: in, Indicates the first The health of each node N 紧急 This represents the number of times the application has issued emergency alerts. S 紧急 This represents the points that will be deducted for this emergency alarm. Similarly, N 重要 This represents the number of times the application has issued significant alerts. S 重要 This represents the points deducted for important warnings. N 一般 This represents the number of times the application has generated general alerts. S 一般 This represents the points deducted for a typical alarm. The minimum value is limited to 0; Calculate the health of the node group Application deployment node clusters are divided into critical nodes and non-critical nodes. Critical nodes play a crucial role in application availability and have a greater impact on application health. The health score of the node cluster is calculated by dividing the critical node score by 100 and then multiplying it by the average health score of the non-critical nodes. The formula is as follows: ; in, This indicates the health status of the entire node cluster of the application. Indicates key nodes health Indicates non-critical nodes Health status; and These represent the total number of critical nodes and non-critical nodes, respectively. Calculate the health status of the test Multiple tests are performed on each application node and key functional module. Emergency, critical, and general alarms are generated based on the test return codes and latency. A single test health status is assessed. The minimum value is 0. The node health algorithm calculates the overall health by subtracting the alarm score from the specified total score. The following values were derived from the average of all health assessments: ; in, Indicates the total number of dialing tests; Health of the calculation application The application's health score is calculated by combining the health status of the monitoring system with the health status of the node group. : .
[0028] In one specific embodiment, the display module is specifically used for: Design the primary interface of a large screen for health monitoring applications. The primary interface of the application health monitoring dashboard focuses on displaying the usage status of application systems. Building upon basic network and resource monitoring, it takes a business-oriented approach, organizing the ITI resources that make up the business system into a business logic model based on their relationships. This ends the traditional decentralized resource monitoring and management, establishing a monitoring interface from a business perspective. The dashboard displays content including core application health, ranking of all applications under monitoring, application availability, abnormal application statistics, number of monitored devices, current number of alarms, and alarm trend charts. Design a secondary interface for a large screen application for health monitoring. As an application details view, it displays the application health value, application ledger information, application database, middleware, component node health and alarm values, application probing access trend, and alarm information. Device information can be drilled down to the device monitoring details page.
[0029] Although preferred embodiments of the invention have been described, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments as well as all changes and modifications falling within the scope of the invention.
[0030] Obviously, those skilled in the art can make various modifications and variations to this invention without departing from its spirit and scope. Therefore, if these modifications and variations fall within the scope of the claims of this invention and their equivalents, this invention also intends to include these modifications and variations.
Claims
1. An edge probe driven application system health degree calculation method, characterized in that, The method includes: Step 1: Deploy edge nodes and, based on these, deploy monitoring probes to complete data collection; Step 2: Preprocess the collected data locally to obtain preprocessed data; Step 3: Obtain the application system health value based on the preprocessed data; Step 4: Visualize the health status of the application system, presenting an overall overview of system health indicators.
2. The method of claim 1, wherein, Step 1: Deploying edge nodes and, based on these, deploying monitoring probes to complete data collection, specifically includes: Step 1.1 Hardware Integration Deploy edge nodes and mount edge probes directly on the edge nodes via general-purpose input / output (GPIO) interfaces. The edge probes establish a data transmission channel with the local storage module and preprocessing module of the edge nodes through an internal bus. Step 1.2 Deployment of Data Acquisition Software A lightweight data acquisition program is embedded in the edge probe, and the acquisition frequency is set to collect various indicator data of each application node.
3. The method of claim 2, wherein, Step 2: Preprocess the collected data locally to obtain preprocessed data, specifically including: Step 2.1 Z-Score Standardization The collected data of various indicators are normalized to eliminate differences in units; Step 2.2 Outlier Removal in Isolated Forests Set an outlier detection threshold to remove extreme data that deviates from the normal distribution; Step 2.3 SMOTE Data Balancing Since fault data accounts for a small percentage, virtual fault data is generated through interpolation to ensure the effectiveness of model training.
4. The method of claim 3, wherein, Step 3: Obtaining the application system health value based on the preprocessed data, specifically including: The preprocessed data of each indicator of each application node are compared with the corresponding preset thresholds, and the three-level alarm level and frequency of each application node are determined according to the preset rules; the score corresponding to the three-level alarm level is set according to actual needs. The application uses a single server as a node, including database nodes, middleware nodes, and application component nodes. When a metric exceeds a certain threshold, different levels of alerts are triggered. Node health is calculated as: Total Score - Emergency Alerts * Emergency Alert Score - Important Alerts * Important Alert Score - General Alerts * General Alert Score. Application health is calculated by combining the health of the node cluster and the health of the application during probing, as detailed below: Step 3.1 Calculate the health of a single node. The health of a single node is calculated using the following formula: in, Indicates the first The health of each node N 紧急 This represents the number of times the application has issued emergency alerts. S 紧急 This represents the points that will be deducted for this emergency alarm. Similarly, N 重要 This represents the number of times the application has issued significant alerts. S 重要 This represents the points deducted for important warnings. N 一般 This represents the number of times the application has generated general alerts. S 一般 This represents the points deducted for a typical alarm. The minimum value is limited to 0; Step 3.2 Calculate the health of the node group Application deployment node clusters are divided into critical nodes and non-critical nodes. Critical nodes play a crucial role in application availability and have a greater impact on application health. The health score of the node cluster is calculated by dividing the critical node score by 100 and then multiplying it by the average health score of the non-critical nodes. The formula is as follows: ; in, This indicates the health status of the entire node cluster of the application. Indicates key nodes health Indicates non-critical nodes Health status; and These represent the total number of critical nodes and non-critical nodes, respectively. Step 3.3 Calculate the measured health level Multiple tests are performed on each application node and key functional module. Emergency, critical, and general alarms are generated based on the test return codes and latency. A single test health status is assessed. The minimum value is 0. The node health algorithm calculates the overall health by subtracting the alarm score from the specified total score. The following values were derived from the average of all health assessments: ; wherein, represents the total number of probes; Step 3.4 Calculate the application's health. The application's health score is calculated by combining the health status of the monitoring system with the health status of the node group. : 。 5. The method according to claim 4, characterized in that, Step 4: Visualize the health status of the application system, presenting overall system health indicators, specifically including: Step 4.1 Design the primary interface of the application's health monitoring dashboard. The primary interface of the application health monitoring dashboard focuses on displaying the usage status of application systems. Building upon basic network and resource monitoring, it takes a business-oriented approach, organizing the ITI resources that make up the business system into a business logic model based on their relationships. This ends the traditional decentralized resource monitoring and management, establishing a monitoring interface from a business perspective. The dashboard displays content including core application health, ranking of all applications under monitoring, application availability, abnormal application statistics, number of monitored devices, current number of alarms, and alarm trend charts. Step 4.2 Design the secondary interface of the application health monitoring screen. As an application details view, it displays the application health value, application ledger information, application database, middleware, component node health and alarm values, application probing access trend, and alarm information. Device information can be drilled down to the device monitoring details page.
6. An edge probe driven application system health computing system, characterized by, The health calculation method for an application system based on edge probes, as described in any one of claims 1 to 5, comprises: The data acquisition module is used to deploy edge nodes and, based on these, deploy monitoring probes to complete data acquisition. The data preprocessing module is used to preprocess the collected data and perform local data processing to obtain preprocessed data. The health value acquisition module is used to acquire the application system's health value based on preprocessed data; The display module is used to visualize the health status of the application system, presenting an overall picture of the system's health indicators.
7. The system of claim 6, wherein, The deployment and acquisition module is specifically used for: Hardware integration Deploy edge nodes and mount edge probes directly on the edge nodes via general-purpose input / output (GPIO) interfaces. The edge probes establish a data transmission channel with the local storage module and preprocessing module of the edge nodes through an internal bus. Data collection software deployment A lightweight data acquisition program is embedded in the edge probe, and the acquisition frequency is set to collect various indicator data of each application node.
8. The system of claim 7, wherein, The data preprocessing module is specifically used for: Z-Score Standardization The collected data of various indicators are normalized to eliminate differences in units; Outlier removal in isolated forests Set an outlier detection threshold to remove extreme data that deviates from the normal distribution; SMOTE Data Balancing Since fault data accounts for a small proportion, virtual fault data is generated through interpolation to ensure the model training effect.
9. The system of claim 8, wherein, The health value acquisition module is specifically used for: The preprocessed data of each indicator of each application node are compared with the corresponding preset thresholds, and the three-level alarm level and frequency of each application node are determined according to the preset rules; the score corresponding to the three-level alarm level is set according to actual needs. The application uses a single server as a node, including database nodes, middleware nodes, and application component nodes. When a metric exceeds a certain threshold, different levels of alerts are triggered. Node health is calculated as: Total Score - Emergency Alerts * Emergency Alert Score - Important Alerts * Important Alert Score - General Alerts * General Alert Score. Application health is calculated by combining the health of the node cluster and the health of the application during probing, as detailed below: Calculate the health of a single node The health of a single node is calculated using the following formula: in, Indicates the first The health of each node N 紧急 This represents the number of times the application has issued emergency alerts. S 紧急 This represents the points that will be deducted for this emergency alarm. Similarly, N 重要 This represents the number of times the application has issued significant alerts. S 重要 This represents the points deducted for important warnings. N 一般 This represents the number of times the application has generated general alerts. S 一般 This represents the points deducted for a typical alarm. The minimum value is limited to 0; Calculate the health of the node group Application deployment node clusters are divided into critical nodes and non-critical nodes. Critical nodes play a crucial role in application availability and have a greater impact on application health. The health score of the node cluster is calculated by dividing the critical node score by 100 and then multiplying it by the average health score of the non-critical nodes. The formula is as follows: ; in, This indicates the health status of the entire node cluster of the application. Indicates key nodes health Indicates non-critical nodes Health status; and These represent the total number of critical nodes and non-critical nodes, respectively. Calculate the health status of the test Multiple tests are performed on each application node and key functional module. Emergency, critical, and general alarms are generated based on the test return codes and latency. A single test health status is assessed. The minimum value is 0. The node health algorithm calculates the overall health by subtracting the alarm score from the specified total score. The following values were derived from the average of all health assessments: ; wherein, represents the total number of probes; Health of the calculation application With the health degree of the dialysis as the influencing factor, the health degree of the application is calculated in combination with the health degree of the node group : 。 10. The system according to claim 9, characterized in that, The display module is specifically used for: Design the primary interface of a large screen for health monitoring applications. The application health monitoring dashboard's primary interface focuses on displaying the usage status of application systems. Building upon basic network and resource monitoring, it takes a business perspective by organizing the ITI resources that make up the business system into a business logic model according to their relationships. This ends the traditional, decentralized resource monitoring and management and establishes a monitoring interface from a business perspective. The large screen displays the following information: health status of core applications, ranking of all applications under monitoring, application availability, statistics of abnormal applications, number of monitored devices, number of current alarms, and alarm trend chart. Design a secondary interface for a large screen application for health monitoring. As an application details view, it displays the application health value, application ledger information, application database, middleware, component node health and alarm values, application probing access trend, and alarm information. Device information can be drilled down to the device monitoring details page.
