Methods, devices, and apparatuses for configuring a topology graph of a system

Abstract

The present disclosure provides a method, device and apparatus for configuring a topology graph of a system. The method comprises: obtaining configuration information through a graphical user interface; generating drawing data with a preset format according to the configuration information; and generating and displaying a topology graph of the system according to the drawing data.

Description

Technical Field

[0001] This disclosure relates to the field of computer technology, and more specifically, to a method, apparatus, and device for configuring a system topology. Background Technology

[0002] With the development of information technology, computer systems are increasingly used to manage various business operations. Typically, a system may include multiple servers that are interconnected and communicatively linked to perform corresponding functions. However, as the number of servers in the system increases and the connections between them become more complex, the difficulty of monitoring the system also increases. For example, if one or more servers fail, it may be difficult to quickly assess the impact of such a failure on the entire system. Therefore, it is necessary to draw a system topology diagram to help improve management. Summary of the Invention

[0003] One of the purposes of this disclosure is to provide a method, apparatus, and device for configuring a system topology diagram.

[0004] According to a first aspect of this disclosure, a method for configuring a system topology diagram is provided, comprising:

[0005] Configuration information is obtained through a graphical user interface, wherein the system includes one or more subsystems, the subsystems include one or more clusters, the clusters include one or more servers, and the configuration information includes at least one of the following: server basic information associated with the server, cluster basic information associated with the cluster, subsystem basic information associated with the subsystem, server dependency information indicating the dependency relationship between the server and the cluster, cluster relationship information indicating the relationship between the clusters, and subsystem relationship information indicating the relationship between the subsystems.

[0006] Generate drawing data with a preset format based on the configuration information; and

[0007] The system topology map is generated and displayed based on the drawing data.

[0008] In some embodiments, the server basic information includes at least one of the following: server name, server number, server network address, server type, server physical address, server monitoring metrics, server monitoring metric thresholds, and server administrator information. The server type includes at least one of database server, application server, load balancer server, and caching server. The server monitoring metrics include at least one of server memory usage, server virtual machine memory usage, server disk space usage, server tablespace usage, server connection usage, and server heartbeat metrics.

[0009] The cluster basic information includes at least one of the following: cluster name, cluster number, cluster network address, cluster type, and cluster administrator information; or

[0010] The basic information of the subsystem includes at least one of the following: the name of the subsystem, the subsystem number, the network address of the subsystem, the type of the subsystem, and the administrator information of the subsystem; or

[0011] The cluster relationship information includes at least one of cluster call information and cluster nesting information, wherein the cluster call information is used to indicate the call relationship between clusters, and the cluster nesting information is used to indicate the nesting relationship between clusters, and a cluster that can directly call other clusters or be directly called by other clusters cannot contain other clusters nested within it; or

[0012] The subsystem relationship information is used to indicate the communication relationship or interface protocol between a subsystem and other subsystems located upstream or downstream of the subsystem, or to indicate the network address of other subsystems located upstream or downstream of the subsystem.

[0013] In some embodiments, the system topology is a vector diagram; or

[0014] In the system's topology diagram:

[0015] The server is configured to be represented by a node icon.

[0016] One or more node icons corresponding to one or more servers belonging to the same cluster are configured to be located in the same cluster region.

[0017] One or more cluster regions corresponding to one or more clusters belonging to the same subsystem are configured to be located in the same subsystem region.

[0018] The cluster call information in the cluster relationship information is configured to be represented by lines connecting cluster regions.

[0019] The cluster nesting information in the cluster relationship information is configured to be represented by nesting between cluster regions.

[0020] The subsystem relationship information is configured to be represented by lines connecting subsystem regions, or

[0021] The display of a node icon in configuration mode differs from that in non-configuration mode.

[0022] In some embodiments, obtaining configuration information through a graphical user interface includes:

[0023] Get configuration request;

[0024] Search the configuration information database for existing configuration information corresponding to the configuration request;

[0025] If existing configuration information is found, a graphical user interface with preloaded existing configuration information is provided for adding or modifying configuration information.

[0026] If no existing configuration information is found, an initial graphical user interface is provided for adding new configuration information.

[0027] In some embodiments, the configuration request at least indicates the name, number, or network address of the subsystem, cluster, or server to be configured.

[0028] Searching the configuration information database for existing configuration information corresponding to the configuration request includes:

[0029] The configuration information database is used to search for existing configuration information corresponding to the subsystem, cluster, or server to be configured, based on the name, number, or network address of the subsystem, cluster, or server to be configured.

[0030] In some embodiments, obtaining configuration information through a graphical user interface further includes:

[0031] The newly added or modified configuration information is stored or encrypted and stored in the configuration information database.

[0032] In some embodiments, obtaining configuration information through a graphical user interface further includes:

[0033] If existing configuration information is found, generate initial drawing data with a preset format based on the existing configuration information; and

[0034] The initial topology map of the system is generated and displayed based on the initial drawing data.

[0035] In some embodiments, obtaining configuration information through a graphical user interface includes:

[0036] Obtain a configuration request, wherein the configuration request at least indicates the type of server to be configured;

[0037] The set of monitoring metrics for a server is determined based on its type; and

[0038] A graphical user interface containing the set of monitoring indicators is provided for selecting the monitoring indicators to be monitored by the server.

[0039] In some embodiments, in a graphical user interface, the configuration information is configured to be represented by one or more lists.

[0040] In some embodiments, generating drawing data with a preset format based on the configuration information includes:

[0041] Determine whether the configuration information contains preset characters;

[0042] If the configuration information contains preset characters, the preset characters are filtered, and drawing data with a preset format is generated based on the filtered configuration information; and

[0043] If the configuration information does not contain preset characters, drawing data with a preset format is generated directly based on the configuration information.

[0044] In some embodiments, the drawing data is generated in real time based on the configuration information; or

[0045] The system's topology map is generated and displayed in real time based on the drawing data.

[0046] In some embodiments, the preset format includes JSON format; or

[0047] The topology map of the system was generated using the Mermaid plugin based on the drawing data.

[0048] In some embodiments, the system topology diagram includes a structural topology diagram indicating the system structure and a state topology diagram indicating the system operating state.

[0049] The method further includes:

[0050] Obtain monitoring request;

[0051] The system retrieves configuration information associated with the monitoring request from the configuration information database and generates and displays the system's structural topology based on the configuration information.

[0052] The monitoring metric values ​​of the corresponding server are obtained according to the monitoring request, or the monitoring metric values ​​and monitoring metric thresholds of the corresponding server are obtained according to the monitoring request; and

[0053] The system's structural topology is rendered based on the acquired monitoring index values ​​or based on the acquired monitoring index values ​​and monitoring index thresholds to generate and display the system's state topology.

[0054] In some embodiments, the operation of obtaining the configuration information corresponding to the monitoring request from the configuration information database and the operation of obtaining the monitoring indicator value of the corresponding server according to the monitoring request, or obtaining the monitoring indicator value and monitoring indicator threshold of the corresponding server according to the monitoring request, are performed simultaneously.

[0055] In some embodiments, the method further includes:

[0056] The acquired monitoring indicator values ​​are stored or encrypted and stored in the configuration information database.

[0057] In some embodiments, the method further includes:

[0058] Get the object lookup request;

[0059] Traverse the system's topology graph to determine the portion of the topology graph that matches the object lookup request; and

[0060] The portion is rendered to indicate the object corresponding to the object lookup request.

[0061] In some embodiments, the method further includes:

[0062] Get the object lookup request;

[0063] Retrieve configuration information associated with the object indicated by the object lookup request from the configuration information database; and

[0064] A topology map of the objects is generated and displayed based on the configuration information.

[0065] In some embodiments, the method further includes:

[0066] Obtain an information display request, wherein the information display request at least indicates the object whose information is to be displayed;

[0067] Retrieve configuration information associated with the object from a configuration information database or topology diagram; and

[0068] The configuration information is displayed as a details page or list overlaid on the topology map.

[0069] According to a second aspect of this disclosure, an apparatus for configuring a system topology is provided, comprising:

[0070] An information acquisition unit is configured to acquire configuration information through a graphical user interface. The system includes one or more subsystems, each subsystem includes one or more clusters, and each cluster includes one or more servers. The configuration information includes at least one of the following: server basic information associated with a server, cluster basic information associated with a cluster, subsystem basic information associated with a subsystem, server dependency information indicating the dependency relationship between a server and a cluster, cluster relationship information indicating the relationship between clusters, and subsystem relationship information indicating the relationship between subsystems.

[0071] A data conversion unit is configured to generate drawing data with a preset format based on the configuration information.

[0072] A drawing unit, configured to generate a system topology map based on the drawing data; and

[0073] Display unit, which is configured to display the topology of the system.

[0074] According to a third aspect of this disclosure, an apparatus for configuring a topology map of a system is provided, comprising a memory and a processor, wherein the memory stores instructions that, when executed by the processor, implement the operation of the method for configuring a topology map of a system as described above.

[0075] According to a fourth aspect of this disclosure, a non-transitory computer-readable storage medium is provided, wherein instructions are stored on the non-transitory computer-readable storage medium, which, when executed by a processor, implement the operation of the method for configuring a system topology as described above.

[0076] According to a fifth aspect of this disclosure, a computer program product is provided, the computer program product including instructions that, when executed by a processor, implement the operation of the method for configuring a system topology as described above.

[0077] Other features and advantages of this disclosure will become clearer from the following detailed description of exemplary embodiments with reference to the accompanying drawings. Attached Figure Description

[0078] The accompanying drawings, which form part of this specification, illustrate embodiments of this disclosure and, together with the specification, serve to explain the principles of this disclosure.

[0079] This disclosure will become clearer with reference to the accompanying drawings and the following detailed description, wherein:

[0080] Figure 1A flowchart illustrating a method for configuring a system topology graph according to an exemplary embodiment of the present disclosure is shown.

[0081] Figure 2 A topology diagram of a system according to a specific embodiment of the present disclosure is shown;

[0082] Figure 3 A partial flowchart of a method for configuring a system topology diagram according to a specific embodiment of the present disclosure is shown.

[0083] Figure 4 It shows the basis Figure 3 The operations in the rendered system topology graph;

[0084] Figure 5 A partial flowchart of a method for configuring a system topology diagram according to another specific embodiment of the present disclosure is shown;

[0085] Figure 6 It shows the basis Figure 5 The operations in the rendered system topology graph;

[0086] Figure 7 A partial flowchart illustrating a method for configuring a system topology diagram according to yet another specific embodiment of the present disclosure is shown.

[0087] Figure 8 A partial flowchart illustrating a method for configuring a system topology diagram according to yet another specific embodiment of the present disclosure is shown.

[0088] Figure 9 It shows the basis Figure 8 The operations within include a topology diagram of the system containing configuration information;

[0089] Figure 10 A block diagram of a device for configuring a system topology according to an exemplary embodiment of the present disclosure is shown;

[0090] Figure 11 A block diagram of an apparatus for configuring a system topology graph according to an exemplary embodiment of the present disclosure is shown.

[0091] Note that in the embodiments described below, the same reference numerals are sometimes used across different figures to denote the same parts or parts having the same function, and repeated descriptions are omitted. In this specification, similar reference numerals and letters are used to denote similar items; therefore, once an item is defined in one figure, it does not need to be discussed further in subsequent figures.

[0092] For ease of understanding, the positions, dimensions, and extents of the structures shown in the accompanying drawings and other materials may not represent actual positions, dimensions, and extents. Therefore, the disclosed invention is not limited to the positions, dimensions, and extents disclosed in the accompanying drawings and other materials. Furthermore, the drawings are not necessarily drawn to scale, and some features may be enlarged to show details of specific components. Detailed Implementation

[0093] Various exemplary embodiments of the present disclosure will now be described in detail with reference to the accompanying drawings. It should be noted that, unless otherwise specifically stated, the relative arrangement, numerical expressions, and values ​​of the components and steps set forth in these embodiments do not limit the scope of the present disclosure.

[0094] The following description of at least one exemplary embodiment is merely illustrative and is in no way intended to limit this disclosure or its application or use. Those skilled in the art will understand that they merely illustrate exemplary ways that can be used to implement this disclosure, and are not exhaustive.

[0095] Techniques, methods, and equipment known to those skilled in the art may not be discussed in detail, but where appropriate, such techniques, methods, and equipment should be considered part of the specification.

[0096] To facilitate monitoring of system operation, such as quickly assessing the impact of server or other component failures on the entire system and taking effective troubleshooting measures, a system topology diagram can be provided. Currently, application system administrators or developers typically collect information on all servers and other components in the system and their interrelationships in advance, and then manually draw the system topology diagram using flowchart drawing tools such as Visio, PowerPoint, and Word. However, this manual drawing method is very labor-intensive and prone to errors, especially with large systems containing a large number of servers or other components. Moreover, manually drawn topology diagrams are static images, requiring manual modification when the system changes, making it difficult to adapt to system changes in a timely manner, leading to reduced monitoring efficiency and increased monitoring costs.

[0097] To address the aforementioned issues, this disclosure proposes a method for configuring a system topology diagram. The system may include one or more subsystems. Different subsystems can be used to implement different functions. Furthermore, different subsystems can be communicatively connected; for example, an upstream subsystem can transmit relevant data to a downstream subsystem, or vice versa, a downstream subsystem can feed back relevant data to an upstream subsystem, thus achieving collaboration between subsystems. A subsystem may include one or more clusters to systematically allocate the operations required to implement the corresponding subsystem functions. One or more other clusters may be nested within a cluster, or a cluster may call other clusters or be called by other clusters, without limitation. A cluster may include one or more servers, which can be used to specifically perform various operations. The allocation of servers to clusters can be determined based on various methods, without limitation. In addition, the system may include other components besides servers, such as sensing sensors, client devices, etc., which may exist independently or be organized in corresponding clusters or subsystems, without limitation. During the topology diagram drawing process, corresponding icons or lines can be used to represent other components that may exist. The following text will use a system containing only servers as an example to illustrate the method for drawing the system topology diagram. However, those skilled in the art can derive methods for drawing the topology diagram of systems containing other components based on the content of this disclosure, and such methods also fall within the scope of protection of this disclosure.

[0098] In one exemplary embodiment of this disclosure, such as Figure 1 As shown, the method for configuring the system topology map may include:

[0099] Step S110: Obtain configuration information through the graphical user interface (GUI).

[0100] Here, the configuration information can be selected or filled in by a user (e.g., a system administrator or developer) on a provided graphical user interface. Providing a graphical user interface allows users to input configuration information visually, facilitating user operation. In some embodiments, the graphical user interface may include one or more switchable pages, each providing information input components such as radio buttons, checkboxes, option lists, and input boxes, allowing users to select or input configuration information at appropriate locations. In subsequent operations of this method, a topology diagram can be drawn based on the configuration information obtained through the graphical user interface.

[0101] In some embodiments, the configuration information may include at least one of the following: server basic information associated with a server, cluster basic information associated with a cluster, subsystem basic information associated with a subsystem, server dependency information indicating the dependency relationship between a server and a cluster, cluster relationship information indicating the relationship between clusters, and subsystem relationship information indicating the relationship between subsystems. Furthermore, where the system includes other components, the configuration information may also include information indicating the component itself, and information indicating the association relationship between the component and other parts of the system, etc., without limitation.

[0102] Server basic information refers to information associated with a single server itself, such as at least one of the following: server name, server serial number, server network address (e.g., IP address, URL address), server type, server physical address (e.g., address of the data center where the server is located, the specific location of the server within the data center), server monitoring metrics, server monitoring metric thresholds, and server administrator information (e.g., the department to which the server belongs, the management department of the server, the administrators of the server, etc.). Generally, a server can be uniquely identified based on its name, serial number, network address, or specific physical address. Additionally, the server type can be determined based on the operations, functions, or business processes performed. In a specific example, the server type can include at least one of the following: database server (for providing database services, such as a server based on the Oracle operating system), application server (for executing applications, such as a server based on the Windows operating system), load balancing server (for providing load balancing services), and caching server (for providing caching services). Depending on the server type, one or more monitoring metrics can be monitored to understand the server's operational status. For example, server monitoring metrics may include at least one of the following: server memory usage, server virtual machine memory usage, server disk space usage, server tablespace usage, server connection usage, and server heartbeat metrics. Furthermore, server monitoring metric thresholds can be provided or set. By comparing the monitored server metric values ​​with the corresponding thresholds, users can more effectively assess the server's operational status, as will be explained in detail later.

[0103] Cluster basic information refers to information associated with a single cluster itself, such as at least one of the following: cluster name, cluster ID, cluster network address (e.g., IP address, URL address), cluster type, and cluster administrator information (e.g., department to which the cluster belongs, management department, administrators). Generally, a cluster can be uniquely identified by its name, ID, or network address. It's important to note that when a cluster contains multiple servers, these servers may be located in different places, meaning they may have different physical addresses. Therefore, the cluster may not be located in a specific physical location but rather distributed across a wide spatial range.

[0104] In the exemplary embodiments of this disclosure, the calling relationship can be configured on a cluster basis during system operation. This type of cluster, capable of directly calling other clusters or being directly called by other clusters, can also be called a communication cluster. That is, if a server needs to be called to perform a corresponding operation, the cluster to which that server belongs can actually be called (e.g., by the cluster's name, number, or network address), and the specific server to perform the operation is determined within the cluster. In other words, the caller outside the cluster directly "manipulates" or "sees" the cluster, not the specific server; the specific server is determined internally and is "invisible" to the outside. Various methods can be used to organize communication clusters, and no limitation is made here. In a specific example, multiple servers with the same functionality can be placed in the same communication cluster; for example, several servers under a load balancer can be included in the same communication cluster. Understandably, if one or more servers in a communication cluster fail (for example, due to a power outage in the data center where the server or servers are located), a server located at a different physical address within the same communication cluster can take over the operation of the failed server, thereby ensuring the reliability of the system operation.

[0105] Furthermore, a cluster can contain or nest one or more other clusters. This type of cluster, with other clusters nested within it, can also be called a parent cluster. It's important to note that because a parent cluster contains other clusters, it generally cannot directly call or be called by other clusters, as this could lead to ambiguity or confusion in the calling relationships. In other words, a cluster that can directly call or be called by other clusters cannot contain other clusters nested within it. Setting up various clusters and their interrelationships helps to further clarify the relationships between the multiple servers in the system, and by reflecting these relationships in the subsequently generated topology diagram, it helps users maintain the system more clearly and conveniently.

[0106] Accordingly, in some embodiments, the cluster relationship information in the configuration information, which is used to indicate the relationship between clusters, may include at least one of cluster call information and cluster nesting information. The cluster call information can be used to indicate the call relationship between clusters, while the cluster nesting information can be used to indicate the nesting relationship between clusters, so that a corresponding topology graph can be generated subsequently based on the cluster relationship information.

[0107] In some embodiments, the basic information of a subsystem may include at least one of the following: the subsystem's name, subsystem number, subsystem's network address (e.g., IP address, URL address, etc.), subsystem type, and subsystem administrator information (e.g., the department to which the subsystem belongs, the department in charge of the subsystem, the administrators of the subsystem, etc.). Generally, a subsystem can be uniquely identified by its name, number, or network address. Similarly, a subsystem may contain multiple clusters, and each cluster may contain multiple servers. These servers may be located in different places, i.e., they may have different physical addresses. Therefore, a subsystem may not be located in a specific physical location but may be distributed over a wide spatial range. The type of subsystem can be classified or determined according to the specific functions it is to perform, without limitation. For example, in the aviation industry, the corresponding system may include a sales subsystem for selling tickets, a check-in subsystem for providing check-in services to customers, a scheduling subsystem for scheduling flights, etc. These subsystems can be managed by corresponding departments or personnel. Furthermore, as mentioned above, different subsystems can have communication relationships. Subsystem relationship information can be used to indicate the communication relationship or interface protocol between a subsystem and other subsystems located upstream or downstream of it, or to indicate the network address of other subsystems located upstream or downstream of it. This allows for the generation of a corresponding topology map based on the subsystem relationship information, enabling users to clearly and intuitively see the relationships between multiple subsystems in the topology map. This, in turn, helps users determine the potential impact of the operating status of a certain subsystem on other subsystems.

[0108] In some embodiments, as described above, the graphical user interface may include one or more pages where users can directly select or fill in configuration information to generate a system topology diagram. The layout of the configuration information to be entered on one or more pages can be set as needed and is not limited here. For example, in the graphical user interface, configuration information can be represented by one or more lists. Users can select the desired configuration information using components such as radio buttons and checkboxes, or they can directly enter the configuration information into components such as input boxes in the graphical user interface; this is not limited here.

[0109] In a specific example, on the first page, a user can enter the name of the subsystem to be configured and the subsystem's administrator information. After completing the entry, they can click the "Save" button on the page to save the configuration information and proceed to the second page. On the second page, the user can enter the basic server information to be configured, such as the server's name, ID, or network address, as well as the server's monitoring metrics. After completing the entry, they can click the "Save" button on the page to save the configuration information and proceed to the third page. On the third page, the user can enter the cluster information associated with the cluster to be configured. Group basic information and / or cluster relationship information, such as editing relevant cluster information in the list of queried and displayed clusters. After completing the entry, you can click the "Save" button on the page to save the entered configuration information and enter the fourth page. On the fourth page, users can enter subsystem relationship information to configure the communication relationship between the subsystem and other upstream and downstream subsystems (e.g., subsystem interface address, protocol, port number, etc.). In addition, users can also configure the clusters in the subsystem that involve call relationships. Finally, you can click the "Save" button on the page to save the entered configuration information.

[0110] In other embodiments, considering that in some cases, at least some configuration information may already be stored in a pre-set configuration information database, and the user only needs to supplement some configuration information or modify some existing configuration information, obtaining configuration information through a graphical user interface can include: obtaining a configuration request; searching for existing configuration information corresponding to the configuration request in the configuration information database; if existing configuration information is found, providing a graphical user interface preloaded with the existing configuration information for adding or modifying configuration information; and if no existing configuration information is found, providing an initial graphical user interface for adding configuration information. The configuration request may originate from the user and may contain at least information indicating the subsystem, cluster, or server that the user wants to configure, such as the name, number, or network address of the subsystem, cluster, or server to be configured. The configuration information database can search for existing configuration information corresponding to the subsystem, cluster, or server based on its name, number, or network address, and if existing configuration information exists, it can be preloaded into the graphical user interface, thereby significantly reducing the amount of configuration information the user needs to input and facilitating fast and efficient configuration. Especially when there are only minor changes to the system, subsystem, cluster, or server, users can quickly provide modified configuration information to generate a modified topology diagram. This greatly facilitates users in updating the topology diagram in a timely manner according to system changes, ensuring the effectiveness of system maintenance based on the topology diagram.

[0111] In a specific example, a user can issue a configuration request via relevant buttons on the graphical user interface. Based on the user's configuration request, the system searches the configuration information database for existing configuration information and loads the found information into one or more corresponding pages within the graphical user interface. Users can modify the configuration information on these pages, or add subsystems, clusters, or servers using relevant buttons and enter the corresponding configuration information to achieve efficient system configuration.

[0112] Furthermore, to facilitate subsequent modifications to configuration information and topology diagrams, in some embodiments, obtaining configuration information through a graphical user interface may further include storing or encrypting the newly added or modified configuration information in a configuration information database. Various methods can be used to encrypt the configuration information, and no limitation is set here. Additionally, the security of the configuration information can be ensured by setting the configuration information database locally, and no limitation is set here either.

[0113] In some embodiments, depending on the type of server, a set of monitoring metrics for each server can be provided, allowing users to select the specific monitoring metrics needed for that server type. For example, the set of server monitoring metrics may include all monitoring metrics that can be monitored for that type of server. Specifically, obtaining configuration information through a graphical user interface may include: obtaining a configuration request; determining the set of monitoring metrics for the server based on its type; and providing a graphical user interface containing the aforementioned set of monitoring metrics for selecting the monitoring metrics to be monitored for that server. The configuration request may at least indicate the type of server to be configured, so that the set of monitoring metrics provided can be determined based on the server type. For example, a server may be configured with multiple ports, and a configuration table may configure configurable monitoring metrics for different types of servers. For example, the set of monitoring metrics for application servers (e.g., Windows-based servers) may include server memory usage, virtual machine memory usage, and disk space usage. The set of monitoring metrics for database servers (e.g., Oracle-based servers) may include tablespace usage, connection usage, and heartbeat metrics. The set of monitoring metrics for load balancing servers may be an empty set, meaning no monitoring metrics are monitored for this type of server. In some embodiments, the set of server monitoring metrics can be determined immediately upon receiving a configuration request and displayed on the server's configuration page. Users can then select the monitoring metrics of interest by checking boxes or other means to monitor these metrics. Furthermore, in some embodiments, users can also enter the threshold values ​​of the selected monitoring metrics on the server's configuration page or other configuration pages for comparison with the detected metric values, thereby determining the server's operating status.

[0114] In some embodiments, especially when existing configuration information exists, to facilitate user modification or addition of configuration information, an initial topology diagram can be drawn based on the existing configuration information, allowing users to more intuitively understand the current system's status. Specifically, obtaining configuration information through a graphical user interface may further include: generating initial drawing data with a preset format based on existing configuration information when it is found; and generating and displaying the system's initial topology diagram based on the initial drawing data. Here, the method of generating the initial topology diagram can be similar to the method of generating the topology diagram of the configured system, which will be described in detail below. In a specific example, the graphical user interface can be divided into, for example, left and right parts or top and bottom parts. One part of the graphical user interface can display configuration information, and the other part can display the topology diagram corresponding to the current configuration information, so that users can intuitively see the display effect of the topology diagram corresponding to the current configuration information.

[0115] return Figure 1 In an exemplary embodiment of this disclosure, the method for configuring the topology of the system may further include:

[0116] Step S120: Generate drawing data with a preset format based on the configuration information.

[0117] Understandably, configuration information obtained directly through a graphical user interface may be in natural language or other formats. To facilitate the drawing of topology diagrams, it is necessary to convert it into plotting data in a preset format. For example, the specific format of the plotting data to be converted can be determined based on the specific requirements of the application, plugin, or software used to draw the topology diagram. In a specific example, the preset format may include JSON format.

[0118] In some embodiments, particularly in configuration information presented in natural language, there may be characters that cannot be automatically recognized by the corresponding applications, plugins, or software. Therefore, some preprocessing of the configuration information is necessary. Specifically, generating drawing data with a preset format based on the configuration information may include: determining whether the configuration information contains preset characters; if the configuration information contains preset characters, filtering the preset characters and generating drawing data with a preset format based on the filtered configuration information; and if the configuration information does not contain preset characters, directly generating drawing data with a preset format based on the configuration information.

[0119] For example, when users enter configuration information in the graphical user interface, they may include explanatory information in parentheses in the corresponding positions. These parentheses and their contents may interfere with subsequent data conversion. To address this, we can check whether the configuration information contains parentheses (i.e., preset characters). If so, the parentheses and their contents can be filtered out to generate plot data with a preset format based on the remaining configuration information. If not, plot data with a preset format can be directly generated based on the configuration information for subsequent topology drawing.

[0120] In some embodiments, the drawing data can be generated in real time based on the configuration information. For example, whenever a user completes the input and saving of configuration information on the graphical user interface, the corresponding drawing data can be generated immediately. As described later, the corresponding topology diagram can be generated immediately based on the generated drawing data, so that the generated topology diagram can reflect the latest system structure in real time, achieving a WYSIWYG effect and facilitating user configuration. Alternatively, in other embodiments, in order to save configuration or computing resources, the corresponding drawing data and the corresponding topology diagram can be generated and drawn after the user has completed the input of all configuration information; this is not limited here.

[0121] return Figure 1 In an exemplary embodiment of this disclosure, the method for configuring the topology of the system may further include:

[0122] Step S130: Generate and display the system topology diagram based on the drawing data.

[0123] Various applications, plugins, or software for drawing can be used to generate a topology map from the drawing data and display the generated topology map on the monitor. For example, if the default format of the drawing data is JSON, the system's topology map can be generated using the open-source Mermaid plugin based on the drawing data.

[0124] Furthermore, in some embodiments, the system's topology map can be generated and displayed in real time based on the drawing data. As mentioned above, whenever a user completes the input and saving of configuration information on the graphical user interface, the corresponding drawing data can be generated immediately, and the corresponding topology map can be generated immediately based on the generated drawing data, thereby achieving a WYSIWYG effect and facilitating user configuration.

[0125] In some embodiments, the system topology diagram can be a vector graphic, which does not lose its quality when enlarged, thereby allowing users to zoom in and out of the system topology diagram as needed to view or monitor the overall or partial status of the system.

[0126] Various methods can be used to indicate the various components of the system and their connections or communication relationships in a topology diagram, and no limitation is made herein. In one specific embodiment, such as Figure 2 As shown in the topology diagram of system 200, server 210 can be configured to be represented by node icons. Furthermore, different shapes, colors, fill patterns, or display effects can be used to render the node icons to reflect the server's basic information and / or current status, as will be explained in detail later.

[0127] Furthermore, in the topology diagram of system 200, one or more node icons corresponding to one or more servers 210 belonging to the same cluster 220 can be configured to be located in the same cluster region (e.g., Figure 2 Within the cluster box (represented by dashed lines), it is indicated that these servers 210 are grouped into the same cluster 220. A cluster may include a parent cluster that can nest other clusters, for example... Figure 2 Cluster 3 shown may also include a communication cluster that can be directly called by other clusters or directly call other clusters, for example... Figure 2 The diagram shows clusters 1, 2, and 4. Similarly, different shapes, colors, fill patterns, or display effects can be used to render cluster areas to reflect the relevant configuration information of the corresponding clusters. Figure 2 In the topology diagram, the cluster nesting information in the cluster relationship information can be configured to be represented by the nesting relationship between cluster regions, for example... Figure 2 Cluster 3 contains nested clusters 1 and 2. Furthermore, cluster call information within the cluster relationship information can be configured to be represented by lines connecting cluster regions, such as lines with arrows, where the arrow points from the caller to the callee. Figure 2 Cluster 1 calls Cluster 4, and Cluster 4 calls Cluster 2.

[0128] exist Figure 2 In the topology diagram of system 200 shown, one or more cluster regions corresponding to one or more clusters 220 belonging to the same subsystem 230 can be configured to be located in the same subsystem region (e.g., Figure 2 In the subsystem bounding box (represented by a dashed line), these clusters 220 belong to the same subsystem 230. Similarly, different shapes, colors, fill patterns, or display effects can be used to render subsystem areas to reflect the relevant configuration information of the corresponding subsystems. Furthermore, subsystem relationship information can be configured to be represented by lines connecting subsystem areas. For example, in... Figure 2 In the topology diagram of system 200 shown, subsystem 2 can be connected to its upstream subsystem 1 and downstream subsystem 3 by lines to indicate that there is a communication relationship between the connected subsystems.

[0129] It is understood that in some embodiments, the system may also include other components besides servers, clusters and subsystems. In the system topology diagram, corresponding node icons or regions may be provided to represent these components, and corresponding forms of connections may be provided to represent various relationships between components, without limitation.

[0130] Furthermore, in some embodiments, especially where the topology map can reflect the configuration information entered by the user in real time, to facilitate user configuration, the display effect of the node icon in the configuration state can be different from that of the node icon in the non-configuration state. This allows the user to clearly see which components in the system are being configured or edited, avoiding confusion. For example, the fill color of the node icon in the configuration state can be yellow, while the fill color of the node icon in the non-configuration state can be white, thus providing the user with necessary prompts.

[0131] In some embodiments, the system topology diagram may include a structural topology diagram indicating the system structure and a state topology diagram indicating the system's operating status. In other words, the structural topology diagram is configured to reflect the components such as servers, clusters, and subsystems included in the system, as well as the connections or communication relationships between them; while the state topology diagram can not only reflect the aforementioned components and their connections or communication relationships, but also reflect the operating status of the servers, clusters, and subsystems included in the system, thereby enabling system monitoring. It is understood that the method for configuring the system topology diagram described above mainly focuses on the method of drawing the system's structural topology diagram, while the system's state topology diagram can be further drawn based on the structural topology diagram, as detailed below. It is also understood that the relevant drawing data used to further draw the state topology diagram can also be in a preset format, such as JSON format, and can be generated using plugins such as Merimaid based on the preset format drawing data.

[0132] In some embodiments of this disclosure, such as Figure 3 As shown, the method for configuring the system topology diagram may further include:

[0133] Step S310: Obtain a monitoring request;

[0134] Step S320: Obtain the configuration information associated with the monitoring request from the configuration information database, and generate and display the system's structural topology diagram based on the configuration information;

[0135] Step S330: Obtain the monitoring indicator value of the corresponding server according to the monitoring request, or obtain the monitoring indicator value and monitoring indicator threshold of the corresponding server according to the monitoring request; and

[0136] Step S340: Render the system's structural topology diagram based on the acquired monitoring index values ​​or based on the acquired monitoring index values ​​and monitoring index thresholds, so as to generate and display the system's state topology diagram.

[0137] The monitoring request can indicate relevant information about the subsystem, cluster, or server to be configured, so that configuration information associated with the monitoring request can be retrieved from the configuration information database. In step S320, the specific operations described in steps S120 and S130 above can be used to generate and display the system's structural topology diagram based on the configuration information, and will not be repeated here. It should be noted that, to improve user experience and avoid excessively long loading times for the system's state topology diagram, step S330 does not necessarily have to be executed after step S320. For example, steps S320 and S330 can be executed simultaneously or substantially simultaneously, or even before step S320. That is, while obtaining configuration information and drawing the structural topology diagram, or even before obtaining configuration information and drawing the structural topology diagram, the monitoring indicator values ​​of the corresponding server can be obtained according to the monitoring request, or the monitoring indicator values ​​and monitoring indicator thresholds of the corresponding server can be obtained according to the monitoring request. Specifically, during step S330, instructions can be sent to sensors used to detect corresponding monitoring indicators of the server to instruct them to detect and return corresponding monitoring indicator values, or instructions can be sent to memory or databases used to store corresponding monitoring indicators of the server to obtain the corresponding server monitoring indicator values. Furthermore, instructions can be sent to the corresponding memory or database to obtain the monitoring indicator threshold values ​​of the server corresponding to the monitoring request. After obtaining the monitoring indicator values, the system's structural topology diagram can be rendered based on the obtained monitoring indicator values, or based on the obtained monitoring indicator values ​​and monitoring indicator thresholds, to generate and display the system's state topology diagram. Additionally, if necessary, lists or other methods can be used to display the relevant operating status information of servers, clusters, or subsystems included in the system; this is not limited. Furthermore, in some embodiments, if a monitoring indicator value or monitoring indicator threshold is not successfully obtained, it can be marked and displayed graphically or otherwise in the topology diagram to prompt the user.

[0138] For example, when monitoring server memory usage, a system topology diagram can be generated and displayed based on steps S310 and S320. Alternatively, the memory usage values ​​of each server in the system can be obtained based on step S330, and the system topology diagram can be rendered based on the obtained memory usage values ​​to generate and display the system's state topology diagram. Or, the memory usage thresholds of each server in the system can be obtained, and the system topology diagram can be rendered based on the obtained memory usage values ​​and the memory usage thresholds to generate and display the system's state topology diagram. Figure 4 In the system state topology diagram shown, the node icons representing server 210 can be rendered with different fill patterns to indicate different health states of the server. For example, as Figure 4 As shown, white fill indicates servers with memory usage less than 50% (Servers 2, 3, and 4), indicating a healthy operating status; sparser fill with diagonal lines indicates servers with memory usage between 50% and 80% (Server 6), indicating a moderate operating status; and denser fill with diagonal lines indicates servers with memory usage greater than 80% (Servers 1 and 5), indicating an unhealthy operating status. Therefore, users can clearly understand the operating status of each server in the system based on the system's status topology diagram and take corresponding measures to improve system performance.

[0139] Furthermore, in some embodiments, to facilitate subsequent backtracking or retrieval of server monitoring indicator values ​​and / or monitoring indicator thresholds, the method for configuring the system topology map may further include: storing or encrypting the acquired monitoring indicator values ​​in a configuration information database. Various methods can be used to encrypt the server's monitoring indicator values ​​and / or monitoring indicator thresholds, and no limitation is imposed here. Additionally, the security of the server's monitoring indicator values ​​and / or monitoring indicator thresholds can also be ensured by setting the configuration information database locally, and no limitation is imposed here either.

[0140] In some embodiments, the user may need an overview of the distribution of components that meet specific conditions in the system's topology diagram. In this case, such as... Figure 5 As shown, the method for configuring the system topology diagram may further include:

[0141] Step S510: Obtain the object lookup request;

[0142] Step S520: Traverse the system's topology graph to determine the portions of the topology graph that match the object lookup request; and

[0143] Step S530: Render the portion to indicate the object corresponding to the object lookup request.

[0144] In a specific example, a user can issue an object lookup request to find all servers located in a specific data center. To do this, the system's topology (e.g., a structural topology) can be traversed based on the object lookup request to identify the servers located in the aforementioned data center. Node icons representing these servers are then rendered to indicate the servers corresponding to the object lookup request in the topology map. Figure 6 Servers 1, 3, and 6 are marked in the image.

[0145] In another specific example, a user can issue an object lookup request to find all servers located in the same data center across various clusters. To do this, the system's topology (e.g., a structural topology or a state topology) can be traversed based on the object lookup request. For each cluster region, the node icons corresponding to the servers located in the same data center can be rendered to indicate the servers corresponding to the object lookup request in the topology.

[0146] Understandably, users can also issue other types of object lookup requests, which are not restricted here.

[0147] In some embodiments, users may need to draw additional topology diagrams based on other principles for components in the system that meet specific conditions, in order to clearly understand the information related to these components. In such cases, such as... Figure 7 As shown, the method for configuring the system topology diagram may further include:

[0148] Step S710: Obtain the object lookup request;

[0149] Step S720: Retrieve configuration information associated with the object indicated by the object lookup request from the configuration information database; and

[0150] Step S730: Generate and display the topology diagram of the object based on the configuration information.

[0151] For example, users can draw topology diagrams based on the physical addresses of servers instead of their network addresses. Specifically, all servers located in the same data center can be drawn in the same area of ​​the topology diagram, instead of drawing all servers in the same cluster as described above. To do this, users can issue corresponding object lookup requests to obtain data center-related configuration information and draw a separate topology diagram based on that information. It's important to note that this topology diagram can be either a structural topology diagram containing system structure information or a state topology diagram containing the operational status of components within the system.

[0152] It is understandable that users can draw topology diagrams based on other principles, and no restrictions are imposed here.

[0153] In exemplary embodiments of this disclosure, to simplify the system topology diagram, components such as servers, clusters, or subsystems in the system can be represented using node icons or region boxes, resulting in some specific information about them not being directly displayed in the topology diagram. However, in some cases, users may want to know specific information about a certain component in the system; in such cases, additional methods can be used to display this specific information. Specifically, in some embodiments, such as... Figure 8 As shown, the method for configuring a system topology diagram may further include: step S810, obtaining an information display request, wherein the information display request may at least indicate an object whose information is to be displayed; step S820, obtaining configuration information associated with the object from a configuration information database or topology diagram; and step S830, displaying the configuration information in the form of a details page or list overlaid on the topology diagram. For example, Figure 9 The details page 211 of server 1, which is overlaid on the topology diagram, is shown.

[0154] According to another aspect of this disclosure, such as Figure 10 As shown, a device 1000 for configuring a system topology map is also provided, which can implement the method for configuring a system topology map as described above. In an exemplary embodiment of this disclosure, the device 1000 may include an information acquisition unit 1001, a data conversion unit 1002, a drawing unit 1003, and a display unit 1004. The information acquisition unit 1001 may be configured to acquire configuration information through a graphical user interface. The data conversion unit 1002 may be configured to generate drawing data with a preset format based on the configuration information. The drawing unit 1003 may be configured to generate a system topology map based on the drawing data. The display unit 1004 may be configured to display the system topology map. The specific operation of each unit in this device can be referred to the detailed description above regarding the method for configuring a system topology map, and will not be repeated here.

[0155] According to another aspect of this disclosure, such as Figure 11 As shown, an apparatus 1100 for configuring a system topology map is also provided. The apparatus 1100 may include a memory 1101 and a processor 1102. The memory 1101 may store instructions, which, when executed by the processor 1102, can implement the operation of the method for configuring the system topology map as described above.

[0156] Specifically, processor 1102 can execute various actions and processes according to instructions stored in memory 1101. Processor 1102 can be an integrated circuit chip with signal processing capabilities. The processor can be a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), off-the-shelf programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component. It can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of this disclosure. The general-purpose processor can be a microprocessor or any conventional processor, and can be an x86 architecture or an ARM architecture, etc.

[0157] Memory 1101 stores executable instructions that, when executed by processor 1102, implement the method described above for configuring the system topology. Memory 1101 may be volatile memory or non-volatile memory, or may include both. Non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory may be random access memory (RAM) used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct memory bus random access memory (DR RAM). It should be noted that the memory used in the methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0158] This disclosure also proposes a non-transitory computer-readable storage medium storing instructions that, when executed by a processor, can implement the operation of the method for configuring a system topology as described above.

[0159] Similarly, the non-transitory computer-readable storage media in the embodiments of this disclosure are intended to include, but are not limited to, the above and any other suitable types of memory.

[0160] This disclosure also proposes a computer program product that may include instructions that, when executed by a processor, can implement the operation of the method for configuring a system topology as described above.

[0161] Instructions can be any set of instructions that will be executed directly by one or more processors, such as machine code, or any set of instructions that will be executed indirectly, such as a script. The terms “instruction,” “application,” “process,” “step,” and “program” used herein are interchangeable. Instructions can be stored in object code format for direct processing by one or more processors, or stored in any other computer language, including scripts or sets of independent source code modules that are interpreted on demand or compiled ahead of time. Instructions can include instructions that cause one or more processors to act as various neural networks, if any. The function, methods, and routines of instructions are explained in more detail in other parts of this document.

[0162] This disclosure provides a general method for automatically drawing system topology diagrams based on configuration information, which saves a significant amount of work compared to manual drawing. Furthermore, in some embodiments, the topology diagram can be generated dynamically and in real-time based on modified configuration information, enabling users to update and maintain system-related data promptly. Referring to the generated topology diagram, users can easily collect, organize, and store relevant information about various components in the system, helping to save on documentation and efficiently maintain and monitor the system. For example, it can help users promptly identify existing or potential system failures and determine necessary maintenance measures. Moreover, in some embodiments, a visual user interface and a real-time updated topology diagram can be provided, achieving a WYSIWYG effect, allowing users to configure the topology diagram simply and intuitively. Additionally, in some embodiments, users can query and display relevant components and their information in the topology diagram according to their needs, thereby improving the scientific nature of system deployment. For example, server information can be queried based on data center location, thus intuitively displaying the system's disaster recovery and resilience capabilities.

[0163] The terms “left,” “right,” “front,” “back,” “top,” “bottom,” “upper,” “lower,” “high,” “lower,” etc., used in the specification and claims, if present, are for descriptive purposes and not necessarily for describing unchanging relative positions. It should be understood that such terms are interchangeable where appropriate, enabling embodiments of this disclosure described herein to operate, for example, in orientations different from those shown or otherwise described herein. For example, when the device in the drawings is reversed, a feature previously described as “above” other features may now be described as “below” other features. The device may also be oriented in other ways (rotated 90 degrees or in other orientations), in which case the relative spatial relationships will be interpreted accordingly.

[0164] In the specification and claims, when an element is described as being "on top of," "attached to," "connected to," "coupled to," or "in contact with" another element, the element may be directly located on top of, directly attached to, directly connected to, directly coupled to, or directly in contact with the other element, or one or more intermediate elements may be present. Conversely, when an element is described as being "directly" located on top of, directly attached to, directly connected to, directly coupled to, or directly in contact with another element, no intermediate elements are present. In the specification and claims, when a feature is arranged "adjacent" to another feature, it may mean that a feature has a portion overlapping with the adjacent feature or a portion located above or below the adjacent feature.

[0165] As used herein, the term “exemplary” means “serving as an example, instance, or illustration” and not as a “model” to be precisely copied. Any implementation described herein by example is not necessarily to be construed as preferred or advantageous over other implementations. Moreover, this disclosure is not limited to any theory expressed or implied as given in the field of art, background art, summary of invention, or detailed description.

[0166] As used herein, the term "substantially" means any minor variation resulting from design or manufacturing defects, device or component tolerances, environmental influences, and / or other factors. The term "substantially" also allows for differences from the perfect or ideal situation due to parasitic effects, noise, and other practical considerations that may exist in the actual implementation.

[0167] Furthermore, terms such as “first,” “second,” etc., may be used in this document for reference purposes only and are not intended to be limiting. For example, unless the context clearly indicates otherwise, the words “first,” “second,” and other such numerical terms relating to structures or elements do not imply order or sequence.

[0168] It should also be understood that when the term “including / contains” is used herein, it indicates the presence of the indicated feature, whole, step, operation, unit and / or component, but does not preclude the presence or addition of one or more other features, wholes, steps, operations, units and / or components and / or combinations thereof.

[0169] In this disclosure, the term “provide” is used broadly to cover all ways of obtaining an object, and therefore “provide an object” includes, but is not limited to, “purchasing,” “preparing / manufacturing,” “arranging / setting up,” “installing / assembling,” and / or “ordering” an object.

[0170] As used herein, the term “and / or” includes any and all combinations of one or more of the listed items in association. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of this disclosure. As used herein, the singular forms “a,” “an,” and “the” are also intended to include the plural forms unless the context clearly indicates otherwise.

[0171] Those skilled in the art will recognize that the boundaries between the above operations are merely illustrative. Multiple operations may be combined into a single operation, a single operation may be distributed among additional operations, and operations may be performed with at least partial overlap in time. Moreover, alternative embodiments may include multiple instances of a particular operation, and the order of operations may be changed in various other embodiments. However, other modifications, variations, and substitutions are equally possible. Aspects and elements of all the embodiments disclosed above may be combined in any way and / or in combination with aspects or elements of other embodiments to provide multiple additional embodiments. Therefore, this specification and the accompanying drawings should be considered illustrative rather than restrictive.

[0172] While specific embodiments of this disclosure have been described in detail by way of example, those skilled in the art should understand that the examples are for illustrative purposes only and not intended to limit the scope of this disclosure. The various embodiments disclosed herein can be combined in any way without departing from the spirit and scope of this disclosure. Those skilled in the art should also understand that various modifications can be made to the embodiments without departing from the scope and spirit of this disclosure. The scope of this disclosure is defined by the appended claims.

Claims

1. A method for configuring a system topology graph, characterized in that, The system's topology diagram includes a structural topology diagram indicating the system's structure and a state topology diagram indicating the system's operating state. The method includes: Configuration information is obtained through a graphical user interface, wherein the system includes one or more subsystems, the subsystems include one or more clusters, the clusters include one or more servers, and the configuration information includes at least one of the following: server basic information associated with the server, cluster basic information associated with the cluster, subsystem basic information associated with the subsystem, server dependency information indicating the dependency relationship between the server and the cluster, cluster relationship information indicating the relationship between the clusters, and subsystem relationship information indicating the relationship between the subsystems. Generate drawing data with a preset format based on the configuration information; Generate and display the system topology map based on the drawing data; Store the configuration information in the configuration information database or update the configuration information database using the configuration information; Obtain a monitoring request, wherein the monitoring request indicates relevant information about the subsystem, cluster, or server to be configured; The system retrieves configuration information associated with the monitoring request from the configuration information database and generates and displays the system's structural topology based on the configuration information. The monitoring metric values ​​of the corresponding server are obtained according to the monitoring request, or the monitoring metric values ​​and monitoring metric thresholds of the corresponding server are obtained according to the monitoring request; and The system's structural topology is rendered based on the acquired monitoring index values ​​or based on the acquired monitoring index values ​​and monitoring index thresholds to generate and display the system's state topology.

2. The method according to claim 1, characterized in that, The server basic information includes at least one of the following: server name, server ID, server network address, server type, server physical address, server monitoring metrics, server monitoring metric thresholds, and server administrator information. The server type includes at least one of database server, application server, load balancer server, and caching server. The server monitoring metrics include at least one of server memory usage, server virtual machine memory usage, server disk space usage, server tablespace usage, server connection usage, and server heartbeat metrics. The cluster basic information includes at least one of the following: cluster name, cluster number, cluster network address, cluster type, and cluster administrator information; or The basic information of the subsystem includes at least one of the following: the name of the subsystem, the subsystem number, the network address of the subsystem, the type of the subsystem, and the administrator information of the subsystem; or The cluster relationship information includes at least one of cluster call information and cluster nesting information, wherein the cluster call information is used to indicate the call relationship between clusters, and the cluster nesting information is used to indicate the nesting relationship between clusters, and a cluster that can directly call other clusters or be directly called by other clusters cannot contain other clusters nested within it; or The subsystem relationship information is used to indicate the communication relationship or interface protocol between a subsystem and other subsystems located upstream or downstream of the subsystem, or to indicate the network address of other subsystems located upstream or downstream of the subsystem.

3. The method according to claim 1, characterized in that, The system's topology is a vector diagram; or In the system's topology diagram: The server is configured to be represented by a node icon. One or more node icons corresponding to one or more servers belonging to the same cluster are configured to be located in the same cluster region. One or more cluster regions corresponding to one or more clusters belonging to the same subsystem are configured to be located in the same subsystem region. The cluster call information in the cluster relationship information is configured to be represented by lines connecting cluster regions. The cluster nesting information in the cluster relationship information is configured to be represented by nesting between cluster regions. The subsystem relationship information is configured to be represented by lines connecting subsystem regions, or The display of a node icon in configuration mode differs from that in non-configuration mode.

4. The method according to claim 1, characterized in that, Obtaining configuration information through the graphical user interface includes: Get configuration request; Search the configuration information database for existing configuration information corresponding to the configuration request; If existing configuration information is found, a graphical user interface with preloaded existing configuration information is provided for adding or modifying configuration information. If no existing configuration information is found, an initial graphical user interface is provided for adding new configuration information.

5. The method according to claim 4, characterized in that, The configuration request at least indicates the name, number, or network address of the subsystem, cluster, or server to be configured. Searching the configuration information database for existing configuration information corresponding to the configuration request includes: The configuration information database is used to search for existing configuration information corresponding to the subsystem, cluster, or server to be configured, based on the name, number, or network address of the subsystem, cluster, or server to be configured.

6. The method according to claim 4, characterized in that, Obtaining configuration information via a graphical user interface also includes: The newly added or modified configuration information is stored or encrypted and stored in the configuration information database.

7. The method according to claim 4, characterized in that, Obtaining configuration information via a graphical user interface also includes: If existing configuration information is found, generate initial drawing data with a preset format based on the existing configuration information; and The initial topology map of the system is generated and displayed based on the initial drawing data.

8. The method according to claim 1, characterized in that, Obtaining configuration information through the graphical user interface includes: Obtain a configuration request, wherein the configuration request at least indicates the type of server to be configured; The set of monitoring metrics for a server is determined based on its type; and A graphical user interface containing the set of monitoring indicators is provided for selecting the monitoring indicators to be monitored by the server.

9. The method according to claim 1, characterized in that, In the graphical user interface, the configuration information is configured to be represented by one or more lists.

10. The method according to claim 1, characterized in that, Generating drawing data with a preset format based on the configuration information includes: Determine whether the configuration information contains preset characters; If the configuration information contains preset characters, the preset characters are filtered, and drawing data with a preset format is generated based on the filtered configuration information; and If the configuration information does not contain preset characters, drawing data with a preset format is generated directly based on the configuration information.

11. The method according to claim 1, characterized in that, The drawing data is generated in real time based on the configuration information; or The system's topology map is generated and displayed in real time based on the drawing data.

12. The method according to claim 1, characterized in that, The preset format includes JSON format; or The topology map of the system was generated using the Mermaid plugin based on the drawing data.

13. The method according to claim 1, characterized in that, The operation of obtaining the configuration information corresponding to the monitoring request from the configuration information database and the operation of obtaining the monitoring indicator value of the corresponding server according to the monitoring request, or obtaining the monitoring indicator value and monitoring indicator threshold of the corresponding server according to the monitoring request, are performed simultaneously.

14. The method according to claim 1, characterized in that, The method further includes: The acquired monitoring indicator values ​​are stored or encrypted and stored in the configuration information database.

15. The method according to claim 1, characterized in that, The method further includes: Get the object lookup request; Traverse the system's topology graph to determine the portion of the topology graph that matches the object lookup request; and The portion is rendered to indicate the object corresponding to the object lookup request.

16. The method according to claim 1, characterized in that, The method further includes: Get the object lookup request; Retrieve configuration information associated with the object indicated by the object lookup request from the configuration information database; and A topology map of the objects is generated and displayed based on the configuration information.

17. The method according to claim 1, characterized in that, The method further includes: Obtain an information display request, wherein the information display request at least indicates the object whose information is to be displayed; Retrieve configuration information associated with the object from a configuration information database or topology diagram; and The configuration information is displayed as a details page or list overlaid on the topology map.

18. A device for configuring a system topology, characterized in that, The system topology diagram includes a structural topology diagram indicating the system structure and a state topology diagram indicating the system operating status. The device includes: An information acquisition unit is configured to acquire configuration information through a graphical user interface. The system includes one or more subsystems, each subsystem includes one or more clusters, and each cluster includes one or more servers. The configuration information includes at least one of the following: server basic information associated with a server, cluster basic information associated with a cluster, subsystem basic information associated with a subsystem, server dependency information indicating the dependency relationship between a server and a cluster, cluster relationship information indicating the relationship between clusters, and subsystem relationship information indicating the relationship between subsystems. A data conversion unit is configured to generate drawing data with a preset format based on the configuration information. A drawing unit, configured to generate a system topology map based on the drawing data; and The display unit is configured to display the topology of the display system. The device is also configured to: Store the configuration information in the configuration information database or update the configuration information database using the configuration information; Obtain a monitoring request, wherein the monitoring request indicates relevant information about the subsystem, cluster, or server to be configured; The system retrieves configuration information associated with the monitoring request from the configuration information database and generates and displays the system's structural topology based on the configuration information. The monitoring metric values ​​of the corresponding server are obtained according to the monitoring request, or the monitoring metric values ​​and monitoring metric thresholds of the corresponding server are obtained according to the monitoring request; and The system's structural topology is rendered based on the acquired monitoring index values ​​or based on the acquired monitoring index values ​​and monitoring index thresholds to generate and display the system's state topology.

19. An apparatus for configuring a system topology, characterized in that, The apparatus includes a memory and a processor, the memory storing instructions that, when executed by the processor, implement the operation of the method for configuring a system topology according to any one of claims 1 to 17.

20. A non-transitory computer-readable storage medium, characterized in that, The non-transitory computer-readable storage medium stores instructions that, when executed by a processor, implement the operation of the method for configuring a system topology according to any one of claims 1 to 17.

21. A computer program product, characterized in that, The computer program product includes instructions that, when executed by a processor, implement the operation of the method for configuring a system topology map according to any one of claims 1 to 17.

Images