Network node processing method and device, equipment and storage medium
By identifying and evaluating performance glitches in network nodes, determining their duration, and mapping them to severity levels, differentiated maintenance is implemented, solving the problem of low efficiency in the allocation of operational resources in existing technologies, and improving system stability and fault handling efficiency.
Patent Information
- Application Number
- CN202610083231.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-01-21
- Publication Date
- 2026-05-08
AI Technical Summary
Existing technologies cannot accurately assess the severity of network node performance anomalies, resulting in inefficient allocation of operational resources and difficulty in effectively ensuring system stability.
By acquiring network node performance data, identifying performance glitches, determining their duration, and mapping them to preset severity levels, differentiated maintenance is implemented, including root cause analysis, impact assessment, and trend prediction.
It enables differentiated responses to anomalies of varying degrees, avoiding excessive consumption of operational resources for minor issues while ensuring timely intervention for serious faults, optimizing resource allocation efficiency, and enhancing system stability.
Smart Images

Figure CN122001785A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of Internet technology, and in particular to a method, apparatus, device and storage medium for processing network nodes. Background Technology
[0002] In the field of information technology, large-scale distributed systems consist of numerous network nodes. During operation, these nodes generate performance data including Central Processing Unit (CPU) utilization, memory usage, and request latency. Performance spikes, i.e., instantaneous abnormal fluctuations in these metrics, are key factors affecting system stability.
[0003] Existing technologies typically employ monitoring schemes based on fixed thresholds. This scheme pre-sets a static threshold for each performance indicator. When the monitoring system detects that the performance data of a certain node exceeds the threshold, it triggers a unified alarm signal to notify the operations and maintenance personnel to conduct an inspection.
[0004] However, this existing solution cannot accurately assess the severity of performance anomalies and make differentiated operation and maintenance responses accordingly, resulting in inefficient allocation of operation and maintenance resources and difficulty in effectively ensuring system stability. Summary of the Invention
[0005] This application provides a method, apparatus, device, and storage medium for processing network nodes to solve the problem that existing technologies cannot accurately assess the severity of performance anomalies and make differentiated operation and maintenance responses accordingly, resulting in low efficiency in operation and maintenance resource allocation and difficulty in effectively ensuring system stability.
[0006] Firstly, this application provides a method for processing network nodes, including: Obtain performance data of network nodes; The performance data is identified and processed to obtain multiple performance glitch points; For each performance glitch, determine the duration of the performance glitch. Among multiple non-overlapping preset duration intervals, the target duration interval to which the duration belongs is determined, and the severity level corresponding to the target duration interval is determined as the target level corresponding to the performance glitch. Based on the target level corresponding to each performance glitch point, perform corresponding maintenance processing on the network node.
[0007] In one possible implementation, the step of performing corresponding maintenance processing on the network nodes based on the target level corresponding to each performance spike includes: Root cause analysis is performed based on the target level corresponding to each performance burr point to obtain the analysis results; Based on the analysis results, a maintenance decision is generated. The network node is subjected to corresponding maintenance processing based on the maintenance decision.
[0008] In one possible implementation, the root cause analysis based on the target level corresponding to each performance burr point, to obtain the analysis results, includes: For each performance spike, based on the target level corresponding to the performance spike and the occurrence time and node attributes of the performance spike, the system event logs and resource status indicators of the same period are queried in association. Based on the system event logs and the resource status indicators, a correlation analysis report is generated, and the correlation analysis report is used as the analysis result.
[0009] In one possible implementation, the root cause analysis based on the target level corresponding to each performance burr point, to obtain the analysis results, includes: For each performance glitch, assess the scope of its impact on the business service chain based on the target level of the performance glitch. Based on the stated scope of influence, an impact scope assessment report is generated, and this impact scope assessment report is used as the analysis result.
[0010] In one possible implementation, the root cause analysis based on the target level corresponding to each performance burr point, to obtain the analysis results, includes: Cluster analysis was performed on multiple performance spikes with the same target level within a historical period to obtain the time distribution pattern; Based on the time distribution pattern, a trend prediction report is generated, and the trend prediction report is used as the analysis result.
[0011] In one possible implementation, the method further includes: The analysis results are then linked to the maintenance decisions to form strategy entries in the processing knowledge base; Upon identifying a new performance glitch, a matching search is performed in the processing knowledge base based on the attributes of the new performance glitch. If a matching policy entry is found, the maintenance decision recorded in the policy entry is pushed to the maintenance interface.
[0012] In one possible implementation, the step of performing corresponding maintenance processing on the network nodes based on the target level corresponding to each performance spike includes: For each performance glitch, an alarm message of corresponding severity is generated based on the target level corresponding to the performance glitch. Based on a preset notification routing strategy, the alarm information is distributed to the corresponding maintenance terminal.
[0013] In one possible implementation, the method further includes: Count the number of alarm messages of a preset level generated within the first preset time period; If the number reaches a first threshold, an escalation alarm message is generated; The upgrade alarm information is sent to the pre-designated upgrade notification terminal.
[0014] Secondly, this application provides a processing apparatus for a network node, comprising: The acquisition module is used to acquire performance data of network nodes; The identification module is used to identify and process the performance data to obtain multiple performance glitch points; The first determining module is used to determine the duration of each performance glitch. The second determining module is used to determine the target duration interval to which the duration belongs among multiple non-overlapping preset duration intervals, and to determine the severity level corresponding to the target duration interval as the target level corresponding to the performance glitch. The processing module is used to perform corresponding maintenance processing on the network nodes according to the target level corresponding to each performance glitch point.
[0015] In one possible implementation, the processing module is specifically used for: Root cause analysis is performed based on the target level corresponding to each performance burr point to obtain the analysis results; Based on the analysis results, a maintenance decision is generated. The network node is subjected to corresponding maintenance processing based on the maintenance decision.
[0016] In one possible implementation, the processing module is further configured to: For each performance spike, based on the target level corresponding to the performance spike and the occurrence time and node attributes of the performance spike, the system event logs and resource status indicators of the same period are queried in association. Based on the system event logs and the resource status indicators, a correlation analysis report is generated, and the correlation analysis report is used as the analysis result.
[0017] In one possible implementation, the processing module is further configured to: For each performance glitch, assess the scope of its impact on the business service chain based on the target level of the performance glitch. Based on the stated scope of influence, an impact scope assessment report is generated, and this impact scope assessment report is used as the analysis result.
[0018] In one possible implementation, the processing module is further configured to: Cluster analysis was performed on multiple performance spikes with the same target level within a historical period to obtain the time distribution pattern; Based on the time distribution pattern, a trend prediction report is generated, and the trend prediction report is used as the analysis result.
[0019] In one possible implementation, the device further includes a push module for: The analysis results are then linked to the maintenance decisions to form strategy entries in the processing knowledge base; Upon identifying a new performance glitch, a matching search is performed in the processing knowledge base based on the attributes of the new performance glitch. If a matching policy entry is found, the maintenance decision recorded in the policy entry is pushed to the maintenance interface.
[0020] In one possible implementation, the processing module is further configured to: For each performance glitch, an alarm message of corresponding severity is generated based on the target level corresponding to the performance glitch. Based on a preset notification routing strategy, the alarm information is distributed to the corresponding maintenance terminal.
[0021] In one possible implementation, the apparatus further includes a transmitting module for: Count the number of alarm messages of a preset level generated within the first preset time period; If the number reaches a first threshold, an escalation alarm message is generated; The upgrade alarm information is sent to the pre-designated upgrade notification terminal.
[0022] Thirdly, this application provides an apparatus comprising: a processor and a memory, the processor being configured to execute a processing program for a network node stored in the memory to implement the network node processing method described in any one of the first aspects.
[0023] Fourthly, this application provides a storage medium storing one or more programs that can be executed by one or more processors to implement the network node processing method described in any one aspect.
[0024] Compared with the prior art, the technical solution provided in this application has the following advantages: The method provided in this application first acquires the performance data of network nodes and identifies performance spikes to complete anomaly detection; then, it determines the duration of each spike and converts it into a quantifiable evaluation criterion; next, it matches the duration with multiple preset non-overlapping intervals and automatically maps them to the corresponding severity level to achieve an objective assessment of the anomaly degree; finally, it performs corresponding maintenance processing according to the determined level to ensure that the response measures accurately correspond to the severity of the spike. Through this solution, the system can implement differentiated responses to anomalies of different degrees, avoiding excessive consumption of operation and maintenance resources for minor problems while ensuring timely intervention for serious faults, thereby optimizing resource allocation efficiency and enhancing system stability overall. Attached Figure Description
[0025] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.
[0026] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0027] One or more embodiments are illustrated by way of example with reference numerals in the accompanying drawings. These illustrations do not constitute a limitation on the embodiments. Elements with the same reference numerals in the drawings are denoted as similar elements. Unless otherwise stated, the figures in the drawings are not to be limited by scale.
[0028] Figure 1 A flowchart illustrating an embodiment of a network node processing method provided in this application; Figure 2 A flowchart illustrating an embodiment of another network node processing method provided in this application; Figure 3 A flowchart illustrating an embodiment of another network node processing method provided in this application; Figure 4 A block diagram illustrating an embodiment of a network node processing apparatus provided in this application; Figure 5 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation
[0029] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.
[0030] The following disclosure provides numerous different embodiments or examples for implementing various structures of this application. To simplify the disclosure, specific examples of components and arrangements are described below. These are merely examples and are not intended to limit the scope of this application. Furthermore, reference numerals and / or letters may be repeated in different examples. Such repetition is for simplification and clarity and does not in itself indicate a relationship between the various embodiments and / or arrangements discussed.
[0031] To address the technical problem that existing technologies cannot accurately assess the severity of performance anomalies and thus fail to provide differentiated operational and maintenance responses, leading to inefficient allocation of operational and maintenance resources and difficulty in effectively ensuring system stability, this application provides a network node processing method that can implement differentiated responses to anomalies of different degrees. This avoids excessive consumption of operational and maintenance resources for minor issues while ensuring timely intervention for serious faults, thereby optimizing resource allocation efficiency and enhancing system stability overall.
[0032] Figure 1 This is a flowchart illustrating an embodiment of a network node processing method provided in this application. Figure 1 As shown, the method includes the following steps: Step 101: Obtain the performance data of the network nodes.
[0033] Performance data refers to a set of metrics generated by network nodes during operation that reflect their working status, including but not limited to key metrics such as CPU (Central Processing Unit) utilization, memory usage, disk I / O (Input / Output) throughput, and network latency.
[0034] In this embodiment of the application, the system continuously collects performance data through monitoring agents or remote probes deployed on the nodes in real-time streaming or timed batch processing to form a complete node operating status data stream.
[0035] Step 102: Identify and process the performance data to obtain multiple performance glitch points.
[0036] Performance spikes refer to abnormal data points or segments in a performance data sequence that significantly deviate from the normal fluctuation range.
[0037] In this embodiment of the application, the system performs real-time analysis on the continuously input performance data stream through a preset threshold comparison algorithm or anomaly detection model. When any performance index value exceeds the upper or lower limit of its normal fluctuation range, it is marked as a performance spike point and its start timestamp is recorded.
[0038] Step 103: For each performance glitch, determine the duration of the performance glitch.
[0039] Duration refers to the length of time from the start to the end of a single performance glitch.
[0040] In this embodiment, the system continuously monitors the performance index value of each identified burr point. When the index value returns to the normal fluctuation range, it records the end timestamp and calculates the difference between the start timestamp and the end timestamp to accurately obtain the duration of the burr point.
[0041] Step 104: Among multiple non-overlapping preset duration intervals, determine the target duration interval to which the duration belongs, and determine the severity level corresponding to the target duration interval as the target level corresponding to the performance glitch.
[0042] The preset duration interval refers to a time segment that is pre-defined and non-overlapping, based on the severity of its impact on system stability.
[0043] Severity level is a priority indicator corresponding to each duration interval.
[0044] In this embodiment of the application, the system matches the calculated duration of the glitch with multiple preset intervals to determine the specific target interval to which it belongs, and automatically assigns the severity level corresponding to the interval to the glitch. The severity level includes at least three levels based on different duration intervals. For example, T0 level glitch: duration greater than or equal to 25 minutes; T1 level glitch: duration greater than or equal to 15 minutes and less than 25 minutes; T2 level glitch: duration less than 15 minutes.
[0045] Step 105: Perform corresponding maintenance processing on the network nodes according to the target level corresponding to each performance glitch point.
[0046] In this embodiment, the system triggers differentiated operation and maintenance responses based on the target level assigned to each glitch: for high-level glitches, emergency alarms and resource scheduling operations are executed; for medium-level glitches, important alarms and optimization analysis are executed; and for low-level glitches, logs are recorded and continuous monitoring is performed. This tiered response mechanism enables precise allocation of operation and maintenance resources.
[0047] The technical solution provided in this application first acquires network node performance data and identifies performance spikes to complete anomaly detection; then, it determines the duration of each spike and converts it into quantifiable evaluation criteria; next, it matches the duration with multiple preset non-overlapping intervals and automatically maps them to corresponding severity levels to achieve objective assessment of the anomaly degree; finally, it executes corresponding maintenance processing according to the determined level to ensure that the response measures accurately correspond to the severity of the spike. Through this solution, the system can implement differentiated responses to anomalies of different degrees, avoiding excessive consumption of operational resources for minor issues while ensuring timely intervention for serious faults, thereby optimizing overall resource allocation efficiency and enhancing system stability.
[0048] Figure 2 A flowchart illustrating an embodiment of another network node processing method provided in this application. Figure 2 The process shown is in Figure 1 Based on the illustrated process, the following steps are included: Step 201: Perform root cause analysis based on the target level corresponding to each performance burr point to obtain the analysis results.
[0049] Step 202: Generate maintenance decisions based on the analysis results.
[0050] Step 203: Perform corresponding maintenance processing on the network node according to the maintenance decision.
[0051] For ease of understanding, steps 201-203 will be explained uniformly below: Root cause analysis refers to the technical process of locating the root cause of performance abnormalities through multidimensional data correlation; maintenance decision refers to the targeted treatment plan generated based on the analysis results.
[0052] In this embodiment, the system establishes a linkage mechanism between hierarchical alarms and intelligent analysis. After obtaining spike level information, it implements a differentiated analysis strategy: For T0-level high-severity spikes (i.e., the highest-level spikes with the longest duration), it synchronously queries system event logs (such as deployment records and configuration changes) and fine-grained resource indicators (such as CPU single-core load and memory fragmentation rate) within a preset time window before and after the spike's occurrence, performing deep root cause tracing; for T1-level medium-severity spikes (i.e., spikes with moderate duration), it focuses on analyzing their impact range in the business service topology, determining the affected downstream services and user range through service dependency graphs; for periodically occurring spikes of the same type (i.e., spikes with shorter durations), it uses clustering algorithms to extract features based on their occurrence time and duration patterns, identifying potential patterns. Based on the above analysis results, the system dynamically generates matching maintenance decisions: when a resource bottleneck is identified, it generates a capacity expansion decision; when a code defect is identified, it generates a rollback decision; and when attack characteristics are discovered, it generates a protection decision. Finally, by calling the infrastructure management interface, the decisions are translated into specific resource scheduling, service restart, or traffic scheduling operations.
[0053] Figure 2 The process shown demonstrates a shift from extensive alarming to refined operation and maintenance by precisely matching glitch levels with differentiated analysis strategies. This not only solves the problem of low fault location efficiency in traditional solutions but also avoids resource waste during maintenance through precise decision-making and execution, significantly improving the intelligence level of system operation and maintenance and the efficiency of fault handling.
[0054] In one embodiment, step 201 may specifically include the following steps: for each performance spike, based on the target level corresponding to the performance spike and the occurrence time and node attributes of the performance spike, query the system event logs and resource status indicators of the same period; generate a correlation analysis report based on the system event logs and the resource status indicators, and use the correlation analysis report as the analysis result.
[0055] Node attributes include a node's unique identifier, cluster affiliation, node type, and geographical location; system event logs record key operational events such as configuration changes, code deployments, and system restarts; resource status indicators include fine-grained performance data such as CPU core utilization, memory fragmentation rate, and disk queue depth; and correlation analysis reports are structured documents that reflect the correlation between performance spikes and potential causes.
[0056] In the specific implementation of this step, the system determines the analysis depth based on the target level of the performance spike, and combines its precise occurrence timestamp and node attribute characteristics. It then queries the full system event logs and resource status time-series data within the time window in the operation and maintenance database. Through time series alignment and correlation calculation, it identifies key operation events or resource anomaly patterns that overlap with the spike occurrence period, and finally generates a correlation analysis report that clearly points out the potential causes.
[0057] This solution establishes an automatic correlation mechanism for multi-dimensional data, intelligently linking isolated monitoring data and operation records in traditional operations and maintenance. This effectively solves the problem of information fragmentation during fault diagnosis, significantly improves the accuracy and efficiency of root cause identification, and provides reliable data support for subsequent precise operations and maintenance.
[0058] In another embodiment, step 201 may further include the following steps: for each performance glitch, assess the impact range of the performance glitch on the business service chain according to the target level of the performance glitch; generate an impact range assessment report based on the impact range, and use the impact range assessment report as the analysis result.
[0059] A business service chain refers to a complete business process consisting of multiple interdependent service components in a specific call order; an impact assessment report is an assessment document used to quantify the impact of performance anomalies on business services.
[0060] In the specific implementation of this step, the system determines the evaluation granularity based on the target level of the performance spikes, locates the position of the node where the spikes occurred in the business service chain by querying the preset business service topology diagram, and then automatically traces the upstream service nodes and downstream service call paths based on service dependencies. Combining the business criticality weight of each service, the system comprehensively calculates the set of affected service components, the potential user range, and the degree of damage to business functions, and finally generates an impact range assessment report that includes quantitative indicators of the impact range.
[0061] This solution establishes a visualized mapping relationship between infrastructure anomalies and business impacts, enabling correlation analysis between technical indicators and business value. It effectively addresses the pain point of traditional monitoring's inability to accurately assess the consequences of abnormal business operations, providing key business dimensions for operation and maintenance priority determination and emergency decision-making, and significantly improving the accuracy and business orientation of fault management.
[0062] In another embodiment, step 201 may further include the following steps: performing cluster analysis on multiple performance glitch points with the same target level within a historical period to obtain a time distribution pattern; generating a trend prediction report based on the time distribution pattern, and using the trend prediction report as the analysis result.
[0063] Historical period refers to the preset statistical analysis time span; cluster analysis refers to the technical method of automatically grouping puncture points with similar characteristics through machine learning algorithms; time distribution pattern is a set of features that reflects the time regularity of puncture point occurrence; trend prediction report is a predictive document that contains the probability and distribution characteristics of puncture occurrence in the future time period.
[0064] In this step, the system extracts a dataset of all spur points with the same target level within a specified period from the historical database. It then uses a clustering algorithm to perform pattern mining on the timestamps of these spur points, identifying periodic occurrences, concentrated outbreaks, or patterns that evolve over time. Based on the identified time distribution patterns, a prediction model is built to generate a trend prediction report that includes the trend of spur occurrence in future periods, high-frequency period warnings, and suggested observation periods.
[0065] This solution transforms the operation and maintenance model from passive response to proactive prediction by mining the temporal patterns of historical spike data. It effectively solves the problem of lack of foresight for recurring failures in traditional solutions, provides data support for system stability optimization and preventive maintenance, and significantly improves the foresight and planning of operation and maintenance work.
[0066] In addition, in another embodiment of this application, the method may further include the following steps: binding the analysis results with the maintenance decisions to form strategy entries in the processing knowledge base; when a new performance spike is identified, performing a matching search in the processing knowledge base based on the attributes of the new performance spike; and when a corresponding strategy entry is matched, pushing the maintenance decisions recorded in the strategy entry to the maintenance interface.
[0067] The processing knowledge base refers to a structured database that stores historical fault handling experience; strategy entries refer to knowledge units that contain the correspondence between problem characteristics, analysis results and handling solutions; attributes refer to multi-dimensional characteristics that cover the duration of performance glitches, node type, performance index type and other features.
[0068] In the specific implementation of this step, the system associates and binds the analysis results obtained from each root cause analysis with the final maintenance decision to form standardized strategy entries and stores them in the processing knowledge base. When the system identifies a new performance spike, it extracts its multi-dimensional attribute features in real time and performs a matching retrieval based on similarity calculation in the knowledge base. When the similarity with historical cases exceeds a preset threshold, the system automatically pushes the mature maintenance decision recorded in the strategy entry to the operation and maintenance management interface.
[0069] This solution transforms operational experience into reusable knowledge assets, establishing a continuously optimized intelligent operation and maintenance system. It effectively solves the problems of low processing efficiency and difficulty in knowledge transfer caused by reliance on human experience in traditional operation and maintenance. It not only accelerates the fault handling process but also ensures the scientific nature and consistency of the handling plan, significantly improving the automation level and knowledge management level of operation and maintenance work.
[0070] Figure 3 A flowchart illustrating an embodiment of another network node processing method provided in this application. Figure 3 The process shown is in Figure 1 Based on the illustrated process, the following steps are included: Step 301: For each performance glitch, generate alarm information of corresponding severity based on the target level corresponding to the performance glitch.
[0071] Step 302: Based on the preset notification routing strategy, distribute the alarm information to the corresponding maintenance terminal.
[0072] Alarm information refers to a notification message that contains basic information about the glitch and its severity; notification routing policy is a distribution rule that defines the correspondence between alarm information and recipients; maintenance terminal refers to the information receiving equipment used by operation and maintenance personnel, including computer terminals and mobile devices.
[0073] In the specific implementation of this solution, the system automatically generates differentiated alarm information based on the target level of the performance spike: alarms with an emergency indicator are generated for high-level spikes, important alarms are generated for medium-level spikes, and general prompts are generated for low-level spikes. Subsequently, based on a preset notification routing strategy, alarm information of different levels is distributed to the corresponding maintenance terminals through interface calls. For example, emergency alarms are pushed in real time through the collaboration platform and telephone channels, important alarms are pushed through the collaboration platform, and general alarms are only displayed on the operation and maintenance interface.
[0074] Figure 3 The process shown effectively solves the problems of indiscriminate alarm information and lack of specificity in traditional monitoring systems by establishing a precise mapping relationship between glitch levels and alarm levels, and by using an intelligent information routing mechanism. This ensures timely detection of major faults and avoids excessive interference from minor alarms to maintenance personnel, significantly improving the refinement and effectiveness of alarm management.
[0075] In addition, in another embodiment of this application, the method may further include the following steps: counting the number of alarm messages of a preset level generated within a first preset time; generating an upgrade alarm message when the number reaches a first threshold; and sending the upgrade alarm message to a pre-designated upgrade notification terminal.
[0076] The first preset time refers to the statistical time window set by the system; the preset level refers to the alarm level that needs to be monitored in advance; the upgraded alarm information is a higher-level alarm generated when the number of alarms reaches a threshold; the upgraded notification terminal is a higher-level alarm receiving device or notification group that is set in advance.
[0077] In the specific implementation of this step, the system continuously counts the number of alarms of a specific level (such as T0 level) generated within a preset time window (such as 10 minutes). When the cumulative number reaches a preset threshold (such as 3 times), it automatically generates an upgraded alarm information containing the original alarm summary and frequency statistics, and sends the upgraded alarm to a pre-configured upgrade notification terminal, such as the operation and maintenance supervisor group or the duty manager's mobile terminal.
[0078] This solution effectively addresses the lack of effective follow-up on repetitive critical alarms in traditional alarm systems by establishing an alarm frequency monitoring and automatic escalation mechanism. It ensures that critical faults can be reported in a timely manner, preventing the escalation of faults due to the omission or failure to handle a single alarm, and significantly improving the emergency response capability and management visibility for critical faults.
[0079] Figure 4 This is a block diagram illustrating an embodiment of a network node processing apparatus provided in this application. Figure 4 As shown, the device includes: Module 41 is used to acquire performance data of network nodes; The identification module 42 is used to identify and process the performance data to obtain multiple performance glitch points; The first determining module 43 is used to determine the duration of each performance glitch point. The second determining module 44 is used to determine the target duration interval to which the duration belongs among multiple non-overlapping preset duration intervals, and to determine the severity level corresponding to the target duration interval as the target level corresponding to the performance glitch. The processing module 45 is used to perform corresponding maintenance processing on the network nodes according to the target level corresponding to each performance glitch point.
[0080] In one possible implementation, the processing module is specifically used for: Root cause analysis is performed based on the target level corresponding to each performance burr point to obtain the analysis results; Based on the analysis results, a maintenance decision is generated. The network node is subjected to corresponding maintenance processing based on the maintenance decision.
[0081] In one possible implementation, the processing module is further configured to: For each performance spike, based on the target level corresponding to the performance spike and the occurrence time and node attributes of the performance spike, the system event logs and resource status indicators of the same period are queried in association. Based on the system event logs and the resource status indicators, a correlation analysis report is generated, and the correlation analysis report is used as the analysis result.
[0082] In one possible implementation, the processing module is further configured to: For each performance glitch, assess the scope of its impact on the business service chain based on the target level of the performance glitch. Based on the stated scope of influence, an impact scope assessment report is generated, and this impact scope assessment report is used as the analysis result.
[0083] In one possible implementation, the processing module is further configured to: Cluster analysis was performed on multiple performance spikes with the same target level within a historical period to obtain the time distribution pattern; Based on the time distribution pattern, a trend prediction report is generated, and the trend prediction report is used as the analysis result.
[0084] In one possible implementation, the device further includes a push module for: The analysis results are then linked to the maintenance decisions to form strategy entries in the processing knowledge base; Upon identifying a new performance glitch, a matching search is performed in the processing knowledge base based on the attributes of the new performance glitch. If a matching policy entry is found, the maintenance decision recorded in the policy entry is pushed to the maintenance interface.
[0085] In one possible implementation, the processing module is further configured to: For each performance glitch, an alarm message of corresponding severity is generated based on the target level corresponding to the performance glitch. Based on a preset notification routing strategy, the alarm information is distributed to the corresponding maintenance terminal.
[0086] In one possible implementation, the apparatus further includes a transmitting module for: Count the number of alarm messages of a preset level generated within the first preset time period; If the number reaches a first threshold, an escalation alarm message is generated; The upgrade alarm information is sent to the pre-designated upgrade notification terminal.
[0087] like Figure 5 As shown in the figure, this application provides a device including a processor 111, a communication interface 112, a memory 113, and a communication bus 114, wherein the processor 111, the communication interface 112, and the memory 113 communicate with each other through the communication bus 114. Memory 113 is used to store computer programs; In one embodiment of this application, when the processor 111 executes the program stored in the memory 113, it implements the network node processing method provided in any of the foregoing method embodiments, including: Obtain performance data of network nodes; The performance data is identified and processed to obtain multiple performance glitch points; For each performance glitch, determine the duration of the performance glitch. Among multiple non-overlapping preset duration intervals, the target duration interval to which the duration belongs is determined, and the severity level corresponding to the target duration interval is determined as the target level corresponding to the performance glitch. Based on the target level corresponding to each performance glitch point, perform corresponding maintenance processing on the network node.
[0088] This application also provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the steps of the network node processing method provided in any of the foregoing method embodiments.
[0089] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs.
[0090] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented using software plus a general-purpose hardware platform, or of course, using hardware. Based on this understanding, the above technical solutions, in essence or the parts that contribute to the related technology, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.
[0091] It should be understood that the terminology used herein is for the purpose of describing particular exemplary embodiments only and is not intended to be limiting. Unless the context clearly indicates otherwise, the singular forms “a,” “an,” and “described” as used herein may also include the plural forms. The terms “comprising,” “including,” “containing,” and “having” are inclusive and therefore indicate the presence of the stated features, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, elements, components, and / or combinations thereof. The method steps, processes, and operations described herein are not construed as requiring them to be performed in a particular order described or illustrated unless the order of performance is explicitly indicated. It should also be understood that additional or alternative steps may be used.
[0092] The above description is merely a specific embodiment of this application, enabling those skilled in the art to understand or implement this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features claimed herein.
Claims
1. A method for processing network nodes, characterized in that, The method includes: Obtain performance data of network nodes; The performance data is identified and processed to obtain multiple performance glitch points; For each performance glitch, determine the duration of the performance glitch. Among multiple non-overlapping preset duration intervals, the target duration interval to which the duration belongs is determined, and the severity level corresponding to the target duration interval is determined as the target level corresponding to the performance glitch. Based on the target level corresponding to each performance glitch point, perform corresponding maintenance processing on the network node.
2. The method according to claim 1, characterized in that, The step of performing corresponding maintenance processing on the network nodes based on the target level corresponding to each performance glitch point includes: Root cause analysis is performed based on the target level corresponding to each performance burr point to obtain the analysis results; Based on the analysis results, a maintenance decision is generated. The network node is subjected to corresponding maintenance processing based on the maintenance decision.
3. The method according to claim 2, characterized in that, The root cause analysis is performed based on the target level corresponding to each performance burr point, and the analysis results are as follows: For each performance spike, based on the target level corresponding to the performance spike and the occurrence time and node attributes of the performance spike, the system event logs and resource status indicators of the same period are queried in association. Based on the system event logs and the resource status indicators, a correlation analysis report is generated, and the correlation analysis report is used as the analysis result.
4. The method according to claim 2, characterized in that, The root cause analysis is performed based on the target level corresponding to each performance burr point, and the analysis results are as follows: For each performance glitch, assess the scope of its impact on the business service chain based on the target level of the performance glitch. Based on the stated scope of influence, an impact scope assessment report is generated, and this impact scope assessment report is used as the analysis result.
5. The method according to claim 2, characterized in that, The root cause analysis is performed based on the target level corresponding to each performance burr point, and the analysis results are as follows: Cluster analysis was performed on multiple performance spikes with the same target level within a historical period to obtain the time distribution pattern; Based on the time distribution pattern, a trend prediction report is generated, and the trend prediction report is used as the analysis result.
6. The method according to claim 2, characterized in that, The method further includes: The analysis results are then linked to the maintenance decisions to form strategy entries in the processing knowledge base; Upon identifying a new performance glitch, a matching search is performed in the processing knowledge base based on the attributes of the new performance glitch. If a matching policy entry is found, the maintenance decision recorded in the policy entry is pushed to the maintenance interface.
7. The method according to claim 1, characterized in that, The step of performing corresponding maintenance processing on the network nodes based on the target level corresponding to each performance glitch point includes: For each performance glitch, an alarm message of corresponding severity is generated based on the target level corresponding to the performance glitch. Based on a preset notification routing strategy, the alarm information is distributed to the corresponding maintenance terminal.
8. The method according to claim 7, characterized in that, The method further includes: Count the number of alarm messages of a preset level generated within the first preset time period; If the number reaches a first threshold, an escalation alarm message is generated; The upgrade alarm information is sent to the pre-designated upgrade notification terminal.
9. A processing device for a network node, characterized in that, The device includes: The acquisition module is used to acquire performance data of network nodes; The identification module is used to identify and process the performance data to obtain multiple performance glitch points; The first determining module is used to determine the duration of each performance glitch. The second determining module is used to determine the target duration interval to which the duration belongs among multiple non-overlapping preset duration intervals, and to determine the severity level corresponding to the target duration interval as the target level corresponding to the performance glitch. The processing module is used to perform corresponding maintenance processing on the network nodes according to the target level corresponding to each performance glitch point.
10. An electronic device, characterized in that, include: A processor and a memory, the processor being configured to execute a processing program for a network node stored in the memory to implement the processing method for a network node according to any one of claims 1-8.
11. A storage medium, characterized in that, The storage medium stores one or more programs, which can be executed by one or more processors to implement the network node processing method according to any one of claims 1-8.
