Historical performance monitoring data management method and device, equipment and storage medium

Abstract

The invention relates to a historical performance monitoring data management method and device, equipment and a storage medium, and relates to the technical field of servers. According to the method, the performance monitoring configuration file is set for setting the index items as the monitoring items, the monitoring items are summarized to form the monitoring item list, and different monitoring item lists are selectively set for different users to monitor the performance monitoring data of different manufacturers in a differentiated manner; in addition, a task script for regularly collecting monitoring data is set to regularly traverse monitoring items in a monitoring item list to obtain corresponding performance monitoring data, index item performance monitoring data matched with the monitoring items in the monitoring item list is uploaded to a cloud server to be stored, and long-term storage of historical performance monitoring data is supported. The method supports quick query of cross-cluster backup performance monitoring data and displays the data on an interface.

Description

Technical Field

[0001] The present application relates to the field of server technology, and in particular to a method, device, computer equipment and storage medium for managing historical performance monitoring data. Background Art

[0002] Performance monitoring is to monitor and record the performance indicators of software, hardware or system during operation in order to analyze and optimize system performance. By collecting and analyzing performance data, you can identify system bottlenecks, optimize resource allocation, and improve system reliability and stability.

[0003] However, with the development of digitalization, large data centers need to operate, manage, and monitor more and more storage nodes, and it is becoming increasingly complex to query the performance monitoring data of a cluster node in a timely manner. For a single cluster, there are hundreds of performance indicators of more than ten types of performance monitoring records, and data centers contain thousands of storage nodes. The recording and display methods of different manufacturers are different, making operation and maintenance more and more difficult. Historical performance monitoring data cannot be stored for a long time. In large-scale storage clusters, the amount of performance monitoring data generated is large. It is necessary to reduce the data storage time to reduce the pressure on the database. Historical performance monitoring data needs to be deleted regularly to ensure the normal operation of the cluster. Therefore, how to save the massive monitoring data accumulated over a long period of time and support fast query and display of monitoring data has become a technical problem that needs to be solved urgently. Summary of the invention

[0004] Based on this, a historical performance monitoring data management method, device, computer equipment and storage medium are provided to solve the technical problem of how to preserve the massive monitoring data accumulated over a long period of time and support the rapid query and display of the monitoring data.

[0005] In one aspect, a method for managing historical performance monitoring data is provided, the method comprising:

[0006] Set a performance monitoring configuration file for setting indicator items as monitoring items, and summarize the monitoring items to form a monitoring item list;

[0007] Set a task script for collecting monitoring data at regular intervals, wherein the task script includes a list of database paths corresponding to monitoring items, a transfer cycle, a last transfer time, and a remote server path for storing monitoring data;

[0008] In response to starting the task script, obtaining the latest performance monitoring configuration file from the remote server path storing the monitoring data, and updating the monitoring item list and the database path list corresponding to the indicator item;

[0009] Determine whether the transfer time has arrived according to the last transfer data time and the transfer cycle, and if so, trigger the transfer of performance monitoring data, match the indicator performance monitoring data collected by the task script with the monitoring item list, and upload the indicator performance monitoring data that matches the monitoring items in the monitoring item list to the cloud server for storage;

[0010] In response to displaying monitoring data of monitoring items of a target cluster, the performance monitoring data of the indicator items collected by the target cluster is retrieved, and a monitoring chart is generated and displayed.

[0011] In one embodiment, the step of setting a performance monitoring configuration file for setting indicator items as monitoring items and aggregating the monitoring items to form a monitoring item list includes:

[0012] Get performance monitoring indicators for a single storage cluster;

[0013] According to the monitoring requirements of each user, the indicator items to be monitored are selected as monitoring items, and a monitoring item list for each user is formed by summarizing the monitoring items.

[0014] In one embodiment, the step of setting a task script for periodically collecting monitoring data includes:

[0015] A storage folder is set corresponding to each user's monitoring item list, and a remote server path for storing monitoring data is formed according to the address of the storage folder;

[0016] Set the daily start time and shutdown time of the task script.

[0017] In one embodiment, the step of determining whether the transfer time has arrived based on the last transfer data time and the transfer cycle, and triggering the transfer of performance monitoring data if so, and matching the indicator performance monitoring data collected by the task script with the monitoring item list includes:

[0018] Detecting whether the current time is later than the sum of the last data transfer time and the transfer period;

[0019] If yes, the performance monitoring data will be transferred and the list of monitoring items for each user will be obtained;

[0020] Obtain all indicator items collected by the task script, and traverse the indicator items collected by the task script one by one in the monitoring item list of each user to determine whether the monitoring item exists;

[0021] In response to the presence of a monitoring item identical to the target indicator item in the monitoring item list, generating a transfer directory according to the monitoring level of the monitoring item and the transfer data time, and exporting the performance monitoring data in the cluster directory;

[0022] In response to the absence of a monitoring item identical to the target indicator item in the monitoring item list, traversing monitoring items in the monitoring item list of the next user to determine whether the target indicator item exists;

[0023] In response to the absence of a monitoring item identical to the target indicator item in the monitoring item lists of all users, obtaining the next indicator item collected by the task script, and traversing the monitoring items in the monitoring item lists of each user one by one to determine whether there is the next indicator item;

[0024] Determine whether all indicator items collected by the task script are matched and the exported performance monitoring data is uploaded to the cloud server for storage. If so, end the process. If not, obtain the next indicator item collected by the task script, and traverse the monitoring items in each user's monitoring item list one by one to determine whether there is the next indicator item.

[0025] In one embodiment, the step of uploading the performance monitoring data of the indicator items matching the monitoring items in the monitoring item list to the cloud server for storage includes:

[0026] Obtaining the indicator item performance monitoring data that matches the monitoring items in the monitoring item list of each user, and obtaining the remote server path of the storage folder corresponding to each user's monitoring item list setting;

[0027] The performance monitoring level of the monitoring item in the monitoring item list is obtained, and the monitoring items are classified and stored in the storage folder corresponding to the remote server path according to the performance monitoring level of the monitoring items.

[0028] In one embodiment, in response to displaying monitoring data of monitoring items of a target cluster, the steps of retrieving performance monitoring data of indicator items collected by the target cluster, generating monitoring charts and displaying the charts include:

[0029] Query the remote server, update the monitoring item list and the cluster network interconnection protocol for which monitoring data has been collected, and return the cluster network interconnection protocol for which performance monitoring data has been collected to the interface;

[0030] Create corresponding monitoring charts based on the cluster network interconnection protocol selected by the user. Based on the collected monitoring data information, use the first-level directory under the cluster monitoring data as the monitoring object type and the second-level directory as a monitoring instance. Set a monitoring object type to match multiple monitoring items.

[0031] The remote server calculates and returns the time period of the backed-up monitoring data according to the performance monitoring level classification storage directory, and provides the user with selection;

[0032] Import the monitoring data corresponding to the time period selected by the user into the database, query and obtain the monitoring indicators in the monitoring data corresponding to the time period selected by the user for the user to query;

[0033] According to the monitoring indicators queried by the user, the saved monitoring data is generated into a monitoring chart and returned to the interface to display the query results.

[0034] In one embodiment, the historical performance monitoring data management method further includes:

[0035] Export and back up the performance monitoring data corresponding to the monitoring items queried by the user. The storage directory of the exported backup is IP address / monitoring object type / first-level monitoring / second-level monitoring item / time / monitoring item name;

[0036] In response to receiving the metadata of the target monitoring item to be retrieved, creating a metadata monitoring chart, and obtaining the monitoring object type, monitoring item name and time corresponding to the target monitoring item;

[0037] The user obtains the remote path for storing the monitoring data of the monitoring item according to the monitoring object type, monitoring item name and time corresponding to the target monitoring item;

[0038] If the path exists and the sub-path is time, the metadata of the target monitoring item within the time is retrieved and imported into the database and displayed to the user; if the sub-path is not time, all sub-paths are returned to the interface. After the user selects one of the sub-paths, the queried metadata of the target monitoring item is returned to the interface for display.

[0039] In another aspect, a historical performance monitoring data management device is provided, the device comprising:

[0040] Setting a performance monitoring profile module, used to set a performance monitoring profile, used to set indicator items as monitoring items, and aggregate the monitoring items to form a monitoring item list;

[0041] Setting a task script module, used to set a task script for regularly collecting monitoring data, wherein the task script includes a list of database paths corresponding to monitoring items, a transfer cycle, a last transfer time, and a remote server path for storing monitoring data;

[0042] A monitoring information updating module, for, in response to starting the task script, obtaining the latest performance monitoring configuration file from the remote server path storing the monitoring data, and updating the monitoring item list and the database path list corresponding to the indicator item;

[0043] A monitoring data backup module is used to determine whether the transfer time has arrived according to the last data transfer time and the transfer cycle, and if so, trigger the transfer of performance monitoring data, match the index item performance monitoring data collected by the task script with the monitoring item list, and upload the index item performance monitoring data that matches the monitoring item in the monitoring item list to the cloud server for storage;

[0044] The import display module is used to retrieve the index item performance monitoring data collected by the target cluster in response to the display of the monitoring data of the monitoring items of the target cluster, generate a monitoring chart and display it.

[0045] In another aspect, a computer device is provided, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the following steps are implemented:

[0046] Set a performance monitoring configuration file for setting indicator items as monitoring items, and summarize the monitoring items to form a monitoring item list;

[0047] Set a task script for collecting monitoring data at regular intervals, wherein the task script includes a list of database paths corresponding to monitoring items, a transfer cycle, a last transfer time, and a remote server path for storing monitoring data;

[0048] In response to starting the task script, obtaining the latest performance monitoring configuration file from the remote server path storing the monitoring data, and updating the monitoring item list and the database path list corresponding to the indicator item;

[0049] Determine whether the transfer time has arrived according to the last transfer data time and the transfer cycle, and if so, trigger the transfer of performance monitoring data, match the indicator performance monitoring data collected by the task script with the monitoring item list, and upload the indicator performance monitoring data that matches the monitoring items in the monitoring item list to the cloud server for storage;

[0050] In response to displaying monitoring data of monitoring items of a target cluster, the performance monitoring data of the indicator items collected by the target cluster is retrieved, and a monitoring chart is generated and displayed.

[0051] In another aspect, a computer-readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:

[0052] Set a performance monitoring configuration file for setting indicator items as monitoring items, and summarize the monitoring items to form a monitoring item list;

[0053] Set a task script for collecting monitoring data at regular intervals, wherein the task script includes a list of database paths corresponding to monitoring items, a transfer cycle, a last transfer time, and a remote server path for storing monitoring data;

[0054] In response to starting the task script, obtaining the latest performance monitoring configuration file from the remote server path storing the monitoring data, and updating the monitoring item list and the database path list corresponding to the indicator item;

[0055] Determine whether the transfer time has arrived according to the last transfer data time and the transfer cycle, and if so, trigger the transfer of performance monitoring data, match the indicator performance monitoring data collected by the task script with the monitoring item list, and upload the indicator performance monitoring data that matches the monitoring items in the monitoring item list to the cloud server for storage;

[0056] In response to displaying monitoring data of monitoring items of a target cluster, the performance monitoring data of the indicator items collected by the target cluster is retrieved, and a monitoring chart is generated and displayed.

[0057] The above-mentioned historical performance monitoring data management method, device, computer equipment and storage medium, by setting a performance monitoring configuration file, are used to set indicator items as monitoring items, summarize the monitoring items to form a monitoring item list, selectively set different monitoring item lists for different users to differentiate the performance monitoring data of different manufacturers, and further set a task script for periodically collecting monitoring data to periodically traverse the monitoring items in the monitoring item list to obtain the corresponding performance monitoring data, upload the indicator item performance monitoring data that matches the monitoring items in the monitoring item list to the cloud server for storage, support long-term storage of historical performance monitoring data, support fast query of backup performance monitoring data across clusters and display it on the interface. BRIEF DESCRIPTION OF THE DRAWINGS

[0058] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0059] Figure 1 This is an application environment diagram of a historical performance monitoring data management method in one embodiment of the present application;

[0060] Figure 2 This is a flow chart of a method for managing historical performance monitoring data in one embodiment of the present application;

[0061] Figure 3A flow chart showing the steps of setting a performance monitoring configuration file in one embodiment of the present application, for setting indicator items as monitoring items, and aggregating the monitoring items to form a monitoring item list;

[0062] Figure 4 A flowchart of a step of matching the index item performance monitoring data collected by the task script with the monitoring item list is provided in one embodiment of the present application, according to the last data transfer time and the transfer cycle to determine whether the transfer time has arrived, and if so, triggering the transfer of performance monitoring data;

[0063] Figure 5 A flowchart of the steps of collecting performance monitoring data of indicator items using a performance monitoring configuration file and a task script in one embodiment of the present application;

[0064] Figure 6 In one embodiment of the present application, in response to displaying monitoring data of monitoring items of a target cluster, the performance monitoring data of the indicator items collected by the target cluster is retrieved, a monitoring chart is generated, and a flow chart showing the steps is shown;

[0065] Figure 7 A schematic diagram of a flow chart of querying historical performance monitoring data to generate a monitoring chart and display query results in one embodiment of the present application;

[0066] Figure 8 This is a structural block diagram of a historical performance monitoring data management device in one embodiment of the present application;

[0067] Fig. 9 This is a diagram of the internal structure of a computer device in one embodiment of the present application. DETAILED DESCRIPTION

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

[0069] As described in the background technology, performance monitoring is to monitor and record the performance indicators of software, hardware or system during operation in order to analyze and optimize system performance. By collecting and analyzing performance data, system bottlenecks can be identified, resource allocation can be optimized, and system reliability and stability can be improved. The monitoring objects of performance monitoring, such as clusters, nodes, network cards, hard disks, etc., refer to the types that need to be monitored. Monitoring items are specific items corresponding to the types of monitoring objects. Monitoring indicators of monitoring items, such as bandwidth and IOPS of clusters, bandwidth and packet loss rate of monitoring network cards, etc.

[0070] However, with the development of digitalization, large data centers need to operate, manage, and monitor more and more storage nodes, and it is becoming increasingly complex to query the performance monitoring data of a cluster node in a timely manner. For a single cluster, performance monitoring records hundreds of performance indicators of more than ten types (such as various indicators of services such as clusters, nodes, hard disks, network ports, files, objects, blocks, etc.), and data centers contain thousands of storage nodes. Different manufacturers have different recording and display methods, making operation and maintenance more and more difficult. How to save the massive monitoring data accumulated over a long period of time and support fast query and display of monitoring data has become an issue worth discussing.

[0071] In the existing storage management platform, according to the storage service deployed in the cluster, the management system monitors and counts the cluster operation status, saves the monitoring data in the database, and supports interface display. When it is necessary to query the historical performance data of the monitoring item, the management interface sends the query conditions. The server queries the database and returns the data to the interface according to the query conditions. The interface renders the data as a chart for users to view. In the existing performance monitoring system, monitoring data is collected periodically and recorded in the database. In a large-scale storage cluster, there are many storage nodes and many monitoring items to be supported by the business. The long-term storage of performance monitoring data puts a lot of pressure on the cluster database. Generally, a regular deletion mechanism is set to delete the historical performance monitoring data. The existing performance monitoring system supports data export. Users choose to save the data in text format so that users can save historical performance monitoring data for a long time. However, historical performance monitoring data cannot be saved for a long time. In a large-scale storage cluster, the amount of performance monitoring data generated is large. It is necessary to reduce the data storage time to reduce the pressure on the database and ensure the normal operation of the cluster. In the data center, the management platforms of different manufacturers have different implementations for the storage, export and display of performance monitoring data. The data cannot be managed uniformly, which is inconvenient for operation and maintenance. The cluster export data is in text format, and it is not easy for operation and maintenance personnel and users to compare the cluster operation status when querying the long-term saved historical performance statistics. Data centers generate massive amounts of performance monitoring data every day, and the existing methods cannot quickly query the required historical performance data.

[0072] To solve the above problems, the embodiment of the present invention creatively proposes a historical performance monitoring data management method, which backs up and imports and displays historical performance monitoring data, is compatible with regular backup of performance monitoring data of different management systems, and supports quick query of historical backup data and import interface display in massive data backup, thereby solving the problem of long-term preservation of historical performance monitoring data.

[0073] The historical performance monitoring data management method provided in this application can be applied to Figure 1In the application environment shown. Among them, the terminal 102, the remote server 103 and the cloud server 104 communicate through the network. Among them, the terminal 102 can be but not limited to various personal computers, laptops, smart phones, tablet computers and portable wearable devices, and the remote server 103 and the cloud server 104 can be implemented with an independent server or a server cluster composed of multiple servers. The terminal 102 is operated by the user to obtain the index item performance monitoring data of the remote server 103 to understand the performance of the remote server 103. The remote server 103 is set with a performance monitoring configuration file and a task script for regularly collecting monitoring data to obtain the index item set by the user corresponding to the remote server 103 as the performance monitoring data corresponding to the monitoring item. The remote server 103 stores the corresponding performance monitoring data. The terminal 102 can download and view the performance monitoring data corresponding to the monitoring item, and transfer the historical performance monitoring data in the cloud server 104, so that the user can retrieve and view the historical performance monitoring data through the terminal 102.

[0074] In one embodiment, Figure 2 As shown, a historical performance monitoring data management method is provided, which is applied to Figure 1 The remote server 103 in the example is used as an example to illustrate, and the following steps are included:

[0075] Step S1, setting a performance monitoring configuration file, which is used to set indicator items as monitoring items, and aggregating the monitoring items to form a monitoring item list;

[0076] Step S2, setting a task script for collecting monitoring data at a fixed time, wherein the task script includes a list of database paths corresponding to monitoring items, a transfer cycle, a last transfer time, and a remote server path for storing monitoring data;

[0077] Step S3, in response to starting the task script, obtaining the latest performance monitoring configuration file from the remote server path storing the monitoring data, and updating the monitoring item list and the database path list corresponding to the indicator item;

[0078] Step S4, judging whether the transfer time has been reached according to the last transfer data time and the transfer cycle, and if so, triggering the transfer of performance monitoring data, matching the index item performance monitoring data collected by the task script with the monitoring item list, and uploading the index item performance monitoring data matching the monitoring items in the monitoring item list to the cloud server for storage;

[0079] Step S5, in response to displaying the monitoring data of the monitoring items of the target cluster, retrieve the performance monitoring data of the indicator items collected by the target cluster, generate a monitoring chart and display it.

[0080] Among them, by setting a performance monitoring configuration file for setting indicator items as monitoring items, the monitoring items are summarized to form a monitoring item list, different monitoring item lists are selectively set for different users to differentiate the performance monitoring data of different manufacturers, and a task script for collecting monitoring data at regular intervals is set to periodically traverse the monitoring items in the monitoring item list to obtain the corresponding performance monitoring data, and the performance monitoring data of the indicator items that match the monitoring items in the monitoring item list are uploaded to the cloud server for storage, supporting long-term storage of historical performance monitoring data, and supporting fast query of backup performance monitoring data across clusters and displaying it on the interface.

[0081] like Figure 3 As shown, in this embodiment, the performance monitoring configuration file is set to set indicator items as monitoring items, and the steps of aggregating the monitoring items to form a monitoring item list include:

[0082] Step S11, obtaining performance monitoring indicators for a single storage cluster;

[0083] Step S12: selecting the indicator items to be monitored as monitoring items according to the monitoring requirements of each user, and forming a monitoring item list for each user by summarizing the monitoring items.

[0084] Among them, in response to the performance monitoring data needs of different manufacturers, the storage cluster can select the indicator items to be monitored as monitoring items according to the monitoring needs of each user, and then summarize the monitoring items to form a monitoring item list for each user to meet the performance monitoring data needs of different users. The monitoring item lists with different needs are stored in the performance monitoring configuration file, and the monitoring items in the monitoring item list can be periodically traversed in the subsequent period to obtain the corresponding performance monitoring data.

[0085] It is understandable that the setting of the performance monitoring configuration file includes:

[0086] Obtain the access address corresponding to each user, and set the user name for the access address corresponding to each user;

[0087] Monitor and obtain whether the access address corresponding to each user name has the selected indicator item. If so, use the selected indicator item as the monitoring item and set the performance monitoring level for the monitoring item;

[0088] The user name is associated with the monitoring items and the monitoring items are summarized to form a monitoring item list corresponding to the user name.

[0089] User names can be set for access addresses corresponding to different users, and monitoring item lists corresponding to user name partitions can be set. In order to meet the performance monitoring data needs of different users, the storage cluster can select the indicator items to be monitored as monitoring items according to the monitoring needs of each user, and then summarize the monitoring items to form a monitoring item list for each user to meet the performance monitoring data needs of different users, and store the monitoring item lists with different needs in the performance monitoring configuration file.

[0090] In this embodiment, the task script steps of setting up the timed collection of monitoring data include:

[0091] A storage folder is set corresponding to each user's monitoring item list, and a remote server path for storing monitoring data is formed according to the address of the storage folder;

[0092] Set the daily start time and shutdown time of the task script.

[0093] Among them, setting the daily start time and shutdown time of the task script can realize the daily start of the task script. The task script includes a list of database paths corresponding to the monitoring items, a transfer cycle, the last transfer data time, and a remote server path for storing monitoring data. A storage folder is set in the remote server 103 and / or the cloud server 104 corresponding to the monitoring item list of each user to store the corresponding performance monitoring data. The performance monitoring data in the remote server 103 can be cleared regularly, and the cloud server 104 stores historical performance monitoring data for a long time.

[0094] like Figure 4 As shown, in this embodiment, the step of judging whether the transfer time has been reached according to the last transfer data time and the transfer cycle, and triggering the transfer of performance monitoring data if so, and matching the index item performance monitoring data collected by the task script with the monitoring item list includes:

[0095] Step S41, detecting whether the current time is later than the sum of the last data transfer time and the transfer cycle;

[0096] Step S42: If yes, then trigger the transfer of performance monitoring data and obtain the monitoring item list of each user;

[0097] Step S43, obtaining all indicator items collected by the task script, and traversing the indicator items collected by the task script one by one in the monitoring item list of each user to determine whether the monitoring item exists;

[0098] Step S44, in response to the presence of a monitoring item identical to the target indicator item in the monitoring item list, generating a transfer directory according to the monitoring level of the monitoring item and the transfer data time, and exporting the performance monitoring data in the cluster directory;

[0099] Step S45, in response to the absence of a monitoring item identical to the target indicator item in the monitoring item list, traversing the monitoring items in the monitoring item list of the next user to determine whether the target indicator item exists;

[0100] Step S46, in response to the fact that there is no monitoring item identical to the target indicator item in the monitoring item list of all users, obtaining the next indicator item collected by the task script, and traversing the monitoring items in the monitoring item list of each user one by one to determine whether there is the next indicator item;

[0101] Step S47, determine whether all the indicator items collected by the task script are matched and the exported performance monitoring data is uploaded to the cloud server for storage. If so, end; if not, obtain the next indicator item collected by the task script, traverse the monitoring items in each user's monitoring item list one by one to determine whether there is the next indicator item.

[0102] In order to preserve the massive logs generated by the data center for a long time and to quickly query the backup data, historical performance monitoring data is transferred according to different performance items, cluster IP, indicator items, nodes, time and other multi-level directories, and the data is regularly backed up and synchronized to prevent data loss. When transferring data, performance monitoring data from different manufacturers can be saved compatibly.

[0103] Specifically, if Figure 5 As shown in the figure, in the storage cluster, a performance monitoring configuration file perf_save.conf and a script perf_collect.py for periodically collecting monitoring data are required. The configuration file records the collected monitoring items to form a monitoring item list perf_level. The indicator items correspond to the database path indi_path list, the transfer period period_t, the last transfer data time last_t, and the remote server path ip_path for saving monitoring data.

[0104] Among them, i is a different monitoring performance data type, j is the number of database query commands, for example, when i is a cluster, there are multiple vendors' data to be transferred, and each vendor exports data from the database differently, it will traverse the database path indi_path[i], each database export command. len is a built-in function in Python that is used to calculate the number of elements in a sequence or set.

[0105] For data transfer, run the collection performance monitoring script regularly every day.

[0106] (1) Pull the latest configuration file from the remote server path ip_path that stores the monitoring data, update the indicator perf_level monitoring item list, the indicator item corresponding database path indi_path list and the transfer period period_t.

[0107] (2) Detect whether the current time current_t is later than the last update time plus the transfer period, that is, when current_t < last_t + period_t, trigger the transfer of performance monitoring data, start the timed monitoring data collection script perf_collect.py, traverse the list of database paths indi_path corresponding to the metric items at the corresponding positions of the monitoring item indicator, and check whether the database table exists. If it does not exist, it means that the management system does not record the monitoring item indicator and there is no need to transfer. Query the next monitoring item; if it exists, the monitoring item indicator needs to be exported.

[0108] In this embodiment, the step of uploading the performance monitoring data of the metric items matching the monitoring items in the monitoring item list to the cloud server for storage includes:

[0109] Obtain the performance monitoring data of the metric items matching the monitoring items in the monitoring item list for each user, and obtain the remote server path of the storage folder set for the monitoring item list corresponding to each user.

[0110] Obtain the performance monitoring level of the monitoring items in the monitoring item list, and classify and store them in the storage folder corresponding to the remote server path according to the performance monitoring level of the monitoring items.

[0111] For the performance metrics recorded for the cluster, query the monitoring item list perf_level. If it is a cluster-level performance metric, the data storage path is: ip / cluster / last_t - current_t / cluster.csv,

[0112] If the query is for the cluster-node level of the perf_level monitoring item, the data storage path is: ip / node / node_ip / last_t - current_t / node_ip.csv, where node_ip is the ip address after deduplication of the node column recorded in the monitoring item database. For example, in the node.sql table, the data of two nodes ip1 and ip2 are recorded, and the column name of the node is the node column, which will be recorded at the corresponding position of perf_level. The script will first query and generate the node ip, and then save and export the data: ip / node / ip1 / last_t - current_t / ip1.csv, ip / node / ip2 / last_t - current_t / ip2.csv;

[0113] If other more detailed monitoring data is stored, it will be saved according to the above rules. For example, for cluster-level_1-…-level_n data, it will be recorded as: ip / level_1 / .. / level_n / last_t-current_t / level_n.csv, where level_1 indicates different monitoring types and level_n indicates monitoring instances.

[0114] As mentioned above, when the data is transferred, the performance monitoring data is stored in the remote server path IP folder, and the data is classified and saved according to different performance monitoring levels.

[0115] When the data transfer is completed, compress the transferred data IP folder and transfer it to the cloud or a server dedicated to storing monitoring data for decompression and storage.

[0116] When a data center is connected to a new vendor's management platform, it only needs to add the remote server path ip_path, the monitoring item list perf_level, and the indicator item corresponding database path indi_path list configuration content in the remote server that saves the monitoring data to achieve compatibility with performance monitoring data saved by different vendors. You can also update the transfer period period_t to adjust the saving period.

[0117] After the collected monitoring data is uploaded to the server, the management platform implements cross-cluster query by querying the monitoring data collected in the server.

[0118] like Figure 6 As shown, in this embodiment, in response to displaying the monitoring data of the monitoring items of the target cluster, the steps of retrieving the performance monitoring data of the indicator items collected by the target cluster, generating a monitoring chart and displaying the chart include:

[0119] Step S51, querying the remote server, updating the monitoring item list and the cluster network interconnection protocol for which monitoring data has been collected, and returning the cluster network interconnection protocol for which performance monitoring data has been collected to the interface;

[0120] Step S52, according to the cluster network interconnection protocol selected by the user, create a corresponding monitoring chart, according to the collected monitoring data information, the first-level directory under the cluster monitoring data is used as the monitoring object type, the second-level directory is used as a monitoring instance, and one monitoring object type is set to match multiple monitoring items;

[0121] Step S53, the remote server calculates and returns the time period of the backed-up monitoring data according to the performance monitoring level classification storage directory, and provides it to the user for selection;

[0122] Step S54, importing the monitoring data corresponding to the time period selected by the user into the database, querying and obtaining the monitoring indicators in the monitoring data corresponding to the time period selected by the user for the user to query;

[0123] Step S55, based on the monitoring indicators queried by the user, the saved monitoring data is used to generate a monitoring chart and return it to the interface to display the query results.

[0124] In performance monitoring, there are many monitoring items of different granularities, such as cluster, node level, or monitoring of the node's network port, mounting client, node's hard disk, etc. For data of different granularities, the present invention provides a set of query processes. Users can create performance monitoring charts on the management platform. The historical performance monitoring data of any cluster in the data center, the query process is as follows: Figure 7 .

[0125] like Figure 7 As shown, the query process is as follows:

[0126] (1) First, query the remote server, update the monitoring item list perf_level and the cluster IP of the collected monitoring data, and return the cluster IP of the collected performance monitoring data to the interface.

[0127] (2) The user selects the cluster IP and creates the corresponding monitoring chart. Based on the collected information, the first-level directory under the IP is used as the monitoring object type, and the second-level directory to the upper-level directory of / last_t-current_t is used as a monitoring instance. Multiple monitoring items can be selected for one monitoring object type.

[0128] (3) The remote server calculates and returns the data for the backup time period based on the last_t-current_t level directory and provides user selection.

[0129] (4) Import the data saved in the time period selected by the user into the database, and query which monitoring indicators are saved for the user to query. According to the monitoring indicators queried by the user, the saved data is returned to the interface to complete the query display process.

[0130] For cluster monitoring object types, for monitoring items, directly corresponding monitoring indicators, other steps are the same.

[0131] In this embodiment, the historical performance monitoring data management method further includes:

[0132] Export and back up the performance monitoring data corresponding to the monitoring items queried by the user. The storage directory of the exported backup is IP address / monitoring object type / first-level monitoring / second-level monitoring item / time / monitoring item name;

[0133] In response to receiving the metadata of the target monitoring item to be retrieved, creating a metadata monitoring chart, and obtaining the monitoring object type, monitoring item name and time corresponding to the target monitoring item;

[0134] The user obtains the remote path for storing the monitoring data of the monitoring item according to the monitoring object type, monitoring item name and time corresponding to the target monitoring item;

[0135] If the path exists and the sub-path is time, the metadata of the target monitoring item within the time is retrieved and imported into the database and displayed to the user; if the sub-path is not time, all sub-paths are returned to the interface. After the user selects one of the sub-paths, the queried metadata of the target monitoring item is returned to the interface for display.

[0136] In a large data center, it is difficult to quickly select a cluster IP and a monitoring item by conventional searching methods for thousands of storage clusters. In order to quickly select a certain monitoring data, the present invention designs a display module based on metadata import.

[0137] When exporting and backing up performance monitoring, the monitoring item list perf_level has recorded the monitoring object types of each manufacturer, and the directory rule is ip / monitoring object type / level one monitoring / … / level N monitoring item / time / monitoring item.csv. According to the above rules, a metadata retrieval and import is implemented.

[0138] First, the user creates a metadata monitoring chart, in which the IP, monitoring object type, monitoring item, and time must be entered. After it is sent, the IP, monitoring object type, and monitoring item are concatenated to obtain the remote path. If the path exists and the sub-path is time, the data within the user data time is retrieved and imported into the database and displayed to the user; if the sub-path is not time, all sub-paths are returned to the interface. After the user selects one of the sub-paths, the query data is returned to the interface for display.

[0139] Through the above solution, it is possible to achieve long-term storage of the massive logs generated by the data center, be compatible with the storage of performance monitoring data from different manufacturers, support quick query of backup data, display it on the interface, and support long-term storage of historical performance monitoring data.

[0140] The remote server 103 includes a monitoring data backup, import and display module and a metadata import and display module. The embodiment of the method for implementing the historical performance monitoring data backup and import by the remote server 103 is shown as follows.

[0141] 1. Monitoring data backup module

[0142] In the monitoring data backup module, it is assumed that there are two sets of storage management clusters from different manufacturers.

[0143] A ip: 100.100.100.1, nodes: 100.100.100.2, 100.100.100.3, each node has a network card nic1;

[0144] B ip: 100.100.101.1, nodes: 100.100.101.2, 100.100.101.3, each node has two disks disk1 and disk2.

[0145] The configuration file is shown in the table:

[0146] ip_path:100.100.100.100: / var / perf_data

[0147] perf_level:["cluster","cluster-node","cluster-node-nic","cluster-node-disk"]

[0148] indi_path:[

[0149] ["sqlite3 data.db"SELECT*FROM cluster","sqlite3 data2.db"SELECT*FROMcluster"],

[0150] ["sqlite3 data.db"SELECT*FROM node","sqlite3 data2.db"SELECT*FROMnode"],

[0151] ["sqlite3 data.db"SELECT*FROM nic"],

[0152] ["sqlite3 data2.db"SELECT*FROM disk"]]

[0153] last_t:2024-01-0100:00:00

[0154] period_t:7.

[0155] The cluster A management platform records data in the data.db database, and the cluster B management platform records data in data2.db. Cluster A records the monitoring data of the cluster, nodes, and network cards, and B records the cluster, node, and hard disk data.

[0156] The data transfer cycle is 7 days. The data is transferred to the / var / perf_data path of the remote server 100.100.100.100. The cluster records the last transfer time last_t = 2024-01-0100:00:00.

[0157] Clusters A and B run once a day to check whether data transfer is required. When the next transfer time arrives at 2024-01-08 00:00:00, data transfer is triggered.

[0158] Cluster A, for cluster monitoring items, query the data from 2024-01-01 00:00:00 to 2024-01-08 00:00:00 in the cluster table in the data.db library, export and save

[0159] 100.100.100.1 / cluster / 2024-01-01_2024-01-08 / cluster.csv file;

[0160] For node monitoring item data, first query the data in the node table in the data.db library. The perf_level record is cluster-node. You need to query the node column in the node table to check the nodes 100.100.100.2 and 100.100.100.3 in the cluster. Transfer the data of the two nodes respectively.

[0161] 100.100.100.1 / node / 100.100.100.2 / 2024-01-01_2024-01-08 / node.csv

[0162] 100.100.100.1 / node / 100.100.100.3 / 2024-01-01_2024-01-08 / node.csv

[0163] For the network card data, the node column of the transfer query has two nodes, one for each network card, and the data is saved as:

[0164] 100.100.100.1 / nic / 100.100.100.2 / nic1 / 2024-01-01_2024-01-08 / nic.csv100.100.100.1 / nic / 100.100.100.3 / nic1 / 2024-01-01_2024-01-08 / nic.csv

[0165] For hard disk data, it is detected that cluster A does not have the data2.db database, indicating that the A management platform does not collect hard disk indicators, so there is no need to transfer the hard disk data.

[0166] Complete the transfer of cluster A performance data, upload all data in the "100.100.100.1 / " directory to / var / perf_data on 100.100.100.100, and change the local transfer time to: last_t = 2024-01-08

[0167] 00:00:00, waiting for next transfer.

[0168] The data transfer of cluster B is similar to that of cluster A, with the following differences: when querying cluster B, there is no data.db database. When transferring cluster and node data, the second SQL of indi_path will be used to query the data2.db database data. The network port monitoring items will not be transferred, but the network port monitoring object types will be transferred.

[0169] 2. Import the display module

[0170] View historical performance data, taking the example of a user viewing cluster A, data from 2024-01-05 to 2024-01-10, and three monitoring object types: cluster, node, and hard disk.

[0171] When the user needs to query the performance monitoring data of cluster A from 2024-01-05 to 2024-01-10.

[0172] (1) Create a monitoring chart for cluster A node on the management platform interface, obtain the structure under the 100.100.100.1 directory, and query the monitoring object types based on the 100.100.100.1 directory structure: cluster, node, and nic.

[0173] (2) If you select cluster monitoring object type,

[0174] 100.100.100.1 / cluster / 2024-01-01_2024-01-08 / cluster.csv,

[0175] 100.100.100.1 / cluster / 2024-01-08_2024-01-15 / cluster.csv, exports the data to the database, and returns the monitoring indicators recorded in the database, such as IOPS, cluster bandwidth, etc., on the interface for users to query.

[0176] (3) If the node monitoring object type is selected, according to the two node data 100.100.100.2 and 100.100.100.3 in the "100.100.100.1 / cluster" directory, the user selects which node is needed, that is, selects the indicator item. After selection, the node.csv data is imported for query. The interface returns the monitoring indicators, such as IOPS and node bandwidth, for the user to query.

[0177] (4) If you select the nic monitoring object type, according to the "100.100.100.1 / nic" directory, select the indicator items as 100.100.100.2-nic1, 100.100.100.3-nic. After the user selects, import nic.csv. After selecting, import the node.csv data for query. The interface returns monitoring indicators such as IOPS and network port bandwidth for users to query.

[0178] 3. Metadata import and display module

[0179] The metadata import demonstration takes the creation of cluster A nodes and cluster B network cards as an example:

[0180] Cluster A node: Create a metadata retrieval monitoring chart, enter the query ip:100.100.100.1, node:100.100.100.2, time 2024-01-01_2024-01-08, monitoring item node, splice the directory to the remote server and find that the 100.100.100.1 / 100.100.100.2 subdirectory is time, then

[0181] 100.100.100.1 / node / 100.100.100.2 / 2024-01-01_2024-01-08, the node.csv data in the directory is imported and displayed in the interface.

[0182] Cluster B network card: Create a metadata retrieval monitoring chart, enter the query ip:100.100.101.1, time 2024-01-01_2024-01-10, monitoring item nic, at this time the user enters the metadata item without node value to query the ip100.100.101.1 / nic directory. Before the time, there are two directories at the same level, 100.100.101.2 and 100.100.101.3. After returning to the interface, the user selects 100.100.101.2.

[0183] 100.100.101.1 / nic / 100.100.101.2 / 2024-01-01_2024-01-08 / nic.csv,

[0184] The data at 100.100.101.1 / nic / 100.100.101.2 / 2024-01-08_2024-01-15 / nic.csv is imported into the database, and the data at 2024-01-01_2024-01-10 is returned to the front-end interface.

[0185] This enables long-term storage of the massive logs generated by the data center, and is compatible with different vendor platforms, allowing for unified backup query and interface display of monitoring different data.

[0186] This application supports the long-term preservation of historical performance monitoring and implements a method for long-term preservation of performance monitoring data. It is compatible with data preservation of storage management platforms of different manufacturers and saves performance data of different platforms. It implements a method for querying massive performance monitoring data. The management platform can query performance monitoring data of different clusters and is compatible with data queries of different granularities. It proposes a metadata retrieval method that can quickly query the saved performance monitoring data.

[0187] In the above-mentioned historical performance monitoring data management method, a performance monitoring configuration file is set to set indicator items as monitoring items, and the monitoring items are summarized to form a monitoring item list. Different monitoring item lists are selectively set for different users to differentiate the performance monitoring data of different manufacturers. In addition, a task script for collecting monitoring data at regular intervals is set to periodically traverse the monitoring items in the monitoring item list to obtain the corresponding performance monitoring data, and the indicator item performance monitoring data that matches the monitoring items in the monitoring item list is uploaded to the cloud server for storage, supporting long-term storage of historical performance monitoring data, and supporting fast query of backup performance monitoring data across clusters and displaying it on the interface.

[0188] It should be understood that although Figure 2-Figure 7 The steps in the flowchart are shown in sequence as indicated by the arrows, but these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified in this document, there is no strict order restriction for the execution of these steps, and these steps can be executed in other orders. Moreover, Figure 2-Figure 7 At least part of the steps may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily executed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be executed in turn or alternately with other steps or at least part of the sub-steps or stages of other steps.

[0189] In one embodiment, Figure 8 As shown, a historical performance monitoring data management device 10 is provided, including: a performance monitoring configuration file setting module 1, a task script setting module 2, a monitoring information update module 3, a monitoring data backup module 4, and an import display module 5.

[0190] The performance monitoring configuration file setting module 1 is used to set a performance monitoring configuration file, to set indicator items as monitoring items, and to aggregate the monitoring items to form a monitoring item list.

[0191] The task script setting module 2 is used to set a task script for periodically collecting monitoring data, and the task script includes a list of database paths corresponding to monitoring items, a transfer cycle, a last data transfer time, and a remote server path for storing monitoring data.

[0192] The monitoring information updating module 3 is used for obtaining the latest performance monitoring configuration file from the remote server path storing the monitoring data in response to starting the task script, and updating the monitoring item list and the database path list corresponding to the indicator item.

[0193] The monitoring data backup module 4 is used to determine whether the transfer time has arrived based on the last data transfer time and the transfer cycle. If so, it triggers the performance monitoring data transfer, matches the indicator performance monitoring data collected by the task script with the monitoring item list, and uploads the indicator performance monitoring data that matches the monitoring items in the monitoring item list to the cloud server for storage.

[0194] The import and display module 5 is used to retrieve the index item performance monitoring data collected by the target cluster, generate and display a monitoring chart in response to displaying the monitoring data of the monitoring items of the target cluster.

[0195] In this embodiment, the step of setting a performance monitoring configuration file for setting indicator items as monitoring items and aggregating the monitoring items to form a monitoring item list includes:

[0196] Get performance monitoring indicators for a single storage cluster;

[0197] According to the monitoring requirements of each user, the indicator items to be monitored are selected as monitoring items, and a monitoring item list for each user is formed by summarizing the monitoring items.

[0198] In this embodiment, the task script steps of setting up the timed collection of monitoring data include:

[0199] A storage folder is set corresponding to each user's monitoring item list, and a remote server path for storing monitoring data is formed according to the address of the storage folder;

[0200] Set the daily start time and shutdown time of the task script.

[0201] In this embodiment, the step of determining whether the transfer time has been reached according to the last transfer data time and the transfer cycle, and triggering the transfer of performance monitoring data if so, and matching the indicator item performance monitoring data collected by the task script with the monitoring item list includes:

[0202] Detecting whether the current time is later than the sum of the last data transfer time and the transfer period;

[0203] If yes, the performance monitoring data will be transferred and the list of monitoring items for each user will be obtained;

[0204] Obtain all indicator items collected by the task script, and traverse the indicator items collected by the task script one by one in the monitoring item list of each user to determine whether the monitoring item exists;

[0205] In response to the presence of a monitoring item identical to the target indicator item in the monitoring item list, generating a transfer directory according to the monitoring level of the monitoring item and the transfer data time, and exporting the performance monitoring data in the cluster directory;

[0206] In response to the absence of a monitoring item identical to the target indicator item in the monitoring item list, traversing monitoring items in the monitoring item list of the next user to determine whether the target indicator item exists;

[0207] In response to the absence of a monitoring item identical to the target indicator item in the monitoring item lists of all users, obtaining the next indicator item collected by the task script, and traversing the monitoring items in the monitoring item lists of each user one by one to determine whether there is the next indicator item;

[0208] Determine whether all indicator items collected by the task script are matched and the exported performance monitoring data is uploaded to the cloud server for storage. If so, end the process. If not, obtain the next indicator item collected by the task script, and traverse the monitoring items in each user's monitoring item list one by one to determine whether there is the next indicator item.

[0209] In this embodiment, the step of uploading the indicator item performance monitoring data matching the monitoring item in the monitoring item list to the cloud server for storage includes:

[0210] Obtaining the indicator item performance monitoring data that matches the monitoring items in the monitoring item list of each user, and obtaining the remote server path of the storage folder corresponding to each user's monitoring item list setting;

[0211] The performance monitoring level of the monitoring item in the monitoring item list is obtained, and the monitoring items are classified and stored in the storage folder corresponding to the remote server path according to the performance monitoring level of the monitoring items.

[0212] In this embodiment, in response to displaying monitoring data of monitoring items of the target cluster, the steps of retrieving the performance monitoring data of the indicator items collected by the target cluster, generating a monitoring chart and displaying the chart include:

[0213] Query the remote server, update the monitoring item list and the cluster network interconnection protocol for which monitoring data has been collected, and return the cluster network interconnection protocol for which performance monitoring data has been collected to the interface;

[0214] Create corresponding monitoring charts based on the cluster network interconnection protocol selected by the user. Based on the collected monitoring data information, use the first-level directory under the cluster monitoring data as the monitoring object type and the second-level directory as a monitoring instance. Set a monitoring object type to match multiple monitoring items.

[0215] The remote server calculates and returns the time period of the backed-up monitoring data according to the performance monitoring level classification storage directory, and provides the user with selection;

[0216] Import the monitoring data corresponding to the time period selected by the user into the database, query and obtain the monitoring indicators in the monitoring data corresponding to the time period selected by the user for the user to query;

[0217] According to the monitoring indicators queried by the user, the saved monitoring data is generated into a monitoring chart and returned to the interface to display the query results.

[0218] In this embodiment, if Figure 8 As shown, the historical performance monitoring data management device 10 also includes a metadata import and display module 6 .

[0219] The metadata import and display module 6 is used to: export and back up the performance monitoring data corresponding to the monitoring item queried by the user, and the storage directory of the exported backup is IP address / monitoring object type / first-level monitoring / second-level monitoring item / time / monitoring item name; in response to receiving the metadata of the retrieved target monitoring item, create a metadata monitoring chart to obtain the monitoring object type, monitoring item name and time corresponding to the target monitoring item; the user obtains the remote path for storing the monitoring data of the monitoring item according to the monitoring object type, monitoring item name and time corresponding to the target monitoring item; if the path exists and the sub-path is time, the metadata of the target monitoring item within the time is retrieved and imported into the database, and displayed to the user; if the sub-path is not time, all sub-paths are returned to the interface, and after the user selects one of the sub-paths, the queried target monitoring item metadata is returned to the interface for display.

[0220] In the above-mentioned historical performance monitoring data management device, a performance monitoring configuration file is set to set indicator items as monitoring items, and the monitoring items are summarized to form a monitoring item list. Different monitoring item lists are selectively set for different users to differentiate the performance monitoring data of different manufacturers. In addition, a task script for collecting monitoring data at a regular time is set to periodically traverse the monitoring items in the monitoring item list to obtain the corresponding performance monitoring data, and the indicator item performance monitoring data that matches the monitoring items in the monitoring item list is uploaded to the cloud server for storage, supporting long-term storage of historical performance monitoring data, and supporting fast query of backup performance monitoring data across clusters and displaying it on the interface.

[0221] For the specific limitations of the historical performance monitoring data management device, please refer to the limitations of the historical performance monitoring data management method above, which will not be repeated here. Each module in the above-mentioned historical performance monitoring data management device can be implemented in whole or in part by software, hardware and a combination thereof. The above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules.

[0222] In one embodiment, a computer program product is provided, comprising a computer program, which, when executed by a processor, implements the following steps:

[0223] Set a performance monitoring configuration file for setting indicator items as monitoring items, and summarize the monitoring items to form a monitoring item list;

[0224] Set a task script for collecting monitoring data at regular intervals, wherein the task script includes a list of database paths corresponding to monitoring items, a transfer cycle, a last transfer time, and a remote server path for storing monitoring data;

[0225] In response to starting the task script, obtaining the latest performance monitoring configuration file from the remote server path storing the monitoring data, and updating the monitoring item list and the database path list corresponding to the indicator item;

[0226] Determine whether the transfer time has arrived according to the last transfer data time and the transfer cycle, and if so, trigger the transfer of performance monitoring data, match the indicator performance monitoring data collected by the task script with the monitoring item list, and upload the indicator performance monitoring data that matches the monitoring items in the monitoring item list to the cloud server for storage;

[0227] In response to displaying monitoring data of monitoring items of a target cluster, the performance monitoring data of the indicator items collected by the target cluster is retrieved, and a monitoring chart is generated and displayed.

[0228] In one embodiment, the computer program further implements the following steps when executed by a processor:

[0229] The step of setting a performance monitoring configuration file for setting indicator items as monitoring items and aggregating the monitoring items to form a monitoring item list includes:

[0230] Get performance monitoring indicators for a single storage cluster;

[0231] According to the monitoring requirements of each user, the indicator items to be monitored are selected as monitoring items, and a monitoring item list for each user is formed by summarizing the monitoring items.

[0232] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0233] The task script steps for setting up the timed collection of monitoring data include:

[0234] A storage folder is set corresponding to each user's monitoring item list, and a remote server path for storing monitoring data is formed according to the address of the storage folder;

[0235] Set the daily start time and shutdown time of the task script.

[0236] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0237] The step of judging whether the transfer time has been reached according to the last transfer data time and the transfer cycle, triggering the transfer of performance monitoring data if so, and matching the index item performance monitoring data collected by the task script with the monitoring item list comprises:

[0238] Detecting whether the current time is later than the sum of the last data transfer time and the transfer period;

[0239] If yes, the performance monitoring data will be transferred and the list of monitoring items for each user will be obtained;

[0240] Obtain all indicator items collected by the task script, and traverse the indicator items collected by the task script one by one in the monitoring item list of each user to determine whether the monitoring item exists;

[0241] In response to the presence of a monitoring item identical to the target indicator item in the monitoring item list, generating a transfer directory according to the monitoring level of the monitoring item and the transfer data time, and exporting the performance monitoring data in the cluster directory;

[0242] In response to the absence of a monitoring item identical to the target indicator item in the monitoring item list, traversing monitoring items in the monitoring item list of the next user to determine whether the target indicator item exists;

[0243] In response to the absence of a monitoring item identical to the target indicator item in the monitoring item lists of all users, obtaining the next indicator item collected by the task script, and traversing the monitoring items in the monitoring item lists of each user one by one to determine whether there is the next indicator item;

[0244] Determine whether all indicator items collected by the task script are matched and the exported performance monitoring data is uploaded to the cloud server for storage. If so, end the process. If not, obtain the next indicator item collected by the task script, and traverse the monitoring items in each user's monitoring item list one by one to determine whether there is the next indicator item.

[0245] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0246] The step of uploading the indicator item performance monitoring data matching the monitoring items in the monitoring item list to the cloud server for storage includes:

[0247] Obtaining the indicator item performance monitoring data that matches the monitoring items in the monitoring item list of each user, and obtaining the remote server path of the storage folder corresponding to each user's monitoring item list setting;

[0248] The performance monitoring level of the monitoring item in the monitoring item list is obtained, and the monitoring items are classified and stored in the storage folder corresponding to the remote server path according to the performance monitoring level of the monitoring items.

[0249] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0250] In response to displaying the monitoring data of the monitoring items of the target cluster, the steps of retrieving the performance monitoring data of the indicator items collected by the target cluster, generating a monitoring chart and displaying the chart include:

[0251] Query the remote server, update the monitoring item list and the cluster network interconnection protocol for which monitoring data has been collected, and return the cluster network interconnection protocol for which performance monitoring data has been collected to the interface;

[0252] Create corresponding monitoring charts based on the cluster network interconnection protocol selected by the user. Based on the collected monitoring data information, use the first-level directory under the cluster monitoring data as the monitoring object type and the second-level directory as a monitoring instance. Set a monitoring object type to match multiple monitoring items.

[0253] The remote server calculates and returns the time period of the backed-up monitoring data according to the performance monitoring level classification storage directory, and provides the user with selection;

[0254] Import the monitoring data corresponding to the time period selected by the user into the database, query and obtain the monitoring indicators in the monitoring data corresponding to the time period selected by the user for the user to query;

[0255] According to the monitoring indicators queried by the user, the saved monitoring data is generated into a monitoring chart and returned to the interface to display the query results.

[0256] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0257] Export and back up the performance monitoring data corresponding to the monitoring items queried by the user. The storage directory of the exported backup is IP address / monitoring object type / first-level monitoring / second-level monitoring item / time / monitoring item name;

[0258] In response to receiving the metadata of the target monitoring item to be retrieved, creating a metadata monitoring chart, and obtaining the monitoring object type, monitoring item name and time corresponding to the target monitoring item;

[0259] The user obtains the remote path for storing the monitoring data of the monitoring item according to the monitoring object type, monitoring item name and time corresponding to the target monitoring item;

[0260] If the path exists and the sub-path is time, the metadata of the target monitoring item within the time is retrieved and imported into the database and displayed to the user; if the sub-path is not time, all sub-paths are returned to the interface. After the user selects one of the sub-paths, the queried metadata of the target monitoring item is returned to the interface for display.

[0261] For specific limitations on the steps implemented when the computer program is executed by the processor, please refer to the limitations on the method for managing historical performance monitoring data above, which will not be repeated here.

[0262] In one embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as follows: Fig. 9 As shown. The computer device includes a processor, a memory, a network interface and a database connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store historical performance monitoring data management data. The network interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a historical performance monitoring data management method is implemented.

[0263] Those skilled in the art will understand that Fig. 9The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0264] In one embodiment, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the following steps when executing the computer program:

[0265] Set a performance monitoring configuration file for setting indicator items as monitoring items, and summarize the monitoring items to form a monitoring item list;

[0266] Set a task script for collecting monitoring data at regular intervals, wherein the task script includes a list of database paths corresponding to monitoring items, a transfer cycle, a last transfer time, and a remote server path for storing monitoring data;

[0267] In response to starting the task script, obtaining the latest performance monitoring configuration file from the remote server path storing the monitoring data, and updating the monitoring item list and the database path list corresponding to the indicator item;

[0268] Determine whether the transfer time has arrived according to the last transfer data time and the transfer cycle, and if so, trigger the transfer of performance monitoring data, match the indicator performance monitoring data collected by the task script with the monitoring item list, and upload the indicator performance monitoring data that matches the monitoring items in the monitoring item list to the cloud server for storage;

[0269] In response to displaying monitoring data of monitoring items of a target cluster, the performance monitoring data of the indicator items collected by the target cluster is retrieved, and a monitoring chart is generated and displayed.

[0270] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0271] The step of setting a performance monitoring configuration file for setting indicator items as monitoring items and aggregating the monitoring items to form a monitoring item list includes:

[0272] Get performance monitoring indicators for a single storage cluster;

[0273] According to the monitoring requirements of each user, the indicator items to be monitored are selected as monitoring items, and a monitoring item list for each user is formed by summarizing the monitoring items.

[0274] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0275] The task script steps for setting up the timed collection of monitoring data include:

[0276] A storage folder is set corresponding to each user's monitoring item list, and a remote server path for storing monitoring data is formed according to the address of the storage folder;

[0277] Set the daily start time and shutdown time of the task script.

[0278] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0279] The step of judging whether the transfer time has been reached according to the last transfer data time and the transfer cycle, triggering the transfer of performance monitoring data if so, and matching the index item performance monitoring data collected by the task script with the monitoring item list comprises:

[0280] Detecting whether the current time is later than the sum of the last data transfer time and the transfer period;

[0281] If yes, the performance monitoring data will be transferred and the list of monitoring items for each user will be obtained;

[0282] Obtain all indicator items collected by the task script, and traverse the indicator items collected by the task script one by one in the monitoring item list of each user to determine whether the monitoring item exists;

[0283] In response to the presence of a monitoring item identical to the target indicator item in the monitoring item list, generating a transfer directory according to the monitoring level of the monitoring item and the transfer data time, and exporting the performance monitoring data in the cluster directory;

[0284] In response to the absence of a monitoring item identical to the target indicator item in the monitoring item list, traversing monitoring items in the monitoring item list of the next user to determine whether the target indicator item exists;

[0285] In response to the absence of a monitoring item identical to the target indicator item in the monitoring item lists of all users, obtaining the next indicator item collected by the task script, and traversing the monitoring items in the monitoring item lists of each user one by one to determine whether there is the next indicator item;

[0286] Determine whether all indicator items collected by the task script are matched and the exported performance monitoring data is uploaded to the cloud server for storage. If so, end the process. If not, obtain the next indicator item collected by the task script, and traverse the monitoring items in each user's monitoring item list one by one to determine whether there is the next indicator item.

[0287] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0288] The step of uploading the indicator item performance monitoring data matching the monitoring items in the monitoring item list to the cloud server for storage includes:

[0289] Obtaining the indicator item performance monitoring data that matches the monitoring items in the monitoring item list of each user, and obtaining the remote server path of the storage folder corresponding to each user's monitoring item list setting;

[0290] The performance monitoring level of the monitoring item in the monitoring item list is obtained, and the monitoring items are classified and stored in the storage folder corresponding to the remote server path according to the performance monitoring level of the monitoring items.

[0291] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0292] In response to displaying the monitoring data of the monitoring items of the target cluster, the steps of retrieving the performance monitoring data of the indicator items collected by the target cluster, generating a monitoring chart and displaying the chart include:

[0293] Query the remote server, update the monitoring item list and the cluster network interconnection protocol for which monitoring data has been collected, and return the cluster network interconnection protocol for which performance monitoring data has been collected to the interface;

[0294] Create corresponding monitoring charts based on the cluster network interconnection protocol selected by the user. Based on the collected monitoring data information, use the first-level directory under the cluster monitoring data as the monitoring object type and the second-level directory as a monitoring instance. Set a monitoring object type to match multiple monitoring items.

[0295] The remote server calculates and returns the time period of the backed-up monitoring data according to the performance monitoring level classification storage directory, and provides the user with selection;

[0296] Import the monitoring data corresponding to the time period selected by the user into the database, query and obtain the monitoring indicators in the monitoring data corresponding to the time period selected by the user for the user to query;

[0297] According to the monitoring indicators queried by the user, the saved monitoring data is generated into a monitoring chart and returned to the interface to display the query results.

[0298] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0299] Export and back up the performance monitoring data corresponding to the monitoring items queried by the user. The storage directory of the exported backup is IP address / monitoring object type / first-level monitoring / second-level monitoring item / time / monitoring item name;

[0300] In response to receiving the metadata of the target monitoring item to be retrieved, creating a metadata monitoring chart, and obtaining the monitoring object type, monitoring item name and time corresponding to the target monitoring item;

[0301] The user obtains the remote path for storing the monitoring data of the monitoring item according to the monitoring object type, monitoring item name and time corresponding to the target monitoring item;

[0302] If the path exists and the sub-path is time, the metadata of the target monitoring item within the time is retrieved and imported into the database and displayed to the user; if the sub-path is not time, all sub-paths are returned to the interface. After the user selects one of the sub-paths, the queried metadata of the target monitoring item is returned to the interface for display.

[0303] For specific limitations on the steps implemented when the processor executes a computer program, please refer to the limitations on the method for managing historical performance monitoring data in the above text, which will not be repeated here.

[0304] In one embodiment, a computer readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:

[0305] Set a performance monitoring configuration file for setting indicator items as monitoring items, and summarize the monitoring items to form a monitoring item list;

[0306] Set a task script for collecting monitoring data at regular intervals, wherein the task script includes a list of database paths corresponding to monitoring items, a transfer cycle, a last transfer time, and a remote server path for storing monitoring data;

[0307] In response to starting the task script, obtaining the latest performance monitoring configuration file from the remote server path storing the monitoring data, and updating the monitoring item list and the database path list corresponding to the indicator item;

[0308] Determine whether the transfer time has arrived according to the last transfer data time and the transfer cycle, and if so, trigger the transfer of performance monitoring data, match the indicator performance monitoring data collected by the task script with the monitoring item list, and upload the indicator performance monitoring data that matches the monitoring items in the monitoring item list to the cloud server for storage;

[0309] In response to displaying monitoring data of monitoring items of a target cluster, the performance monitoring data of the indicator items collected by the target cluster is retrieved, and a monitoring chart is generated and displayed.

[0310] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0311] The step of setting a performance monitoring configuration file for setting indicator items as monitoring items and aggregating the monitoring items to form a monitoring item list includes:

[0312] Get performance monitoring indicators for a single storage cluster;

[0313] According to the monitoring requirements of each user, the indicator items to be monitored are selected as monitoring items, and a monitoring item list for each user is formed by summarizing the monitoring items.

[0314] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0315] The task script steps for setting up the timed collection of monitoring data include:

[0316] A storage folder is set corresponding to each user's monitoring item list, and a remote server path for storing monitoring data is formed according to the address of the storage folder;

[0317] Set the daily start time and shutdown time of the task script.

[0318] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0319] The step of judging whether the transfer time has been reached according to the last transfer data time and the transfer cycle, triggering the transfer of performance monitoring data if so, and matching the index item performance monitoring data collected by the task script with the monitoring item list comprises:

[0320] Detecting whether the current time is later than the sum of the last data transfer time and the transfer period;

[0321] If yes, the performance monitoring data will be transferred and the list of monitoring items for each user will be obtained;

[0322] Obtain all indicator items collected by the task script, and traverse the indicator items collected by the task script one by one in the monitoring item list of each user to determine whether the monitoring item exists;

[0323] In response to the presence of a monitoring item identical to the target indicator item in the monitoring item list, generating a transfer directory according to the monitoring level of the monitoring item and the transfer data time, and exporting the performance monitoring data in the cluster directory;

[0324] In response to the absence of a monitoring item identical to the target indicator item in the monitoring item list, traversing monitoring items in the monitoring item list of the next user to determine whether the target indicator item exists;

[0325] In response to the absence of a monitoring item identical to the target indicator item in the monitoring item lists of all users, obtaining the next indicator item collected by the task script, and traversing the monitoring items in the monitoring item lists of each user one by one to determine whether there is the next indicator item;

[0326] Determine whether all indicator items collected by the task script are matched and the exported performance monitoring data is uploaded to the cloud server for storage. If so, end the process. If not, obtain the next indicator item collected by the task script, and traverse the monitoring items in each user's monitoring item list one by one to determine whether there is the next indicator item.

[0327] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0328] The step of uploading the indicator item performance monitoring data matching the monitoring items in the monitoring item list to the cloud server for storage includes:

[0329] Obtaining the indicator item performance monitoring data that matches the monitoring items in the monitoring item list of each user, and obtaining the remote server path of the storage folder corresponding to each user's monitoring item list setting;

[0330] The performance monitoring level of the monitoring item in the monitoring item list is obtained, and the monitoring items are classified and stored in the storage folder corresponding to the remote server path according to the performance monitoring level of the monitoring items.

[0331] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0332] In response to displaying the monitoring data of the monitoring items of the target cluster, the steps of retrieving the performance monitoring data of the indicator items collected by the target cluster, generating a monitoring chart and displaying the chart include:

[0333] Query the remote server, update the monitoring item list and the cluster network interconnection protocol for which monitoring data has been collected, and return the cluster network interconnection protocol for which performance monitoring data has been collected to the interface;

[0334] Create corresponding monitoring charts based on the cluster network interconnection protocol selected by the user. Based on the collected monitoring data information, use the first-level directory under the cluster monitoring data as the monitoring object type and the second-level directory as a monitoring instance. Set a monitoring object type to match multiple monitoring items.

[0335] The remote server calculates and returns the time period of the backed-up monitoring data according to the performance monitoring level classification storage directory, and provides the user with selection;

[0336] Import the monitoring data corresponding to the time period selected by the user into the database, query and obtain the monitoring indicators in the monitoring data corresponding to the time period selected by the user for the user to query;

[0337] According to the monitoring indicators queried by the user, the saved monitoring data is generated into a monitoring chart and returned to the interface to display the query results.

[0338] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0339] Export and back up the performance monitoring data corresponding to the monitoring items queried by the user. The storage directory of the exported backup is IP address / monitoring object type / first-level monitoring / second-level monitoring item / time / monitoring item name;

[0340] In response to receiving the metadata of the target monitoring item to be retrieved, creating a metadata monitoring chart, and obtaining the monitoring object type, monitoring item name and time corresponding to the target monitoring item;

[0341] The user obtains the remote path for storing the monitoring data of the monitoring item according to the monitoring object type, monitoring item name and time corresponding to the target monitoring item;

[0342] If the path exists and the sub-path is time, the metadata of the target monitoring item within the time is retrieved and imported into the database and displayed to the user; if the sub-path is not time, all sub-paths are returned to the interface. After the user selects one of the sub-paths, the queried metadata of the target monitoring item is returned to the interface for display.

[0343] For specific limitations on the steps implemented when the computer program is executed by the processor, please refer to the limitations on the method for managing historical performance monitoring data above, which will not be repeated here.

[0344] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

[0345] The technical features of the above embodiments may be arbitrarily combined. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0346] The above-mentioned embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the invention patent. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the patent of the present application shall be subject to the attached claims.

Claims

1. A method for managing historical performance monitoring data, characterized in that: include: Set a performance monitoring configuration file for setting indicator items as monitoring items, and summarize the monitoring items to form a monitoring item list; Set a task script for collecting monitoring data at regular intervals, wherein the task script includes a list of database paths corresponding to monitoring items, a transfer cycle, a last transfer time, and a remote server path for storing monitoring data; In response to starting the task script, obtaining the latest performance monitoring configuration file from the remote server path storing the monitoring data, and updating the monitoring item list and the database path list corresponding to the indicator item; Determine whether the transfer time has arrived according to the last transfer data time and the transfer cycle, and if so, trigger the transfer of performance monitoring data, match the indicator performance monitoring data collected by the task script with the monitoring item list, and upload the indicator performance monitoring data that matches the monitoring items in the monitoring item list to the cloud server for storage; In response to displaying monitoring data of monitoring items of a target cluster, the performance monitoring data of the indicator items collected by the target cluster is retrieved, and a monitoring chart is generated and displayed.

2. The historical performance monitoring data management method according to claim 1, characterized in that: The step of setting a performance monitoring configuration file for setting indicator items as monitoring items and aggregating the monitoring items to form a monitoring item list includes: Get performance monitoring indicators for a single storage cluster; According to the monitoring requirements of each user, the indicator items to be monitored are selected as monitoring items, and a monitoring item list for each user is formed by summarizing the monitoring items.

3. The historical performance monitoring data management method according to claim 2, characterized in that: The task script steps for setting up the timed collection of monitoring data include: A storage folder is set corresponding to each user's monitoring item list, and a remote server path for storing monitoring data is formed according to the address of the storage folder; Set the daily start time and shutdown time of the task script.

4. The historical performance monitoring data management method according to claim 1, characterized in that: The step of judging whether the transfer time has been reached according to the last transfer data time and the transfer cycle, triggering the transfer of performance monitoring data if so, and matching the index item performance monitoring data collected by the task script with the monitoring item list comprises: Detecting whether the current time is later than the sum of the last data transfer time and the transfer cycle; If yes, the performance monitoring data will be transferred and the list of monitoring items for each user will be obtained; Obtain all indicator items collected by the task script, and traverse the indicator items collected by the task script one by one in the monitoring item list of each user to determine whether the monitoring item exists; In response to the presence of a monitoring item identical to the target indicator item in the monitoring item list, generating a transfer directory according to the monitoring level of the monitoring item and the transfer data time, and exporting the performance monitoring data in the cluster directory; In response to the absence of a monitoring item identical to the target indicator item in the monitoring item list, traversing monitoring items in the monitoring item list of the next user to determine whether the target indicator item exists; In response to the absence of a monitoring item identical to the target indicator item in the monitoring item lists of all users, obtaining the next indicator item collected by the task script, and traversing the monitoring items in the monitoring item lists of each user one by one to determine whether there is the next indicator item; Determine whether all indicator items collected by the task script are matched and the exported performance monitoring data is uploaded to the cloud server for storage. If so, end the process. If not, obtain the next indicator item collected by the task script, and traverse the monitoring items in each user's monitoring item list one by one to determine whether there is the next indicator item.

5. The historical performance monitoring data management method according to claim 3 is characterized in that: The step of uploading the indicator item performance monitoring data matching the monitoring items in the monitoring item list to the cloud server for storage includes: Obtaining the indicator item performance monitoring data that matches the monitoring items in the monitoring item list of each user, and obtaining the remote server path of the storage folder corresponding to each user's monitoring item list setting; The performance monitoring level of the monitoring item in the monitoring item list is obtained, and the monitoring items are classified and stored in the storage folder corresponding to the remote server path according to the performance monitoring level of the monitoring items.

6. The historical performance monitoring data management method according to claim 1, characterized in that: In response to displaying the monitoring data of the monitoring items of the target cluster, the steps of retrieving the performance monitoring data of the indicator items collected by the target cluster, generating a monitoring chart and displaying the chart include: Query the remote server, update the monitoring item list and the cluster network interconnection protocol for which monitoring data has been collected, and return the cluster network interconnection protocol for which performance monitoring data has been collected to the interface; Create corresponding monitoring charts based on the cluster network interconnection protocol selected by the user. Based on the collected monitoring data information, use the first-level directory under the cluster monitoring data as the monitoring object type and the second-level directory as a monitoring instance. Set a monitoring object type to match multiple monitoring items. The remote server calculates and returns the time period of the backed-up monitoring data according to the performance monitoring level classification storage directory, and provides the user with selection; Import the monitoring data corresponding to the time period selected by the user into the database, query and obtain the monitoring items in the monitoring data corresponding to the time period selected by the user for the user to query; According to the monitoring items queried by the user, the saved monitoring data is generated into a monitoring chart and returned to the interface to display the query results.

7. The historical performance monitoring data management method according to claim 5, characterized in that: The method further comprises: Export and back up the performance monitoring data corresponding to the monitoring items queried by the user. The storage directory for the exported backup is IP address / monitoring object type / first-level monitoring / second-level monitoring items / time / monitoring item name; In response to receiving the metadata of the target monitoring item to be retrieved, creating a metadata monitoring chart, obtaining the monitoring object type, monitoring item name and time corresponding to the target monitoring item; The user obtains the remote path for storing the monitoring data of the monitoring item according to the monitoring object type, monitoring item name and time corresponding to the target monitoring item; If the path exists and the sub-path is time, the metadata of the target monitoring item within the time is retrieved and imported into the database and displayed to the user; if the sub-path is not time, all sub-paths are returned to the interface. After the user selects one of the sub-paths, the queried metadata of the target monitoring item is returned to the interface for display.

8. A historical performance monitoring data management device, characterized in that: The device comprises: Setting a performance monitoring profile module, used to set a performance monitoring profile, used to set indicator items as monitoring items, and aggregate the monitoring items to form a monitoring item list; Setting a task script module, used to set a task script for regularly collecting monitoring data, wherein the task script includes a list of database paths corresponding to monitoring items, a transfer cycle, a last transfer time, and a remote server path for storing monitoring data; A monitoring information updating module, for, in response to starting the task script, obtaining the latest performance monitoring configuration file from the remote server path storing the monitoring data, and updating the monitoring item list and the database path list corresponding to the indicator item; A monitoring data backup module is used to determine whether the transfer time has arrived according to the last data transfer time and the transfer cycle, and if so, trigger the transfer of performance monitoring data, match the index item performance monitoring data collected by the task script with the monitoring item list, and upload the index item performance monitoring data that matches the monitoring item in the monitoring item list to the cloud server for storage; The import display module is used to retrieve the index item performance monitoring data collected by the target cluster in response to the display of the monitoring data of the monitoring items of the target cluster, generate a monitoring chart and display it.

9. A computer device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

Images