IDC machine room equipment data management method and device, medium and electronic equipment

Abstract

The invention provides an equipment data management method and device for an IDC machine room, a medium and electronic equipment, and the method comprises the steps: returning mapping configuration data to a target collection plug-in according to a mapping configuration obtaining request from the target collection plug-in, the mapping configuration data comprises an original index of a target data source corresponding to the target collection plug-in and a mapping relation between the original index and a target index; and according to a connection parameter acquisition request from the target acquisition plug-in, returning a connection parameter of a target data source to the target acquisition plug-in, so that the target acquisition plug-in acquires original index data corresponding to the original index from the target data source after establishing connection with the target data source according to the connection parameter, and sends the original index data to the target acquisition plug-in. Converting the original index data into target index data corresponding to the target index according to the mapping relation; and when a data storage request from the target acquisition plug-in is received, storing the target index data. The method can be applied to a digital twinning scene, and unified management of the equipment data of the IDC machine room is realized.

Description

Technical Field

[0001] The present application relates to the field of IDC operation and maintenance technology, and in particular to an IDC computer room equipment data management method, device, medium and electronic equipment. Background Art

[0002] With the development of information technology, the management of equipment in IDC computer rooms also needs to undergo digital transformation.

[0003] However, in the current solution, due to the large number of types of equipment in the IDC computer room, it is difficult to achieve unified management of the equipment data in the IDC computer room, and the management of the equipment in the IDC computer room is relatively complex. Summary of the invention

[0004] The embodiments of the present application provide a method, apparatus, medium and electronic device for managing device data in an IDC computer room, thereby enabling unified management of device data in the IDC computer room, at least to a certain extent, and simplifying management operations on the devices in the IDC computer room.

[0005] Other features and advantages of the present application will become apparent from the following detailed description, or may be learned in part by the practice of the present application.

[0006] According to one aspect of an embodiment of the present application, a device data management method for an IDC computer room is provided, the method comprising: returning mapping configuration data to the target acquisition plug-in according to a mapping configuration acquisition request from a target acquisition plug-in, the mapping configuration data comprising original indicators of a target data source corresponding to the target acquisition plug-in and a mapping relationship between the original indicators and the target indicators, the target data source being one of a plurality of data sources, the plurality of data sources being used to provide relevant data of each device in the IDC computer room; returning connection parameters of the target data source corresponding to the target acquisition plug-in to the target acquisition plug-in according to a connection parameter acquisition request from the target acquisition plug-in, so that after the target acquisition plug-in establishes a connection with the target data source according to the connection parameters, the target acquisition plug-in acquires original indicator data corresponding to the original indicator from the target data source, and converts the original indicator data into target indicator data corresponding to the target indicator according to the mapping relationship between the original indicator and the target indicator; and storing the target indicator data when a data storage request carrying the target indicator data is received from the target acquisition plug-in.

[0007] According to one aspect of an embodiment of the present application, there is provided an equipment data management device for an IDC computer room, the device comprising: a configuration data returning unit, configured to return mapping configuration data to a target acquisition plug-in according to a mapping configuration acquisition request from a target acquisition plug-in, the mapping configuration data comprising original indicators of a target data source corresponding to the target acquisition plug-in and a mapping relationship between the original indicators and the target indicators, the target data source being one of a plurality of data sources, the plurality of data sources being used to provide relevant data of each device in the IDC computer room; a connection parameter returning unit, configured to return connection parameters of a target data source corresponding to the target acquisition plug-in to the target acquisition plug-in according to a connection parameter acquisition request from the target acquisition plug-in, so that after the target acquisition plug-in establishes a connection with the target data source according to the connection parameters, the target acquisition plug-in acquires original indicator data corresponding to the original indicator from the target data source, and converts the original indicator data into target indicator data corresponding to the target indicator according to the mapping relationship between the original indicator and the target indicator; a data storage unit, configured to store the target indicator data when a data storage request carrying the target indicator data is received from the target acquisition plug-in.

[0008] According to one aspect of an embodiment of the present application, a computer-readable medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the device data management method of the IDC computer room as described in the above embodiment is implemented.

[0009] According to one aspect of an embodiment of the present application, an electronic device is provided, comprising: one or more processors; a storage device for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the device data management method of the IDC computer room as described in the above embodiments.

[0010] According to one aspect of an embodiment of the present application, a computer program product is provided, which includes computer instructions, the computer instructions are stored in a computer-readable storage medium, a processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the device data management method of the IDC computer room as described in the above embodiments.

[0011] In the technical solutions provided in some embodiments of the present application, after receiving a mapping configuration acquisition request from a target acquisition plug-in, the mapping configuration data including the original indicators of the target data source corresponding to the target acquisition plug-in and the mapping relationship between the original indicators and the target indicators are returned to the target acquisition plug-in, and upon receiving a connection parameter acquisition request from the target acquisition plug-in, the connection parameters of the target data source corresponding to the target acquisition plug-in are returned to the target acquisition plug-in. In this way, the target acquisition plug-in can establish a connection with the target data source according to the connection parameters, so that the original indicator data corresponding to the original indicator can be obtained from the target data source, and the original indicator data can be converted into target indicator data corresponding to the target indicator according to the mapping relationship between the original indicator and the target indicator. Finally, when the target acquisition plug-in requests to store the target indicator data, the target indicator data can be stored locally for the administrator to view.

[0012] Therefore, the solution of the present application realizes the collection of relevant data of various types of equipment in the IDC computer room by setting corresponding plug-ins that can record the relevant data of equipment in the IDC computer room. Since the present application also provides a mapping relationship between original indicators and target indicators to the target collection plug-in, the original indicator data can be converted into target indicator data corresponding to the target indicator that can be managed in a standardized manner in the current system. Therefore, unified management of the equipment data in the IDC computer room is realized, the complexity of managing the equipment in the IDC computer room is reduced, and the management operations of the equipment in the IDC computer room are greatly simplified.

[0013] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] The drawings herein are incorporated into the specification and constitute a part of the specification, showing embodiments consistent with the present application, and together with the specification, are used to explain the principles of the present application. Obviously, the drawings described below are only some embodiments of the present application, and for ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work. In the drawings:

[0015] Figure 1 A block diagram showing an overall architecture according to an embodiment of the present application;

[0016] Figure 2 A flow chart showing a method for managing device data in an IDC computer room according to an embodiment of the present application is shown;

[0017] Figure 3 A block diagram of a data access management module according to an embodiment of the present application is shown;

[0018] Figure 4 A block diagram of a device operation and maintenance management module according to an embodiment of the present application is shown;

[0019] Figure 5 A block diagram of a device operation and maintenance monitoring management module according to an embodiment of the present application is shown;

[0020] Figure 6 A block diagram showing the relationship between modules according to an embodiment of the present application;

[0021] Figure 7 A schematic diagram showing a principle of a data access management module according to an embodiment of the present application is shown;

[0022] Figure 8 A timing diagram of a data acquisition process according to an embodiment of the present application is shown;

[0023] Fig. 9 A timing diagram of a DCIM plug-in according to an embodiment of the present application is shown;

[0024] Fig.10 A schematic diagram of a process flow related to a Zabbix plug-in according to an embodiment of the present application is shown;

[0025] Fig.11 A timing diagram of collecting CMDB data according to an embodiment of the present application is shown;

[0026] Fig.12 A timing diagram of data indicator configuration according to an embodiment of the present application is shown;

[0027] Fig.13 A timing diagram of data indicator calculation according to an embodiment of the present application is shown;

[0028] Fig.14 A timing diagram of data indicator writing and querying according to an embodiment of the present application is shown;

[0029] Fig.15 A timing diagram of neatlogic integrated single sign-on according to an embodiment of the present application is shown;

[0030] Fig.16 A timing diagram of constructing a space tree according to an embodiment of the present application is shown;

[0031] Fig.17 A schematic diagram showing the principle of equipment operation and maintenance monitoring according to an embodiment of the present application is shown;

[0032] Fig.18 A timing diagram of large-screen message push according to an embodiment of the present application is shown;

[0033] Fig.19 A timing diagram of alarm management according to an embodiment of the present application is shown;

[0034] Fig. 20 A timing diagram of alarm management by device type according to an embodiment of the present application is shown;

[0035] Fig.21 A timing diagram of daily analysis of power consumption in a computer room according to an embodiment of the present application is shown;

[0036] Fig. 22 A block diagram of an equipment data management device for an IDC computer room according to an embodiment of the present application is shown;

[0037] Fig.23 A schematic diagram of the structure of a computer system suitable for implementing an electronic device of an embodiment of the present application is shown. DETAILED DESCRIPTION

[0038] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in a variety of forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this application will be more comprehensive and complete and fully convey the concept of the example embodiments to those skilled in the art.

[0039] In addition, described feature, structure or characteristic can be combined in one or more embodiments in any suitable manner. In the following description, many specific details are provided to provide a full understanding of the embodiments of the present application. However, those skilled in the art will appreciate that the technical scheme of the present application can be put into practice without one or more of the specific details, or other methods, components, devices, steps, etc. can be adopted. In other cases, known methods, devices, realizations or operations are not shown or described in detail to avoid blurring the various aspects of the application.

[0040] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities may be implemented in software form, or in one or more hardware modules or integrated circuits, or in different networks and / or processor devices and / or microcontroller devices.

[0041] The flowcharts shown in the accompanying drawings are only exemplary and do not necessarily include all the contents and operations / steps, nor must they be executed in the order described. For example, some operations / steps can be decomposed, and some operations / steps can be combined or partially combined, so the actual execution order may change according to actual conditions.

[0042] Figure 1A block diagram showing the overall architecture of an embodiment of the present application is shown. Figure 1 As shown in the figure, it shows the overall architecture of the IDC operation and maintenance management system, which includes the IDC front end and the IDC back end. The IDC front end includes the UE large screen and the management desk front end. The UE large screen is the screen of the front-end device driven by the Unreal Engine (UE), and the digital twin application of the IDC computer room can be displayed through the UE large screen. UE usually refers to Unreal Engine 5 (UE5 for short), which is an advanced game engine widely used in game development and film and television production.

[0043] The IDC backend includes business configuration management module, equipment operation and maintenance management module, data access management module, operation and maintenance monitoring and alarm module, emergency management module and BI management module. Among them, the business configuration management module includes two sub-modules, namely energy consumption configuration and IDC space management. The equipment operation and maintenance management module includes four sub-modules, namely equipment management, inspection management, operation and maintenance knowledge base, and maintenance management. The data access management module includes four sub-modules, namely data source configuration, data collection, data indicators and data services. The operation and maintenance monitoring and alarm module includes four sub-modules, namely video monitoring, access control monitoring, alarm management and alarm notification. The emergency management module includes three sub-modules, namely plan management, plan evaluation and plan simulation. The BI management module includes two sub-modules, namely BI material management and BI project management.

[0044] The third-party systems that the IDC operation and maintenance management system relies on include DCIM, cloud management system, and network management system. Each third-party system can serve as an external data source to provide the IDC operation and maintenance management system with relevant data of each device in the IDC computer room. The IDC operation and maintenance management system also relies on the internal system of the digital twin basic platform. The digital twin basic platform (Digital twinsApplication Foundation Platform) is the Foundation platform. The IDC operation and maintenance management system uses the unified user system provided by the Foundation platform and also uses Foundation FSDK to complete the use of twin capabilities, such as scene model loading, twin tagging, panel functions, etc.

[0045] Figure 2 The flowchart of the device data management method of the IDC computer room according to an embodiment of the present application is shown. The device data management method of the IDC computer room can be executed by any device such as a server that is deployed with the IDC operation and maintenance management system. Figure 2 As shown, the device data management method of the IDC computer room may specifically include the following steps:

[0046] In step 210, based on the mapping configuration acquisition request from the target acquisition plug-in, the mapping configuration data is returned to the target acquisition plug-in. The mapping configuration data includes the original indicators of the target data source corresponding to the target acquisition plug-in and the mapping relationship between the original indicators and the target indicators. The target data source is one of multiple data sources, and the multiple data sources are used to provide relevant data of each device in the IDC computer room.

[0047] Step 210 can be performed by a data access management module. The main function of data access management is to complete the access, processing and data opening of external data. Before introducing step 210 in detail, various modules in the IDC background are first introduced.

[0048] Figure 3 FIG. 1 shows a block diagram of a data access management module according to an embodiment of the present application. Figure 3As shown, the data access management module may include four submodules: data source management (configuration), data collection, data indicators and data services. Among them, data source management may include two units: data source configuration and data source classification; data collection may include three units: indicator mapping, plug-in management and data collection; data indicators may include four units: indicator dimension, indicator definition, indicator calculation and indicator query. The data source classification in the data source management may include types such as relational database, time series database, message middleware, API interface, etc.; the data source configuration provides configuration items with data source access, including information such as connection address and connection port, and the configuration information of different data sources may be different. The data service is used to provide the processed data to other modules through the interface. In the embodiment of the present application, different plug-ins can be developed for different data sources. Since different data sources are often different types of data sources, different plug-ins can be developed for different types of data sources. The plug-in management unit can realize the management of each plug-in. The plug-in can be used to collect data from the corresponding external data source, and convert the collected indicator data into indicator data corresponding to the system indicators used inside the IDC operation and maintenance management system. The data in the IDC operation and maintenance management system can mainly be collected through the DCIM system. Regarding the data indicator submodule, indicator dimensions and indicators can be defined. Indicator dimensions are dimension labels. Floors, computer rooms, cabinets, etc. can all be indicator dimensions. Indicator dimensions can be associated with corresponding indicators. When storing indicators in the IDC operation and maintenance management system, the corresponding indicator dimension information will be included. The IDC operation and maintenance management system can support secondary processing of indicator data. For example, the average temperature indicator data of the computer room can be calculated based on the temperature indicator data of the cabinet. The secondary processing of indicator data can be achieved based on the indicator dimension associated with the indicator. For example, the average temperature indicator data of the computer room can be calculated based on the temperature indicator data corresponding to the temperature indicators of each device associated with the indicator dimension of the computer room, that is, the statistical indicator data corresponding to the statistical indicator of the average temperature indicator. The statistical indicator data is returned to the IDC front end according to the query request from the IDC front end.

[0049] Figure 4 FIG. 1 shows a block diagram of a device operation and maintenance management module according to an embodiment of the present application. Figure 4 As shown, the device management submodule in the device operation and maintenance management module can include three units: device model management, device file management, and device instance management. The device management submodule is mainly used to maintain device information such as device basic information and device operation and maintenance information.

[0050] Figure 5 A block diagram of a device operation and maintenance monitoring management module according to an embodiment of the present application is shown. Figure 5As shown, the equipment operation and maintenance monitoring management module is the aforementioned operation and maintenance monitoring alarm module, which may include three sub-modules: equipment real-time monitoring, equipment alarm and security monitoring. The equipment real-time monitoring sub-module may include two units: equipment monitoring indicator configuration and equipment monitoring indicator query. The equipment alarm sub-module may include three units: alarm record, alarm access, alarm push and alarm rule configuration.

[0051] Figure 6 A block diagram showing the relationship between modules according to an embodiment of the present application is shown. Figure 6 As shown, the IDC front end will call the Foundation platform through FSDK to realize the capabilities of scene control and twin control; the Foundation platform will also provide user information to the IDC backend and obtain data pushed by the IDC backend. That is to say, the IDC operation and maintenance management system in this application can provide data support for digital twin applications; the data access management module of the IDC backend will obtain data from the DCIM platform through the plug-in, and the BI management module can query the required data from the data access management module.

[0052] Figure 7 FIG. 1 shows a schematic diagram of a data access management module according to an embodiment of the present application. Figure 7 As shown, it mainly shows the three submodules of data source configuration, data collection and data indicators of the data access management module. Among them, the data indicator submodule sends the indicator definition and indicator dimension to the data collection module. The data collection submodule can collect indicator data from the configured data source through the collection plug-in corresponding to the data source, and write the indicator data to the data indicator submodule. The MySQL database can interact with the data indicator submodule for indicator configuration, and the time series database can interact with the data indicator submodule for indicator data. The business configuration management module can synchronize business dimension data to the data indicator submodule.

[0053] The configured data sources may include DCIM, network management platform NMP, Zabbix and cloud management platform CMP / Categrf. Among them, DCIM is an infrastructure information management platform, which can be used to collect data, monitor and manage infrastructure. The infrastructure may include UPS, batteries, precision air conditioners, access control, environmental sensors, cameras, distribution cabinets, and refrigerators; the network management platform NMP and Zabbix can be used to perform equipment management, performance monitoring, traffic analysis and security monitoring of IT facilities. IT facilities may include servers, storage devices, and network devices; the cloud management platform CMP / Categrf can be used to perform resource management, security management and automation management of applications. Applications may include operating systems, databases, middleware, and applications. In the embodiments of the present application, the main data sources involved include DCIM and Zabbix. Zabbix is ​​an enterprise-level monitoring tool that can monitor various network parameters to ensure the safe operation of the enterprise service architecture.

[0054] The multiple data sources in step 210 may be multiple different types of data sources, for example, the multiple data sources may include the above-mentioned DCIM and Zabbix. Different data sources may be used to provide relevant data of different devices in the IDC room.

[0055] The target collection plug-in can be a collection plug-in corresponding to DCIM or Zabbix, which is used to collect data from DCIM or Zabbix. The mapping relationship between different indicators is the indicator mapping configuration. For example, for the DCIM data source, it is necessary to configure the mapping relationship between the DCIM GUID and the indicator ID, where the DCIM GUID can be the original indicator and the indicator ID can be the target indicator. The target indicator can be the indicator used to store data in the MySql database. The original indicator of the target data source corresponding to the target collection plug-in in the mapping configuration data is the data source mapping configuration, and the data source mapping configuration is the mapping relationship between the data source and the indicator.

[0056] In one embodiment of the present application, the target acquisition plug-in sends a mapping configuration acquisition request after receiving a mapping configuration change notification, and the mapping configuration change notification is generated after the mapping configuration data newly configured by the administrator is updated locally.

[0057] The mapping configuration data may be stored in the di_metrics_dcim_mapping table; once the administrator updates the mapping configuration data, the target collection plug-in needs to obtain the new mapping configuration data in a timely manner so that the target collection plug-in can collect data based on the new mapping configuration data.

[0058] When the mapping configuration data changes, a mapping configuration change notification is sent. If the collection plug-in is deployed on a single machine, Spring Event can be used for processing. If the collection plug-in is a cluster, Redis PubSub subscription events can be used. When the plug-in receives the event change, it obtains the mapping configuration data from the MySql database and updates the cache, such as updating it to the Redis database.

[0059] In step 220, based on the connection parameter acquisition request from the target acquisition plug-in, the connection parameters of the target data source corresponding to the target acquisition plug-in are returned to the target acquisition plug-in, so that after the target acquisition plug-in establishes a connection with the target data source based on the connection parameters, it obtains the original indicator data corresponding to the original indicator from the target data source, and converts the original indicator data into target indicator data corresponding to the target indicator based on the mapping relationship between the original indicator and the target indicator.

[0060] Returning the connection parameters of the target data source corresponding to the target acquisition plug-in to the target acquisition plug-in may be performed before returning the mapping configuration data to the target acquisition plug-in, or may be performed after returning the mapping configuration data to the target acquisition plug-in.

[0061] Connection parameters may include connection address, connection port, etc. Administrators can configure each data source that needs to collect data in advance on the management console. Specific configuration information may include data source type, data source name, data source connection parameters, etc. This information will be written to the di_datasource table of the MySql database.

[0062] Figure 8 FIG. 1 shows a timing diagram of a data collection process according to an embodiment of the present application. Figure 8 As shown, the data collection process involves the administrator, management station (Boss), data access management (DataSource), collection plug-in and data source. The following steps can be included in the data source configuration stage: 1.1 Configure data connection parameters: The administrator configures the database connection parameters to the management station; 1.2 Configure data connection parameters: The management station configures the database connection parameters to the data access management module; 1.3 Save data source connection parameters: The data access management module saves the data source connection parameters to the MySql database; 1.4 Return: The data access management module returns the response information to the management station; 1.5 Return: The management station returns the response information to the administrator.

[0063] The data indicator and data source mapping configuration stage may include: 2.1 Data indicator mapping configuration: the administrator configures the mapping configuration data to the management console; 2.2 Data indicator mapping configuration: the management console configures the mapping configuration data to the data access management module; 2.3 Save data mapping configuration: the data access management module saves the mapping configuration data to the MySql database; 2.4 Notify the plug-in of mapping configuration changes: the data access management module notifies the collection plug-in of changes in mapping configuration data; 2.5 Update data mapping configuration: the collection plug-in caches events that update data mapping configuration; 2.6 Return: the collection plug-in returns response information to the data access management module; 2.7 Return: the data access management module returns response information to the management console; 2.8 Return: the management console returns response information to the administrator.

[0064] The startup phase may include: 3.1 Obtaining indicators and data source mapping configuration data: the collection plug-in requests the data access management module to obtain mapping configuration data; 3.2 Return: the data access management module returns the mapping configuration data to the collection plug-in; 3.3 Cache mapping configuration: the collection plug-in caches mapping configuration data; 3.4 Obtaining data source connection parameters: the collection plug-in requests the data access management module to obtain data source connection parameters; 3.5 Return: the data access management module returns the data source connection parameters to the collection plug-in; 3.6 Establishing network communication: the collection plug-in requests to establish network communication with the data source; 3.7 Return: the data source returns response information to the collection plug-in.

[0065] In step 230, when a data storage request carrying target indicator data is received from the target acquisition plug-in, the target indicator data is stored.

[0066] Please continue to see Figure 8 The data collection stage may include: 3.8 Pushing data source (such as DCIM) point data: the data source pushes the original indicator data corresponding to the original indicator to the collection plug-in; 3.9 Point data conversion indicator: the collection plug-in converts the original indicator data into target indicator data corresponding to the target indicator; 3.10 Data storage: the collection plug-in returns the target indicator data to the data access management module for storage; 3.11 Return: the data access management module returns response information to the collection plug-in; 3.12 Return: the collection plug-in returns a response message to the data source.

[0067] In one embodiment of the present application, the target acquisition plug-in establishes a heartbeat connection with the target data source after logging in to the target data source. The target data source pushes the original indicator data corresponding to the original indicator to the target acquisition plug-in while the heartbeat connection is maintained.

[0068] In one embodiment of the present application, the target acquisition plug-in logs in to the target data source by preempting the current process as the login process. The target acquisition plug-in accesses the target data source based on the token information obtained from the target data source after logging in to the target data source. The token information and the key corresponding to the token information are stored in the form of a key-value pair in the cache corresponding to the target acquisition plug-in. The target acquisition plug-in maintains a heartbeat connection by sending heartbeat information to the target data source at predetermined intervals, and the predetermined duration is less than the key timeout duration.

[0069] The token information is token; the preset duration can be 2 seconds; the key timeout can be 5 seconds.

[0070] The target data source can be DCIM, and the target collection plug-in can be the plug-in corresponding to DCIM. Since DCIM only allows one user to log in at a time, a distributed lock is required to ensure that multiple login processes cannot exist in the cache at the same time. A cache (Redis) can be opened in the system. The key used to record the login process in the cache (Redis) can be used to determine whether there is a login process in the cache based on whether the key of the login process exists in the cache. If there is no login process in the cache, you can use DCIM:LOGIN:$DCIM_ID as the key to try to preempt the current process as the login process; if the current process is not preempted as the login process, you can continue to try to preempt it every 6 seconds.

[0071] If the current process is preempted as a login process, the DCIM login interface is called to obtain token information, and the token is recorded in the redis cache. The key corresponding to the token in redis can be DCIM:TOKEN:$DCIM_ID, and the timeout period of the key can be 5 seconds; the collection plug-in can send a heartbeat to DCIM every 2 seconds and update the timeout period of DCIM:TOKEN:$DCIM_ID. Specifically, if the collection plug-in sends a heartbeat when there are 3 seconds left in the timeout period of DCIM:TOKEN:$DCIM_ID, the timeout period of the key can be updated to 5 seconds; if the heartbeat fails to be sent, the plug-in can try to log in again.

[0072] In one embodiment of the present application, the target data source pushes original indicator data corresponding to the original indicator to the target acquisition plug-in according to the subscription strategy provided by the target acquisition plug-in, and the subscription strategy is obtained by the target data source from the subscription request from the target acquisition plug-in.

[0073] In one embodiment of the present application, a subscription request is generated by the target acquisition plug-in after obtaining token information from the target data source. The subscription request carries the token information. The target data source saves the subscription policy after confirming that the token information in the subscription request is valid.

[0074] Specifically, when the target collection plug-in needs to call the DCIM interface, it can read the token value of DCIM:TOKEN:$DCIM_ID from redis. If the token cannot be read, an alarm log is printed.

[0075] In one embodiment of the present application, the subscription strategy is one of the following: each time the original indicator data corresponding to the original indicator is collected, the original indicator data is pushed to the target collection plug-in; each time the original indicator data corresponding to the collected original indicator changes, the changed original indicator data corresponding to the original indicator is pushed to the target collection plug-in; the original indicator data corresponding to the original indicator is pushed to the target collection plug-in at specified intervals.

[0076] Of course, the subscription strategy may also include: uploading the original indicator data corresponding to the original indicator that has changed within the specified time period at specified time intervals.

[0077] Fig. 9 FIG. 1 shows a timing diagram of a DCIM plug-in according to an embodiment of the present application. Fig. 9 As shown, the sequence diagram involves which entity the data access management DataSource, the collection plug-in and the DCIM are. The startup phase may include: 1.1 Obtaining data source connection parameters: the collection plug-in obtains the data source connection parameters from the data access management module; 1.2 Return: the data access management module returns the data source connection parameters to the collection plug-in; 1.3 Obtaining indicators and data source mapping configuration data: the collection plug-in requests the data access management module to obtain the mapping configuration data; 1.4 Return: the data access management module returns the mapping configuration data to the collection plug-in; 1.5 Locally cache mapping configuration: the collection plug-in caches the mapping configuration data locally; 1.6 Subscribe to indicator mapping configuration change events: the collection plug-in subscribes to mapping configuration data change events from the data access management module; 1.7 Return: the data access management module returns the mapping configuration data to the collection plug-in Return response information; 1.8 Call DCIM interface login / north / login: The collection plug-in calls the DCIM interface to request to log in to the DCIM platform; 1.9 Return: The DCIM platform returns a token to the collection plug-in; 1.10 Cache token: The collection plug-in caches the token locally; 1.11 Subscribe to DCIM data / north / online_data_strategy_add: The collection plug-in sends a subscription policy for data in DCIM to the DCIM platform; 1.12 Update subscription policy: The DCIM platform updates the recorded subscription policy; 1.13 Return: The DCIM platform returns a response information to the collection plug-in;

[0078] The loop stage is an operation of sending a heartbeat every 2 seconds, which may include: 1.14 Heartbeat connection with DCIM / north / heartbeat: the collection plug-in sends a heartbeat to the DCIM platform; 1.15 Return: the DCIM platform returns a response message to the collection plug-in;

[0079] The data collection stage may include: 1.16 Receiving push data source (such as: DCIM) point data / north / online_data_strategy_push: the DCIM platform pushes the collected point data to the collection plug-in; 1.17 Point data conversion index: the collection plug-in performs index conversion on the point data; 1.18 Data storage: the collection plug-in stores the converted index data to the data access management module; 1.19 Return: the data access management module returns response information to the collection plug-in; 1.20 Return: the collection plug-in returns response information to the DCIM platform.

[0080] The stop phase may include: 1.21 calling DCIM / north / logout to disconnect: the collection plug-in calls the interface of the DCIM platform to disconnect from the platform; 1.22 return: the DCIM platform returns a response message to the collection plug-in; 1.23 destruction: the collection plug-in destroys the cached information.

[0081] In one embodiment of the present application, after returning the connection parameters of the target data source corresponding to the target acquisition plug-in to the target acquisition plug-in, the method also includes: when receiving a status access request for the target data source, obtaining the status information of the target data source from the cache corresponding to the target acquisition plug-in, and the status information of the target data source in the cache is updated in real time according to the status of the heartbeat connection between the target acquisition plug-in and the target data source.

[0082] The administrator can send a status access request through the management console front end, and the status information can be returned to the sender of the status access request.

[0083] Specifically, it can be determined whether the key DCIM:HEARTBEAT:{datasourceId} exists in the Redis cache corresponding to the target collection plug-in. If it does not exist, the disconnected notification information can be returned to the management console front end, and the management console front end will display disconnected; if it exists, the value corresponding to the key is the status information, and the value corresponding to the key can be returned to the management console front end.

[0084] The target collection plug-in can also be a Zabbix plug-in.

[0085] In one embodiment of the present application, after returning the connection parameters of the target data source corresponding to the target acquisition plug-in to the target acquisition plug-in, the method also includes: obtaining a dimension tag query request from the target acquisition plug-in, the dimension tag query request is generated after the target acquisition plug-in collects the original indicator data corresponding to the target IP address from the target data source corresponding to the target acquisition plug-in, and the dimension tag query request includes the target IP address; determining at least one information item associated with the target IP address in the dimension tag query request, and returning the at least one information item as the dimension tag corresponding to the target IP address to the target acquisition plug-in, so that the target acquisition plug-in writes the original indicator data and dimension tag corresponding to the target IP address into the target time series database in a predefined format.

[0086] In one embodiment of the present application, before returning the connection parameters of the target data source corresponding to the target acquisition plug-in to the target acquisition plug-in based on the connection parameter acquisition request from the target acquisition plug-in, the method may also include: obtaining asset configuration data corresponding to at least one asset device in the configured IDC computer room, the asset configuration data including multiple information items corresponding to the corresponding asset device, and the multiple information items including an IP address; obtaining a dimension tag query request from the target acquisition plug-in, the dimension tag query request is periodically generated by the target acquisition plug-in, and the dimension tag query request includes at least one IP address; determining from the asset configuration data the information items associated with each IP address in the dimension tag query request, and returning the information items associated with each IP address as the dimension tag value corresponding to each IP address to the target acquisition plug-in, so that after the target acquisition plug-in collects the original indicator data corresponding to the target IP address from the target data source corresponding to the target acquisition plug-in, it determines the dimension tag value corresponding to the target IP address from the dimension tag values ​​corresponding to each IP address, and writes the original indicator data and dimension tag value corresponding to the target IP address into the target time series database in a predefined format.

[0087] The target collection plug-in can send dimension label query requests every 5 minutes. The original indicator data and dimension label values ​​in the target time series database can be used for query and display.

[0088] Specifically, asset equipment may include servers, network equipment, etc. The information items corresponding to each asset equipment may include device ID, device code, cabinet, cabinet row, room, floor, building, IP address, etc.; among them, the device code can be used to identify the device type, and information items such as device code, cabinet, cabinet row, room, floor, building, etc. can all be used as dimension labels.

[0089] Fig.10A schematic diagram of a process flow related to the Zabbix plug-in according to an embodiment of the present application is shown. Fig.10 As shown, the following processes may be included: 1. Configuring server IP: The administrator configures the IP of each server in the CMDB submodule of the equipment operation and maintenance management module, and establishes a corresponding relationship between information items such as asset equipment ID, equipment code, and IP address; 2. Synchronizing asset configuration data: The equipment operation and maintenance management module regularly synchronizes asset configuration data to the data access management module, and the asset configuration data may be written into the relational database; 3. Querying indicator dimension label data based on IP: The Zabbix plug-in provides the IP address of the server to the data access management module, and queries the device number, cabinet, floor, etc. corresponding to the IP address from the relational database as the dimension label value corresponding to the IP address; 4. Writing monitoring indicator data: The Zabbix plug-in writes the original indicator data and the corresponding dimension label value collected from the server corresponding to the IP address into Prometheus in the format defined by Prometheus. Prometheus is the aforementioned target time series database; 5. Querying monitoring indicators: The data access management module queries the indicator data from Prometheus and performs secondary processing.

[0090] Please continue to see Figure 6 As shown, the business configuration management module will synchronize the business dimension (ie, dimension tag value) to the data access management module. The business dimension is constructed by the business configuration management module based on the device information obtained from the device operation and maintenance management module.

[0091] The data access management module may obtain the asset configuration data from the equipment operation and maintenance management module through a collection plug-in, for example, the asset configuration data may be obtained through a collection plug-in corresponding to the CMDB submodule.

[0092] Fig.11 FIG. 1 shows a timing diagram of collecting CMDB data according to an embodiment of the present application. Fig.11 As shown, collecting CMDB data involves three entities: data access management (DataSource), CMDB, and the collection plug-in corresponding to CMDB, which can include the following processes:

[0093] The startup phase may include: 1.1 Obtaining data source connection parameters: the CMDB acquisition plug-in obtains data source connection parameters from the data access management module; 1.2 Returning: the data access management module returns the data source connection parameters to the CMDB acquisition plug-in; 1.3 Establishing connection with CMDB: the CMDB acquisition plug-in establishes a connection with CMDB; 1.4 Returning: the CMDB returns a response message to the CMDB acquisition plug-in;

[0094] The data collection phase can be scheduled for 5 minutes and carried out regularly, which may include: 1.5 Obtaining CMDB asset information: The CMDB collection plug-in obtains CMDB asset information from CMDB; 1.6 Return: CMDB returns CMDB asset information to the CMDB collection plug-in; 1.7 Data conversion index (cabinet U-position index): The CMDB collection plug-in converts the CMDB asset information into asset index data specified by the data access management module. For example, a cabinet can contain multiple U positions, and each device (such as a server) can occupy at least one U position. The U position occupancy rate of each cabinet can be statistically obtained as asset index data; 1.8 Data storage: The CMDB collection plug-in stores the asset index data in the data access management module; 1.9 Return: The data access management module returns a response message to the CMDB collection plug-in;

[0095] The stop phase may include: 1.10 disconnection: the CMDB acquisition plug-in requests to disconnect from the CMDB; 1.11 return: the CMDB returns a response message to the CMDB acquisition plug-in; 1.12 destruction: the CMDB acquisition plug-in destroys the related data of the connection.

[0096] The connection status between the CMDB acquisition plug-in and the CMDB is displayed according to the connect_status status value of the di_datasource table in the MySql database. The connection status can be disconnected, connecting, or connected. When the scheduled task obtains CMDB assets, it is judged according to the connect_status of the data source: when it is disconnected or connecting, CMDB asset information synchronization is not performed; when connect_status is connected, CMDB asset information is synchronized.

[0097] In one embodiment of the present application, before writing the original indicator data and dimension label values ​​corresponding to the target IP address into the target time series database in a predefined format, the method also includes: obtaining the configured statistical indicator definition data corresponding to at least one statistical indicator; after writing the original indicator data and dimension label values ​​corresponding to the target IP address into the target time series database in a predefined format, the method also includes: calling the target time series database according to the statistical indicator definition data corresponding to each statistical indicator, obtaining statistical indicator data corresponding to at least one statistical indicator calculated by the target time series database according to at least one original indicator data in the target time series database, and writing the statistical indicator data corresponding to each statistical indicator into the target time series database.

[0098] Specifically, the statistical indicator can be defined based on the original indicator data and the corresponding dimension tag value. For example, the cabinet has the original indicator data of temperature, and it has the dimension tag of computer room. The average temperature of the actual computer room corresponding to the dimension tag can be calculated as the statistical indicator data.

[0099] After the statistical indicator data is written into the target time series database, the statistical indicator data in the target time series database can be queried according to the user's request, and the queried statistical indicator data is returned to the user front end.

[0100] Fig.12 FIG. 1 shows a timing diagram of data indicator configuration according to an embodiment of the present application. Fig.12 As shown in the figure, data indicator configuration involves the following entities: administrator, management desk (Boss), business configuration management (Config), data access management (DataSource), Quartz and Promethus VictoriaMetrics. PromethusVictoriaMetrics is a real-time series database. Quartz is a powerful scheduling library widely used in Java applications to execute scheduled and planned tasks. It provides a flexible task scheduling mechanism to support complex scheduling requirements.

[0101] The data dimension definition stage may include: 1.1 Configuring data dimensions: The administrator configures dimension labels to the management console through the front end. In fact, the dimension name, dimension code, etc. can also be configured. These dimension-related data are written into the di_metrics_dim table; 1.2 Configuring data dimensions: The management console configures dimension labels to the data access management module; 1.3 Saving configured data dimensions: The data access management module saves dimension labels; 1.4 Return: The data access management module returns response information to the management console; 1.5 Return: The management console returns response information to the administrator's front end.

[0102] The data dimension synchronization stage may include: 2.1 Timed triggering of data dimension synchronization: Timed triggering of the business configuration management module through Quartz to synchronize dimension tag values; 2.2 Synchronizing data dimensions: The business configuration management module synchronizes dimension tag values ​​to the data access management module; 2.3 Saving data dimensions: The data access management module saves dimension tag values; 2.4 Writing data dimensions: The data access management module writes dimension tag values ​​to Promethus VictoriaMetrics; 2.5 Saving data dimensions: Promethus VictoriaMetrics saves dimension tag values; 2.6 Return: PromethusVictoriaMetrics returns response data to the data access management module; 2.7 Return: The data access management module returns response data to the business configuration management module; 2.8 Return: The business configuration management module returns response data to Quartz.

[0103] The data indicator definition stage may include: 1.1 Configuring data indicators: The administrator configures the data indicator definition (such as statistical indicator definition data) on the management console, including indicator number, indicator name, indicator dimension (multiple selections are allowed), indicator type, etc.; 1.2 Configuring data indicators: The management console sends the data indicator definition to the data access management module; 1.3 Saving the data indicator definition: The data access management module saves the data indicator definition; 1.4 Creating an indicator calculation scheduling task: The data access management module requests Quartz to create an indicator calculation scheduling task. The indicator calculation scheduling task is an indicator calculation task that is executed at a fixed time. Therefore, the indicator corresponding to the data indicator definition is a calculation indicator, that is, a statistical indicator. When creating an indicator calculation scheduling task, it is necessary to configure the calculation SQL statement and scheduling cycle, and write the configuration data into the di_metrics table; 1.5 Return: Quartz returns a response message to the data access management module; 1.6 Return: The data access management module returns a response message to the management console; 1.7 Return: The management console returns a response message to the front end.

[0104] Fig.13 A timing diagram of data indicator calculation according to an embodiment of the present application is shown. Fig.13 The task involved may be to calculate the statistical indicator data corresponding to the statistical indicator; see Fig.13As shown, it involves the entities of administrator, data access management (DataSource), Quartz and Promethus VictoriaMetrics, and can specifically include the following steps: 1.1 indicator calculation task triggering: Quartz triggers the indicator calculation task to execute the indicator calculation process; 1.2 obtain indicator configuration information: the data access management module obtains the indicator ID from the Quartz context, and queries the di_metrics table according to the indicator ID to obtain the configured data indicator definition; 1.3 execute indicator calculation: the data access management module obtains the address of Promethus from the configuration center, calls the Promethus data query interface according to the address, sends the data indicator definition to Promethus, and uses metrics_calc_sql as the query condition to perform the calculation of the corresponding statistical indicator data; 1.4 execution: Promethus executes the calculation of the corresponding statistical indicator data; 1.5 return the calculation result: Promethus returns the calculation result to the data access management module; 1.6 Data analysis and processing: The data access management module analyzes the calculation results; 1.7 Write calculation indicators: The data access management module writes the analyzed calculation results into Promethus; 1.8 Save: Promethus saves the obtained calculation results; 1.9 Return: Promethus returns response information to the data access management module; 1.10 Update the latest indicator data: The data access management module stores the analyzed calculation results into the di_metrics_last_value table of the relational database; 1.11 Record abnormal indicator calculation tasks: The data access management module records abnormal indicator calculation tasks. If the query data is abnormal, such as the interface call fails, the data access management module writes the scheduled task failure results into the indicator scheduling failure record table di_metrics_schedule_fail; 1.12 Return: The data access management module returns a response message to Quartz.

[0105] The abnormal compensation for calculation indicators can be executed three times, which can specifically include: 2.1 Query indicator abnormality task: Quartz requests the data access management module to query the abnormal task of indicator calculation, and the data access management module will re-call the indicator calculation process; 2.2 Return: The data access management module returns a response message to Quartz.

[0106] Therefore, the system will periodically scan the data in the di_metrics_schedule_fail table and retry the failed call task up to three times; if it exceeds three times, the task is set to be processed completed.

[0107] Fig.141 shows a timing diagram of data pointer writing and querying according to an embodiment of the present application. Fig.14 As shown in Figure 1, it involves the administrator, management console (Boss), business configuration management (Config), data access management (DataSource), Quartz and PromethusVictoriaMetrics entities, and includes the indicator query phase and the indicator writing phase. The indicator query phase can be Fig.13 Corresponding to step 1.3 in the above, the indicator writing phase can be done with Fig.13 Corresponding to step 1.7 in, the indicator query phase may include: 1.1 Query indicator: the administrator requests the management station to query indicator data (such as statistical indicator data) through the front end; 1.2 Query indicator: the management station requests the data access management module to query indicator data (such as statistical indicator data); 1.3 Save data indicator definition; 1.4 Query indicator: the data access management module requests Promethus to perform calculations of corresponding statistical indicator data; 1.5 Query: Promethus performs calculations of corresponding statistical indicator data; 1.6 Return result: Promethus returns the calculation result to the data access management module, that is, returns the calculated statistical indicator data; 1.7 Data packaging: the data access management module encapsulates the calculation result in a predetermined format; 1.8 Return: the data access management module returns the encapsulated calculation result to the management station; 1.9 Return: the management station returns the encapsulated calculation result to the front end.

[0108] The indicator writing stage may include: 1.1 Writing indicators: the administrator requests the management console through the front end to write the calculated statistical indicator data into Promethus; 1.2 Writing indicators: the management console requests the data access management module to write the calculated statistical indicator data into Promethus; 1.3 Verifying indicator dimensions: the data access management module verifies the legitimacy of the dimension label values ​​corresponding to the statistical indicator data; 1.4 Writing data indicators: the data access management module writes the statistical indicator data into Promethus; 1.5 Saving data: Promethus saves the statistical indicator data; 1.6 Returning results: Promethus returns the saved results to the data access management module; 1.7 Return: the data access management module returns the saved results to the management console; 1.8 Return: the management console returns the saved results to the front end.

[0109] In one embodiment of the present application, the asset configuration data corresponding to at least one asset device in the IDC computer room is configured through the target module of the current system. The target module and the target system that the current system depends on use the same domain name. The target module processes the login request after determining that the token information of the target system carried in the login request and the session cookie of the target module have passed verification. The token information of the target system is obtained from the target system when the sender of the login request logs in to the target system for the first time. The session cookie of the target module is returned by the target module when the token information of the target system sent by the sender of the login request when logging in to the target module for the first time has passed verification.

[0110] Specifically, the target module of the current system may be a CMDB submodule.

[0111] Fig.15 The timing diagram of the neatlogic integrated single sign-on according to an embodiment of the present application is shown. The neatlogic integrated single sign-on can simplify the login operation. Fig.15 As shown, it involves several entities, namely, administrator, equipment operation and maintenance management Neatlogic and Foundation, among which Neatlogic is the aforementioned CMDB submodule. Specifically, it may include the following processes: 1.1 User login: As a user, the administrator sends a login request through the front end. When requesting to log in to the NeatLogic submodule, he will log in through the page of the Foundation platform. The Foundation and NeatLogic domain names must be the same, and the nginx forwarding rules can be configured through the url prefix; 1.2 Return user Token: The Foundation platform returns a Token containing the sessionId to the front end, and the Token will be stored in the front end cookie; 1.3 Save data indicator definition: The front end requests to save the data indicator definition to the Neatlogic submodule of equipment operation and maintenance management.

[0112] The first access phase may include: 1.4 Carrying Foundation Token: When the administrator accesses the NeatLogic submodule through the front end, a cookie carrying sessionId will be sent; 1.5 Verifying the legitimacy of the Token: NeatLogic verifies the validity of the Foundation session based on the sessionId of Foundation; 1.6 Return: The Foundation platform returns the verification result to the Neatlogic submodule of device operation and maintenance management; 1.7 Obtaining user information: The Neatlogic submodule of device operation and maintenance management obtains the corresponding user information and user permission information from the Foundation platform based on the sessionId request; 1.8 Return: The Foundation platform returns the corresponding user information and user permission information to the Neatlogic submodule. If it is determined based on the user permission information that the user does not have the access rights of the Neatlogic submodule, a login failure is returned; 1.9 Initializing system session information: The Neatlogic submodule initializes the system session Cookie information; 1.10 Returning NeatLogic's session Cookie: The Neatlogic submodule returns the session Cookie with the NeatLogic submodule to the front end; 1.11 Carrying Foundation Token and NeatLogic Cookie information: When you visit the Neatlogic submodule again, you will carry both the NeatLogic session cookie and the cookie containing the Foundation sessionId; 1.12 Verify session validity: The Neatlogic submodule verifies session validity based on the NeatLogic session cookie; 1.13 Verify Foundation Token session validity: The Neatlogic submodule verifies Foundation Token session validity based on Foundation sessionId; 1.14 Return to user: The Foundation platform requests the Neatlogic submodule to return the verification result; 1.15 Return: The Neatlogic submodule returns the verification result to the front end.

[0113] The relationship between the various devices in the scenario of this application can form a spatial tree. For example, the device belongs to the cabinet, the cabinet belongs to the cabinet column, the cabinet column belongs to the room, the room belongs to the floor, and the floor belongs to the building. A spatial tree can be constructed based on these belonging relationships. Fig.16 FIG. 1 shows a timing diagram of constructing a space tree according to an embodiment of the present application. Fig.16As shown in the figure, there are several entities, including administrator, Quartz, equipment operation and maintenance management, and CMDB. Among them, CMDB can be a part of the actual equipment operation and maintenance management. Fig.16 The equipment operation and maintenance management in can represent other parts of the actual equipment operation and maintenance management.

[0114] like Fig.16 As shown, the space tree construction phase may include: 1.1 Creating a scheduled task for constructing a space tree: the device operation and maintenance management module creates a scheduled task for constructing a space tree in Quartz; 1.2 Data response: Quartz returns response information to the device operation and maintenance management module.

[0115] The scheduled task loop stage may include: 1.3 Scheduled call: Quartz schedules to call the equipment operation and maintenance management module to build a space tree, for example, once every 6 minutes; 1.4 Query the enabled scene: The equipment operation and maintenance management module queries the currently enabled scene information in the CMDB; 1.5 Data response: CMDB returns the currently enabled scene information to the equipment operation and maintenance management module; 1.6 Recursively query the child nodes under the scene and query the Column: The equipment operation and maintenance management module recursively queries the child nodes under the scene in the CMDB until the cabinet column (Column) is queried; 1.7 Data Response: CMDB returns the queried data to the equipment operation and maintenance management module; 1.8 The spatial tree is written to the cache, with the scene's assetid as the key: the equipment operation and maintenance management module writes the returned data into a tree structure and writes it to the cache. The cache key can be: ASSET:TREE:{scene_asset_id}; 1.9 Response: The equipment operation and maintenance management module returns response information to Quartz; the query stage may include: 2.1 Query the spatial tree: the front end requests to query the spatial tree; 2.2 Data response: the equipment operation and maintenance management module returns the spatial tree to the front end.

[0116] Fig.17 The schematic diagram of the principle of equipment operation and maintenance monitoring according to an embodiment of the present application is shown. Fig.17As shown, the management station can send a websocket message to the front end through a websocket connection, and the front end can also request to query the management station for alarm information. The management station can query the basic information of the equipment, the equipment operation and maintenance information, etc. from the equipment operation and maintenance management module, and return this information to the front end in the form of a websocket message; DCIM and Promethus can generate alarm notifications based on the stored data, and the alarm notifications can be sent to the data access management module. The data access management module can standardize the format of the received alarm notifications to obtain the standardized alarm information used by the system, and push the standardized alarm information to the equipment monitoring alarm module, that is, the aforementioned operation and maintenance monitoring alarm module. The equipment monitoring alarm module will assemble the standardized alarm information with the equipment information obtained from the equipment operation and maintenance management module to obtain the final alarm information; the equipment monitoring alarm module can push the final alarm information to the front end in the form of a websocket message, and can also return the final alarm information to the front end according to the query request from the front end.

[0117] In one embodiment of the present application, after writing the statistical indicator data corresponding to each statistical indicator into the target time series database, the method also includes: obtaining an original message from the target time series database, the original message is generated by the target time series database based on the device-related indicator data stored in the target time series database; generating a target message of the target topic based on the original message, and sending the target message to the message queue corresponding to the target topic in the message bus, so that the message bus determines each subscriber corresponding to the target topic based on the stored subscription information, and pushes the target message to each subscriber corresponding to the target topic, the message bus includes a message queue corresponding to at least one topic.

[0118] The topic is the category of the message. For example, messages can be divided into notification messages, alarm messages, etc.

[0119] Fig.18 1 shows a timing diagram of large screen message push according to an embodiment of the present application. Fig.18 As shown, it involves several entities including administrator, management console (Boss), message bus (EventBus), and business module.

[0120] exist Fig.18In the process, the long connection establishment stage may include: 1.1 Establishing a long connection through websocket: After the front-end user logs in, the front-end user establishes a long connection with the management station through websocket, and sends a request carrying a token to the management station; 1.2 User Token authentication and verification: The management station authenticates and verifies the request based on the token 1.3 Establishing a websocket session: The management station establishes websocket session information; 1.4 Return: The management station returns the websocket session information to the front-end, and the front-end can maintain the correspondence between the user ID and the websocket session information locally; 1.5 Subscribing to Topic messages: The management station sends the subscribed topic information to the message bus; 1.6 Recording subscription information: The message bus records the subscribed topic information; 1.7 Return: The message bus returns the response information to the management station.

[0121] The message push stage may include: 1.2 Sending a message to a specified Topic: the business module requests to send a message to the message queue corresponding to the specified topic in the message bus; 1.3 Message format verification: the message bus performs message format verification; 1.4 Return: the message bus returns a response message to the business module; 1.5 Obtaining the Topic subscriber: the message bus determines the subscriber corresponding to the specified topic (that is, the management station that has subscribed to the specified topic).

[0122] During the Loop phase, the same operations need to be performed on all subscribers. The operations performed on any subscriber may include: 1.6 Push message: the message bus pushes messages of the specified topic to which it has subscribed to the management station; 1.7 Message parsing (broadcast message, specified receiving message): the management station parses the received message. The received message can be a message broadcast to all front-end users or a message that can be received by specified front-end users; 1.8 Push message: the management station pushes messages to the corresponding front-end users; 1.9 Return: the front-end returns a response message to the management station; 1.10 Return: the management station returns a response message to the message bus.

[0123] Through the above method, the system can push various information such as alarm messages to various front-end users such as the front-end large screen.

[0124] In one embodiment of the present application, obtaining the original message from the target time series database includes: obtaining an alarm generation notification message or an alarm recovery notification message from the target time series database; generating a target message of the target topic according to the original message, and sending the target message to a message queue corresponding to the target topic in the message bus, including: generating an alarm generation message or an alarm recovery message of the target topic according to the alarm generation notification message or the alarm recovery notification message, and sending the alarm generation message or the alarm recovery message of the target topic to the message queue corresponding to the target topic in the message bus.

[0125] Fig.19 FIG. 1 shows a timing diagram of alarm management according to an embodiment of the present application. Fig.19 As shown, the entities involved may include: administrator, management console (Boss), message bus (EventBus), operation and maintenance monitoring management module, facility operation and maintenance management module, and Prometheus.

[0126] exist Fig.19 In the process, the alarm generation notification stage may include: 1.1 alarm generation notification: Prometheus returns the alarm generation notification information to the operation and maintenance monitoring management module; 1.2 analysis of alarm information: the operation and maintenance monitoring management module parses the obtained alarm generation notification information; 1.3 conversion of standard information: the operation and maintenance monitoring management module converts the parsing result into a standard alarm generation message; 1.4 saving alarm information to the database: the operation and maintenance monitoring management module saves the standard alarm generation message to the database; 1.5 return: the operation and maintenance monitoring management module returns a response message to Prometheus; 1.6 push alarm information to eventBus: the operation and maintenance monitoring management module pushes the standard alarm generation message to the message bus; 1.7 return: the message bus returns a response message to the operation and maintenance monitoring management module.

[0127] The alarm recovery notification stage may include: 1.2 Alarm recovery notification: Prometheus returns alarm recovery notification information to the operation and maintenance monitoring management module; 1.3 Parse alarm information: The operation and maintenance monitoring management module parses the obtained alarm recovery notification information; 1.4 Convert standard information: The operation and maintenance monitoring management module converts the parsing result into a standard alarm recovery message; 1.5 Query alarm information according to alarm ID: Query the standard alarm recovery message that needs to be updated to the database from the local according to the alarm ID; 1.6 Update alarm information to the database: The operation and maintenance monitoring management module saves the queried standard alarm recovery message to the database; 1.7 Return: The operation and maintenance monitoring management module returns a response message to Prometheus; 1.8 Push alarm recovery to eventBus: The operation and maintenance monitoring management module pushes the standard alarm recovery message to the message bus; 1.9 Return: The message bus returns a response message to the operation and maintenance monitoring management module.

[0128] The alarm information query stage may include: 1.3 Query alarm information: the administrator requests the management console through the front end to query alarm information such as alarm generation messages and alarm recovery messages; 1.4 Query alarm information: the management console requests to query alarm information; 1.5 Obtain alarm information from the database: the operation and maintenance monitoring management module obtains alarm information from the database; 1.6 Return: the operation and maintenance monitoring management module returns the alarm information to the management console; 1.7 Return: the management console returns the alarm information to the administrator's front end.

[0129] In one embodiment of the present application, the method may further include the following steps: obtaining the configured device type and the predetermined target indicator to be monitored corresponding to each device type; when receiving an indicator data acquisition request for a device corresponding to the target device type, determining and returning the predetermined target indicator to be monitored corresponding to the target device type to the sender of the indicator data acquisition request, so that the sender of the indicator data acquisition request can query the target indicator data of the device corresponding to the target device type based on the predetermined target indicator to be monitored corresponding to the target device type.

[0130] The embodiments of the present application implement monitoring of corresponding indicator data according to device type. For example, for ordinary servers, relevant indicator data such as CPU and memory can be monitored; and for network servers, indicator data such as bandwidth and delay can be monitored.

[0131] Fig. 20 FIG. 1 shows a timing diagram of alarm management by device type according to an embodiment of the present application. Fig. 20 As shown, the entities involved include: administrator, management console (Boss), operation and maintenance monitoring management module, facility operation and maintenance management module, data access management module, Prometheus, among which the facility operation and maintenance management module is the aforementioned equipment operation and maintenance management module.

[0132] exist Fig. 20In the configuration of equipment monitoring indicators, the stage of configuring equipment monitoring indicators may include: 1.1 Obtaining a list of equipment types: the administrator requests the management console through the front end to obtain a list of equipment types that can be configured for monitoring; 1.2 Obtaining a list of equipment types: the management console requests the facility operation and maintenance management module to obtain a list of equipment types that can be configured for monitoring; 1.3 Return: the facility operation and maintenance management module returns a list of equipment types that can be configured for monitoring to the management console; 1.4 Return: the management console returns a list of equipment types that can be configured for monitoring to the administrator's front end; 1.5 Obtaining an indicator list: the administrator requests the management console through the front end to obtain a list of indicators that can be monitored by equipment of each equipment type; 1.6 Obtaining an indicator list: the management console requests the facility operation and maintenance management module to obtain a list of equipment types that can be configured for monitoring; Get the list of indicators that can be monitored by devices of each device type; 1.7 Return: the facility operation and maintenance management module returns the list of indicators that can be monitored by devices of each device type to the management console; 1.8 Return: the management console returns the list of indicators that can be monitored by devices of each device type to the administrator's front end; 1.9 Save equipment monitoring indicators: the administrator requests the management console through the front end to save the indicators required to be monitored for devices of each device type; 1.10 Save equipment monitoring indicators: the management console saves the indicators required to be monitored selected for devices of each device type to the operation and maintenance monitoring management module; 1.11 Return: the operation and maintenance monitoring management module returns response information to the management console; 1.12 Return: the management console returns response information to the administrator's front end.

[0133] The stage of obtaining device monitoring data may include: 1.2 Obtaining device monitoring indicators: The administrator requests the management station to obtain device monitoring indicator data through the front end; 1.3 Obtaining device monitoring indicators: The management station requests the operation and maintenance monitoring management module to obtain the indicators to be monitored; 1.4 Return: The operation and maintenance monitoring management module returns the indicators to be monitored to the management station; 1.5 Query indicator data: The management station requests the data access management module to query the corresponding indicator data according to the indicators to be monitored, and the data access management module can obtain the corresponding indicator data from Prometheus; 1.6 Return: The data access management module returns the corresponding indicator data to the management station; 1.7 Assemble data: The management station assembles data, such as format conversion, packaging data into a predetermined data structure, etc. 1.8 Return: The management station returns the requested monitoring indicator data to the front end.

[0134] In one embodiment of the present application, the method may further include the following steps: when a data analysis request triggered at the end of the current cycle is received, obtaining from the target time series database the original indicator data corresponding to at least one monitoring indicator collected at predetermined time periods during the current cycle; for each monitoring indicator, obtaining statistical result data corresponding to the monitoring indicator and the current cycle based on statistics of the original indicator data corresponding to the monitoring indicator collected at predetermined time periods during the current cycle, and storing the statistical result data.

[0135] Each cycle can be 24 hours, and the current cycle can be the 24 hours before the current time; therefore, a data analysis request can be triggered at 00:00:01 every day. The scheduled time period can be of any length, for example, 5 minutes or 10 minutes; for different monitoring indicators, the corresponding raw indicator data can be collected based on scheduled time periods of different lengths.

[0136] The statistical result data of the monitoring indicator may be, for example, the average value, maximum value, minimum value, etc. of the original indicator data corresponding to the monitoring indicator.

[0137] After storing the various statistical result data, the various statistical result data can be returned to the front end according to the request from the administrator's front end for the administrator to analyze.

[0138] In one embodiment of the present application, after obtaining the original indicator data corresponding to at least one monitoring indicator collected at predetermined time periods within the current cycle from the target time series database, the method further includes: for each monitoring indicator, determining the abnormal point data corresponding to the monitoring indicator and the current cycle based on the original indicator data corresponding to the monitoring indicator collected at time periods corresponding to the monitoring indicator within the current cycle, and storing the abnormal point data.

[0139] Corresponding alarm notifications can be generated based on abnormal point data and pushed to the front end.

[0140] In the embodiment of the present application, the system can automatically analyze abnormal point data to detect faults in a timely manner.

[0141] Fig.21 A timing diagram of daily power analysis of a computer room according to an embodiment of the present application is shown. Fig.21 As shown, it involves scheduled tasks, operation and maintenance monitoring management module, facility operation and maintenance management module, data access management module and Prometheus.

[0142] The scheduled task will trigger the scheduled trigger data analysis at 00:00:01 every morning. Specifically, the following content can be analyzed: The equipment power analysis (cabinet, air conditioner) stage can include: 1.1 Query the indicator data of daily power consumption of (cabinet, air conditioner) equipment: the operation and maintenance monitoring management module requests the data access management module to query the daily power consumption of cabinets, air conditioners and other equipment; 1.2 Query data: the data access management module requests to obtain the daily power consumption data of cabinets, air conditioners and other equipment from Prometheus; 1.3 Return: Prometheus returns the daily power consumption data of cabinets, air conditioners and other equipment to the data access management module; 1.4 Return data: the data access management module returns the daily power consumption data of cabinets, air conditioners and other equipment to the operation and maintenance monitoring management module; 1.5 Calculate the daily power consumption of equipment on a month-on-month basis: for each device, the operation and maintenance monitoring management module calculates the month-on-month change data of the daily power consumption of the device relative to the daily power consumption of the device on the previous day; 1.6 Store data in the om_energy_analysis_daily_electricity table: the operation and maintenance monitoring management module stores the daily power consumption data and month-on-month change data of each device in the database table.

[0143] The hot and cold channel analysis stage of the computer room may include: 2.1 Query the index data of temperature and humidity of the hot and cold channel sensors in the computer room every 5 minutes: the operation and maintenance monitoring management module requests the data access management module to query the temperature and humidity data collected every 5 minutes by the hot and cold channel sensors in the computer room; 2.2 Query data: the data access management module requests to query the temperature and humidity data collected every 5 minutes by the hot and cold channel sensors in the computer room from Prometheus; 2.3 Return: Prometheus returns the temperature and humidity data collected every 5 minutes by the hot and cold channel sensors in the computer room to the data access management module; 2.4 Return data: the data access management module requests the operation and maintenance monitoring management module to query the temperature and humidity data collected every 5 minutes by the hot and cold channel sensors in the computer room from Prometheus; Return the temperature and humidity data collected by the hot and cold channel sensors in the computer room every 5 minutes; 2.5 Calculate the daily average temperature and humidity, maximum temperature and humidity, etc. of the hot and cold channels: The operation and maintenance monitoring and management module calculates the daily average temperature and humidity, maximum temperature and humidity, etc. of the hot and cold channels based on the acquired temperature and humidity data; 2.6 Store the data in the om_energy_analysis_daily_environment table: The operation and maintenance monitoring and management module stores the calculated daily average temperature and humidity, maximum temperature and humidity, etc. of the hot and cold channels in the database; 2.7 Calculate the abnormal point data: The operation and maintenance monitoring and management module determines the abnormal point data based on the acquired temperature and humidity data;

[0144] 2.8 Store data in the om_energy_analysis_daily_abnormal table: The operation and maintenance monitoring management module stores abnormal point data in the database.

[0145] The daily analysis of the temperature and humidity of the cabinets in the computer room can query the data according to each cabinet column. The daily analysis stage of the temperature and humidity of the cabinets in the computer room can include: 2.1 Query the index data of the temperature and humidity of the cabinet column every 5 minutes: the operation and maintenance monitoring management module requests the data access management module to query the temperature and humidity data collected every 5 minutes for each cabinet in the cabinet column; 2.2 Query data: the data access management module requests to query the temperature and humidity data collected every 5 minutes for each cabinet in the cabinet column from Prometheus; 2.3 Return: Prometheus returns the temperature and humidity data collected every 5 minutes for each cabinet in the cabinet column to the data access management module; 2.4 Return data: the data access management module returns the temperature and humidity data collected every 5 minutes for each cabinet in the cabinet column to the operation and maintenance monitoring management module; 2.5 Calculate the average temperature of the cabinet Humidity, maximum temperature and humidity, etc.: The operation and maintenance monitoring and management module calculates the average temperature and humidity, maximum temperature and humidity and other data of each cabinet in the cabinet row based on the acquired data; 2.6 Store data in the om_energy_analysis_daily_environment table: The operation and maintenance monitoring and management module stores the calculated average temperature and humidity, maximum temperature and humidity and other data in the database; 2.7 Calculate abnormal point data: The operation and maintenance monitoring and management module determines the abnormal point data based on the acquired temperature and humidity data; 2.8 Store data in the om_energy_analysis_daily_abnormal table: The operation and maintenance monitoring and management module stores the abnormal point data in the database.

[0146] The abnormal point data stage of the computer room may specifically include the following steps: 2.9 Calculate abnormal point data: The operation and maintenance monitoring management module calculates the abnormal point data of the entire computer room based on all the acquired data; 2.10 Store data in the om_energy_analysis_daily_abnormal table: The operation and maintenance monitoring management module stores the abnormal point data of the entire computer room in the database.

[0147] The daily data summary stage of the computer room may include: 3.1 Query the basic information of the computer room: the operation and maintenance monitoring management module requests the facility operation and maintenance management module to query the basic information of the computer room; 3.2 Return data: the facility operation and maintenance management module returns the basic information of the computer room to the operation and maintenance monitoring management module; 3.3 Calculate summary data: the operation and maintenance monitoring management module calculates the summary data based on the obtained basic information of the computer room and the data calculated in the above stages; 3.4 Storing data in the om_energy_analysis_daily_summary table: the operation and maintenance monitoring management module stores the summary data in the database.

[0148] When the daily data aggregation phase of the computer room is over, you can execute step: 3.5 Scheduled task execution completed: notify the scheduled task module that the scheduled task has been completed.

[0149] The following describes an apparatus embodiment of the present application, which can be used to execute the device data management method of the IDC room in the above embodiment of the present application. For details not disclosed in the apparatus embodiment of the present application, please refer to the embodiment of the device data management method of the IDC room in the above embodiment of the present application.

[0150] Fig. 22 A block diagram of an equipment data management device for an IDC computer room according to an embodiment of the present application is shown. Fig. 22 As shown, according to an embodiment of the present application, an equipment data management device 2200 for an IDC computer room includes: a configuration data returning unit 2210 , a connection parameter returning unit 2220 and a data storage unit 2230 . Among them, the configuration data returning unit 2210 is used to return mapping configuration data to the target acquisition plug-in according to a mapping configuration acquisition request from the target acquisition plug-in, the mapping configuration data including the original indicators of the target data source corresponding to the target acquisition plug-in and the mapping relationship between the original indicators and the target indicators, the target data source is one of multiple data sources, and the multiple data sources are used to provide relevant data of each device in the IDC computer room; the connection parameter returning unit 2220 is used to return the connection parameters of the target data source corresponding to the target acquisition plug-in to the target acquisition plug-in according to the connection parameter acquisition request from the target acquisition plug-in, so that the target acquisition plug-in can obtain the original indicator data corresponding to the original indicator from the target data source after establishing a connection with the target data source according to the connection parameters, and convert the original indicator data into target indicator data corresponding to the target indicator according to the mapping relationship between the original indicator and the target indicator; the data storage unit 2230 is used to store the target indicator data when receiving a data storage request carrying the target indicator data from the target acquisition plug-in.

[0151] Fig.23 A schematic diagram of the structure of a computer system suitable for implementing an electronic device of an embodiment of the present application is shown.

[0152] It should be noted that Fig.23 The computer system 2300 of the electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0153] like Fig.23As shown, the computer system 2300 includes a central processing unit (CPU) 2301, which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM) 2302 or the program loaded from the storage part 2308 to the random access memory (RAM) 2303, such as executing the method described in the above embodiment. In RAM 2303, various programs and data required for system operation are also stored. CPU 2301, ROM 2302 and RAM 2303 are connected to each other through bus 2304. Input / output (I / O) interface 2305 is also connected to bus 2304.

[0154] The following components are connected to the I / O interface 2305: an input section 2306 including a keyboard, a mouse, etc.; an output section 2307 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 2308 including a hard disk, etc.; and a communication section 2309 including a network interface card such as a LAN (Local Area Network) card, a modem, etc. The communication section 2309 performs communication processing via a network such as the Internet. A drive 2310 is also connected to the I / O interface 2305 as needed. A removable medium 2311, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 2310 as needed so that a computer program read therefrom is installed into the storage section 2308 as needed.

[0155] In particular, according to an embodiment of the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present application includes a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 2309, and / or installed from the removable medium 2311. When the computer program is executed by the central processing unit (CPU) 2301, various functions defined in the system of the present application are executed.

[0156] It should be noted that the computer-readable medium shown in the embodiment of the present application may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, - but not limited to - an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, a computer-readable storage medium may be any tangible medium containing or storing a program, which may be used by an instruction execution system, device or device or used in combination with it. In the present application, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, wherein a computer-readable program code is carried. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, which may send, propagate, or transmit programs for use by or in conjunction with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0157] The flowchart and block diagram in the accompanying drawings illustrate the possible architecture, functions and operations of the system, method and computer program product according to various embodiments of the present application. Wherein, each box in the flowchart or block diagram can represent a module, a program segment, or a part of the code, and the above-mentioned module, program segment, or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flowchart, and the combination of boxes in the block diagram or flowchart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0158] The units involved in the embodiments described in this application may be implemented by software or hardware, and the units described may also be set in a processor. The names of these units do not, in some cases, constitute limitations on the units themselves.

[0159] As one aspect, the present application also provides a computer-readable medium, which may be included in the electronic device described in the above embodiment; or may exist independently without being assembled into the electronic device. The above computer-readable medium carries one or more programs, and when the above one or more programs are executed by an electronic device, the electronic device implements the method described in the above embodiment.

[0160] It should be noted that, although several modules or units of the equipment for action execution are mentioned in the above detailed description, this division is not mandatory. In fact, according to the embodiments of the present application, the features and functions of two or more modules or units described above can be embodied in one module or unit. On the contrary, the features and functions of one module or unit described above can be further divided into being embodied by multiple modules or units.

[0161] Through the description of the above implementation methods, it is easy for those skilled in the art to understand that the example implementation methods described here can be implemented by software or by combining software with necessary hardware. Therefore, the technical solution according to the implementation methods of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which can be a personal computer, a server, a touch terminal, or a network device, etc.) to execute the method according to the implementation methods of the present application.

[0162] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the embodiments disclosed herein. The present application is intended to cover any variations, uses or adaptations of the present application, which follow the general principles of the present application and include common knowledge or customary technical means in the art that are not disclosed in the present application.

[0163] It should be understood that the present application is not limited to the precise structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.

Claims

1. A method for managing equipment data in an IDC computer room, characterized in that: The method comprises: According to a mapping configuration acquisition request from a target acquisition plug-in, mapping configuration data is returned to the target acquisition plug-in, wherein the mapping configuration data includes an original indicator of a target data source corresponding to the target acquisition plug-in and a mapping relationship between the original indicator and the target indicator, wherein the target data source is one of a plurality of data sources, and the plurality of data sources are used to provide relevant data of each device in the IDC computer room; According to a connection parameter acquisition request from the target acquisition plug-in, the connection parameters of the target data source corresponding to the target acquisition plug-in are returned to the target acquisition plug-in, so that after the target acquisition plug-in establishes a connection with the target data source according to the connection parameters, the target acquisition plug-in acquires the original indicator data corresponding to the original indicator from the target data source, and converts the original indicator data into the target indicator data corresponding to the target indicator according to the mapping relationship between the original indicator and the target indicator; When a data storage request carrying the target indicator data is received from the target acquisition plug-in, the target indicator data is stored.

2. The device data management method of the IDC computer room according to claim 1, characterized in that: The target acquisition plug-in sends the mapping configuration acquisition request after receiving a mapping configuration change notification, and the mapping configuration change notification is generated after the mapping configuration data newly configured by the administrator is updated locally.

3. The device data management method of the IDC computer room according to claim 1, characterized in that: The target acquisition plug-in establishes a heartbeat connection with the target data source after logging into the target data source, and the target data source pushes the original indicator data corresponding to the original indicator to the target acquisition plug-in when the heartbeat connection is maintained.

4. The device data management method of the IDC computer room according to claim 3 is characterized in that: The target acquisition plug-in logs in to the target data source by preempting the current process as the login process. The target acquisition plug-in accesses the target data source based on token information obtained from the target data source after logging in to the target data source. The token information and the key corresponding to the token information are stored in the form of a key-value pair in a cache corresponding to the target acquisition plug-in. The target acquisition plug-in maintains the heartbeat connection by sending heartbeat information to the target data source at predetermined intervals, and the predetermined duration is less than the timeout duration of the key.

5. The device data management method of the IDC computer room according to claim 4, characterized in that: The target data source pushes the original indicator data corresponding to the original indicator to the target acquisition plug-in according to the subscription strategy provided by the target acquisition plug-in, and the subscription strategy is obtained by the target data source from the subscription request from the target acquisition plug-in.

6. The device data management method of the IDC computer room according to claim 5, characterized in that: The subscription request is generated by the target acquisition plug-in after obtaining token information from the target data source. The subscription request carries the token information. The target data source saves the subscription policy when confirming that the token information in the subscription request is valid.

7. The device data management method of the IDC computer room according to claim 5, characterized in that: The subscription strategy is one of the following: each time the original indicator data corresponding to the original indicator is collected, the original indicator data is pushed to the target collection plug-in; each time the original indicator data corresponding to the collected original indicator changes, the changed original indicator data corresponding to the original indicator is pushed to the target collection plug-in; the original indicator data corresponding to the original indicator is pushed to the target collection plug-in at specified intervals.

8. An equipment data management device for an IDC computer room, characterized in that: The device comprises: a configuration data returning unit, configured to return mapping configuration data to the target acquisition plug-in according to a mapping configuration acquisition request from the target acquisition plug-in, wherein the mapping configuration data includes an original indicator of a target data source corresponding to the target acquisition plug-in and a mapping relationship between the original indicator and the target indicator, wherein the target data source is one of a plurality of data sources, and the plurality of data sources are used to provide relevant data of each device in the IDC computer room; a connection parameter returning unit, configured to return the connection parameters of the target data source corresponding to the target acquisition plug-in to the target acquisition plug-in according to the connection parameter acquisition request from the target acquisition plug-in, so that after the target acquisition plug-in establishes a connection with the target data source according to the connection parameters, it acquires the original indicator data corresponding to the original indicator from the target data source, and converts the original indicator data into target indicator data corresponding to the target indicator according to the mapping relationship between the original indicator and the target indicator; The data storage unit is used to store the target indicator data upon receiving a data storage request carrying the target indicator data from the target acquisition plug-in.

9. A computer readable medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the device data management method for an IDC computer room according to any one of claims 1 to 7 is implemented.

10. An electronic device, characterized in that: include: one or more processors; A storage device for storing one or more programs, when the one or more programs are executed by the one or more processors, enables the one or more processors to implement the device data management method for an IDC computer room as described in any one of claims 1 to 7.

Images