CN112615743A - Topological graph drawing method and device - Google Patents
Topological graph drawing method and device Download PDFInfo
- Publication number
- CN112615743A CN112615743A CN202011502967.1A CN202011502967A CN112615743A CN 112615743 A CN112615743 A CN 112615743A CN 202011502967 A CN202011502967 A CN 202011502967A CN 112615743 A CN112615743 A CN 112615743A
- Authority
- CN
- China
- Prior art keywords
- service
- micro
- topology
- data
- relationship
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/12—Discovery or management of network topologies
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/903—Querying
- G06F16/9038—Presentation of query results
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computational Linguistics (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The embodiment of the application provides a topological graph drawing method and a topological graph drawing device, wherein a service topology detection tool is called to collect micro-service topological data at regular time, the micro-service topological data are uploaded to a topology database and then are connected with the topology database to inquire corresponding micro-service topological data, the running state data of each micro-service are obtained according to the inquiry result, and the corresponding micro-service topological graph is drawn according to the micro-service topological data and the running state data of each micro-service, so that a micro-service topological graph for representing a relation model between micro-services can be drawn, materials are provided for related personnel to quickly, really and conveniently know the micro-service architecture, the position condition of the micro-service in the micro-service architecture is conveniently and quickly inquired, the fault range can be quickly known when a certain micro-service fails in the production process, reference data are provided for the later-stage technical optimization direction, and the problem that the topology accuracy of a manual maintenance system is low is solved, Low dependence on special personnel, low real-time performance and the like.
Description
Technical Field
The application relates to the technical field of computers, in particular to a topological graph drawing method and device.
Background
Along with the rapid development of express delivery business, the intelligent express delivery cabinet is a new thing along with the continuous development of express delivery business. The intelligent express cabinet has the functions of mainly assisting couriers in receiving and sending express, and the facing users are vast couriers and recipients. As a 24-hour unattended express temporary storage cabinet, the intelligent express cabinet interacts with a server through an Internet of things card and is used as an application of the Internet of things technology in the modern logistics industry, the intelligent express cabinet is the most effective solution for the last kilometer of electronic commerce terminal logistics, the delivery efficiency of couriers is improved, the delivery cost is reduced, the privacy and the safety of users are guaranteed, and the intelligent express cabinet is gradually and widely recognized and popularized.
The intelligent express cabinet system is used as a service end of an express terminal, provides data services such as user authentication, terminal configuration, grid scheduling, software monitoring, operation logs and linkage third-party systems, is used as a system for continuously providing services for 24 hours and using the services at high frequency, and has the characteristics of system complexity, 7-24-hour continuous serviceability, high pressure and the like, so that the problems of numerous system modules and complex system architecture are solved, and the intelligent express cabinet system is a very challenging matter for safe, efficient and stable operation if a huge and complex system is maintained.
With the development of internet technology, the application scale is continuously enlarged, and the software architecture is also continuously evolved. The early single application architecture is gradually developed into a micro-service architecture, the micro-services are generally divided according to the functions of an application system, each micro-service is used as a functional module of the system, and the micro-services are represented as a unified whole in service. Each micro service is independently deployed, operated and upgraded in a system architecture, and each micro service is loosely coupled on the architecture, so that the throughput, reliability and continuity of the whole system are improved through function disassembly.
With the development of services, more and more micro services are provided, and it follows that the system architecture is more and more complex, the calling relationship between the micro services is more and more complex, and how to maintain the whole system topology also brings new challenges.
Disclosure of Invention
Based on the defects of the existing design, the application provides a topological graph drawing method and a topological graph drawing device, which can draw a micro-service topological graph for representing a relation model between micro-services, provide materials for related personnel to quickly, truly and conveniently know a micro-service framework, facilitate quick inquiry of the position condition of the micro-service in the micro-service framework, quickly know a fault range when a certain micro-service breaks down in the production process, provide reference data for the later-stage technical optimization direction, and solve the problems of low accuracy, low dependence on special personnel, low real-time performance and the like of manual maintenance system topology.
Based on the first aspect of the embodiments of the present application, a method for drawing a topology map is provided, which is applied to a server, and the method includes:
calling a service topology detection tool to acquire micro-service topology data at regular time and uploading the micro-service topology data to a topology database, wherein the micro-service topology data is used for representing the front-back example relationship between micro-services and other micro-services;
after receiving a request for drawing a service architecture topological graph, connecting the topological database to inquire corresponding micro-service topological data, acquiring running state data of each micro-service according to an inquiry result, and drawing a corresponding micro-service topological graph according to the micro-service topological data and the running state data of each micro-service, wherein the micro-service topological graph is used for showing the position of each micro-service in a micro-service architecture and the dependency subordination relationship between each micro-service and other micro-services;
and processing the received service request based on the micro service topological graph.
In a possible implementation manner of the first aspect, the step of invoking a service topology detection tool to periodically collect microservice topology data and upload the microservice topology data to a topology database includes:
calling a service topology detection tool to acquire micro-service topology data, assembling the micro-service topology data into a JSON data format, and uploading the micro-service topology data in the JSON data format to a topology database through a POST request, wherein the micro-service topology data comprises one or more of a micro-service name, a third-party micro-service name needing interaction, an interaction address, a micro-service operation state and acquisition time.
In a possible implementation manner of the first aspect, the step of drawing a corresponding micro service topology map according to the micro service topology data and the operation state data of each micro service includes:
analyzing the micro-service topological data to obtain micro-service name field information, and inquiring whether a name node of the micro-service name field information exists in a topological database, if not, newly building a corresponding name node;
acquiring the field information of the interactive address, inquiring whether a name node of the field information of the interactive address exists in a topology database, and if not, establishing a corresponding name node;
checking the node relationship and relationship attribute between the name node of the micro-service name field and the name node of the interactive address field information, if no node relationship exists, establishing a corresponding node relationship, and setting the relationship attribute as an subordinate relationship attribute, if the node exists, detecting whether the relationship attribute is the subordinate relationship attribute, and if not, updating the relationship attribute as the subordinate relationship attribute;
acquiring the field content of the micro-service operation state, and executing the following operations one by one according to the sequence:
according to the field information of the micro service operation state, inquiring whether a name node of the field information of the micro service operation state exists in a topology database, and if not, establishing a corresponding name node;
checking the node relationship and relationship attribute between the name node of the micro-service operation state field and the name node of the interactive address field information, if the node relationship does not exist, establishing a corresponding node relationship, setting the relationship attribute as a dependency relationship attribute, if the node relationship exists, detecting whether the relationship attribute is the dependency relationship attribute, if the relationship attribute is not the dependency relationship attribute, updating the relationship attribute as the dependency relationship attribute, and completing the establishment of micro-service topology basic data;
and drawing a corresponding micro-service topological graph based on the created micro-service topological basic data and the running state data of each micro-service.
In a possible implementation manner of the first aspect, the step of drawing a corresponding micro service topology map based on the created micro service topology base data and the running state data of each micro service includes:
acquiring service dependence subordinate information of a hierarchical relationship unit in the micro-service hierarchical relationship data of the micro-service topology basic data;
acquiring object service labels matched with a plurality of service dependent subordinate objects and a target label description control corresponding to the object service labels based on the service dependent subordinate information, wherein the target label description control is a label description control of a label operation object to which label coverage information of the object service labels belongs, and the target label description control comprises at least one description control unit;
analyzing a plurality of service dependent subordinate objects to obtain a target topology data module having a topology data relationship with at least one description control unit, and generating topology drawing data mapping information between the target topology data module and the target description control unit according to topology drawing data parameters of the target topology data module and the at least one description control unit under a target topology drawing data label;
and loading topology drawing data mapping information corresponding to the running state data of each micro service between the target topology data module and the target description control unit under each topology drawing data label in each target label description control, selecting target micro service topology creating information matched with the target service label according to the loading result, and then combining and drawing all the target micro service topology creating information according to the association relationship to obtain a corresponding micro service topology map.
In a possible implementation manner of the first aspect, the obtaining service dependency subordinate information of a hierarchical relationship unit in the micro-service hierarchical relationship data of the micro-service topology base data includes:
acquiring micro-service hierarchical relationship data of the micro-service topological basic data, and performing hierarchical relationship feature extraction processing on the micro-service hierarchical relationship data to obtain hierarchical relationship feature information of hierarchical relationship units in the micro-service hierarchical relationship data, wherein the micro-service hierarchical relationship data is hierarchical relationship information formed by hierarchical coverage information recorded by each hierarchical relationship unit and acquired based on a single interaction request;
extracting service dependence information based on the hierarchical relationship characteristic information of the hierarchical relationship unit to obtain a target service dependence characteristic of the hierarchical relationship unit;
extracting service subordinate characteristics of the micro-service hierarchical relationship data to obtain service subordinate characteristic information of the hierarchical relationship unit;
and performing service dependence subordinate relationship fusion on the target service dependence characteristics of the hierarchical relationship unit in the micro-service hierarchical relationship data and the service subordinate characteristic information of the hierarchical relationship unit to obtain the service dependence subordinate relationship fusion information of the hierarchical relationship unit, and obtaining the service dependence subordinate information of the hierarchical relationship unit based on the service dependence subordinate relationship fusion information of the hierarchical relationship unit.
According to a second aspect of the embodiments of the present application, there is provided a topology drawing apparatus, applied to a server, the apparatus including:
the system comprises a calling module, a topology database and a service topology detection module, wherein the calling module is used for calling a service topology detection tool to acquire micro-service topology data at regular time and uploading the micro-service topology data to the topology database, and the micro-service topology data is used for representing the front-back example relationship between micro-services and other micro-services;
the acquisition module is used for connecting the topology database to inquire corresponding micro-service topology data after receiving a request for drawing a service architecture topology map, acquiring the running state data of each micro-service according to the inquiry result, and drawing the corresponding micro-service topology map according to the micro-service topology data and the running state data of each micro-service, wherein the micro-service topology map is used for showing the position of each micro-service in the micro-service architecture and the dependency subordination relationship between each micro-service and other micro-services;
and the processing module is used for processing the received service request based on the micro service topological graph.
Based on any one of the aspects, the micro-service topology data are acquired at regular time by calling the service topology detection tool and are uploaded to the topology database, the topology database is connected to inquire the corresponding micro-service topology data, the running state data of each micro-service is acquired according to the inquiry result, the corresponding micro-service topology map is drawn according to the micro-service topology data and the running state data of each micro-service, therefore, the micro-service topology map used for representing the relation model between the micro-services can be drawn, materials are provided for related personnel to quickly, really and conveniently know the micro-service architecture, the position condition of the micro-service in the micro-service architecture is conveniently and quickly inquired, the fault range can be quickly known when a certain micro-service breaks down in the production process, reference data are provided for the later-stage technical optimization direction, and the problem that the topology accuracy of a manual maintenance system is low is solved, Low dependence on special personnel, low real-time performance and the like.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained from the drawings without inventive effort.
Fig. 1 is a schematic flowchart illustrating a topological graph drawing method according to an embodiment of the present application;
FIG. 2 is a functional block diagram of a topology drawing apparatus provided in an embodiment of the present application;
fig. 3 shows a component structural diagram of a server for executing the above-described topology drawing method according to an embodiment of the present application.
Detailed Description
In order to make the purpose, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it should be understood that the drawings in the present application are for illustrative and descriptive purposes only and are not used to limit the scope of protection of the present application. Additionally, it should be understood that the schematic drawings are not necessarily drawn to scale. The flowcharts used in this application illustrate operations implemented according to some of the embodiments of the present application. It should be understood that the operations of the flow diagrams may be performed out of order, and steps without logical context may be performed in reverse order or simultaneously. One skilled in the art, under the guidance of this application, may add one or more other operations to, or remove one or more operations from, the flowchart.
Fig. 1 shows a flowchart of a topology drawing method provided in an embodiment of the present application, where in the embodiment, the topology drawing method may be executed by the server 100 shown in fig. 3. It should be understood that, in other embodiments, the order of some steps in the topology drawing method of the present embodiment may be interchanged according to actual needs, or some steps may be omitted or deleted. The detailed steps of the topology drawing method are described as follows.
Step S110, calling a service topology detection tool to collect micro-service topology data at regular time, and uploading the micro-service topology data to a topology database.
Wherein the microservice topology data is used to represent contextual instance relationships between microservices and other microservices.
And step S120, after receiving the request for drawing the service architecture topological graph, connecting the topological database to inquire corresponding micro-service topological data, acquiring the running state data of each micro-service according to the inquiry result, and drawing the corresponding micro-service topological graph according to the micro-service topological data and the running state data of each micro-service.
The microservice topological graph is used for showing the position of each microservice in the microservice architecture and the dependency subordinated relation between each microservice and other microservices.
Step S130, the received service request is processed based on the micro service topological graph.
Based on the above steps, in this embodiment, the service topology detection tool is called to collect micro-service topology data at regular time, and after the micro-service topology data is uploaded to the topology database, the topology database is connected to query the corresponding micro-service topology data, the operating state data of each micro-service is obtained according to the query result, and the corresponding micro-service topology map is drawn according to the micro-service topology data and the operating state data of each micro-service, so that the micro-service topology map used for representing the relationship model between the micro-services can be drawn, materials are provided for relevant personnel to quickly, truly and conveniently know the micro-service architecture, the position condition of the micro-service in the micro-service architecture is conveniently and quickly queried, the fault range can be quickly known when a certain micro-service fails in the production process, reference data is provided for the post-technical optimization direction, and the problem of low accuracy of the topology of the manual maintenance system is solved, Low dependence on special personnel, low real-time performance and the like.
In a possible implementation manner, for step S110, a service topology detection tool may be called to collect micro-service topology data, assemble the micro-service topology data into a JSON data format, and upload the micro-service topology data in the JSON data format to a topology database through a POST request.
The micro-service topology data comprises one or more of a micro-service name, a third-party micro-service name needing interaction, an interaction address, a micro-service operation state and acquisition time.
For example, the data format of the microservice topology data may be represented as follows:
the data format is as follows:
{ "service _ name": micro service name "," host _ IP ": server IP address", "time": acquisition time "," service _ dependency ": [" dependent service name 1 "," dependent service name 2 "… ] }
Data type:
service _ name: character string
host _ ip: character string
time: unix time stamp
service _ dependency slice ([ ] string)
In one possible embodiment, the step S120 can be implemented by the following substeps.
And a substep S121, analyzing the micro-service topology data, obtaining the field information of the micro-service name, and inquiring whether the topology database has the name node of the field information of the micro-service name, if not, establishing the corresponding name node.
And a substep S122, acquiring the field information of the interactive address, inquiring whether a name node of the field information of the interactive address exists in a topology database, and if not, establishing a corresponding name node.
And a substep S123 of checking the node relationship and the relationship attribute between the name node of the micro-service name field and the name node of the interactive address field information, if the node relationship does not exist, establishing a corresponding node relationship, setting the relationship attribute as a subordinate relationship attribute, if the node exists, detecting whether the relationship attribute is the subordinate relationship attribute, and if not, updating the relationship attribute to be the subordinate relationship attribute.
And a substep S124, obtaining the field content of the micro-service operation state, and executing the following operations one by one according to the sequence:
and a substep S125, inquiring whether a name node of the field information of the micro service operation state exists in the topology database according to the field information of the micro service operation state, and if not, establishing a corresponding name node.
And a substep S126 of checking the node relationship and the relationship attribute between the name node of the micro-service operation state field and the name node of the interactive address field information, if the node relationship does not exist, establishing a corresponding node relationship, setting the relationship attribute as a dependency relationship attribute, if the node relationship exists, detecting whether the relationship attribute is the dependency relationship attribute, and if the relationship attribute is not the dependency relationship attribute, updating the relationship attribute as the dependency relationship attribute to complete the establishment of the micro-service topology basic data.
And a substep S127 of drawing a corresponding micro-service topological graph based on the created micro-service topological basic data and the running state data of each micro-service.
In one possible implementation, for sub-step S127, the following exemplary implementation may be implemented:
(1) and acquiring the service dependence subordinate information of the hierarchical relation unit in the micro-service hierarchical relation data of the micro-service topology basic data.
For example, the micro-service hierarchical relationship data of the micro-service topology base data may be acquired, and the hierarchical relationship feature extraction processing may be performed on the micro-service hierarchical relationship data to obtain the hierarchical relationship feature information of the hierarchical relationship unit in the micro-service hierarchical relationship data.
It should be noted that the microservice hierarchical relationship data is hierarchical relationship information formed by hierarchical coverage information recorded by each hierarchical relationship unit collected based on a single interaction request.
On the basis, the service dependence information can be extracted based on the hierarchical relationship characteristic information of the hierarchical relationship unit, and the target service dependence characteristic of the hierarchical relationship unit is obtained.
Therefore, the service subordinate feature extraction can be carried out on the micro-service hierarchical relation data, and the service subordinate feature information of the hierarchical relation unit is obtained. Then, performing service dependence subordinate relationship fusion on the target service dependence feature of the hierarchical relationship unit in the micro-service hierarchical relationship data and the service subordinate feature information of the hierarchical relationship unit to obtain service dependence subordinate relationship fusion information of the hierarchical relationship unit, and obtaining the service dependence subordinate information of the hierarchical relationship unit based on the service dependence subordinate relationship fusion information of the hierarchical relationship unit.
(2) And acquiring object service labels matched with a plurality of service dependent subordinate objects and target label description controls corresponding to the object service labels based on the service dependent subordinate information.
It is worth to be noted that the target label description control is a label description control of a label operation object to which label coverage information of the object service label belongs, wherein the target label description control includes at least one description control unit.
(3) And analyzing the plurality of service dependent subordinate objects to obtain a target topology data module having a topology data relationship with the at least one description control unit, and generating topology drawing data mapping information between the target topology data module and the target description control unit according to topology drawing data parameters of the target topology data module and the at least one description control unit under a target topology drawing data label.
(4) And loading topology drawing data mapping information corresponding to the running state data of each micro service between a target topology data module and a target description control unit under each topology drawing data label in each target label description control, selecting target micro service topology creating information matched with the target service label according to the loading result, and then performing combined drawing on all the target micro service topology creating information according to the association relationship to obtain a corresponding micro service topology map.
Based on the same inventive concept, please refer to fig. 2, which shows a functional module diagram of the topology drawing apparatus 110 provided in the embodiment of the present application, and the embodiment may perform functional module division on the topology drawing apparatus 110 according to the above method embodiment. For example, the functional blocks may be divided for the respective functions, or two or more functions may be integrated into one processing block. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. It should be noted that, in the embodiment of the present application, the division of the module is schematic, and is only one logic function division, and there may be another division manner in actual implementation. For example, in the case of dividing each functional module by corresponding functions, the topology drawing device 110 shown in fig. 2 is only a device diagram. The topology drawing apparatus 110 may include a calling module 111, an obtaining module 112, and a processing module 113, and the functions of the functional modules of the topology drawing apparatus 110 are described in detail below.
The invoking module 111 is configured to invoke a service topology detection tool to acquire micro-service topology data at regular time and upload the micro-service topology data to a topology database, where the micro-service topology data is used to represent a front-back instance relationship between a micro-service and other micro-services. It is understood that the invoking module 111 can be used to execute the step S110, and for the detailed implementation of the invoking module 111, reference can be made to the content related to the step S110.
The obtaining module 112 is configured to, after receiving a request for drawing a service architecture topology diagram, connect to a topology database to query corresponding micro-service topology data, obtain operation state data of each micro-service according to a query result, and draw a corresponding micro-service topology diagram according to the micro-service topology data and the operation state data of each micro-service, where the micro-service topology diagram is used to show a position of each micro-service in a micro-service architecture and a dependency relationship between each micro-service and other micro-services. It is understood that the obtaining module 112 may be configured to perform the step S120, and for a detailed implementation of the obtaining module 112, reference may be made to the content related to the step S120.
A processing module 113, configured to process the received service request based on the micro service topology map. It is understood that the processing module 113 may be configured to execute the step S130, and for the detailed implementation of the processing module 113, reference may be made to the content related to the step S130.
Based on the same inventive concept, please refer to fig. 3, which shows a schematic block diagram of a server 100 for executing the above topology drawing method according to an embodiment of the present application, where the server 100 may include a topology drawing apparatus 110, a machine-readable storage medium 120, and a processor 130.
The machine-readable storage medium 120 is used to store machine-executable instructions for performing aspects of the present application. The processor 130 is configured to execute machine executable instructions stored in the machine readable storage medium 120 to implement the topology drawing method provided by the foregoing method embodiments.
The topology drawing apparatus 110 may include software functional modules (such as the calling module 111, the obtaining module 112, and the processing module 113 shown in fig. 2) stored in the machine-readable storage medium 120, when the processor 130 executes the software functional modules in the topology drawing apparatus 110, to implement the topology drawing method provided by the foregoing method embodiment.
Since the server 100 provided in the embodiment of the present application is another implementation form of the method embodiment executed by the server 100, and the server 100 may be configured to execute the topology map drawing method provided in the method embodiment, the technical effect obtained by the server may refer to the method embodiment, and is not described herein again.
The above description is only for various embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of changes or substitutions within the technical scope of the present application, and all such changes or substitutions are included in the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (10)
1. A topological graph drawing method is applied to a server, and comprises the following steps:
calling a service topology detection tool to acquire micro-service topology data at regular time and uploading the micro-service topology data to a topology database, wherein the micro-service topology data is used for representing the front-back example relationship between micro-services and other micro-services;
after receiving a request for drawing a service architecture topological graph, connecting the topological database to inquire corresponding micro-service topological data, acquiring running state data of each micro-service according to an inquiry result, and drawing a corresponding micro-service topological graph according to the micro-service topological data and the running state data of each micro-service, wherein the micro-service topological graph is used for showing the position of each micro-service in a micro-service architecture and the dependency subordination relationship between each micro-service and other micro-services;
and processing the received service request based on the micro service topological graph.
2. The method for drawing the topological graph according to claim 1, wherein the step of calling a service topology detection tool to collect micro-service topology data at regular time and upload the micro-service topology data to a topology database comprises:
calling a service topology detection tool to acquire micro-service topology data, assembling the micro-service topology data into a JSON data format, and uploading the micro-service topology data in the JSON data format to a topology database through a POST request, wherein the micro-service topology data comprises one or more of a micro-service name, a third-party micro-service name needing interaction, an interaction address, a micro-service operation state and acquisition time.
3. The topology drawing method according to claim 1, wherein the step of drawing the corresponding micro-service topology drawing according to the micro-service topology data and the operation state data of each micro-service includes:
analyzing the micro-service topological data to obtain micro-service name field information, and inquiring whether a name node of the micro-service name field information exists in a topological database, if not, newly building a corresponding name node;
acquiring the field information of the interactive address, inquiring whether a name node of the field information of the interactive address exists in a topology database, and if not, establishing a corresponding name node;
checking the node relationship and relationship attribute between the name node of the micro-service name field and the name node of the interactive address field information, if no node relationship exists, establishing a corresponding node relationship, and setting the relationship attribute as an subordinate relationship attribute, if the node exists, detecting whether the relationship attribute is the subordinate relationship attribute, and if not, updating the relationship attribute as the subordinate relationship attribute;
acquiring the field content of the micro-service operation state, and executing the following operations one by one according to the sequence:
according to the field information of the micro service operation state, inquiring whether a name node of the field information of the micro service operation state exists in a topology database, and if not, establishing a corresponding name node;
checking the node relationship and relationship attribute between the name node of the micro-service operation state field and the name node of the interactive address field information, if the node relationship does not exist, establishing a corresponding node relationship, setting the relationship attribute as a dependency relationship attribute, if the node relationship exists, detecting whether the relationship attribute is the dependency relationship attribute, if the relationship attribute is not the dependency relationship attribute, updating the relationship attribute as the dependency relationship attribute, and completing the establishment of micro-service topology basic data;
and drawing a corresponding micro-service topological graph based on the created micro-service topological basic data and the running state data of each micro-service.
4. The topology drawing method according to claim 3, wherein the step of drawing the corresponding micro-service topology drawing based on the created micro-service topology base data and the operation state data of each micro-service comprises:
acquiring service dependence subordinate information of a hierarchical relationship unit in the micro-service hierarchical relationship data of the micro-service topology basic data;
acquiring object service labels matched with a plurality of service dependent subordinate objects and a target label description control corresponding to the object service labels based on the service dependent subordinate information, wherein the target label description control is a label description control of a label operation object to which label coverage information of the object service labels belongs, and the target label description control comprises at least one description control unit;
analyzing a plurality of service dependent subordinate objects to obtain a target topology data module having a topology data relationship with at least one description control unit, and generating topology drawing data mapping information between the target topology data module and the target description control unit according to topology drawing data parameters of the target topology data module and the at least one description control unit under a target topology drawing data label;
and loading topology drawing data mapping information corresponding to the running state data of each micro service between the target topology data module and the target description control unit under each topology drawing data label in each target label description control, selecting target micro service topology creating information matched with the target service label according to the loading result, and then combining and drawing all the target micro service topology creating information according to the association relationship to obtain a corresponding micro service topology map.
5. The method according to claim 4, wherein the obtaining of the service dependency subordinate information of the hierarchical relationship unit in the micro-service hierarchical relationship data of the micro-service topology base data includes:
acquiring micro-service hierarchical relationship data of the micro-service topological basic data, and performing hierarchical relationship feature extraction processing on the micro-service hierarchical relationship data to obtain hierarchical relationship feature information of hierarchical relationship units in the micro-service hierarchical relationship data, wherein the micro-service hierarchical relationship data is hierarchical relationship information formed by hierarchical coverage information recorded by each hierarchical relationship unit and acquired based on a single interaction request;
extracting service dependence information based on the hierarchical relationship characteristic information of the hierarchical relationship unit to obtain a target service dependence characteristic of the hierarchical relationship unit;
extracting service subordinate characteristics of the micro-service hierarchical relationship data to obtain service subordinate characteristic information of the hierarchical relationship unit;
and performing service dependence subordinate relationship fusion on the target service dependence characteristics of the hierarchical relationship unit in the micro-service hierarchical relationship data and the service subordinate characteristic information of the hierarchical relationship unit to obtain the service dependence subordinate relationship fusion information of the hierarchical relationship unit, and obtaining the service dependence subordinate information of the hierarchical relationship unit based on the service dependence subordinate relationship fusion information of the hierarchical relationship unit.
6. A topology drawing device applied to a server, the device comprising:
the system comprises a calling module, a topology database and a service topology detection module, wherein the calling module is used for calling a service topology detection tool to acquire micro-service topology data at regular time and uploading the micro-service topology data to the topology database, and the micro-service topology data is used for representing the front-back example relationship between micro-services and other micro-services;
the acquisition module is used for connecting the topology database to inquire corresponding micro-service topology data after receiving a request for drawing a service architecture topology map, acquiring the running state data of each micro-service according to the inquiry result, and drawing the corresponding micro-service topology map according to the micro-service topology data and the running state data of each micro-service, wherein the micro-service topology map is used for showing the position of each micro-service in the micro-service architecture and the dependency subordination relationship between each micro-service and other micro-services;
and the processing module is used for processing the received service request based on the micro service topological graph.
7. The device for drawing a topological graph according to claim 6, wherein the manner for calling the service topology detection tool to collect the microservice topology data at regular time and upload the microservice topology data to the topology database includes:
calling a service topology detection tool to acquire micro-service topology data, assembling the micro-service topology data into a JSON data format, and uploading the micro-service topology data in the JSON data format to a topology database through a POST request, wherein the micro-service topology data comprises one or more of a micro-service name, a third-party micro-service name needing interaction, an interaction address, a micro-service operation state and acquisition time.
8. The topology drawing device according to claim 6, wherein the drawing a corresponding microservice topology drawing according to the microservice topology data and the operation state data of each microservice, wherein the microservice topology drawing is used for showing the position of each microservice in a microservice architecture and the way of depending on subordinate relations with other microservices, comprises:
analyzing the micro-service topological data to obtain micro-service name field information, and inquiring whether a name node of the micro-service name field information exists in a topological database, if not, newly building a corresponding name node;
acquiring the field information of the interactive address, inquiring whether a name node of the field information of the interactive address exists in a topology database, and if not, establishing a corresponding name node;
checking the node relationship and relationship attribute between the name node of the micro-service name field and the name node of the interactive address field information, if no node relationship exists, establishing a corresponding node relationship, and setting the relationship attribute as an subordinate relationship attribute, if the node exists, detecting whether the relationship attribute is the subordinate relationship attribute, and if not, updating the relationship attribute as the subordinate relationship attribute;
acquiring the field content of the micro-service operation state, and executing the following operations one by one according to the sequence:
according to the field information of the micro service operation state, inquiring whether a name node of the field information of the micro service operation state exists in a topology database, and if not, establishing a corresponding name node;
checking the node relationship and relationship attribute between the name node of the micro-service operation state field and the name node of the interactive address field information, if the node relationship does not exist, establishing a corresponding node relationship, setting the relationship attribute as a dependency relationship attribute, if the node relationship exists, detecting whether the relationship attribute is the dependency relationship attribute, if the relationship attribute is not the dependency relationship attribute, updating the relationship attribute as the dependency relationship attribute, and completing the establishment of micro-service topology basic data;
and drawing a corresponding micro-service topological graph based on the created micro-service topological basic data and the running state data of each micro-service.
9. The topology drawing device according to claim 8, wherein the manner of drawing the corresponding micro-service topology drawing based on the created micro-service topology base data and the operation state data of each micro-service includes:
acquiring service dependence subordinate information of a hierarchical relationship unit in the micro-service hierarchical relationship data of the micro-service topology basic data;
acquiring object service labels matched with a plurality of service dependent subordinate objects and a target label description control corresponding to the object service labels based on the service dependent subordinate information, wherein the target label description control is a label description control of a label operation object to which label coverage information of the object service labels belongs, and the target label description control comprises at least one description control unit;
analyzing a plurality of service dependent subordinate objects to obtain a target topology data module having a topology data relationship with at least one description control unit, and generating topology drawing data mapping information between the target topology data module and the target description control unit according to topology drawing data parameters of the target topology data module and the at least one description control unit under a target topology drawing data label;
and loading topology drawing data mapping information corresponding to the running state data of each micro service between the target topology data module and the target description control unit under each topology drawing data label in each target label description control, selecting target micro service topology creating information matched with the target service label according to the loading result, and then combining and drawing all the target micro service topology creating information according to the association relationship to obtain a corresponding micro service topology map.
10. The apparatus according to claim 9, wherein the means for obtaining the service dependency subordinate information of the hierarchical relationship unit in the micro-service hierarchical relationship data of the micro-service topology base data includes:
acquiring micro-service hierarchical relationship data of the micro-service topological basic data, and performing hierarchical relationship feature extraction processing on the micro-service hierarchical relationship data to obtain hierarchical relationship feature information of hierarchical relationship units in the micro-service hierarchical relationship data, wherein the micro-service hierarchical relationship data is hierarchical relationship information formed by hierarchical coverage information recorded by each hierarchical relationship unit and acquired based on a single interaction request;
extracting service dependence information based on the hierarchical relationship characteristic information of the hierarchical relationship unit to obtain a target service dependence characteristic of the hierarchical relationship unit;
extracting service subordinate characteristics of the micro-service hierarchical relationship data to obtain service subordinate characteristic information of the hierarchical relationship unit;
and performing service dependence subordinate relationship fusion on the target service dependence characteristics of the hierarchical relationship unit in the micro-service hierarchical relationship data and the service subordinate characteristic information of the hierarchical relationship unit to obtain the service dependence subordinate relationship fusion information of the hierarchical relationship unit, and obtaining the service dependence subordinate information of the hierarchical relationship unit based on the service dependence subordinate relationship fusion information of the hierarchical relationship unit.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011502967.1A CN112615743B (en) | 2020-12-18 | 2020-12-18 | Topological graph drawing method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011502967.1A CN112615743B (en) | 2020-12-18 | 2020-12-18 | Topological graph drawing method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112615743A true CN112615743A (en) | 2021-04-06 |
| CN112615743B CN112615743B (en) | 2022-09-16 |
Family
ID=75240476
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011502967.1A Active CN112615743B (en) | 2020-12-18 | 2020-12-18 | Topological graph drawing method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112615743B (en) |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113014674A (en) * | 2021-04-08 | 2021-06-22 | 北京百度网讯科技有限公司 | Method and device for drawing service dependency graph |
| CN113810234A (en) * | 2021-09-18 | 2021-12-17 | 北京字跳网络技术有限公司 | Micro-service link topology processing method and device and readable storage medium |
| CN114553709A (en) * | 2022-04-28 | 2022-05-27 | 恒生电子股份有限公司 | Topological relation display method and related equipment |
| CN114726739A (en) * | 2022-04-18 | 2022-07-08 | 深圳市智象科技有限公司 | Topological data processing method, device, equipment and storage medium |
| CN115130993A (en) * | 2022-07-01 | 2022-09-30 | 江苏海洋大学 | Method for automatically drawing university course establishment relation topology structure diagram |
| CN115277436A (en) * | 2022-07-25 | 2022-11-01 | 浙江大学 | Micro-service software architecture identification method based on topological structure |
| CN116881571A (en) * | 2023-07-27 | 2023-10-13 | 广东麦视互联网科技有限公司 | Data mining method and system based on micro-service |
| CN117155978A (en) * | 2023-10-31 | 2023-12-01 | 山东弘毅节能服务有限公司 | Intelligent campus management system based on artificial intelligence |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108322351A (en) * | 2018-03-05 | 2018-07-24 | 北京奇艺世纪科技有限公司 | Generate method and apparatus, fault determination method and the device of topological diagram |
| CN109933452A (en) * | 2019-03-22 | 2019-06-25 | 中国科学院软件研究所 | A kind of micro services intelligent monitoring method towards anomalous propagation |
| CN110888755A (en) * | 2019-11-15 | 2020-03-17 | 亚信科技（中国）有限公司 | Method and device for searching abnormal root node of micro-service system |
| CN111831548A (en) * | 2020-05-29 | 2020-10-27 | 微民保险代理有限公司 | Method and device for drawing dependency relationship topological graph |
| US20200382388A1 (en) * | 2019-05-31 | 2020-12-03 | International Business Machines Corporation | Constrained optimization of cloud micro services |
-
2020
- 2020-12-18 CN CN202011502967.1A patent/CN112615743B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108322351A (en) * | 2018-03-05 | 2018-07-24 | 北京奇艺世纪科技有限公司 | Generate method and apparatus, fault determination method and the device of topological diagram |
| CN109933452A (en) * | 2019-03-22 | 2019-06-25 | 中国科学院软件研究所 | A kind of micro services intelligent monitoring method towards anomalous propagation |
| US20200382388A1 (en) * | 2019-05-31 | 2020-12-03 | International Business Machines Corporation | Constrained optimization of cloud micro services |
| CN110888755A (en) * | 2019-11-15 | 2020-03-17 | 亚信科技（中国）有限公司 | Method and device for searching abnormal root node of micro-service system |
| CN111831548A (en) * | 2020-05-29 | 2020-10-27 | 微民保险代理有限公司 | Method and device for drawing dependency relationship topological graph |
Cited By (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113014674A (en) * | 2021-04-08 | 2021-06-22 | 北京百度网讯科技有限公司 | Method and device for drawing service dependency graph |
| CN113810234A (en) * | 2021-09-18 | 2021-12-17 | 北京字跳网络技术有限公司 | Micro-service link topology processing method and device and readable storage medium |
| CN114726739B (en) * | 2022-04-18 | 2024-04-09 | 深圳市智象科技有限公司 | Topology data processing method, device, equipment and storage medium |
| CN114726739A (en) * | 2022-04-18 | 2022-07-08 | 深圳市智象科技有限公司 | Topological data processing method, device, equipment and storage medium |
| CN114553709A (en) * | 2022-04-28 | 2022-05-27 | 恒生电子股份有限公司 | Topological relation display method and related equipment |
| CN114553709B (en) * | 2022-04-28 | 2022-08-23 | 恒生电子股份有限公司 | Topological relation display method and related equipment |
| CN115130993A (en) * | 2022-07-01 | 2022-09-30 | 江苏海洋大学 | Method for automatically drawing university course establishment relation topology structure diagram |
| CN115277436A (en) * | 2022-07-25 | 2022-11-01 | 浙江大学 | Micro-service software architecture identification method based on topological structure |
| CN115277436B (en) * | 2022-07-25 | 2023-08-04 | 浙江大学 | Micro-service software architecture identification method based on topological structure |
| CN116881571A (en) * | 2023-07-27 | 2023-10-13 | 广东麦视互联网科技有限公司 | Data mining method and system based on micro-service |
| CN116881571B (en) * | 2023-07-27 | 2024-01-12 | 广东麦视互联网科技有限公司 | Data mining method and system based on micro-service |
| CN117155978A (en) * | 2023-10-31 | 2023-12-01 | 山东弘毅节能服务有限公司 | Intelligent campus management system based on artificial intelligence |
| CN117155978B (en) * | 2023-10-31 | 2024-01-26 | 山东弘毅节能服务有限公司 | Intelligent campus management system based on artificial intelligence |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112615743B (en) | 2022-09-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112615743B (en) | Topological graph drawing method and device | |
| CN111447109B (en) | Monitoring management apparatus and method, computer readable storage medium | |
| CN109800207B (en) | Log analysis method, device and equipment and computer readable storage medium | |
| CN108052408B (en) | Alarm work order rapid submitting method and system based on alarm information content | |
| CN111030857A (en) | Network alarm method, device, system and computer readable storage medium | |
| KR20220124271A (en) | Fault detection method, device, electronic device and readable storage medium of live traffic | |
| CN110727557A (en) | Log collector control method, platform, electronic device and storage medium | |
| CN113505048A (en) | Unified monitoring platform based on application system portrait and implementation method | |
| CN109802842B (en) | Application topology generation method and related equipment | |
| CN110737634A (en) | Log searching method, client, server and computer readable storage medium | |
| CN116974948B (en) | Service system testing method, system, equipment and medium | |
| CN110569140A (en) | operation and maintenance method and device | |
| EP4071616A1 (en) | Method for generating topology diagram, anomaly detection method, device, apparatus, and storage medium | |
| CN103532737A (en) | Method, device and system for processing various types of alarms | |
| CN101771578B (en) | Network performance detection method and equipment | |
| CN111611132B (en) | Operation and maintenance analysis method, device, equipment and medium for service | |
| CN114756301A (en) | Log processing method, device and system | |
| CN114706893A (en) | Fault detection method, device, equipment and storage medium | |
| CN110851293B (en) | Information system linkage processing system and method | |
| CN110727532B (en) | Data restoration method, electronic equipment and storage medium | |
| EP2533153B1 (en) | Unit for managing messages indicating event situations of monitored objects | |
| CN107295087B (en) | System and method for realizing data aggregation between network systems | |
| CN113297218A (en) | Multi-system data interaction method, device and system | |
| CN112804241A (en) | Intelligent monitoring method and system for computer room network | |
| CN112291312B (en) | ETL data synchronization method and device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20210511 Address after: 210000 Room 301, 3rd floor, 138 Fengtai South Road, Yuhuatai District, Nanjing City, Jiangsu Province Applicant after: Nanjing cloud cabinet Network Technology Co.,Ltd. Address before: Room 1501, building 1, Tianhe Plaza, 146 Fengtai South Road, Yuhuatai District, Nanjing, Jiangsu Province 210000 Applicant before: JIANGSU CLOUDBOX NETWORK TECHNOLOGY Co.,Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |