CN116166737A

CN116166737A - Resource topological graph generation method and device, electronic equipment and readable storage medium

Info

Publication number: CN116166737A
Application number: CN202111403590.9A
Authority: CN
Inventors: 陈健
Original assignee: SF Technology Co Ltd
Current assignee: SF Technology Co Ltd
Priority date: 2021-11-24
Filing date: 2021-11-24
Publication date: 2023-05-26

Abstract

The application provides a method and a device for generating a resource topological graph, electronic equipment and a computer readable storage medium. The method for generating the resource topological graph comprises the following steps: acquiring a target system code of a target service system; acquiring various types of resources associated with the target system code; acquiring a first association relationship between first resource types corresponding to the various types of resources from a preset configuration database; and taking the first resource type as a node, and generating a system service topology graph of the target service system according to the first association relation. According to the method and the device, different types of resources in the service system can be associated more pertinently, and the problem that the service pertinence of the resource topological graph is not strong, so that the resource management requirement of a service scene is difficult to meet is solved.

Description

Resource topological graph generation method and device, electronic equipment and readable storage medium

Technical Field

The present invention relates to the field of data processing technologies, and in particular, to a method and an apparatus for generating a resource topological graph, an electronic device, and a computer readable storage medium.

Background

In the existing network environment, various data resources are interrelated, and the abnormality of one resource may cause the abnormality of other resources at the same time.

In order to facilitate the understanding of data processing personnel on resources and facilitate the management of resources such as abnormal processing, updating and the like of the resources, the association relationship among various types of resources is formed into a topological graph for visualization in the prior art.

However, the inventor of the application finds that, in the actual application process, as the existing resource topological graph only correlates different types of resources, the service pertinence in the actual service scene is not strong aiming at all the resource types, and it is difficult to meet the resource management requirement of the service scene.

Disclosure of Invention

The application provides a method, a device, electronic equipment and a computer readable storage medium for generating a resource topological graph, and aims to solve the problem that the resource management requirement of a service scene is difficult to meet due to the fact that the service pertinence of the existing resource topological graph is not strong.

In a first aspect, the present application provides a method for generating a resource topology map, where the method includes:

acquiring a target system code of a target service system;

acquiring various types of resources associated with the target system code;

Acquiring a first association relationship between first resource types corresponding to the various types of resources from a preset configuration database;

and taking the first resource type as a node, and generating a system service topology graph of the target service system according to the first association relation.

In some embodiments of the present application, after the generating the system service topology map of the target service system according to the first association relationship by using the first resource type as a node, the method further includes:

displaying the system service topology graph, wherein the system service topology graph comprises a plurality of resources;

responding to a selection operation for a target resource in the system service topological graph, and acquiring a resource service topological graph of the target resource;

and displaying the resource service topological graph.

In some embodiments of the present application, the obtaining a resource service topology map of the target resource includes:

acquiring target upper and lower layer resources associated with the target resources and a second association relationship between the target upper and lower layer resources;

and generating a resource service topology graph of the target resource according to the second association relation by taking the target upper and lower layer resource as a node.

In some embodiments of the present application, the obtaining the target upper and lower layer resources associated with the target resource and the second association relationship between the target upper and lower layer resources includes:

detecting whether the target resource is an access point resource of a second resource type corresponding to the target resource;

if the target resource is the access point resource, inserting the identification information of the target resource into a preset dynamic structured query statement;

and acquiring the target upper and lower layer resources of the target resource association record and the second association relation from a preset resource association configuration database through the dynamic structured query statement.

In some embodiments of the present application, the method further comprises:

if the target resource is not the access point resource, the identification information of the access point resource is inserted into the dynamic structured query statement;

and acquiring upper and lower layer resources associated with the access point resources from the resource association configuration database through the dynamic structured query statement to serve as the target upper and lower layer resources, and acquiring association relations of the upper and lower layer resources to serve as the second association relations.

In some embodiments of the present application, the displaying the system service topology graph includes:

displaying a first system service topology graph containing first resource types corresponding to the various types of resources;

responding to the unfolding operation aiming at the target resource type in the first system service topological graph, and displaying a second system service topological graph containing all resources corresponding to the target resource type;

the responding to the selection operation of the target resource in the system service topological graph obtains the resource service topological graph of the target resource, and the method further comprises the following steps:

and responding to a selection operation of a target resource in the second system service topological graph, acquiring a resource service topological graph of the target resource, wherein the target resource is acquired from each resource corresponding to the target resource type.

In some embodiments of the present application, the generating, with the first resource type as a node, a system service topology diagram of the target service system according to the first association relationship includes:

acquiring the aggregation quantity of the various types of resources;

and generating a system service topological graph of the target service system according to the first association relation by taking the first resource type and the aggregation number as nodes through a rendering plug-in a preset target terminal.

In a second aspect, the present application provides a device for generating a resource topology map, where the device for generating a resource topology map includes:

the first acquisition unit is used for acquiring a target system code of a target service system;

a second obtaining unit, configured to obtain various types of resources associated with the target system code;

a third obtaining unit, configured to obtain a first association relationship between the first resource types corresponding to the various types of resources from a preset configuration database;

and the generating unit is used for generating a system service topological graph of the target service system according to the first association relation by taking the first resource type as a node.

In some embodiments of the present application, the generating device of the resource topology map further includes a display unit, where after the first resource type is used as a node and the system service topology map of the target service system is generated according to the first association relationship, the display unit is specifically configured to:

And displaying the resource service topological graph.

In some embodiments of the present application, the display unit is specifically configured to:

In some embodiments of the present application, the generating unit is specifically configured to:

acquiring the aggregation quantity of the various types of resources;

In a third aspect, the present application further provides an electronic device, where the electronic device includes a processor and a memory, where the memory stores a computer program, and when the processor invokes the computer program in the memory, the processor executes steps in any one of the resource topology map generating methods provided in the present application.

In a fourth aspect, the present application further provides a computer readable storage medium having stored thereon a computer program, the computer program being loaded by a processor to perform the steps in the method of generating a resource topology map.

According to the method and the system, the first resource types corresponding to the various types of resources associated with the target system codes are used as nodes, and the system service topology diagram of the target service system is generated according to the first association relation among the first resource types, so that on one hand, the association relation of the various types of resources in the target service system can be visualized, and therefore, a user can know the association relation of the various types of resources in the target service system more clearly and quickly, and when data management such as updating, changing and repairing needs to be conducted on the resources in the service system, the affected range before and after the resource management can be known more clearly and quickly. On the other hand, because the service system is used as a dimension to generate the resource topological graph, instead of simply associating the different types of resources, the different types of resources in the service system can be associated more pertinently, and the problem that the service pertinence of the resource topological graph is not strong, so that the resource management requirement of a service scene is difficult to meet is solved.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the description of the embodiments will be briefly introduced below, it being obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

Fig. 1 is a schematic view of a scenario of a resource topology map generating system provided in an embodiment of the present application;

FIG. 2 is a schematic flow chart of a method for generating a resource topology map according to an embodiment of the present application;

FIG. 3 is a schematic diagram illustrating a process for generating a system service topology provided in an embodiment of the present application;

FIG. 4 is a schematic diagram of an architecture of a topology provided in an embodiment of the present application;

FIG. 5 is a schematic diagram of an architecture of a system service topology provided in an embodiment of the present application;

FIG. 6 is a schematic diagram of a display jump flow of a resource topology provided in an embodiment of the present application;

FIG. 7 is a schematic diagram of another architecture scenario of a system service topology provided in an embodiment of the present application;

FIG. 8 is a schematic diagram illustrating a process for generating a resource service topology provided in an embodiment of the application;

FIG. 9 is a schematic structural diagram of one embodiment of a resource topology map generating apparatus provided in an embodiment of the present application;

fig. 10 is a schematic structural diagram of an embodiment of an electronic device provided in an embodiment of the present application.

Detailed Description

The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are only some, but not all, of the embodiments of the present application. All other embodiments, which can be made by those skilled in the art based on the embodiments herein without making any inventive effort, are intended to be within the scope of the present application.

In the description of the embodiments of the present application, it should be understood that the terms "first," "second," and the like are used for descriptive purposes only and are not to be construed as indicating or implying a relative importance or an implicit indication of the number of features indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include one or more of the described features. In the description of the embodiments of the present application, the meaning of "a plurality" is two or more, unless explicitly defined otherwise.

The following description is presented to enable any person skilled in the art to make and use the application. In the following description, details are set forth for purposes of explanation. It will be apparent to one of ordinary skill in the art that the present application may be practiced without these specific details. In other instances, well-known processes have not been described in detail in order to avoid unnecessarily obscuring descriptions of the embodiments of the present application. Thus, the present application is not intended to be limited to the embodiments shown, but is to be accorded the widest scope consistent with the principles and features disclosed in the embodiments of the present application.

The execution main body of the method for generating the resource topological graph in the embodiment of the present application may be a device for generating the resource topological graph provided in the embodiment of the present application, or different types of electronic devices such as a server device, a physical host, or a User Equipment (UE) integrated with the device for generating the resource topological graph, where the device for generating the resource topological graph may be implemented in a hardware or software manner, and the UE may specifically be a terminal device such as a smart phone, a tablet computer, a notebook computer, a palm computer, a desktop computer, or a personal digital assistant (Personal Digital Assistant, PDA).

The electronic equipment can adopt a working mode of independent operation or a working mode of equipment clusters, and different types of resources in a service system can be associated more pertinently by applying the method for generating the resource topological graph provided by the embodiment of the application, so that the problem that the service pertinence of the resource topological graph is not strong, and the resource management requirement of a service scene is difficult to meet is solved.

Referring to fig. 1, fig. 1 is a schematic view of a scenario of a resource topology map generating system provided in an embodiment of the present application. The system for generating the resource topological graph may include an electronic device 100, and a generating device of the resource topological graph is integrated in the electronic device 100. For example, the electronic device may obtain a target system code for a target business system; acquiring various types of resources associated with the target system code; acquiring a first association relationship between first resource types corresponding to the various types of resources from a preset configuration database; and taking the first resource type as a node, and generating a system service topology graph of the target service system according to the first association relation.

In addition, as shown in fig. 1, the resource topology map generating system may further include a memory 200 for storing data, such as various types of resource data.

It should be noted that, the schematic view of the scenario of the generating system of the resource topological graph shown in fig. 1 is only an example, and the generating system and scenario of the resource topological graph described in the embodiments of the present application are for more clearly describing the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application, and as one of ordinary skill in the art can know, along with the evolution of the generating system of the resource topological graph and the appearance of a new service scenario, the technical solutions provided by the embodiments of the present invention are equally applicable to similar technical problems.

Next, a method for generating a resource topology map provided in an embodiment of the present application is described, in this embodiment of the present application, an electronic device is used as an execution body, and in order to simplify and facilitate description, in a subsequent method embodiment, the execution body is omitted, where the method for generating a resource topology map includes: acquiring a target system code of a target service system; acquiring various types of resources associated with the target system code; acquiring a first association relationship between first resource types corresponding to the various types of resources from a preset configuration database; and taking the first resource type as a node, and generating a system service topology graph of the target service system according to the first association relation.

Referring to fig. 2, fig. 2 is a schematic flow chart of a method for generating a resource topology map according to an embodiment of the present application. It should be noted that although a logical order is depicted in the flowchart, in some cases the steps depicted or described may be performed in a different order than presented herein. The method for generating the resource topological graph comprises the following steps 201 to 204, wherein:

201. and obtaining the target system code of the target service system.

The business system refers to a resource system of a basic organization unit of resource management division, for example, a resource system of a company.

The resource system of a certain basic organization unit refers to a generic term of resources related to the basic organization unit.

The target service system is a service system to be generated with respect to a system service topology diagram among the plurality of service systems, for example, the system service topology diagram needs to be generated with respect to a company resource, and the target service system is a company a.

The system code refers to the identification of the service system, and the target system code refers to the identification of the target service system. Such as a company's resource management code.

There are various ways to obtain the target system code in step 201, which illustratively includes:

(1) The system codes of all the service systems are preset and stored in the electronic equipment preset database, and the target terminal can read and display the system codes of all the service systems stored in the electronic equipment preset database; then, the user can input or select the system code of the service system needing to display the topological graph based on the system code of each displayed service system and the target terminal; at this time, the electronic device may receive the system code input or selected by the user from the target terminal as the target system code. For example, in the embodiment of the present application, a User Interface (UI) for querying a resource topological graph is provided, and a User may input, at a UI Interface of a target terminal, a system code of a service system to be queried, and an electronic device obtains the system code input by the User as a target system code. The target terminal and the electronic device may be the same device or two different devices.

Among these, the UI is a medium for interaction and information exchange between a system and a user, and it implements conversion between an internal form of information and a human-acceptable form.

(2) And when the timing task of generating the system service topological graph of the target service system is triggered, the electronic equipment directly acquires the target system code of the target service system stored in the electronic equipment.

202. And acquiring various types of resources associated with the target system code.

In this embodiment of the present application, the resource refers to a software or hardware resource for processing service data, for example, database resources MySQL, mycat for storing service data, and for example, computing resources CVM, BMS for computing service data to form a specific format.

In step 202, various manners of obtaining various types of resources are exemplified, including:

(1) The association between each resource and the system code is stored in a preset resource database, and in step 202, each resource associated with the target system code is obtained first, and then each resource is classified to obtain each type of resource. Referring to fig. 3, fig. 3 is a schematic diagram illustrating a process of generating a system service topology map according to an embodiment of the present application, where step 202 may specifically include steps 2021 to 2022 as follows:

2021. and acquiring each resource associated with the target system code from a preset resource database.

2022. And classifying the resources associated with the target system code to obtain various types of resources associated with the target system code and the aggregate quantity of the various types of resources.

For example, as shown in fig. 3, after receiving the target system code input by the user in the front-end user interface, all the resources associated with the target system code are queried from the preset resource database. Then, according to a preset classification rule, classifying all the resources related to the target system code, for example, using Kafka, redis and the like as middleware type resources; mySQL, mycat and the like are used as database type resources; CVM, BMS, etc. as computing type resources; CRM and the like are taken as machine type resources; finally, various types of resources related to the target system code and the aggregate quantity of the various types of resources are obtained.

Wherein Kafka is a distributed, partitioned, multi-copy, zookeeper-based distributed messaging system.

Wherein Redis is an open source key-value pair storage database written in ANSI C language, compliant with BSD protocol, supporting network, and capable of being based on memory, distributed and optional persistence.

Wherein MySQL is a relational database management system.

Wherein Mycat is a large database cluster which is thoroughly open-sourced and developed for enterprise applications.

The CVM is a cloud server, and is a simple, efficient, safe and reliable computing service with elastically scalable processing capacity.

The BMS is a bare metal server, namely a physical server, and is a computing service with virtual machine elasticity and physical machine performance.

The CRM is a cloud machine room and is an internet-based computing mode, and by the mode, shared software and hardware resources and information can be provided for computers and other devices as required.

(2) The resources are classified in advance according to the resource types, the association between the various types of resources and the system code is stored in a preset resource database, and in step 202, the various types of resources associated with the target system code and the aggregate number of the various types of resources are directly inquired and read.

203. And acquiring a first association relation between the first resource types corresponding to the various types of resources from a preset configuration database.

The system service topology graph in the embodiment of the application takes the first resource types corresponding to the various types of resources as nodes and takes the link relation among the first resource types as edges.

The first resource type refers to a resource category corresponding to each type of resource associated with the target system code, for example, a middleware type, a database type and a calculation type.

The first association relationship refers to a link relationship between a first resource type corresponding to one type of resource and a first resource type corresponding to another type of resource, for example, an upper layer resource type and a lower layer resource type of each resource type; the first association relationship is specifically configured to indicate whether an edge connection relationship exists between nodes where two resource types are located in a system service topology graph, for example, as shown in fig. 4, fig. 4 is a schematic diagram of the topology graph provided in the embodiment of the present application, where an edge connection relationship does not exist between a node where an a resource type and a C resource type are located, and then an edge connection relationship does not exist between a node where an a resource type and a C resource type are located; and if the node where the A resource type and the B resource type are located has an edge connection relationship, the node where the A resource type and the B resource type are located has an edge connection relationship.

Specifically, the preset configuration database records the preconfigured edge connection relationship, and in step 203, the first association relationship between the first resource types corresponding to the various types of resources is read from the preset configuration database directly based on the various types of resources obtained in step 202. At this time, step 203 may further include: constructing an edge connection relation among resource types; and storing the edge connection relation among the resource types into a preset configuration database. The preset configuration database can be a configuration management database (Configuration Management Database, CMDB), which is a logic database containing the information of the full life cycle of the configuration items and the relationship among the configuration items (including physical relationship, real-time communication relationship, non-real-time communication relationship and dependency relationship).

For example, the preset configuration database records a preconfigured edge connection relationship, as shown in the following table 1, the source_object_code in the table 1 represents a resource type corresponding to a start point of an edge, and the dest_object_code represents a resource type corresponding to an end point of the edge. If the first resource types corresponding to the types of resources obtained in step 202 are respectively: arrayInstance, arrayServer, kafkalnstance, kafkaBroker, MWHostInstance, mongodbService, mongodbCluster, mongodbInstance, RDBHost, BMSHost, step 203 may obtain the preconfigured edge connection relationship as shown in table 1 as the first association relationship.

TABLE 1

id	source_object_code	dest_object_code
			1	ArrayInstance	ArrayServer
2	ArrayServer	ArrayHardware
			3	Kafkalnstance	KafkaBroker
4	KafkaBroker	MWHostInstance
			5	MWHostInstance	BMSHost
6	MongodbService	MongodbCluster
			7	MongodbCluster	MongodbInstance
8	MongodbInstance	RDBHost
			9	RDBHost	BMSHost

204. And taking the first resource type as a node, and generating a system service topology graph of the target service system according to the first association relation.

The system service topology graph refers to a topology graph of a target service system, wherein the topology graph takes first resource types corresponding to various types of resources corresponding to target system codes as nodes and takes association relations among the first resource types as edges. The system service topology graph is a resource topology graph taking a business system as a dimension. Wherein each resource type acts as a node of the system service topology.

There are various ways to generate the system service topology in step 204, including, illustratively:

(1) And the rendering plug-in the target terminal is integrated with the rendering plug-in for forming the topological graph, and a system service topological graph is generated according to the first resource type and the first association relation through the rendering plug-in the target terminal. Illustratively, at this time, the target system code is acquired based on the target terminal in step 201, and the first resource type acquired in step 202 and the first association relationship acquired in step 203 are returned to the target terminal in step 204; and drawing a graph according to the first resource type and the first association relation by a rendering plug-in the target terminal to form a system service topological graph of the target service system.

(2) The system service topology map may also be generated directly at the electronic device. At this time, the electronic device integrates a rendering plug-in for forming a topology map, and in step 204, the rendering plug-in the electronic device draws a map according to the first resource type acquired in step 202 and the first association relationship acquired in step 203 to form a system service topology map of the target service system.

For example, assume that the first resource types corresponding to the types of resources of the target system code "123" acquired in step 202 are respectively: arrayInstance, arrayServer, kafkalnstance, kafkaBroker, MWHostInstance, mongodbService, mongodbCluster, mongodbInstance, RDBHost, BMSHost the step 203 obtains the preconfigured edge connection relationships shown in table 1 as the first association relationships, and by using the first resource types (ArrayInstance, arrayServer, kafkalnstance, kafkaBroker, MWHostInstance, mongodbService, mongodbCluster, mongodbInstance, RDBHost, BMSHost) as nodes of the system service topology (i.e. each first resource type is used as a node), drawing according to the first association relationships shown in table 1, a system service topology as shown in fig. 5 can be formed, and the system service topology corresponds to the target system code "123".

Further, the system service topology diagram of the target service system further includes an aggregate number of the target system code-associated various types of resources, at this time, in step 202, the aggregate number of the target system code-associated various types of resources may be further counted, and in step 204, the system service topology diagram of the target service system carrying the aggregate number information of various types of resources may be generated based on the aggregate number of the target system code-associated various types of resources obtained by the statistics in step 202. Specifically, in step 204, the first resource type and the aggregate number of the resources of each type are used as nodes, and drawing is performed according to the first association relationship, so as to form a system service topology diagram of the target service system. The aggregate number of the types of resources refers to the total number of the types of resources in the target service system. By taking the first resource type and the aggregate number as nodes, a system service topological graph of the target service system is generated according to the first association relation, so that a user can more intuitively and comprehensively know the influence range and the influence number of the resources when the resource data of the target service system is updated, maintained and the like to be managed later.

Referring to fig. 3, for convenience of understanding, a process of generating a system service topology is described below by taking an example of forming edge and node data (i.e., various types of resources and a first association relationship) of a resource topology at an electronic device and forming a system service topology through an integrated rendering plugin drawing at a WEB front end. For example, the user may input the system code of the service system to be queried at the WEB front end, and transmit the system code as the target system code into the electronic device. The electronic equipment queries various types of resources and the aggregation quantity of the various types of resources which are associated with the target system code in the database, determines the edge and node data (namely the various types of resources and the first association relation) of the resource topological graph to be generated according to the various types of resources and the preset rule, and returns the edge and node data to the WEB front end. The rendering plug-in unit (such as Echarts plug-in unit and Antv.G6 plug-in unit) for forming the topological graph is integrated in the WEB front end, the rendering plug-in unit in the WEB front end draws the graph according to the edge and node data (namely various types of resources and the first association relation) returned by the electronic equipment to form a system service topological graph of a target service system corresponding to the target system code, and the system service topological graph of the target service system is displayed in the WEB front end.

By taking the first resource types corresponding to the various types of resources associated by the target system codes as nodes and generating a system service topological graph of the target service system according to the first association relationship among the first resource types, on one hand, the association relationship of the various types of resources in the target service system can be visualized, so that a user can know the association relationship of the various types of resources in the target service system more clearly and quickly, and therefore, when the data management such as updating, changing and repairing of the resources in the service system is required, the affected range before and after the resource management can be known more clearly and quickly. On the other hand, because the service system is used as a dimension to generate the resource topological graph, instead of simply associating the different types of resources, the different types of resources in the service system can be associated more pertinently, and the problem that the service pertinence of the resource topological graph is not strong, so that the resource management requirement of a service scene is difficult to meet is solved.

On one hand, in order to improve the service pertinence of the topological graph in the actual service scene; on the other hand, in order to meet the mining requirement of the business scene on the upper and lower layers of the resources, a resource service topological graph (i.e. a topological graph taking the resources as dimensions) of the upper and lower layer link resources of a certain resource can be provided on the basis of forming a system service topological graph taking the business system as dimensions. However, considering that, due to the limitation of the page size, if there are too many nodes in the topology map, the formed graph is particularly dense and difficult to observe, in this embodiment of the present application, the system service topology map with the service system as a dimension is displayed first, and then, for each resource in the system service topology map, the resource service topology map for the resource is further jumped to the resource service topology map for displaying the link resources of the upper layer and the lower layer of the resource. As shown in fig. 6, at this time, in step 204, "taking the first resource type as a node, after generating the system service topology map of the target service system according to the first association relationship", the following steps 601 to 603 may be further included, where:

601. And displaying the system service topological graph.

Wherein the system service topology comprises a plurality of resources.

Step 601 shows a system service topology in a variety of ways, including, illustratively:

mode 1: the system service topology displayed in step 601 displays icons of the first resource types corresponding to the various types of resources, and displays respective resource lists corresponding to the first resource types under the icons of the respective first resource types, as shown in (a) of fig. 7. At this time, displaying a plurality of resources under one resource type is realized through the system service topology.

Mode 2: in order to simplify the page display and facilitate the inquiry of the link relation among the various types of resources so as to more intuitively observe the link relation among the various types of resources, a first system service topology diagram containing a first resource type corresponding to the various types of resources is displayed in step 601; then, detecting whether a user unfolding operation aiming at a first resource type in the first system service topological graph exists or not; when it is detected that there is a spreading operation of a user on a first resource type in the first system service topology, in response to the spreading operation on a target resource type (e.g., a P resource type in (b) of fig. 7) in the first system service topology, displaying a second system service topology including resources corresponding to the target resource type, as shown in (b) of fig. 7. At this time, displaying a plurality of resources under one resource type can be similarly achieved through the second system service topology.

The terminal implementation used to display the system topology in step 601 is various and illustratively includes:

(1) And generating and displaying a system topological graph to be different terminals. For example, in step 201, a system code input by a user from a target terminal is received as a target system code, in steps 202-203, various types of resources associated with the target system code and a first management relationship are acquired through electronic equipment and fed back to the target terminal, in step 204, a system service topology diagram of a target service system is generated according to the various types of resources and the first association relationship through a rendering plug-in the target terminal, and in step 601, the target terminal displays the generated system service topology diagram of the target service system.

(2) And generating and displaying a system topological graph to be different terminals. For example, in step 201, a system code input by a user from a target terminal is received as a target system code, in steps 202-203, various types of resources associated with the target system code and a first management relationship are acquired through the electronic device, and in step 204, a system service topology diagram of the target service system is directly generated in the electronic device. The electronic device feeds back the generated system service topology diagram of the target service system to the target terminal, and in step 601, the target terminal displays the system service topology diagram of the target service system generated by the electronic device.

(3) And generating and displaying a system topological graph to be the same terminal. For example, a system service topology diagram of the target service system is generated as a timing task of the electronic device, and when the timing task of generating the system service topology diagram of the target service system is completed each time, the system service topology diagram of the target service system is generated, and the system service topology diagram of the target service system is sent to a preset display management platform, and the system service topology diagram of the target service system is displayed through the preset display management platform. Here, the preset display management platform may be a representation form of a server, a terminal, etc., and the specific representation form of the preset display management platform in the embodiment of the present application is not limited.

602. And responding to the selection operation of the target resource in the system service topological graph, and acquiring the resource service topological graph of the target resource.

The selection operation refers to an operation of selecting a target resource, for example, a clicking operation of a target resource icon in a system service topological graph displayed on the target terminal by a user.

The resource service topological graph refers to a resource topological graph taking single resources as dimensions.

The target resource refers to a resource which corresponds to the selection operation and is used for generating a resource topological graph.

In some embodiments, the system service topology diagram displayed in step 601 displays icons of first resource types corresponding to each type of resource, and displays each resource list corresponding to each first resource type under each icon of the first resource type. At this time, the user may directly perform the selection operation of the target resource based on the system service topology map displayed in step 601.

In some embodiments, in order to simplify the page display, the system service topology diagram displayed in step 601 only displays icons of various types of resources, and in order to facilitate the query, when clicking on an icon of a certain type of resource in the system service topology diagram displayed in step 601, each resource list corresponding to the type of resource may be further displayed. The user can perform a selection operation of the target resource based on the further displayed resource list. At this time, step 601 may specifically include: displaying a first system service topology graph containing first resource types corresponding to the various types of resources; and responding to the unfolding operation aiming at the target resource type in the first system service topological graph, and displaying a second system service topological graph containing all the resources corresponding to the target resource type. Step 602 may specifically include: and responding to a selection operation of a target resource in the second system service topological graph, and acquiring a resource service topological graph of the target resource, wherein the target resource is acquired from each resource corresponding to the target resource type.

There are various ways to obtain the resource service topology map in step 602, which illustratively includes:

1. and generating in real time. Referring to fig. 8, fig. 8 is a schematic diagram illustrating a process of generating a resource service topology map provided in the application embodiment, and in this case, step 602 may specifically include the following steps 6021 to 6022:

6021. and acquiring the target upper and lower layer resources associated with the target resources and a second association relationship between the target upper and lower layer resources.

The upper and lower layer resources are resources which have an association relation with a certain resource and are positioned at the upper layer of the resource, and resources which have an association relation with the resource and are positioned at the lower layer of the resource.

The target upper and lower layer resources refer to resources which have an association relationship with the target resources and are positioned at the upper layer of the target resources, and resources which have an association relationship with the target resources and are positioned at the lower layer of the target resources.

The second association relationship is specifically used for indicating whether an edge connection relationship exists at a node where two resources are located in the resource service topological graph, and the link relationship between the two resources in the resource service topological graph can be represented by edge connection.

Illustratively, in step 6021, the target upper and lower layer resources and the second association relationship may be queried by a preconfigured dynamic SQL statement. In this case, step 6021 may specifically include the following steps A1 to A4:

a1, detecting whether the target resource is an access point resource of a second resource type corresponding to the target resource.

The second resource type refers to a resource class corresponding to the target resource, for example, the second resource type corresponding to the target resource is a middleware type, a database type, or a computing type.

The access point resource refers to a resource serving as a query access point among the resources of the link relationship corresponding to the second resource type.

In order to ensure that the upper and lower layer resources of each resource and the association relationship between the resources and the upper and lower layer resources thereof can be normally queried, the method further comprises the following steps before the step A1: pre-configuring a plurality of types of link relations to be stored in a resource association configuration database, wherein each type of link relation comprises an upper layer resource and a lower layer resource which are associated with each resource; and, one resource is selected from the resources under each type of link relation as the access point resource of the type of link relation.

In this embodiment of the present application, the purpose of selecting the access point resource is: because there are many resources, if the link relation of the upper and lower layer resources is queried based on any one resource, the number of the resources to be traversed is large, so the speed of querying the upper and lower layer resources of the resources is also slow; therefore, each type of link relation is provided with one access point resource, so that the number of resources to be traversed can be reduced, and further, the target upper and lower layer resources associated with the target resources can be quickly queried. The access point resource is selected in various manners, for example, one resource can be selected from the resources in each type of link relation at will, and the selected resource is used as the access point resource; for another example, a specific type (such as a predetermined access point resource type) of resource may be selected from the resources under each type of link relationship as the access point resource.

In step A1, whether the target resource is the access point resource of the second resource type corresponding to the target resource is determined by detecting whether the target resource is the same as the access point resource of the second resource type. In this case, the step A1 may specifically include: firstly, acquiring an access point resource of a second resource type corresponding to a target resource; then, detecting whether the access point resources of the target resource and the second resource type are the same; and when the target resource is the same as the access point resource of the second resource type, determining that the target resource is the access point resource. And when the target resource and the access point resource of the second resource type are different, determining that the target resource is not the access point resource.

A2, if the target resource is the access point resource, inserting the identification information of the target resource into a preset dynamic structural query statement.

A3, acquiring the target upper and lower layer resources of the target resource association record and the second association relation from a preset resource association configuration database through the dynamic structured query statement.

The identification information of the target resource is information for uniquely identifying the target resource, for example, the identification information of the target resource may be srn: prd:fbox:1:depth:fbox-IiME 7s5Q, abbreviated as resource sm, and the meanings of the several formulas are:

srn: a fixed beginning identification of all resources;

prd: identifying an environment, such as a production and test environment;

fbox: is the type of this resource;

deployment: identifying a depth type under fbox;

fbox-IiME7s5Q: and (5) unique identification.

In the embodiment of the application, a dynamic structured query statement (Structured Query Language, SQL) is configured for each resource type, and is used for querying the target upper and lower layer resources associated with the target resource and the second association relationship between the target upper and lower layer resources. For example, the second resource type is configured as a dynamic SQL, and the target upper and lower layer resources of the target resource association record can be queried from the preset resource association configuration database by inserting the identification information of the target resource into the dynamic SQL.

Illustratively, the dynamic SQL for the second resource type corresponding configuration may be as follows:

1.{"nodes":"SELECT DISTINCT s.srn AS'source_srn',s.resource_type AS'source_resource_type',CONCAT_WS(':',s.server_ip,s.server_port)AS'source_display_name',null as'service',null as node_type

2.FROM t_res_jboss_server s,t_res_jboss_instance i

3.WHERE s.instance_id＝i.instance_id

4.AND i.srn in($(srn))AND i.resource_status IN($(resourceStatus))AND s.resource_status IN($(resourceStatus))

5.UNION ALL

6.SELECT DISTINCT i.srn AS'source_srn',i.resource_type AS'source_resource_type',CONCAT_WS(':',i.instance_name)AS'source_display_name',null as'service',null as node_type

7.FROM t_res_jboss_instance i

8.WHERE i.srn in($(srn))AND i.resource_status IN($(resourceStatus))",

9."links":"SELECT DISTINCT s.srn AS'dest_srn','JBossServer'AS dest,i.srn AS'source_srn','JBossInstance'AS source

10.FROM t_res_jboss_server s,t_res_jboss_instance i

11.WHERE s.instance_id＝i.instance_id

12.AND i.srn in($(srn))AND i.resource_status IN($(resourceStatus))AND s.resource_status IN($(resourceStatus))

13.UNION ALL

14.SELECT DISTINCT h.srn AS'dest_srn','BMSHost'AS dest,ins.srn AS'source_srn','MWHostInstance'AS source

15.FROM t_res_bms_host h,t_res_jboss_instance i,`t_res_jboss_server`w,`t_res_mwhost_instance`ins

16.WHERE w.instance_id＝i.instance_id

17.AND ins.srn＝w.host_srn

18.AND ins.host_srn＝h.srn

19.AND i.srn in($(srn))AND i.resource_status IN($(resourceStatus))AND h.resource_status IN($(resourceStatus))AND ins.resource_status IN($(resourceStatus))"}

in the dynamic SQL configured corresponding to the second resource type, the 1 st sentence represents the target upper and lower layer resources associated with the query target resource, and the 9 th sentence represents the second association relationship between the query target upper and lower layer resources.

A4, if the target resource is not the access point resource, inserting the identification information of the access point resource into the dynamic structural query statement; and acquiring upper and lower layer resources associated with the access point resources from the resource association configuration database through the dynamic structured query statement to serve as the target upper and lower layer resources, and acquiring association relations of the upper and lower layer resources to serve as the second association relations.

Specifically, in order to ensure that the target upper and lower layer resources associated with the target resources are effectively queried, if the target resources are not the access point resources, the corresponding access point resources can be searched out based on the target resources, and then the identification information of the access point resources is inserted into the dynamic SQL (such as the dynamic SQL correspondingly configured by the second resource type) for execution, so that the target upper and lower layer resources of the target resource association record can be queried from the preset resource association configuration database.

6022. And generating a resource service topology graph of the target resource according to the second association relation by taking the target upper and lower layer resource as a node.

The resource service topological graph takes each resource in the target upper and lower layer resources as a node, and the association relation of two resources in the target upper and lower layer resources is taken as an edge, so that the resource service topological graph of the target resource is generated.

The manner of generating the resource service topology map in step 6022 is similar to the manner of generating the system service topology map in step 204, and the description of step 204 may be referred to specifically, and will not be repeated here.

Through the steps 6021 to 6022, a resource service topology diagram for displaying the resource of the upper layer or the lower layer of the resource with the resource as a dimension can be generated for the resource under any resource type in the system topology diagram.

2. And then reading from a preset database. Before step 602, the resource service topology map of each resource is generated in advance by the method of generating the resource service topology map in real time in the step 1, and the resource service topology map of each resource is stored in a preset database, and in step 602, the resource service topology map associated with the target resource is directly queried and read from the preset database.

603. And displaying the resource service topological graph.

There are various ways to display the resource service topology in step 603, and exemplary ways include:

(1) And switching the service topological graph of the display system in the display page to the resource service topological graph obtained in the display step 602. And jumping from the system service topological graph to the resource service topological graph of the target resource.

(2) And (3) reducing the display of the system service topological graph in the display page, and displaying the resource service topological graph obtained in the step 602 in the same display page for displaying the system service topological graph.

By displaying the system service topology map first in step 601, generating a resource service topology map with a resource as a dimension for a resource under a certain resource type in the system service topology map, and displaying in step 603, the jump to the resource service topology map with the resource as the dimension is realized on the basis of the system service topology map. On one hand, the resource service topological graph taking the resource as the dimension can be deeper into the upper and lower links of the resource; on the other hand, because the system is used as a system service topological graph of the dimension, the service pertinence of the topological graph can be improved, and the problem that too much resources are displayed too densely can be avoided. Therefore, through the steps 601 to 603, the interface display is simplified on the basis of satisfying the deep requirement of the resource association relationship. The simplification of the interface display is more convenient for viewing and understanding, so that the time for a user to know the upper and lower layer relationship of the resources can be reduced to a certain extent, and the resource management requirement of a service scene is met.

And the system service topology diagram for reflecting the relation between the various types of resources in the same service system is displayed first, and then the system service topology diagram is jumped to the resource service topology diagram for reflecting the relation between the various types of resources associated under a certain resource, so that the system service topology diagram is not limited to only displaying the relation between the resource types of a certain service system, and the relation between the resources in a certain service system and the resources in other service systems can be reflected to a certain extent.

Referring to fig. 3, 7 and 8, for convenience of understanding, a process of generating a resource service topology is described below by taking an example of forming edge and node data of the resource topology (i.e. the target upper and lower layer resources and the second association relationship) at the electronic device and forming a system service topology at the WEB front end through the integrated rendering plug-in drawing. For example, the user may input the system code of the service system to be queried at the WEB front end, and transmit the system code as the target system code into the electronic device.

Firstly, the electronic equipment queries various types of resources and the aggregation quantity of the various types of resources which are associated with the target system code in a database, determines the edge and node data (namely various types of resources and a first association relation) of a resource topological graph to be generated according to the various types of resources according to a preset rule, and returns the edge and node data to the WEB front end. The rendering plug-in used for forming the topological graph is integrated in the WEB front end, the rendering plug-in the WEB front end draws the graph according to the edge and node data (namely various types of resources and the first association relation) returned by the electronic equipment, a system service topological graph of a target service system corresponding to the target system code is formed, and the system service topological graph of the target service system is displayed in the WEB front end.

And then, the WEB front end firstly displays a first system service topology graph containing a first resource type corresponding to each type of resource. When detecting that there is a spreading operation of a user on a first resource type in the first system service topology graph, responding to the spreading operation on a target resource type (such as a P resource type in (b) of fig. 7) in the first system service topology graph, the WEB front end displays a second system service topology graph containing each resource corresponding to the target resource type, as shown in (b) of fig. 7.

The user may then perform a selection operation (e.g., click on a resource icon) on the target resource under the resource list of the target resource type. At this time, the WEB front end transmits the identification information (i.e., the resource sm) of the target resource selected by the user to the electronic device. The electronic equipment detects whether the target resource is an access point resource of a second resource type corresponding to the target resource; if the target resource is the access point resource, inserting the identification information (namely the resource sm) of the target resource into a preset dynamic structural query statement for execution; if the target resource is not the access point resource, the identification information (namely the resource sm) of the access point resource is found out and is inserted into a preset dynamic structural query statement for execution; and searching and determining the edge and node data of the resource topological graph to be generated according to a preset rule, and returning the edge and node data (namely the target upper and lower layer resources and the second association relation) to the WEB front end.

And finally, drawing a graph according to the edge and node data (namely the target upper and lower layer resources and the second association relation) returned by the electronic equipment by the rendering plug-in the WEB front end to form a resource service topological graph with the target resources as dimensions, and displaying the resource service topological graph in the WEB front end.

In order to better implement the method for generating the resource topology map in the embodiment of the present application, on the basis of the method for generating the resource topology map, the embodiment of the present application further provides a device for generating the resource topology map, as shown in fig. 9, which is a schematic structural diagram of an embodiment of the device for generating the resource topology map in the embodiment of the present application, where the device 900 for generating the resource topology map includes:

a first obtaining unit 901, configured to obtain a target system code of a target service system;

a second obtaining unit 902, configured to obtain various types of resources associated with the target system code;

a third obtaining unit 903, configured to obtain a first association relationship between the first resource types corresponding to the various types of resources from a preset configuration database;

and the generating unit 904 is configured to generate a system service topology map of the target service system according to the first association relationship by using the first resource type as a node.

In some embodiments of the present application, the generating device 900 of the resource topology map further includes a display unit (not shown in the figure), where after the first resource type is used as a node and the system service topology map of the target service system is generated according to the first association relationship, the display unit is specifically configured to:

and displaying the resource service topological graph.

In some embodiments of the present application, the generating unit 904 is specifically configured to:

acquiring the aggregation quantity of the various types of resources;

In the implementation, each unit may be implemented as an independent entity, or may be implemented as the same entity or several entities in any combination, and the implementation of each unit may be referred to the foregoing method embodiment, which is not described herein again.

Since the apparatus for generating a resource topology map may perform the steps in the method for generating a resource topology map according to any embodiment of the present application, such as fig. 1 to 8, may achieve the beneficial effects that can be achieved by the method for generating a resource topology map according to any embodiment of the present application, see the foregoing description, and will not be repeated here.

In addition, in order to better implement the method for generating the resource topology map in the embodiment of the present application, on the basis of the method for generating the resource topology map, referring to fig. 10, fig. 10 shows a schematic structural diagram of the electronic device in the embodiment of the present application, and specifically, the electronic device provided in the embodiment of the present application includes a processor 1001, where the processor 1001 is configured to implement steps of the method for generating the resource topology map in any embodiment corresponding to fig. 1 to 8 when executing a computer program stored in the memory 1002; alternatively, the processor 1001 is configured to implement the functions of each unit in the corresponding embodiment as in fig. 9 when executing the computer program stored in the memory 1002.

By way of example, a computer program may be partitioned into one or more modules/units that are stored in the memory 1002 and executed by the processor 1001 to accomplish the embodiments of the present application. One or more of the modules/units may be a series of computer program instruction segments capable of performing particular functions to describe the execution of the computer program in a computer device.

Electronic devices may include, but are not limited to, a processor 1001, a memory 1002. It will be appreciated by those skilled in the art that the illustrations are merely examples of electronic devices, and are not limiting of electronic devices, and may include more or fewer components than shown, or may combine some components, or different components, e.g., electronic devices may also include input and output devices, network access devices, buses, etc., through which the processor 1001, memory 1002, input and output devices, network access devices, etc., are connected.

The processor 1001 may be a central processing unit (Central Processing Unit, CPU), but may also be other general purpose processors, digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), off-the-shelf programmable gate arrays (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like, which is a control center for an electronic device, with various interfaces and lines connecting various parts of the overall electronic device.

The memory 1002 may be used to store computer programs and/or modules, and the processor 1001 implements various functions of the computer device by running or executing the computer programs and/or modules stored in the memory 1002 and invoking data stored in the memory 1002. The memory 1002 may mainly include a storage program area that may store an operating system, application programs required for at least one function (such as a sound playing function, an image playing function, etc.), and a storage data area; the storage data area may store data (such as audio data, video data, etc.) created according to the use of the electronic device, and the like. In addition, the memory may include high-speed random access memory, and may also include non-volatile memory, such as a hard disk, memory, plug-in hard disk, smart Media Card (SMC), secure Digital (SD) Card, flash Card (Flash Card), at least one disk storage device, flash memory device, or other volatile solid-state storage device.

It can be clearly understood by those skilled in the art that, for convenience and brevity of description, a specific working process of the apparatus for generating a resource topology map, the electronic device and the corresponding units of the foregoing description may refer to a description of a method for generating a resource topology map in any embodiment, such as fig. 1 to 8, and details are not repeated herein.

Those of ordinary skill in the art will appreciate that all or a portion of the steps of the various methods of the above embodiments may be performed by instructions, or by instructions controlling associated hardware, which may be stored in a computer-readable storage medium and loaded and executed by a processor.

To this end, an embodiment of the present application provides a computer readable storage medium, in which a plurality of instructions capable of being loaded by a processor are stored, so as to execute steps in a method for generating a resource topology map in any embodiment corresponding to fig. 1 to 8, and specific operations may refer to descriptions of the method for generating a resource topology map in any embodiment corresponding to fig. 1 to 8, which are not described herein again.

Wherein the computer-readable storage medium may comprise: read Only Memory (ROM), random access Memory (RAM, random Access Memory), magnetic or optical disk, and the like.

Since the instructions stored in the computer readable storage medium may execute the steps in the method for generating a resource topology map in any embodiment of the present application, such as fig. 1 to 8, the beneficial effects that can be achieved by the method for generating a resource topology map in any embodiment of the present application, such as fig. 1 to 8, are detailed in the foregoing description, and are not repeated herein.

The foregoing describes in detail a method, an apparatus, an electronic device, and a computer readable storage medium for generating a resource topology map provided in the embodiments of the present application, where specific examples are applied to illustrate principles and implementations of the present application, and the description of the foregoing embodiments is only used to help understand the method and core idea of the present application; meanwhile, those skilled in the art will have variations in the specific embodiments and application scope in light of the ideas of the present application, and the present description should not be construed as limiting the present application in view of the above.

Claims

1. A method for generating a resource topology map, the method comprising:

acquiring a target system code of a target service system;

acquiring various types of resources associated with the target system code;

2. The method for generating a resource topology map according to claim 1, wherein after the generating a system service topology map of the target service system according to the first association relationship by using the first resource type as a node, further comprises:

and displaying the resource service topological graph.

3. The method for generating a resource topology map according to claim 2, wherein the obtaining the resource service topology map of the target resource includes:

4. The method for generating a resource topology map according to claim 3, wherein the obtaining the target upper and lower layer resources associated with the target resource and the second association relationship between the target upper and lower layer resources includes:

5. The method for generating a resource topology map of claim 4, further comprising:

6. The method for generating a resource topology map according to claim 2, wherein said displaying the system service topology map comprises:

7. The method for generating a resource topology map according to any one of claims 1 to 6, wherein the generating a system service topology map of the target service system according to the first association relationship by using the first resource type as a node includes:

acquiring the aggregation quantity of the various types of resources;

8. The device for generating the resource topological graph is characterized by comprising the following components:

9. An electronic device comprising a processor and a memory, wherein the memory has stored therein a computer program, and wherein the processor executes the method of generating a resource topology map according to any one of claims 1 to 7 when the processor invokes the computer program in the memory.

10. A computer-readable storage medium, on which a computer program is stored, the computer program being loaded by a processor to perform the steps in the method of generating a resource topology map of any of claims 1 to 7.