System evaluation method, electronic device, storage medium and program product

Abstract

The embodiment of the invention provides a system evaluation method, electronic equipment, a storage medium and a program product. The method comprises the steps of obtaining configuration information and a system log in a target system, determining a static index score of the target system based on the configuration information and a set static index type, determining a dynamic index score of the target system based on the system log and a set dynamic index type, and determining a dynamic index score of the target system based on the static index score and the dynamic index score. And determining and outputting the health state of the target system. According to the method, related personnel can more visually know the overall health condition of the system through a systematic evaluation standard, so that the efficiency of system management is improved, the identification and prevention capabilities for potential problems are enhanced, and powerful support is provided for stable operation of the system.

Description

Technical Field

[0001] The present application relates to the fields of system management technology and data analysis technology, and in particular to a system evaluation method, electronic equipment, storage medium and program product. Background Art

[0002] In enterprises such as banks that rely on office operation application systems to complete related work, whether the basic resources of the application system are in good condition, whether it can meet the office needs of enterprise users, and whether there are many failures are crucial to the availability of the application system and the user experience of the office process.

[0003] In the existing technology, system administrators mainly rely on alarm indicators to evaluate the status of application systems. This method usually focuses on the transaction volume and transaction loss rate at the application level. However, this evaluation method has obvious limitations because it ignores the comprehensive analysis of the overall real-time operation status of the system, making it difficult for system administrators to fully and intuitively understand the operation status of the system, making it difficult to optimize the application system status based on the evaluation results, affecting the user experience. Summary of the invention

[0004] The embodiments of the present application provide a system evaluation method, an electronic device, a storage medium, and a program product to achieve the effect of comprehensively evaluating the status of an application system.

[0005] In a first aspect, an embodiment of the present application provides a system evaluation method, the system evaluation method comprising:

[0006] Obtain the configuration information and system logs in the target system. The configuration information includes the architecture information, technology stack type, and activation time of the physical device of the target system. The system logs include the inspection log, alarm log, system usage log, and system change log of the target system.

[0007] Based on the configuration information and the set static indicator types, determine the static indicator score of the target system. The static indicator is used to evaluate the health status of the basic configuration of the target system.

[0008] Determine the dynamic indicator score of the target system based on system logs and set dynamic indicator types. Dynamic indicators are used to evaluate the health status of the target system during operation.

[0009] Based on the static indicator scores and dynamic indicator scores, the health status of the target system is determined and output.

[0010] In a second aspect, an embodiment of the present application provides a system evaluation device, including:

[0011] The acquisition module is used to obtain the configuration information and system logs in the target system. The configuration information includes the architecture information, technology stack type, and activation time of the physical device of the target system. The system logs include the inspection log, alarm log, system usage log, and system change log of the target system.

[0012] A first calculation module is used to determine the static indicator score of the target system based on the configuration information and the set static indicator type, where the static indicator is used to evaluate the health status of the basic configuration of the target system;

[0013] The second calculation module is used to determine the dynamic indicator score of the target system based on the system log and the set dynamic indicator type, and the dynamic indicator is used to evaluate the health status of the target system during operation;

[0014] The processing module is used to determine and output the health status of the target system based on the static indicator score and the dynamic indicator score.

[0015] In a third aspect, an embodiment of the present application provides a control device, including: a memory, a processor;

[0016] The memory stores computer-executable instructions;

[0017] The processor executes the computer-executable instructions stored in the memory, so that the processor executes the above first aspect and / or various possible implementations of the first aspect.

[0018] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are executed by a processor, they are used to implement the first aspect above and / or various possible implementations of the first aspect.

[0019] In a fifth aspect, an embodiment of the present application provides a computer program product, including a computer program, which, when executed by a processor, implements the above first aspect and / or various possible implementation methods of the first aspect.

[0020] The system evaluation method, electronic device, storage medium and program product provided by the embodiments of the present disclosure obtain the configuration information and system log in the target system, and then determine the static indicator score of the target system based on the configuration information and the set static indicator types, determine the dynamic indicator score of the target system based on the system log and the set dynamic indicator types, and determine and output the health status of the target system based on the static indicator score and the dynamic indicator score. Therefore, by comprehensively integrating the static and dynamic data of the system according to the configuration information and system log of the target system, it is possible to comprehensively evaluate the basic configuration of the system, and by analyzing the inspection log, alarm log, system usage log and system change log, it is possible to monitor and evaluate the dynamic operation status of the system in real time, and through the systematic evaluation criteria, relevant personnel can more intuitively understand the overall health status of the system, which not only improves the efficiency of system management, but also enhances the ability to identify and prevent potential problems, providing strong support for the stable operation of the system. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0022] Figure 1 An application scenario diagram of the system evaluation method provided in the embodiment of the present disclosure;

[0023] Figure 2 A flowchart of a system evaluation method provided for one embodiment of the present disclosure;

[0024] Figure 3 A flowchart of a system evaluation method provided for yet another embodiment of the present disclosure;

[0025] Figure 4 A schematic diagram of the structure of a system evaluation device provided in yet another embodiment of the present disclosure;

[0026] Figure 5 A schematic diagram of the structure of a control device provided in one embodiment of the present disclosure.

[0027] The above drawings have shown clear embodiments of the present application, which will be described in more detail later. These drawings and text descriptions are not intended to limit the scope of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0028] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0029] Figure 1 A schematic diagram of the application scenario of the system evaluation method provided in this application, such as Figure 1 As shown, during the system evaluation process, the server 100 obtains the configuration information and system logs in the target system 110, determines the health status of the target system 110 based on the information, and outputs a health status report 120 to complete the system evaluation process.

[0030] It should be noted that Figure 1 In the scenario shown, only one or a specific number of servers, target systems, and health status reports are used as examples for illustration, but the present disclosure is not limited to this, that is, the number of servers, target systems, and health status reports can be arbitrary.

[0031] In enterprises such as banks that rely on office operation application systems to complete related work, whether the basic resources of the application system are in good condition, whether it can meet the office needs of enterprise users, and whether there are many failures are crucial to the availability of the application system and the user experience of the office process.

[0032] In existing technical solutions, due to the complex functions and diverse configurations of the system, which usually contains a large number of different modules and platforms, obtaining and integrating this information requires spanning multiple technology stacks and data sources. This not only involves parsing and processing multiple data formats, but also requires an in-depth understanding of the system architecture to ensure the accuracy and completeness of the information. At the same time, it is also very difficult to select specific types of information from massive amounts of information to evaluate the health of the system. It requires a comprehensive and in-depth understanding of the normal operating status of the system in order to reasonably evaluate the health of the system. All of these increase the complexity and difficulty of the development and implementation of system status assessment technical solutions.

[0033] At the same time, in the existing technology, system administrators usually rely on scattered alarm and log information, and identifying potential problems often requires a lot of experience and manual analysis. In this case, the discovery of problems is often delayed, which may cause system problems to deteriorate further if they are not identified and handled in time.

[0034] In addition, due to the lack of systematic evaluation criteria, administrators may have subjective biases when selecting indicators to judge the health status of the system, further increasing the difficulty of problem discovery. Therefore, existing technical solutions face significant challenges in identifying and solving problems related to system health.

[0035] The system evaluation method provided in this application obtains the configuration information and system logs in the target system, evaluates the system health from both static and dynamic aspects, and solves the problem of lack of comprehensive evaluation method for the status of existing application systems by selecting a variety of different indicators for evaluation.

[0036] The technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems are described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0037] Figure 2 Schematic diagram of the process of the system evaluation method provided for this application Figure 1 ,like Figure 2 As shown, the method includes:

[0038] S201. Obtain configuration information and system logs in the target system.

[0039] Among them, the configuration information includes the architecture information of the target system, the type of technology stack, and the activation time of the physical device; the system log includes the inspection log, alarm log, system usage log, and system change log of the target system.

[0040] Specifically, this embodiment is used to specifically illustrate the implementation process of the system evaluation method.

[0041] The execution subject of the embodiment of the present disclosure is a device that can obtain the configuration information and system log of the target system, which can be the target system itself, or other processors and servers (hereinafter collectively referred to as servers).

[0042] When the health status of the system needs to be evaluated, the server obtains various information in the system based on predetermined information types.

[0043] Configuration information refers to information related to the hardware and software configuration of the system, such as server architecture, operating system version, network configuration, storage capacity, etc. System logs refer to various log data generated during the operation of the system, such as inspection logs used to record regular inspections and maintenance activities of the system, alarm logs used to record system anomalies and error events, system usage logs used to record user activities and system resource usage, and system change logs used to record the change history of system configuration and software updates.

[0044] When collecting this data, the corresponding configuration information and log files can be extracted from the corresponding interfaces in the system through scripts or automated tools, and then the data from different sources can be formatted and standardized (the collected data can also be stored in a centralized data warehouse for easy calling), and then the various data required for calculating indicators can be extracted.

[0045] Therefore, through systematic data collection, the complexity and error rate of manual operations are reduced, and a comprehensive data basis can be provided for the analysis of system health, supporting subsequent analysis and decision-making.

[0046] S202: Determine a static indicator score of the target system based on the configuration information and the set static indicator type.

[0047] Among them, static indicators are used to evaluate the health status of the basic configuration of the target system.

[0048] Specifically, static indicators mainly evaluate whether the basic configurations of the target system are in a healthy, available and reliable state as a whole.

[0049] For each static indicator, its corresponding scoring status can be determined according to the corresponding configuration information of the target system. Then, a health score that comprehensively evaluates the basic configuration of the target system can be generated by summarizing the scores of each indicator.

[0050] This ensures that the health status assessment of the target system covers all aspects of the target system's basic configuration, helping to identify potential configuration deficiencies.

[0051] S203: Determine the dynamic indicator score of the target system based on the system log and the set dynamic indicator type.

[0052] Among them, dynamic indicators are used to evaluate the health status of the target system during operation.

[0053] Specifically, dynamic indicators mainly evaluate the health status of the target system during operation through the system's real-time performance and stability indicators. Dynamic indicators can include common alarm volume, CPU utilization, memory usage, network latency, error rate, etc.

[0054] By combining dynamic indicators, the implementation and operation status of the system can be analyzed in real time or regularly to ensure the timeliness of the determined dynamic indicator scores. In addition, real-time evaluation of the system operation status can be carried out to assist in timely detection of anomalies in the system.

[0055] Combining the analysis of static and dynamic indicators can enhance the overall understanding of the health status of the system.

[0056] S204: Determine and output the health status of the target system based on the static indicator score and the dynamic indicator score.

[0057] Specifically, the health status can be expressed by a comprehensive score (such as weighted combination of static and dynamic indicator scores to obtain the overall health status score of the system) to reflect the overall health status of the system, such as expressed as a percentage or grade (such as A, B, C). It can also be expressed by a multi-dimensional image composed of multiple indicators to comprehensively and detailedly reflect the health status of the target system.

[0058] Based on the above results, a visual display and detailed report of the analysis conclusions related to the health status can also be output, which comprehensively displays the score details, trend analysis and improvement suggestions related to the health status of the target system.

[0059] In some embodiments, the server can automatically generate and distribute health status reports and send them to relevant personnel on a regular basis. It can also generate corresponding health status reports in real time through the triggering of the system administrator and send the health status reports to relevant personnel to help relevant personnel better manage the application system, thereby improving the transparency and controllability of system management and providing a basis for continuous improvement.

[0060] The system evaluation method provided in the embodiment of the present application obtains the configuration information and system log in the target system, and then determines the static indicator score of the target system based on the configuration information and the set static indicator types, determines the dynamic indicator score of the target system based on the system log and the set dynamic indicator types, and determines and outputs the health status of the target system based on the static indicator score and the dynamic indicator score. Thus, by comprehensively integrating the static and dynamic data of the system according to the configuration information and system log of the target system, it is possible to comprehensively evaluate the basic configuration of the system, and by analyzing the inspection log, alarm log, system usage log and system change log, it is possible to monitor and evaluate the dynamic operation status of the system in real time, and through the systematic evaluation criteria, relevant personnel can more intuitively understand the overall health status of the system, which not only improves the efficiency of system management, but also enhances the ability to identify and prevent potential problems, providing strong support for the stable operation of the system.

[0061] Figure 3 Schematic diagram of the system evaluation process provided for this application Figure 2 ,like Figure 3 As shown, in this embodiment Figure 2 Based on the embodiment, the specific process in the system evaluation method is described in detail, and the method includes:

[0062] S301. Obtain configuration information and system logs in the target system.

[0063] Among them, the configuration information includes the architecture information of the target system, the type of technology stack, and the activation time of the physical device; the system log includes the inspection log, alarm log, system usage log, and system change log of the target system.

[0064] Specifically, the server can collect static data from different sources through CMDB configuration management, health check components, etc., such as obtaining configuration information such as equipment service life and system topology; and collect Lingyun monitoring platform Monitor, Alert and other modules to obtain system component operation data, alarms and other system dynamics-related log information.

[0065] The static indicators involved in system evaluation include: robustness indicators, complexity indicators and service life indicators of the target system; the dynamic indicators include: alarm indicators for evaluating the alarm volume of the target system, inspection indicators for evaluating the inspection results and inspection frequency of the target system, capacity utilization indicators for evaluating the target system database and processor load, system change indicators for evaluating the frequency of changes in the target system, and abnormal component indicators for evaluating the working status of target system components.

[0066] Specifically, the system architecture is a collection of logical relationships among the system's components, from which information such as the calling relationships between upstream and downstream application systems, the data communication relationships among components within the system, and the scale of the system can be quickly obtained. By analyzing information such as the system architecture and technology stack, various static indicators for system evaluation can be derived.

[0067] S302: Based on the system architecture information, if each component in the target system includes at least one backup component, determine that the robustness index score of the target system is high.

[0068] Among them, the static indicators are robustness indicators.

[0069] Specifically, a series of designs are needed at the system architecture level to avoid single-point operation problems in order to ensure the robustness of the system. The indicators for evaluating the robustness of the system are called robustness indicators.

[0070] Each component in a highly robust system should have sufficient high-availability design, such as cluster architecture, active-active architecture, active-standby architecture, etc. For the convenience of evaluation, you can directly check whether each component in the target system contains at least one backup component to determine the robustness of the system components.

[0071] S303: If there is at least one component in the target system that does not include a backup component, determine that the robustness index score of the target system is low.

[0072] Specifically, if there is only one server that undertakes the business, and an accident such as a server crash occurs, which will cause the external service of the application system to be interrupted, then it can be considered that the robustness of the system (target system) is poor and the system may have a single point failure risk.

[0073] The high-scoring and low-scoring branches can be configured according to user needs, such as 3 points for a high score and 1 point (or 0 point) for a low score, or other scoring can be performed.

[0074] The robustness evaluation in steps S302 to S303 helps identify potential problems in the system architecture and ensures high availability of the system.

[0075] S304: Based on the type of technology stack, if there is no old technology stack in the target system, determine that the complexity index score of the target system is high.

[0076] Among them, the static indicator is the complexity indicator. The old technology stack is used to indicate the technology stack whose time interval between the last update date and the current time exceeds the set time threshold and the corresponding version is not the latest version.

[0077] Specifically, the more complex the system's technology stack is, the more difficult it is to manage the system. We usually hope that the complexity of the system's technology stack is as standardized and concise as possible.

[0078] For example, the current standard architecture system in the industry mainly uses TDSQL and GaussDB at the database level (both are common databases, and since they are less relevant to the implementation process of this solution, these terms will not be expanded), cache is implemented using Redis, load balancing is implemented through F5 or Deep, and if there is soft load, the Nginx server under the cloud is used, and the application is generally deployed on the cloud CCE. For each specific application function, usually one solution is used instead of mixing multiple solutions to reduce system complexity.

[0079] A system with a standardized and concise technology stack is conducive to operation and maintenance management at the infrastructure level. Compared with the old technology stack, the new technology stack has more advantages in operation and maintenance support and product updates and iterations. Therefore, the system complexity index is determined here based on the newness and complexity of the technology stack.

[0080] In one case, if there is no old technology stack in the target system, the score is high, indicating that the technology stack is newer and easier to maintain.

[0081] S305: If there is at least one old technology stack in the target system, determine that the complexity index score of the target system is a medium score.

[0082] Specifically, if there are some outdated technology stacks, the score will be medium, indicating that attention needs to be paid to the updating and maintenance of the technology stack.

[0083] S306: If the target system contains old technology stacks whose proportion exceeds a set proportion threshold, determine that the complexity index score of the target system is low.

[0084] Specifically, if the proportion of old technology stacks exceeds the set threshold, the score is low, indicating that the technology stack may affect the operation and maintenance efficiency of the system.

[0085] The complexity index evaluation from step S304 to step S306 helps identify potential problems in the technology stack and ensures that the system's technology stack remains modern and efficient.

[0086] S307: Based on the activation time of the physical device, if there is no overdue device in the target system, determine that the service life index score of the target system is high.

[0087] Among them, the static indicator is the service life indicator, and the overdue equipment is used to indicate that the difference between the activation time and the current time is greater than the set service life of the equipment.

[0088] Specifically, overuse of equipment will lead to an uncontrollable increase in failure rate, which will pose a hidden danger to system stability. Therefore, the service life of physical machines and storage devices (NAS) is included in the static indicators (i.e. service life indicators). Because if the service life of the equipment exceeds the specification, the system administrator needs to replace it in time or try other upgrade solutions.

[0089] In the evaluation of the service life indicator, if there is no overdue equipment in the target system, the service life indicator score is high, indicating that the equipment is in good condition and has low risk.

[0090] S308. If there are expired devices in the target system but no equipment to be scrapped, determine that the service life index score of the target system is a medium score.

[0091] Among them, the equipment to be scrapped is used to indicate the equipment whose difference between the activation time and the current time is greater than the set scrapping time.

[0092] Specifically, if there is equipment that has exceeded its expiration date but no equipment to be scrapped, the score will be medium, indicating that attention needs to be paid to equipment maintenance and updating, but the equipment is still usable.

[0093] S309: If there is equipment to be scrapped in the target system, determine that the service life index score of the target system is low.

[0094] Specifically, if there is equipment to be scrapped, the score is low, indicating that the equipment may pose a threat to system stability.

[0095] The service life indicator evaluation in steps S307 to S309 can help identify potential problems in equipment use and ensure that the infrastructure of the target system remains reliable and stable.

[0096] S310: Based on the set dynamic indicator types, determine the number of occurrences of abnormal situations corresponding to each dynamic indicator.

[0097] Among them, abnormal situations include system alarms, system capacity occupancy ratio higher than the set capacity threshold, system inspection results with records that do not meet specifications, number of system changes and unavailable system components.

[0098] Specifically, dynamic indicators such as system alarms, capacity occupancy ratio, inspection results, number of changes, and unavailable components can help identify abnormal situations that may occur during the operation of the target system by monitoring the real-time operating status of the target system.

[0099] In some embodiments, for alarm indicators, the infrastructure level of the target system usually has corresponding scripts to regularly collect the status of each component of the system. If a keyword or value exceeds an abnormality, an alarm message will be generated to remind the system administrator. For example, at the Linux operating system level, there is a monitoring script that collects operating system logs every minute, and corresponding alarms will be generated when encountering keywords such as "error". The same applies to databases, middleware, and load balancing. System administrators can maintain stable system operation by analyzing and promptly handling alarms.

[0100] According to the number of occurrences of indicators of different severity, the score of the alarm indicator can be calculated. For example, a serious alarm is 3 points, an important alarm is 2 points, and a minor alarm is 1 point. Combined with the number of each alarm during the set monitoring period, the score of the alarm indicator can be obtained.

[0101] Alternatively, the alarm value table can be calculated in combination with the importance of the object corresponding to the alarm. For example, the alarm of an important object (such as a processor) will be multiplied by a high coefficient (such as 3) based on the severity, the alarm of a general object can be multiplied by a medium coefficient (such as 2), and the alarm of an unimportant object can be multiplied by a low coefficient (such as 1). The specific calculation method can also be added instead of multiplied, which is not limited here.

[0102] In some embodiments, for the capacity usage index, which mainly refers to the storage level, on the one hand, by setting different thresholds to generate different levels of alarms, problems can be discovered in time, and on the other hand, a prediction and estimation function can be added, for example, according to the growth rate of the existing data volume, how long it is expected to reach 80% of the database capacity, whether it is necessary to prepare for capacity expansion in advance, etc. Through the monitoring and prediction of capacity indicators, system administrators can improve their ability to predict the operation status of the system and make corresponding preparations in advance.

[0103] The server can be configured with two parts of calculation, one part is the capacity usage ratio and the corresponding ratio threshold, such as 1 point for less than 60%, 2 points for more than 60%, and 3 points for more than 80%; the other part is the capacity growth trend and the corresponding trend threshold, such as 3 points for a growth rate of more than 10% / month, 2 points for more than 2% / month, and 1 point for less than 2% / month. In this way, the capacity usage index score can be obtained.

[0104] In some embodiments, for the system change index, since frequent changes to the system may cause system risks, it is necessary to collect statistics on the number and nature of recent changes to the system, so as to use the system change index as one of the inspection directions.

[0105] For example, the change quantity calculation can be calculated by referring to the change risk score. 100-Σk (change risk value x the number of such changes), where k is the weight. The change risk value can be determined based on the number of bugs caused by the change or the change-related fault reports downloaded from an external server. If there are many faults that may be caused and the faults occur frequently, the corresponding risk value is high, otherwise it is low.

[0106] In some embodiments, for inspection indicators, this item includes security baseline and daily inspection, which are usually periodic scanning inspections. For example, Linux daily inspection and security baseline inspection, GaussDB daily inspection and security baseline inspection, TDSQL daily inspection, etc. This type of regular inspection can find parameters in the system that do not meet the internal standards or security specifications, so as to remind the system administrator to perform maintenance and repair.

[0107] For example, if the system has not been found to be lacking important patches or having non-compliance issues with key indicators, a high score can be assigned. Conversely, if such a situation exists, a low score can be assigned (if there are unimportant non-compliance issues, a mid-range score can also be assigned).

[0108] In some embodiments, the abnormal component index is mainly used to evaluate whether there is a component abnormality (such as partial functional failure but the whole is still available, in this case, the function can also be evaluated whether it is abnormal) or unavailable (that is, the whole is unavailable). If the unavailable object has multiple available backups, its abnormal component index score = unavailable score / total number of available backups, where the unavailable score must be ≥ 0. The unavailable branch can also be evaluated based on whether the component object is important. If the abnormal component is very important, it can be assigned 100 points. When the importance decreases, its score can decrease successively. These component objects can include databases, application servers, middleware, etc., and indirectly related objects include switches, load balancing, etc.

[0109] For example, if a critical processor has no backup and is in an unavailable state, the abnormal component indicator score can be directly 100 points (100 points will be deducted in the overall evaluation, representing the worst system health status); for example, if the component of the function of generating a successful transaction prompt message is abnormal (if this function is assigned 5 points), but there are two backups, its score can be 2.5 (i.e. 5 / 2).

[0110] S311. Determine the dynamic indicator score of the corresponding category based on the number of occurrences and the corresponding abnormal situation assignments.

[0111] Specifically, from the above analysis, we can know that the system can determine the score of each dynamic indicator according to the number of occurrences of abnormal situations and the corresponding assignments. The scoring process takes into account the characteristics such as the severity and frequency of the abnormalities, and can obtain the score of each dynamic indicator through weighted calculation. This helps system administrators understand the health status of the system during operation and promptly discover and handle potential operation problems.

[0112] S312: Based on the weighted sum of the static indicator scores and the dynamic indicator scores, the overall health of the target system is obtained.

[0113] Specifically, the overall health of the target system can be obtained by weighted summation of various indicators, or weighted summation of corresponding static indicator scores and dynamic indicator scores can be calculated for each component object in the target system.

[0114] For example, for a single component object, its health can be 100 minus the score of each indicator corresponding to the component object.

[0115] If the calculation is performed for each component object in the target system, the aforementioned indicators can be refined to calculate the corresponding score for each component in the system.

[0116] S313. Based on the score of each indicator, generate a score radar chart corresponding to the target system.

[0117] Specifically, the overall health score can be used to determine the overall health of the application system infrastructure. However, evaluation based on a single score alone can easily lead to problems such as being too one-sided and lacking a lot of information.

[0118] Therefore, a polygonal radar chart can be used for description. For example, each indicator corresponds to a vertex of the radar chart, and the indicators evaluated by the rating method can be represented by dividing the line segment from the vertex to the center into four equal parts and mapping them to different equal points. Alternatively, the health indicator corresponding to each component can be used as a vertex of the radar chart to reflect the difference in health between different components in more detail and facilitate targeted maintenance.

[0119] S314: Determine the scoring radar degree and the overall health degree as the health status of the target system, and output the health status.

[0120] Specifically, the system determines the scoring radar chart and overall health as the health status of the target system and outputs the health status. This output not only provides system administrators with a comprehensive view of the current system health status, but also provides an important reference for subsequent system maintenance and optimization.

[0121] In some embodiments, the server may include a snapshot storage function to store calculated information related to the health status of the target system, which is convenient for auditing and querying historical data.

[0122] The system evaluation method provided in the embodiment of the present application,

[0123] Through the above execution steps, the system achieves a comprehensive evaluation and display of the health of the target system, which has significant beneficial effects. First, the acquisition and analysis of configuration information and system logs provide a comprehensive perspective of the system infrastructure and operating status, ensuring the accuracy and completeness of the information. Secondly, through the evaluation of static indicators, potential problems in the system architecture, technology stack and equipment life are identified to help administrators optimize system configuration and infrastructure. Real-time monitoring and scoring of dynamic indicators enhance the ability to provide immediate feedback on the system's operating status and support timely detection and handling of anomalies. Finally, the comprehensive score and radar chart display provide an intuitive view of the health status, improve the transparency and controllability of system management, and provide a clear direction for system maintenance and optimization. This systematic health evaluation system not only improves management efficiency, but also enhances the ability to predict and prevent potential problems.

[0124] Figure 4 A schematic diagram of the structure of the system evaluation device provided in this application, such as Figure 4 As shown, the system evaluation device 400 provided in this embodiment includes:

[0125] The acquisition module 410 is used to acquire configuration information and system logs in the target system. The configuration information includes architecture information, technology stack types, and activation time of physical devices of the target system. The system logs include inspection logs, alarm logs, system usage logs, and system change logs of the target system.

[0126] A first calculation module 420 is used to determine a static indicator score of the target system based on the configuration information and the set static indicator type, where the static indicator is used to evaluate the health status of the basic configuration of the target system;

[0127] A second calculation module 430 is used to determine a dynamic indicator score of the target system based on the system log and the set dynamic indicator type, where the dynamic indicator is used to evaluate the health status of the target system during operation;

[0128] The processing module 440 is used to determine and output the health status of the target system based on the static indicator score and the dynamic indicator score.

[0129] In a possible implementation, the acquisition module 410 specifically includes static indicators including: robustness indicators, complexity indicators and service life indicators of the target system; dynamic indicators including: alarm indicators for evaluating the alarm volume of the target system, inspection indicators for evaluating the inspection results and inspection frequency of the target system, capacity utilization indicators for evaluating the target system database and processor load, system change indicators for evaluating the frequency of changes in the target system, and abnormal component indicators for evaluating the working status of target system components.

[0130] In one possible implementation, the first calculation module 420 is specifically used to, if the so-called static indicator is a robustness indicator, based on the system architecture information, if each component in the target system includes at least one backup component, determine that the robustness indicator score of the target system is a high score; if there is at least one component in the target system that does not include a backup component, determine that the robustness indicator score of the target system is a low score.

[0131] In one possible implementation, the first calculation module 420 is specifically used to, if the so-called static indicator is a complexity indicator, based on the type of technology stack, if there is no old technology stack in the target system, determine that the complexity index score of the target system is high, and the old technology stack is used to indicate that the time interval between the last update date and the current time exceeds a set time threshold, and the corresponding version is not the latest version of the technology stack; if there is at least one old technology stack in the target system, determine that the complexity index score of the target system is medium; if there are old technology stacks in the target system whose proportion exceeds a set proportion threshold, determine that the complexity index score of the target system is low.

[0132] In one possible implementation, the first calculation module 420 is specifically used to, if the so-called static indicator is a service life indicator, based on the activation time of the physical device, if there is no overdue equipment in the target system, determine that the service life indicator score of the target system is high, and the overdue equipment is used to indicate that the difference between the activation time and the current time is greater than the set service life; if there is overdue equipment in the target system but no equipment to be scrapped, determine that the service life indicator score of the target system is medium, and the equipment to be scrapped is used to indicate that the difference between the activation time and the current time is greater than the set scrapping duration; if there is equipment to be scrapped in the target system, determine that the service life indicator score of the target system is low.

[0133] In one possible implementation, the second calculation module 430 is specifically used to determine the number of occurrences of abnormal situations corresponding to each dynamic indicator based on the set dynamic indicator types, the abnormal situations including system alarms, system capacity occupancy ratio higher than the set capacity threshold, system inspection results with non-compliant records, number of system changes and unavailable system components; based on the number of occurrences and the assignment of corresponding abnormal situations, determine the dynamic indicator score of the corresponding type.

[0134] In one possible implementation, the processing module 440 is specifically used to obtain the overall health of the target system based on the weighted sum of the static indicator score and the dynamic indicator score; generate a scoring radar chart corresponding to the target system based on the score of each indicator; determine the scoring radar and the overall health as the health status of the target system, and output the health status.

[0135] The system evaluation device provided in this embodiment can execute the method provided in the above method embodiment. Its implementation principle and technical effect are similar, and this embodiment will not be described in detail here.

[0136] Figure 5 This is a schematic diagram of the structure of the control device provided in this application. Figure 5 As shown, the electronic device 50 provided in this embodiment includes: at least one processor 501 and a memory 502. Optionally, the device 50 also includes a communication component 503. The processor 501, the memory 502 and the communication component 503 are connected via a bus 504.

[0137] In a specific implementation process, at least one processor 501 executes the computer-executable instructions stored in the memory 502, so that at least one processor 501 executes the above method.

[0138] The specific implementation process of the processor 501 can be found in the above method embodiment, and its implementation principle and technical effect are similar, so this embodiment will not be repeated here.

[0139] In the above embodiments, it should be understood that the processor may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), etc. A general-purpose processor may be a microprocessor or any conventional processor. The steps of the method disclosed in the invention may be directly implemented as being executed by a hardware processor, or may be executed by a combination of hardware and software modules in the processor.

[0140] The memory may include a high-speed memory (Random Access Memory, RAM), and may also include a non-volatile memory (Non-volatile Memory, NVM), such as at least one disk memory.

[0141] The bus may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, the bus in the drawings of the present application is not limited to only one bus or one type of bus.

[0142] The present application also provides a computer program product, including a computer program, which implements the method in any of the above embodiments when executed by a processor.

[0143] The present application also provides a computer-readable storage medium, in which computer-executable instructions are stored. When a processor executes the computer-executable instructions, the method in any of the above embodiments is implemented.

[0144] The above-mentioned readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk. The readable storage medium can be any available medium that can be accessed by a general or special-purpose computer.

[0145] An exemplary readable storage medium is coupled to a processor so that the processor can read information from the readable storage medium and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can be located in an application specific integrated circuit (Application Specific Integrated Circuits, referred to as: ASIC). Of course, the processor and the readable storage medium can also exist in the device as discrete components.

[0146] The division of units is only a logical function division, and there may be other divisions in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interface, device or unit, which can be electrical, mechanical or other forms.

[0147] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0148] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0149] If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods of each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk, etc. Various media that can store program codes.

[0150] Those skilled in the art can understand that all or part of the steps of implementing the above-mentioned method embodiments can be completed by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, the steps of the above-mentioned method embodiments are executed; and the aforementioned storage medium includes: ROM, RAM, disk or optical disk and other media that can store program codes.

[0151] Finally, it should be noted that those skilled in the art will readily conceive of other embodiments of the present invention after considering the specification and practicing the invention disclosed herein. The present invention is intended to cover any variations, uses or adaptations of the present invention, which follow the general principles of the present invention and include common knowledge or customary technical means in the art not disclosed by the present invention, are not limited to the precise structure described above and shown in the drawings, and may be modified and changed in various ways without departing from the scope thereof. The scope of the present invention is limited only by the appended claims.

Claims

1. A system evaluation method, characterized in that: The system evaluation method includes: Obtaining configuration information and system logs in the target system, wherein the configuration information includes architecture information, technology stack type, and activation time of physical devices of the target system, and the system logs include inspection logs, alarm logs, system usage logs, and system change logs of the target system; Determine a static indicator score of the target system based on the configuration information and the set static indicator type, wherein the static indicator is used to evaluate the health status of the basic configuration of the target system; Determine a dynamic indicator score of the target system based on the system log and the set dynamic indicator type, wherein the dynamic indicator is used to evaluate the health status of the target system during operation; Based on the static indicator score and the dynamic indicator score, a health status of the target system is determined and output.

2. The method according to claim 1, characterized in that The static indicators include: The robustness index, complexity index and service life index of the target system; The dynamic indicators include: Alarm indicators for evaluating the alarm volume of the target system, inspection indicators for evaluating the inspection results and inspection frequency of the target system, capacity usage indicators for evaluating the database and processor load of the target system, system change indicators for evaluating the frequency of changes to the target system, and abnormal component indicators for evaluating the working status of the target system components.

3. The method according to claim 2, characterized in that If the so-called static indicator is a robustness indicator, The step of determining the static indicator score of the target system based on the configuration information and the set static indicator type includes: Based on the system architecture information, if each component in the target system includes at least one backup component, determining that the robustness index score of the target system is high; If there is at least one component in the target system that does not include a backup component, it is determined that the robustness index score of the target system is low.

4. The method according to claim 2, characterized in that: If the so-called static index is a complexity index, The step of determining the static indicator score of the target system based on the configuration information and the set static indicator type includes: Based on the type of technology stack, if there is no old technology stack in the target system, it is determined that the complexity index score of the target system is high, and the old technology stack is used to indicate that the time interval between the last update date and the current time exceeds a set time threshold, and the corresponding version is not the latest version of the technology stack; If there is at least one old technology stack in the target system, determining that the complexity index score of the target system is a medium score; If the target system contains old technology stacks whose proportion exceeds a set proportion threshold, it is determined that the complexity index score of the target system is low.

5. The method according to claim 2, characterized in that: If the so-called static indicator is the service life indicator, The step of determining the static indicator score of the target system based on the configuration information and the set static indicator type includes: Based on the activation time of the physical device, if there is no overdue device in the target system, it is determined that the service life index score of the target system is high, and the overdue device is used to represent a device whose difference between the activation time and the current time is greater than the set service life; If there are overdue devices in the target system but no to-be-scrapped devices, the service life index score of the target system is determined to be a medium score, and the to-be-scrapped devices are used to represent devices whose difference between the activation time and the current time is greater than the set scrapping time; If there is equipment to be scrapped in the target system, it is determined that the service life index score of the target system is low.

6. The method according to claim 1, characterized in that The step of determining the dynamic indicator score of the target system based on the system log and the set dynamic indicator type includes: Based on the set dynamic indicator types, determine the number of occurrences of abnormal situations corresponding to each dynamic indicator, the abnormal situations including system alarms, system capacity occupancy ratio higher than a set capacity threshold, system inspection results with non-compliant records, system change times, and unavailable system components; Based on the number of occurrences and the assignment of the corresponding abnormal conditions, a dynamic indicator score of the corresponding category is determined.

7. The method according to any one of claims 1 to 6, characterized in that The determining and outputting the health status of the target system based on the static indicator score and the dynamic indicator score includes: Obtaining the overall health of the target system based on a weighted sum of the static indicator score and the dynamic indicator score; Based on the score of each indicator, a score radar chart corresponding to the target system is generated; The scoring radar degree and the overall health degree are determined as the health state of the target system, and the health state is output.

8. A system evaluation device, characterized in that: include: An acquisition module, used to acquire configuration information and system logs in the target system, wherein the configuration information includes architecture information, technology stack type, and activation time of physical devices of the target system, and the system logs include inspection logs, alarm logs, system usage logs, and system change logs of the target system; A first calculation module, used to determine a static indicator score of the target system based on the configuration information and a set static indicator type, wherein the static indicator is used to evaluate the health status of the basic configuration of the target system; A second calculation module is used to determine the dynamic indicator score of the target system based on the system log and the set dynamic indicator type, and the dynamic indicator is used to evaluate the health status of the target system during operation; A processing module is used to determine and output the health status of the target system based on the static indicator score and the dynamic indicator score.

9. A control device, characterized in that: include: Memory, processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory, so that the processor performs the method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, which are used to implement the method according to any one of claims 1 to 7 when executed by a processor.

Images