CN114416496B

CN114416496B - Monitoring data display method, device, electronic device and readable storage medium

Info

Publication number: CN114416496B
Application number: CN202210024904.2A
Authority: CN
Inventors: 杨冠飞
Original assignee: Beijing Kingsoft Cloud Network Technology Co Ltd
Current assignee: Beijing Kingsoft Cloud Network Technology Co Ltd
Priority date: 2022-01-11
Filing date: 2022-01-11
Publication date: 2025-07-01
Anticipated expiration: 2042-01-11
Also published as: CN114416496A

Abstract

The embodiment of the application provides a monitoring data display method, a device, electronic equipment and a readable storage medium, and relates to the technical field of cloud, wherein the method comprises the steps of receiving a component identifier of a first component as the first component identifier; the method comprises the steps of obtaining a registry recorded with a first component identifier from a plurality of registries which are generated in advance to be used as a first registry, obtaining a relationship attribute table recorded with the registry identifier of the first registry from a plurality of relationship attribute tables which are generated in advance to be used as a first relationship attribute table, obtaining monitoring data of a first node which the first component belongs to according to a node identifier corresponding to the registry identifier of the first registry in the first relationship attribute table, and displaying the monitoring data in a monitoring data display page. Based on the above processing, the user is enabled to view the operation state of the corresponding node based on the component.

Description

Monitoring data display method and device, electronic equipment and readable storage medium

Technical Field

The present application relates to the field of cloud technologies, and in particular, to a method and apparatus for displaying monitoring data, an electronic device, and a readable storage medium.

Background

With the rapid development of cloud technology, cloud services may be provided based on clusters (e.g., mongoDB-based clusters). In particular, different components (e.g., mongos components, shard components) may be deployed in the nodes that the cluster contains. Mongos components represent routes for data queries and data writes, shard components are used to store data. The Mongos component may distribute data read/write requests to the Shard component, which is responded to by the Shard component to complete the data read/write.

However, in the related art, a corresponding method is not provided so that a user can view the operation state of a corresponding node based on a component.

Disclosure of Invention

The embodiment of the application aims to provide a monitoring data display method, a device, electronic equipment and a readable storage medium, so that a user can view the running state of a corresponding node based on a component. The specific technical scheme is as follows:

In a first aspect of the present application, there is provided a method for displaying monitoring data, the method comprising:

Receiving a component identifier of a first component as the first component identifier;

acquiring a registry recorded with the first component identifier from a plurality of registries which are generated in advance, and taking the registry as a first registry;

Acquiring a relationship attribute table recorded with a registry identifier of the first registry from a plurality of relationship attribute tables which are generated in advance as a first relationship attribute table;

And acquiring monitoring data of the first node to which the first component belongs according to a node identifier corresponding to the registry identifier of the first registry in the first relation attribute table, and displaying the monitoring data in a monitoring data display page.

Optionally, the method further comprises:

receiving a registration request for a second node;

And generating a registry of the second node as a second registry according to the registration request, wherein the second registry is recorded with a node identifier, a network address, a node name and a machine room name of the machine room to which the second node belongs.

Optionally, after the receiving the registration request of the second node, the method further includes:

Generating a registry of the second component deployed in the second node as a third registry, wherein the third registry is recorded with a component identifier, a type identifier and a machine room name of a machine room to which the second component belongs.

Optionally, after the generating the registry of the second component deployed in the second node as the third registry, the method further includes:

and generating a second relation attribute table, wherein the second relation attribute table comprises a corresponding relation between a registry identifier of the third registry and a node identifier of the second node.

Optionally, after the generating the second relationship attribute table, the method further includes:

Receiving a delete request for the second node;

Deleting the second registry, the third registry and the second relationship attribute table.

Optionally, before the receiving the component identifier of the first component as the first component identifier, the method further includes:

Reading a pre-configured relation display table, wherein the relation display table is used for recording the type identification of a currently deployed component in a cluster;

displaying the type identifier recorded in the relation display table;

When a type identifier selection instruction is received, determining a registry recorded with the type identifier indicated by the type identifier selection instruction from the multiple registries as a fourth registry;

displaying the component identification recorded in the fourth registry;

The receiving component identifier, as a first component identifier, includes:

When a component identification selection instruction is received, determining the component identification indicated by the component identification selection instruction as a first component identification from the displayed component identifications.

In a second aspect of the present application, there is provided a monitoring data display apparatus, the apparatus comprising:

the first component identification acquisition module is used for receiving the component identification of the first component and taking the component identification as the first component identification;

the first registry acquisition module is used for acquiring a registry recorded with the first component identifier from a plurality of registries which are generated in advance and used as a first registry;

The first relation attribute table acquisition module is used for acquiring a relation attribute table recorded with a registry identifier of the first registry from a plurality of relation attribute tables which are generated in advance as a first relation attribute table;

and the first display module is used for acquiring the monitoring data of the first node to which the first component belongs according to the node identifier corresponding to the registry identifier of the first registry in the first relation attribute table and displaying the monitoring data in a monitoring data display page.

Optionally, the apparatus further includes:

A registration request acquisition module, configured to receive a registration request for a second node;

and the second registry generation module is used for generating a registry of the second node according to the registration request and taking the registry as a second registry, wherein the node identification, the network address, the node name and the machine room name of the machine room to which the second node belongs are recorded in the second registry.

Optionally, the apparatus further includes:

And the second registry generation module is used for generating a registry of a second component deployed in the second node as a third registry after receiving the registration request of the second node, wherein the third registry is recorded with the component identifier, the type identifier and the machine room name of the machine room to which the second component belongs.

Optionally, the apparatus further includes:

And the second relation attribute table generation module is used for generating a second relation attribute table after generating the registry of the second component deployed in the second node as a third registry, wherein the second relation attribute table comprises the corresponding relation between the registry identifier of the third registry and the node identifier of the second node.

Optionally, the apparatus further includes:

a deletion request obtaining module, configured to receive a deletion request for the second node after the second relationship attribute table is generated;

and the deleting module is used for deleting the second registry, the third registry and the second relation attribute table.

Optionally, the apparatus further includes:

the relation display table acquisition module is used for reading a pre-configured relation display table before receiving the component identifier of the first component as the first component identifier, wherein the relation display table is used for recording the type identifier of the currently deployed component in the cluster;

The second display module is used for displaying the type identifier recorded in the relation display table;

a fourth registry determining module, configured to determine, when receiving a type identifier selection instruction, a registry in which a type identifier indicated by the type identifier selection instruction is recorded from the multiple registries as a fourth registry;

the third display module is used for displaying the component identifiers recorded in the fourth registry;

The first component identifier obtaining module is specifically configured to determine, when a component identifier selection instruction is received, from the displayed component identifiers, that the component identifier indicated by the component identifier selection instruction is the first component identifier.

The embodiment of the application also provides electronic equipment, which comprises a processor, a communication interface, a memory and a communication bus, wherein the processor and the communication interface, and the memory are communicated with each other through the communication bus;

A memory for storing a computer program;

and the processor is used for realizing any one of the monitoring data display methods when executing the program stored in the memory.

The embodiment of the application also provides a computer readable storage medium, wherein a computer program is stored in the computer readable storage medium, and the computer program realizes any one of the monitoring data display methods when being executed by a processor.

The embodiment of the application also provides a computer program product containing instructions, which when run on a computer, cause the computer to execute the monitoring data display method described in any one of the above.

The embodiment of the application has the beneficial effects that:

The monitoring data display method provided by the embodiment of the application receives the component identification of the first component as the first component identification, acquires the registry recorded with the first component identification from a plurality of registries generated in advance as the first registry, acquires the relationship attribute table recorded with the registry identification of the first registry from a plurality of relationship attribute tables generated in advance as the first relationship attribute table, acquires the monitoring data of the first node which the first component belongs to according to the node identification corresponding to the registry identification of the first registry in the first relationship attribute table, and displays the monitoring data in a monitoring data display page.

Based on the above processing, the corresponding relation between the registry identifier and the node is recorded through the relation attribute table, and the corresponding component can be determined through the registry, and then, the node corresponding to the first component represented by the first component identifier, namely, the node deploying the first component, can be determined through combining the registry and the relation attribute table, and the monitoring data of the node is displayed, so that a user can view the running state of the corresponding node based on the component.

Of course, it is not necessary for any one product or method of practicing the application to achieve all of the advantages set forth above at the same time.

Drawings

In order to more clearly illustrate the embodiments of the application or the technical solutions in the prior art, the drawings used in the embodiments or the description of the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the application, and other embodiments may be obtained according to these drawings to those skilled in the art.

FIG. 1 is a flowchart of a method for displaying monitoring data according to an embodiment of the present application;

FIG. 2 is a flowchart of another method for displaying monitoring data according to an embodiment of the present application;

FIG. 3 is a schematic diagram of a page displaying monitoring data according to an embodiment of the present application;

Fig. 4 is a schematic diagram of a monitoring data display according to an embodiment of the present application;

FIG. 5 is a block diagram of a monitor data display device according to an embodiment of the present application;

fig. 6 is a block diagram of an electronic device according to an embodiment of the present application.

Detailed Description

The following description of the embodiments of the present application will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present application, but not all embodiments. Based on the embodiments of the present application, all other embodiments obtained by the person skilled in the art based on the present application are included in the scope of protection of the present application.

The embodiment of the application provides a monitoring data display method which can be applied to electronic equipment, wherein the electronic equipment can communicate with each node (e.g. a host machine) in a cluster to acquire monitoring data of each node, and the monitoring data is displayed based on the method provided by the embodiment of the application.

Referring to fig. 1, fig. 1 is a flowchart of a method for displaying monitoring data according to an embodiment of the present application, where the method may include the following steps:

S101, receiving the component identification of the first component as the first component identification.

S102, acquiring a registry recorded with the first component identifier from a plurality of registries which are generated in advance as a first registry.

S103, acquiring a relationship attribute table recorded with a registry identifier of a first registry from a plurality of relationship attribute tables which are generated in advance as the first relationship attribute table.

S104, according to the node identification corresponding to the registry identification of the first registry in the first relation attribute table, acquiring the monitoring data of the first node to which the first component belongs, and displaying the monitoring data in a monitoring data display page.

According to the monitoring data display method provided by the embodiment of the application, the corresponding relation between the registry identifier and the node is recorded through the relation attribute table, the corresponding component can be determined through the registry, and then, the node corresponding to the first component represented by the first component identifier, namely, the node for deploying the first component can be determined by combining the registry and the relation attribute table, and the monitoring data of the node is displayed, so that a user can view the running state of the corresponding node based on the component.

For step S101, the component identification is used to represent the uniqueness of the component. The components in the embodiment of the present application are components deployed in nodes in a cluster, for example, for a cluster based on MongoDB, the components deployed in the nodes may be Mongos components or Shard components.

In one implementation, the electronic device may assign a random number to each component deployed as a component identifier for the component, e.g., may assign a UUID (Universally Unique Identifier, universal unique identifier) to each component as a component identifier for the component.

For step S102, the first registry is used to record the registration information of the first component characterized by the first component identifier, that is, each component may correspond to a registry, which is used to record the registration information of the component, where the registration information includes the component identifier of the component. In addition, the registration information may further include a type identifier of the component and a machine room name of the machine room to which the component belongs.

Wherein the type identification of the component is used to represent the component type of the component. In one implementation, the component type for the component may be represented by a type value, e.g., for MongoDB-based clusters, the Mongos component may be represented by a type value 51 and the Shard component may be represented by a type value 53.

The machine room name of the machine room to which the component belongs, that is, the machine room name of the machine room to which the node deploying the component belongs.

For step S103, the registry identifier of the first registry is used to represent the uniqueness of the first registry, that is, each registry may be assigned an identifier as a registry identifier. For example, each registry may be assigned an ID based on the manner of self-increasing ID as a registry identification for that registry. Accordingly, each registry may also record the registry identification of that registry.

The first relationship attribute table is used for recording the corresponding relationship between the registry identifier of the first registry and the node to which the first component belongs, that is, in the application, the corresponding relationship between the registry of the component and the node can be recorded through the relationship attribute table, so that the corresponding relationship between the component and the node, that is, the corresponding relationship between the node and the component deployed in the node can be represented through the relationship attribute table.

For step S104, after the node is online, the monitoring data may be periodically sent to the electronic device. The monitoring data may include at least one of memory usage, QPS (Queries Per Second, query rate per second), current connection number, consumed network traffic, maximum number of cursors (Cursors). Thus, after determining the first relationship attribute table and determining the node identifier corresponding to the registry identifier of the first registry in the first relationship attribute table, a node characterized by the node identifier (i.e., a first node), i.e., a node deploying the first component, may be determined. Furthermore, the electronic device can screen the monitoring data of the first node from the monitoring data of each node, and display the monitoring data in the monitoring data display page.

In one embodiment, referring to fig. 2, the method may further include the following steps, based on fig. 1, before the step S101 described above:

s105, reading a preconfigured relation display table.

The relation display table is used for recording type identification of currently deployed components in the cluster.

S106, displaying the type identifier recorded in the relation display table.

And S107, when the type identifier selection instruction is received, determining a registry recorded with the type identifier indicated by the type identifier selection instruction from a plurality of registries as a fourth registry.

S108, displaying the component identification recorded in the fourth registry.

Accordingly, the step S101 may include:

S1011, when a component identification selection instruction is received, determining the component identification indicated by the component identification selection instruction as a first component identification from the displayed component identifications.

In the embodiment of the application, the electronic equipment can be locally configured with a relation display table, wherein the type identification of the currently deployed component in the cluster is recorded.

For example, the fields contained in the relationship presentation table may be referred to in table (1).

Watch (1)

Fields	Type(s)	Key	Summary description
				ID	Bigint	Self-increment ID
Top_type	Int		Top layer type
				Child_type	Int	Subtype
Child_name	Varchar(128)		Component name
				Mark	Varchar(128)	Remarks

As can be seen from Table (1), the relationship display table may include an ID field for indicating an identity of a relationship display table, a Top_type field for indicating a Top-level type of the relationship display table record, a child_type field for indicating a subtype of the relationship display table record, a child_name field for indicating a component name of the relationship display table record (i.e., a component name corresponding to the subtype), and a Mark field for recording remark information. The "type" column is used to identify the type of value for each field. A column of "key" indicates a specific numerical value for each field. Bigint denotes a system data type of Transact-SQL, int denotes an integer type, varchar (128) denotes a variable length string type allowing a maximum length of a saved string to be 128 characters.

Referring to table (2), table (2) is a relationship display table provided in the embodiment of the present application.

Watch (2)

As can be seen from Table (2), the type value of Mongos components is denoted by "51", the type value of Shard components is denoted by "53", and 50 denotes the type value of the node, i.e., the node is the top level of each component, which may also be referred to as the parent level of each component, and accordingly, each component may be referred to as a child class of the node. It will be appreciated that if the cluster is also deployed with other components, other values besides 51 and 53 may be used to represent the type values.

Based on the relationship presentation table, a type value (i.e., child_type) for each subclass may be determined, along with a corresponding type identification (i.e., child_name). For example, based on table (2), the type identifications recorded in the relationship presentation table can be found to include Mongos and Shard.

In one implementation, referring to fig. 3, the electronic device may display a drop down menu containing Mongos and Shard type identifications in the monitored data presentation page. Accordingly, the user may select Mongos or Shard in the drop down menu to view the monitoring data for the corresponding node based on the Mongos component or Shard component.

Furthermore, the electronic device may receive the type identifier selection instruction, and determine, from among the registries recorded locally, a registry in which the type identifier indicated by the type identifier selection instruction is recorded (i.e., a fourth registry), where the determined fourth registry may be one or more. For example, when the user selects Mongos, the electronic device may determine that the registry of Mongos components deployed in the nodes of the cluster is the fourth registry, and when the user selects Shard, the electronic device may determine that the registry of Shard components deployed in the nodes of the cluster is the fourth registry.

The electronic device may then display the determined component identification recorded in the fourth registry. If the fourth registry is determined to be one, the displayed components are identified as one, and if the fourth registry is determined to be a plurality of, the displayed components are identified as a plurality of. For example, the electronic device may display the component identities of Mongos components deployed in the nodes of the cluster when the user selects Mongos, and the electronic device may display the component identities of Shard components deployed in the nodes of the cluster for user selection when the user selects Shard.

Referring to fig. 3, in fig. 3, upon user selection Mongos, on the right side of "monitor type", the electronic device may display the component identification of Mongos components deployed in the nodes of the cluster for user selection.

After the user selects the corresponding component identifier, the electronic device can acquire the monitoring data of the corresponding node based on the method provided by the embodiment of the application and display the monitoring data in the monitoring data display page. For example, referring to fig. 3, in fig. 3, the electronic device may display the CPU usage of the node to which the Mongos component selected by the user belongs. Additionally, based on other controls in fig. 3, memory usage, number of connections, network traffic, QPS, cursors, or current connection percentages of the display node may also be selected. When displaying the monitoring data, a time period corresponding to the monitoring data to be displayed may be set, for example, the monitoring data within 0.5 hour before the monitoring data, the monitoring data within 1 day before the monitoring data, the monitoring data within 3 days before the monitoring data, the monitoring data within 1 week before the monitoring data are displayed, or the user may customize the time period.

In one embodiment, the method may further comprise the steps of:

Step one, a registration request for a second node is received.

And step two, generating a registry of the second node according to the registration request, and taking the registry as a second registry.

The second registry records the node identification, the network address, the node name and the machine room name of the machine room to which the second node belongs.

In the embodiment of the present application, after a new node (i.e., a second node) is online, the node may send a registration request to the electronic device through an API (Application Programming Interface, application program interface), and further, the electronic device may generate a registry of the second node, for recording registration information of the second node.

The electronic device may assign a random number to each node as the node identifier of the node, for example, may assign a UUID to each node as the node identifier of the node.

That is, in the present application, corresponding registries may be generated for both nodes and components. For example, the registry may contain fields that are referred to in Table (3).

Watch (3)

As can be seen from table (3), the registry may include an ID field for indicating a registry identifier of a registry, a UUID field for indicating a UUID of a node/component, a GuestIP field for indicating an IP address of the node, productType for indicating a type value of the node/a type value of the component, a Name field for indicating a Name of the node/a Name of the component, and an IDC field for indicating a machine room Name of a machine room to which the node belongs/a machine room to which the component belongs (i.e., a machine room Name of a machine room to which the machine room of the node belongs). The "type" column is used to identify the type of value for each field. A column of "key" indicates a specific numerical value for each field.

In one embodiment, after receiving the registration request for the second node, the method may further comprise the steps of:

and thirdly, generating a registry of the second component deployed in the second node as a third registry.

The third registry is recorded with the component identifier, the type identifier and the machine room name of the machine room to which the second component belongs.

In the embodiment of the application, when a new node is online, the electronic equipment can acquire the registration information of the components deployed in the node and generate the registry corresponding to the components.

In one embodiment, after generating the third registry, the method may further comprise the steps of:

and step four, generating a second relation attribute table.

The second relation attribute table comprises a corresponding relation between a registry identifier of the third registry and a node identifier of the second node.

In the embodiment of the application, when a new node is online, the electronic equipment can also generate a corresponding relation attribute table to record the corresponding relation between the node and the registry of the components deployed therein.

For example, the fields contained in the relationship properties table may be referred to in table (4).

Watch (4)

As seen from Table (4), the relationship properties table may contain an ID Field for indicating the identity of a relationship properties table, an instance_ID Field for indicating the registry identity of the registry, i.e., the registry/node registry for a component, a Field for recording the UUID of the parent level of a component (i.e., the UUID of the node deploying the component) when the instance_ID Field indicates the registry for the component, and a Field null when the instance_ID Field indicates a node, and a Value for indicating the specific Value of the Field. The "type" column is used to identify the type of value for each field. A column of "key" indicates a specific numerical value for each field.

In one embodiment, after the fourth step, the method may further include the following steps:

and step five, receiving a deleting request aiming at the second node.

And step six, deleting the second registry, the third registry and the second relation attribute table.

In the embodiment of the application, when a node is offline, the related tables, namely the registry of the node, the registry of the components deployed therein and the relationship attribute table containing the corresponding relationship between the node and the registry of the components, can be deleted.

In one embodiment, the electronic device may also store the recorded tables to a database to enable backup of the tables. Further, when the cluster recovers from the failure, tables may be obtained from the database to continue displaying the monitoring data based on the tables.

Referring to fig. 4, fig. 4 is a schematic diagram of a monitoring data display according to an embodiment of the present application.

The monitoring service may obtain updates to the Mongo business product line, for example, determine new nodes to be online or existing nodes to be offline in the cluster of Mongo db. Further, based on the above-described update, the registered table of the node, the registered table of the component, and the relationship attribute table are updated. The monitoring service may obtain, based on each recorded table, monitoring data of a node corresponding to the component indicated by the user, and display the data. In addition, the monitoring service can store the recorded tables to the database to realize data persistence to the database and complete backup of the tables.

Based on the same inventive concept, the embodiment of the present application further provides a monitoring data display device, referring to fig. 5, fig. 5 is a structural diagram of the monitoring data display device provided by the embodiment of the present application, where the device includes:

A first component identifier obtaining module 501, configured to receive a component identifier of a first component as the first component identifier;

A first registry obtaining module 502, configured to obtain, from a plurality of registries that are generated in advance, a registry in which the first component identifier is recorded as a first registry;

a first relationship attribute table obtaining module 503, configured to obtain, from a plurality of relationship attribute tables that are generated in advance, a relationship attribute table in which a registry identifier of the first registry is recorded, as a first relationship attribute table;

The first display module 504 is configured to obtain, according to a node identifier corresponding to a registry identifier of the first registry in the first relationship attribute table, monitoring data of a first node to which the first component belongs, and display the monitoring data in a monitoring data display page.

Optionally, the apparatus further includes:

The first component identifier obtaining module 501 is specifically configured to determine, when receiving a component identifier selection instruction, from the displayed component identifiers, that the component identifier indicated by the component identifier selection instruction is the first component identifier.

According to the monitoring data display device provided by the embodiment of the application, the corresponding relation between the registry identifier and the node is recorded through the relation attribute table, the corresponding component can be determined through the registry, and then, the node corresponding to the first component represented by the first component identifier, namely, the node for deploying the first component can be determined by combining the registry and the relation attribute table, and the monitoring data of the node is displayed, so that a user can view the running state of the corresponding node based on the component.

The embodiment of the application also provides an electronic device, as shown in fig. 6, which comprises a processor 601, a communication interface 602, a memory 603 and a communication bus 604, wherein the processor 601, the communication interface 602 and the memory 603 complete communication with each other through the communication bus 604,

A memory 603 for storing a computer program;

The processor 601 is configured to execute the program stored in the memory 603, and implement the following steps:

The communication bus mentioned above for the electronic device may be a peripheral component interconnect standard (PERIPHERAL COMPONENT INTERCONNECT, PCI) bus or an extended industry standard architecture (Extended Industry Standard Architecture, EISA) bus, etc. The communication bus may be classified as an address bus, a data bus, a control bus, or the like. For ease of illustration, the figures are shown with only one bold line, but not with only one bus or one type of bus.

The communication interface is used for communication between the electronic device and other devices.

The Memory may include random access Memory (Random Access Memory, RAM) or may include Non-Volatile Memory (NVM), such as at least one disk Memory. Optionally, the memory may also be at least one memory device located remotely from the aforementioned processor.

The Processor may be a general-purpose Processor including a central processing unit (Central Processing Unit, CPU), a network Processor (Network Processor, NP), etc., or may be a digital signal Processor (DIGITAL SIGNAL Processor, DSP), application SPECIFIC INTEGRATED Circuit (ASIC), field-Programmable gate array (Field-Programmable GATE ARRAY, FPGA) or other Programmable logic device, discrete gate or transistor logic device, discrete hardware components.

In yet another embodiment of the present application, there is also provided a computer readable storage medium having stored therein a computer program which when executed by a processor implements the steps of any of the above-described monitoring data display methods.

In yet another embodiment of the present application, there is also provided a computer program product containing instructions that, when run on a computer, cause the computer to perform any of the monitoring data display methods of the above embodiments.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, produces a flow or function in accordance with embodiments of the present application, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another, for example, by wired (e.g., coaxial cable, optical fiber, digital Subscriber Line (DSL)), or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid state disk Solid STATE DISK (SSD)), etc.

It is noted that relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises an element.

In this specification, each embodiment is described in a related manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. In particular, for apparatus, systems, electronic devices, computer readable storage media, and computer program product embodiments, the description is relatively simple as it is substantially similar to method embodiments, as relevant points are found in the partial description of method embodiments.

The foregoing description is only of the preferred embodiments of the present application and is not intended to limit the scope of the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application are included in the protection scope of the present application.

Claims

1. A method of displaying monitored data, the method comprising:

2. The method according to claim 1, wherein the method further comprises:

receiving a registration request for a second node;

3. The method of claim 2, wherein after the receiving the registration request of the second node, the method further comprises:

4. A method according to claim 3, wherein after said generating a registry of a second component deployed in the second node as a third registry, the method further comprises:

5. The method of claim 4, wherein after said generating a second relationship property table, the method further comprises:

Receiving a delete request for the second node;

6. The method of claim 1, wherein prior to said receiving the component identification of the first component as the first component identification, the method further comprises:

displaying the type identifier recorded in the relation display table;

displaying the component identification recorded in the fourth registry;

The receiving component identifier, as a first component identifier, includes:

7. A monitoring data display device, the device comprising:

The system comprises a first relation attribute table acquisition module, a relation attribute table acquisition module and a node identification module, wherein the first relation attribute table acquisition module is used for acquiring a relation attribute table recorded with a registry identification of a first registry from a plurality of relation attribute tables which are generated in advance as a first relation attribute table;

8. The apparatus of claim 7, wherein the apparatus further comprises:

9. The apparatus of claim 8, wherein the apparatus further comprises:

10. The apparatus of claim 9, wherein the apparatus further comprises:

11. The apparatus of claim 10, wherein the apparatus further comprises:

12. The apparatus of claim 7, wherein the apparatus further comprises:

13. The electronic equipment is characterized by comprising a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory are communicated with each other through the communication bus;

A memory for storing a computer program;

a processor for carrying out the method steps of any one of claims 1-6 when executing a program stored on a memory.

14. A computer-readable storage medium, characterized in that the computer-readable storage medium has stored therein a computer program which, when executed by a processor, implements the method steps of any of claims 1-6.