Inter-component incidence relation topological graph generation method and system and readable medium

Abstract

The invention provides an inter-component incidence relation topological graph generation method and system and a readable medium, and the method comprises the steps: storing configuration item information of each component in a non-relational database to generate a configuration item list corresponding to each component, the configuration item list comprising a plurality of configuration item fields corresponding to the configuration item information; storing association relationships among the configuration item fields of different components in an association relationship library; converting the association relationship and the configuration item list into graph data in a graph database; and generating an inter-component incidence relation topological graph according to the graph data in the graph database, wherein the inter-component incidence relation topological graph comprises each component and an incidence relation. By means of the method, the inter-component incidence relation topological graph containing all the components can be flexibly and efficiently generated.

Description

Technical Field

[0001] The present application mainly relates to the field of IT operation and maintenance management, and in particular to a method, system and readable medium for generating a topological diagram of association relationships between components. Background Art

[0002] In the field of IT operation and maintenance management, network topology diagrams can intuitively confirm the relationships between various IT components, thereby enabling better management and maintenance of all IT components.

[0003] The current network topology drawing methods are mainly divided into two categories: manual drawing and automatic drawing. The manual drawing method specifically collects device information and connection relationships first, and then draws them online through tools. Therefore, the manual drawing method has the problem of high update and maintenance costs. The existing automatic drawing methods are mainly based on network discovery assistance, such as the Simple Network Management Protocol (SNMP) and Link Layer Discovery Protocol (LLDP) supported by network devices, so as to automatically collect network device information and connection relationships, and then automatically generate a network topology diagram based on this information. Since most network discovery assistance protocols only support devices from specific manufacturers, it is impossible to flexibly and efficiently draw corresponding network topology diagrams for each IT component in devices from different manufacturers. Summary of the Invention

[0004] The technical problem to be solved by the present application is to provide a method, system and readable medium for generating a component association relationship topology map, which can flexibly and efficiently draw a component association relationship topology map containing each component and the relationship between components based on the configuration item information of each component.

[0005] To solve the above technical problems, the present application provides a method for generating a topological diagram of the association relationship between components, including: storing the configuration item information of each component in a non-relational database to generate a configuration item list corresponding to each component, the configuration item list containing multiple configuration item fields corresponding to the configuration item information; storing the association relationship between the configuration item fields of different components in an association relationship library; converting the association relationship and the configuration item list into graph data in a graph database; generating a topological diagram of the association relationship between components based on the graph data in the graph database, the topological diagram of the association relationship between components containing each component and the association relationship.

[0006] Optionally, the step of storing the configuration item information of each component in a non-relational database to generate a configuration item list corresponding to each component further includes: setting the type corresponding to each component in the non-relational database; setting the configuration item list template corresponding to each type in the non-relational database; for each component, selecting data from the configuration item information of the component and inputting the corresponding configuration item list template to generate a configuration item list.

[0007] Optionally, the type includes one or more of a virtualization host, middleware, database, virtualization cluster, virtualization host machine, virtualization platform, storage, and server.

[0008] Optionally, the graph data includes multiple nodes and edges, each node corresponds to a configuration item list of a component, and each edge corresponds to an association relationship between two configuration item lists.

[0009] Optionally, the step of converting the association relationships and configuration item lists into graph data in the graph database further includes: regularly converting all association relationships and configuration item lists into graph data, and / or when some configuration item lists in the non-relational database are changed, updating the graph database according to the association relationships and the changed configuration item lists.

[0010] Optionally, when part of the configuration item list in the non-relational database is changed, the step of updating the graph database according to the association relationship and the changed configuration item list further includes: confirming whether there is any modification to part of the configuration item list in the non-relational database, and confirming whether the configuration item list before and after the modification is different. When the confirmation result is yes, updating the graph database according to the association relationship and the changed configuration item list.

[0011] Optionally, it also includes: obtaining a unique identifier corresponding to the component in the graph database; and constructing an association relationship topology subgraph corresponding to the component based on the node corresponding to the unique identifier in the graph database and the edges associated with the node and other nodes.

[0012] To solve the above technical problems, the present application provides a system for generating a topological diagram of association relationships between components, including: a non-relational database, an association relationship library, a graph database and a configuration module, wherein the non-relational database is suitable for storing a configuration item list corresponding to the configuration item information of each component, and the configuration item list contains multiple configuration item fields; the association relationship library is suitable for storing the association relationships between configuration item fields of different components; the configuration module is suitable for converting the association relationships and the configuration item list into graph data in the graph database, and generating a topological diagram of association relationships between components based on the graph data in the graph database, and the topological diagram of association relationships between components contains each component and the association relationships.

[0013] Optionally, the non-relational database is provided with types corresponding to each component and configuration item list templates corresponding to each type; the configuration module is also suitable for selecting data from the configuration item information of each component and inputting the corresponding configuration item list template to generate a configuration item list.

[0014] Optionally, the graph data includes multiple nodes and edges, each node corresponds to a configuration item list of a component, and each edge corresponds to an association relationship between two configuration item lists.

[0015] Optionally, in the process of converting association relationships and configuration item lists into graph data in a graph database, the configuration module is further used to: regularly convert all association relationships and configuration item lists into graph data, and / or when some configuration item lists in the non-relational database are changed, update the graph database according to the association relationships and the changed configuration item lists.

[0016] Optionally, when part of the configuration item list in the non-relational database is changed, in the process of updating the graph database according to the association relationship and the changed configuration item list, the configuration module is further used to: confirm whether there is any modification to part of the configuration item list in the non-relational database, and confirm whether the configuration item list before and after the modification is different. When the confirmation result is yes, update the graph database according to the association relationship and part of the data.

[0017] To solve the above technical problems, the present application provides a computer-readable medium storing computer program code, which, when executed by a processor, implements the above-mentioned method for generating a topological graph of association relationships between components.

[0018] Compared with the existing technology, the present application has the following advantages: the configuration item information of the component is stored in a non-relational database, and an association relationship library containing various association relationships is established, so that the association relationships and configuration item lists can be flexibly and efficiently converted into graph data in the graph database through the non-relational database and the association relationship library to generate a component-to-component association relationship topology graph containing all components. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] The accompanying drawings are included to provide a further understanding of the present application. They are incorporated into and constitute a part of this application. The accompanying drawings illustrate embodiments of the present application and, together with this specification, serve to explain the principles of the present application. In the accompanying drawings:

[0020] Figure 1 This is a flowchart of a method for generating a topological graph of association relationships between components according to an embodiment of the present application;

[0021] Figure 2 According to this application Figure 1 A schematic flow chart of the sub-steps of step S11 in the illustrated embodiment;

[0022] Figure 3 This is a schematic diagram of a process for generating a topological subgraph of association relationships between specified components according to an embodiment of the present application;

[0023] Figure 4 is a partial schematic diagram of a topological diagram of association relationships between components with types as nodes according to an embodiment of the present application; and

[0024] Figure 5 It is a structural diagram of a system for generating a topological diagram of association relationships between components according to an embodiment of the present application. DETAILED DESCRIPTION

[0025] To more clearly illustrate the technical solutions of the embodiments of this application, the following is a brief introduction to the drawings required for describing the embodiments. Obviously, the drawings described below are merely examples or embodiments of this application. Those skilled in the art can apply this application to other similar scenarios based on these drawings without inventive effort. Unless otherwise apparent from the context or otherwise noted, the same reference numerals in the figures represent the same structure or operation.

[0026] As used in this application and the claims, unless the context clearly indicates otherwise, the words "a," "an," "an," and / or "the" are not intended to refer to the singular but may include the plural. Generally speaking, the terms "comprises" and "include" only indicate the inclusion of the steps and elements specifically identified, and these steps and elements do not constitute an exclusive list. A method or apparatus may also include other steps or elements.

[0027] Unless otherwise specifically stated, the relative arrangement of the parts and steps, numerical expressions and numerical values ​​set forth in these embodiments do not limit the scope of the present application. At the same time, it should be understood that, for ease of description, the sizes of the various parts shown in the drawings are not drawn according to actual proportional relationships. The techniques, methods and equipment known to those of ordinary skill in the relevant art may not be discussed in detail, but where appropriate, the techniques, methods and equipment should be considered as part of the authorization specification. In all examples shown and discussed here, any specific values ​​should be interpreted as being merely exemplary and not as limitations. Therefore, other examples of the exemplary embodiments may have different values. It should be noted that similar numbers and letters represent similar items in the following figures, and therefore, once an item is defined in one figure, it does not need to be further discussed in subsequent figures.

[0028] Flowcharts are used in this application to illustrate the operations performed by systems according to embodiments of the present application. It should be understood that the preceding or following operations are not necessarily performed in exact order. Instead, the various steps may be processed in reverse order or simultaneously. Furthermore, other operations may be added to these processes, or one or more operations may be removed from these processes.

[0029] Example 1

[0030] Figure 1 This is a flow chart of a method for generating a topological diagram of association relationships between components according to an embodiment of the present application. Figure 1 As shown, the method 100 for generating a component association relationship topology diagram includes the following steps.

[0031] Step S11 is to store the configuration item information of each component in a non-relational database to generate a configuration item list corresponding to each component. In this embodiment, the non-relational database is a document database, such as MongoDB. In this embodiment, the components include the Xinchuang component. Figure 2 As shown, step S11 in this embodiment preferably includes the following sub-steps. Step S111 is to set the types corresponding to each component in the non-relational database. In this embodiment, the components of the same type have the same functions. Therefore, for the three components of server A1, server A2, and server A3, their corresponding types can be set to servers. In this embodiment, the types include virtualization host, middleware, database, virtualization cluster, virtualization host, virtualization platform, storage and server, etc. Step S112 is to set the configuration item list template corresponding to each type in the non-relational database. Among them, the configuration item list contains multiple configuration item fields corresponding to the configuration item information. Exemplarily, in this embodiment, the type is host (OS), and the configuration item fields in its corresponding configuration list template include IP, hba name, service name, server type, environment, serial number, system name, NAA, primary key and attributes, etc. It can be understood that in this embodiment, different configuration item list templates are set according to the characteristics of different types. Furthermore, this implementation obtains information about the association relationships between components by setting configuration item fields. For example, by entering the number of another component, "SAN Switch B2," in the configuration item field "SAN Switch" for component "Host B1," this indicates that components "Host B1" and "SAN Switch B2" have an association relationship. Step S113 selects data from the component's configuration item information for each component and inputs it into the corresponding configuration item list template to generate a configuration item list. As can be appreciated, step S113 accurately preserves information about possible association relationships within the configuration item information.

[0032] Further references Figure 1, step S12 is to store the association relationship between the configuration item fields of different components in the association relationship library. Exemplarily, when the switch number can be filled in the configuration item field "SAN switch", and there is a configuration field "SAN switch number" that can also be filled in with the switch number, it can be considered that there is an association relationship between the two configuration fields, and the two configuration fields can be stored in the association relationship library in pairs. In this embodiment, the setting of the association relationship is implemented through the association relationship library, and the association relationship library is independent of the non-relational database. Therefore, the operation and maintenance management personnel who need to draw the association relationship topology diagram between components can flexibly set the association relationship of the association relationship library according to the requirements of the association relationship topology diagram between components without affecting the data in the non-relational database.

[0033] Continue to refer Figure 1 , step S13 is to convert the association relationship and the configuration item list into graph data in the graph database. In this embodiment, the graph data includes multiple nodes and edges, each node corresponds to the configuration item list of a component, and each edge corresponds to the association relationship between two configuration item lists. It can be understood that each node in the graph database can represent a component and contain information in the configuration item list corresponding to the component. In this embodiment, the association relationships that may be contained in each two components are first selected from the association relationship library, and then the corresponding configuration item fields in the configuration item lists corresponding to the two components are checked in turn according to each selected association relationship to see whether they contain the same content. If so, the two components have an association relationship. It should be noted that compared to converting data in a relational database to a graph database, this embodiment converts data to a graph database by cooperating with a non-relational database and an association relationship library, which can more quickly parse the original data in the non-relational database and the association relationship library into graph data, thereby achieving a simple and flexible data model conversion. However, relational databases store data in tabular form, consisting of rows and columns, and use foreign keys to link tables. Therefore, during conversion, due to the multi-layer nesting and intersection of relationships, multiple table joins may be required, making the conversion process extremely complicated.

[0034] In step S13 of this embodiment, different data conversion strategies are used according to different situations of the configuration item list. The first strategy is regular conversion. Specifically, this embodiment converts all association relationships and configuration item lists into graph data regularly (for example, once a day), thereby ensuring that the graph data in the graph database is continuously updated and has a high degree of reliability. It is understandable that in some cases, operation and maintenance management personnel need to uniformly maintain and manage thousands of components. Therefore, the topological diagram of the association relationship between the same components may contain thousands of different components, and uniformly updating the graph data of each component will consume a lot of computing resources. Therefore, the second strategy is local adjustment. Specifically, in this embodiment, when some configuration item lists in the non-relational database are changed, the graph database is updated according to the association relationship and the changed configuration item list, that is, only the corresponding graph data in the graph database is updated for the changed configuration item list, to achieve small-scale local adjustment, which has a faster response speed than the overall update and avoids excessive consumption of computing resources. In the above-mentioned local adjustment process, the specific steps include: confirming whether there is any modification to the partial configuration item list in the non-relational database, and confirming whether the configuration item list before and after the modification is different, and when the result of the confirmation is yes, updating the graph database according to the association relationship and partial data. In this embodiment, it is first confirmed whether there is any modification to the configuration item list to confirm that the operation and maintenance management personnel have performed a modification operation on the configuration item list, and then confirming whether the configuration item list before and after the modification is different to confirm that the operation and maintenance management personnel have performed a valid modification operation on the configuration item list, and then the data is updated. This method can further avoid the waste of computing resources caused by misoperation or invalid operation. In the local adjustment process of this embodiment, when the result of the confirmation is yes, the corresponding graph data update operation is triggered by webhook. It should be noted that in other embodiments of the present application, only the first strategy or the second strategy can be executed.

[0035] Finally, reference Figure 1 , step S14 is to generate a component-to-component relationship topology graph based on the graph data in the graph database, the component-to-component relationship topology graph includes each component and its relationship. In this embodiment, a component-to-component relationship topology subgraph of a specified component can also be generated based on the graph database. Figure 3As shown, the step of generating a topological subgraph of the association relationship between components of a specified component based on a graph database preferably includes the following steps. Step S21 is to obtain the unique identifier corresponding to the component in the graph database. It can be understood that in the process of converting the configuration item list into graph data, this embodiment also generates a unique identifier for each component in the graph data. For example, the number of each component in the available configuration item field can be used as the unique identifier corresponding to the component. The unique identifier can distinguish the corresponding component from other components. In this embodiment, the operation and maintenance management personnel obtain the unique identifier corresponding to the component through step S21. It can be understood that the operation and maintenance management personnel can obtain the unique identifier by querying the graph database, or by recording a table that records the correspondence between the unique identifier and the component. Step S22 is to construct the association relationship topological subgraph corresponding to the component based on the node corresponding to the unique identifier in the graph database and the edges and other nodes associated with the node. Refer to Figure 4 In this embodiment, each type can also be a node to more concisely display the topological diagram of the association relationship between components. Figure 4 As shown, Figure 4 The example shows the nodes corresponding to some types, such as the application system, functional module, cluster, host (OS), host-mounted NAS, non-container middleware, container middleware, rabbit message queue, TDsql-Mysql, OceanBase, MONGODB, ORACLE, database instance, SQLSERVER, INFORMIX, MYSQL, DAMENG, TDSQL_pg, and redis data. It is understandable that Figure 4 A one-way arrow between two nodes indicates an association between the two nodes. Furthermore, the application system to which these nodes belong has a higher-level node, "Application System." The functional modules and clusters to which they belong have a higher-level node, "Function Module." The host (OS) has a higher-level node, "Host." The host-mounted NAS has a higher-level node, "NAS." Non-container middleware and container middleware have a higher-level node, "Middleware." The rabbit message queue has a higher-level node, "Message Queue." TDsql-MySQL, OceanBase, MONGODB, ORACLE, database instances, SQLSERVER, INFORMIX, MYSQL, DAMENG, TDSQL_pg, and Redis data have a higher-level node, "Database."

[0036] Example 2

[0037] Figure 5 This is a schematic diagram of the structure of a system for generating a topological diagram of association relationships between components according to an embodiment of the present application. Figure 5As shown, the component association relationship topology diagram generation system 200 includes a non-relational database 201 , an association relationship library 202 , a graph database 203 , a configuration module 204 and a display module 205 .

[0038] The non-relational database 201 is suitable for storing a configuration item list corresponding to the configuration item information of each component, and the configuration item list contains multiple configuration item fields. In this embodiment, the non-relational database 201 is a document database, such as MongoDB. The non-relational database 201 is also provided with types corresponding to each component, and configuration item list templates corresponding to each type. Accordingly, the configuration module 204 is suitable for selecting data from the configuration item information of the component and inputting the corresponding configuration item list template to generate a configuration item list for each component. It should be noted that the configuration item list and the configuration item fields have been explained in Example 1 and will not be repeated here. It can be understood that the non-relational database 201 of this embodiment can accurately retain information that may contain association relationships in the configuration item information through the configuration item list.

[0039] The association relationship library 202 is suitable for storing the association relationships between the configuration item fields of different components. In this embodiment, the configuration module 204 is suitable for storing each association relationship in the association relationship library 202. It should be noted that the association relationship has also been explained in Example 1 and will not be repeated here. It can be understood that the association relationship library 202 and the non-relational database 201 are independent of each other. Therefore, the operation and maintenance management personnel who need to draw the association relationship topology diagram between components can flexibly set the association relationship of the association relationship library according to the requirements of the association relationship topology diagram between components without affecting the data in the non-relational database.

[0040] Configuration module 204 is also adapted to convert associations and configuration item lists into graph data within graph database 203. Specifically, in this embodiment, graph database 203 is used to store graph data. In this embodiment, graph data comprises multiple nodes and edges, with each node corresponding to a component's configuration item list, and each edge corresponding to an association between two configuration item lists. In this embodiment, configuration module 204 first selects possible associations between two components from association database 202. Then, based on each selected association, it sequentially checks whether the corresponding configuration item fields in the configuration item lists corresponding to the two components contain identical content. If so, the two components are considered to have an association. During the data conversion process, configuration module 204 can perform corresponding conversion operations based on different conversion data scenarios. In the first conversion operation, configuration module 204 periodically (e.g., once a day) converts all associations and configuration item lists into graph data. In the second conversion operation, when some configuration item lists in non-relational database 201 change, configuration module 204 updates graph database 203 based on the associations and the changed configuration item lists. In the second conversion operation, the configuration module 204 specifically operates by confirming whether modifications have been made to a portion of the configuration item list in the non-relational database, confirming whether the configuration item list before and after the modification differs, and, if so, updating the graph database based on the associated relationships and partial data. It will be appreciated that, through the above operations, the configuration module 204 first confirms whether modifications have been made to the configuration item list to verify that the operations and maintenance manager has made any modifications to the configuration item list, then confirms whether the configuration item list before and after the modification differs to verify that the operations and maintenance manager has made any valid modifications to the configuration item list, before performing any data updates. This operation further prevents waste of computing resources caused by invalid updates by the configuration module 204 due to erroneous or invalid operations by the operations and maintenance manager. In the second conversion operation of this embodiment, if the configuration module 204 confirms yes, a corresponding graph data update operation is triggered via a webhook. In this embodiment, both the first and second conversion operations are employed to ensure high accuracy of the graph data. It should be noted that, in other embodiments of the present application, the configuration module 204 may perform only the first or second conversion operation.

[0041] In this embodiment, the inter-component association relationship topology diagram generation system 200 also generates an inter-component association relationship topology diagram based on the graph data in the graph database 203 through the configuration module 204, and displays the inter-component association relationship topology diagram to the operation and maintenance management personnel through the display module 205. Among them, the inter-component association relationship topology diagram contains various components and association relationships. In this embodiment, the configuration module 204 can also generate an inter-component association relationship topology subgraph of a specified component based on the graph database 201. Specifically, the configuration module 204 first obtains the unique identifier corresponding to the component in the graph database 203. Then the configuration module 204 constructs the association relationship topology subgraph corresponding to the component based on the node corresponding to the unique identifier in the graph database 203 and the edges and other nodes associated with the node. In addition, in this embodiment, each type can also be set as a node in the graph database 201, and a more concise inter-component association relationship topology diagram with the type as the node is generated through the configuration module 204.

[0042] In addition, the present application also proposes a computer-readable medium storing computer program code, which implements the above-mentioned method for generating a topological graph of association relationships between components when executed by a processor.

[0043] The basic concepts have been described above. It will be apparent to those skilled in the art that the above disclosures are merely examples and do not limit the present application. Although not explicitly stated herein, those skilled in the art may make various modifications, improvements, and revisions to the present application. Such modifications, improvements, and revisions are suggested in the present application and remain within the spirit and scope of the exemplary embodiments of the present application.

[0044] At the same time, this application uses specific terms to describe the embodiments of this application. For example, "one embodiment," "an embodiment," and / or "some embodiments" refer to a certain feature, structure, or characteristic related to at least one embodiment of this application. Therefore, it should be emphasized and noted that "one embodiment," "an embodiment," or "an alternative embodiment" mentioned twice or multiple times in different locations in this specification does not necessarily refer to the same embodiment. In addition, certain features, structures, or characteristics in one or more embodiments of this application may be appropriately combined.

[0045] Some aspects of the present application can be performed entirely by hardware, entirely by software (including firmware, resident software, microcode, etc.), or by a combination of hardware and software. The above hardware or software can be referred to as "data blocks", "modules", "engines", "units", "components" or "systems". The processor can be one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DAPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors or combinations thereof. In addition, various aspects of the present application may be expressed as computer products located in one or more computer-readable media, which include computer-readable program code. For example, computer-readable media may include, but are not limited to, magnetic storage devices (e.g., hard disks, floppy disks, tapes...), optical disks (e.g., compact disks CDs, digital versatile disks DVDs...), smart cards, and flash memory devices (e.g., cards, sticks, key drives...).

[0046] A computer-readable medium may include a propagated data signal embodying computer program code, for example, in baseband or as part of a carrier wave. The propagated signal may be in a variety of forms, including electromagnetic, optical, etc., or a suitable combination thereof. A computer-readable medium may be any computer-readable medium other than a computer-readable storage medium that can be connected to an instruction execution system, apparatus, or device to communicate, propagate, or transmit the program for use. The program code on the computer-readable medium may be transmitted via any suitable medium, including radio, cable, fiber optic cable, radio frequency signal, or similar medium, or any combination of the above.

[0047] Similarly, it should be noted that, in order to simplify the description of this application and thus facilitate understanding of one or more embodiments of the application, the foregoing description of the embodiments of this application sometimes combines multiple features into a single embodiment, figure, or description thereof. However, this disclosure method does not mean that the subject matter of this application requires more features than those recited in the claims. In fact, the features of an embodiment may be fewer than all the features of the individual embodiments disclosed above.

[0048] Although the present application has been described with reference to the current specific embodiments, ordinary technicians in this technical field should recognize that the above embodiments are only used to illustrate the present application, and various equivalent changes or substitutions can be made without departing from the spirit of the present application. Therefore, as long as the changes and modifications to the above embodiments are within the scope of the essential spirit of the present application, they will fall within the scope of the claims of the present application.

Claims

1. A method for generating a topological graph of association relationships between components, characterized in that: include: Storing the configuration item information of each component in a non-relational database to generate a configuration item list corresponding to each component, wherein the configuration item list includes a plurality of configuration item fields corresponding to the configuration item information; Storing the association relationships between the configuration item fields of different components in an association relationship library; Converting the association relationship and the configuration item list into graph data in a graph database; The inter-component association relationship topology graph is generated according to the graph data in the graph database, and the inter-component association relationship topology graph includes each of the components and the association relationships.

2. The method for generating a component association relationship topology diagram according to claim 1, wherein: The step of storing the configuration item information of each component in a non-relational database to generate a configuration item list corresponding to each component further includes: Setting the type corresponding to each of the components in the non-relational database; Setting a configuration item list template corresponding to each of the types in the non-relational database; For each of the components, data is selected from the configuration item information of the component and input into the corresponding configuration item list template to generate the configuration item list.

3. The method for generating a component association relationship topology diagram according to claim 2, wherein: The types include one or more of a virtualization host, middleware, database, virtualization cluster, virtualization host machine, virtualization platform, storage and server.

4. The method for generating a component association relationship topology diagram according to claim 1, wherein: The graph data includes multiple nodes and edges, each of the nodes corresponds to the configuration item list of the component, and each edge corresponds to the association relationship between two configuration item lists.

5. The method for generating a component association relationship topology diagram according to claim 4, wherein: The step of converting the association relationship and the configuration item list into graph data in a graph database further includes: Periodically converting all the association relationships and the configuration item lists into the graph data, and / or When part of the configuration item list in the non-relational database is changed, the graph database is updated according to the association relationship and the changed configuration item list.

6. The method for generating a topological diagram of association relationships between components according to claim 5, wherein: When part of the configuration item list in the non-relational database is changed, the step of updating the graph database according to the association relationship and the changed configuration item list further includes: Confirm whether some of the configuration item lists in the non-relational database have been modified, and confirm whether the configuration item lists before and after the modification are different. When the confirmation result is yes, update the graph database according to the association relationship and the changed configuration item list.

7. The method for generating a component association relationship topology diagram according to claim 4, wherein: Also includes: Obtain a unique identifier corresponding to the component in the graph database; An association relationship topology subgraph corresponding to the component is constructed according to the node corresponding to the unique identifier in the graph database and the edges and other nodes associated with the node.

8. A system for generating a topological diagram of association relationships between components, characterized in that: include: Non-relational database, relational database, graph database and configuration module, The non-relational database is suitable for storing a configuration item list corresponding to the configuration item information of each component, and the configuration item list includes multiple configuration item fields; The association relationship library is suitable for storing association relationships between the configuration item fields of different components; The configuration module is suitable for converting the association relationship and the configuration item list into graph data in a graph database, and generating the inter-component association relationship topology graph based on the graph data in the graph database, wherein the inter-component association relationship topology graph includes each of the components and the association relationship.

9. The system for generating a topological diagram of component association relationships according to claim 8, wherein: The non-relational database is provided with a type corresponding to each component and a configuration item list template corresponding to each type; The configuration module is further adapted to select data from the configuration item information of each component and input the data into the corresponding configuration item list template to generate the configuration item list.

10. The system for generating a topological diagram of component association relationships according to claim 8, wherein: The graph data includes multiple nodes and edges, each of the nodes corresponds to the configuration item list of the component, and each edge corresponds to the association relationship between two configuration item lists.

11. The system for generating a component association relationship topology diagram according to claim 10, wherein: In the process of converting the association relationship and the configuration item list into graph data in a graph database, the configuration module is further used to: Periodically converting all the association relationships and the configuration item lists into the graph data, and / or When part of the configuration item list in the non-relational database is changed, the graph database is updated according to the association relationship and the changed configuration item list.

12. The system for generating a component association relationship topology diagram according to claim 11, wherein: When part of the configuration item list in the non-relational database is changed, in the process of updating the graph database according to the association relationship and the changed configuration item list, the configuration module is further used to: Confirm whether some of the configuration item lists in the non-relational database have been modified, and confirm whether the configuration item lists before and after the modification are different. When the confirmation result is yes, update the graph database according to the association relationship and the changed configuration item list.

13. A computer-readable medium storing computer program code, wherein when executed by a processor, the computer program code implements the method for generating a component association relationship topology map according to any one of claims 1 to 7.

Images