CN112783720B - Topology structure diagram generation method, device, computer equipment and display system - Google Patents
Topology structure diagram generation method, device, computer equipment and display system Download PDFInfo
- Publication number
- CN112783720B CN112783720B CN202110006873.3A CN202110006873A CN112783720B CN 112783720 B CN112783720 B CN 112783720B CN 202110006873 A CN202110006873 A CN 202110006873A CN 112783720 B CN112783720 B CN 112783720B
- Authority
- CN
- China
- Prior art keywords
- data
- service method
- call
- determining
- calling
- 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.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/3048—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the topology of the computing system or computing system component explicitly influences the monitoring activity, e.g. serial, hierarchical systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/3006—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Computing Systems (AREA)
- Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Mathematical Physics (AREA)
- Quality & Reliability (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application relates to a topology structure diagram generation method, which comprises the following steps: acquiring a call log of a target call chain; determining calling relations among different service methods and operation data corresponding to the service methods according to the calling logs; determining a topological structure of a target call chain according to the call relationship, wherein the topological structure takes each service method as a node and represents the call relationship by connecting lines among the nodes; generating a topological structure diagram of the target call chain according to the topological structure; and sending the topological structure diagram and the operation data to a terminal for display, wherein the operation data is displayed in the topological structure diagram. By adopting the method, the topological structure of the target call chain can be accurately and completely constructed.
Description
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a topology structure diagram generating method, a device, a computer device, a storage medium, and a topology structure diagram display system.
Background
Currently, in the use process of internet software, a client of a service requiring party often needs to perform data interaction with a background service system of a service provider in most cases, and when the client initiates a service request, the background service system responds to the service request and may involve calling among a plurality of applications.
It is necessary for software developers to comb out call relationships between applications, either from the perspective of service troubleshooting or from the perspective of optimizing the service system.
The traditional call relation is combed, a topological structure is formed by analyzing the internal logic of each module code manually, and the topological structure is displayed through a user interface for a software developer to make analysis decisions.
However, the topology structure diagram generated in the above manner is limited by the range and time of manual carding, and the calling relation of the topology structure characterization sometimes has the condition of error or omission.
Disclosure of Invention
In view of the foregoing, it is necessary to provide a method, an apparatus, a computer device, a storage medium, and a topology structure diagram display system for accurately and completely constructing a topology structure of a call chain and generating a topology structure diagram.
A topology structure diagram generating method comprises the following steps:
acquiring a call log of a target call chain;
determining calling relations among different service methods and operation data corresponding to the service methods according to the calling logs;
Determining a topological structure of the target call chain according to the call relationship, wherein the topological structure takes each service method as a node and represents the call relationship by connecting lines among the nodes;
generating a topological structure diagram of the target call chain according to the topological structure;
and sending the topological structure diagram and the operation data to a terminal for display, wherein the operation data is displayed in the topological structure diagram.
In one embodiment, the operational data includes a plurality of index data;
the terminal is used for displaying the topological structure diagram in a preset user interface, the user interface comprises a topological structure diagram display area and an operation area, and the operation area comprises selection controls of the plurality of index data;
the terminal is further used for displaying the currently selected index data in the topological structure diagram display area when any one of the selection controls of the plurality of index data is monitored.
In one embodiment, the plurality of index data includes at least three index data including a query per second rate, a response time, and a fan-out ratio corresponding to the service method.
In one embodiment, the method further comprises:
determining a dependency relationship between a corresponding upstream service method and a corresponding downstream service method according to the calling relationship, wherein the dependency relationship is used for indicating that the upstream service method is available or unavailable when the downstream service method is unavailable;
generating dependency relationship data according to the dependency relationship;
and sending the dependency relationship data to the terminal for display, wherein the dependency relationship data is displayed in the topological structure diagram.
In one embodiment, the determining, according to the call log, a call relationship between different service methods and operation data corresponding to each service method includes:
determining different calling relations generated between the upstream service method and the downstream service method in different service flows according to the calling logs;
and determining operation data corresponding to the upstream service method and the downstream service method respectively in the different call relations.
In one embodiment, the method further comprises:
after the topology structure of the target call chain is determined according to the call relation, executing an update task according to an update instruction, wherein the executing the update task comprises: determining a new call log of the target call chain; sampling and collecting the new call log to obtain a target call log; updating the topological structure or the operation data according to the target call log;
When the topology is updated, correspondingly updating the topology structure map;
and sending the updated flutter structure diagram or the updated operation data to the terminal for display.
In one embodiment, the method further comprises:
before sampling and collecting the new call log, determining a target service method in the service methods;
the sampling and collecting the new call log comprises the following steps:
determining a calling identifier corresponding to the target service method;
and collecting the new call log with the call identifier as the target call log.
In one embodiment, determining the topology of the target call chain according to the call relationship includes:
generating triple data for recording the calling relation according to the calling relation,
the triplet data comprises a business flow identifier, an upstream service method identifier, a downstream service method identifier and a corresponding calling relation identifier;
converting the triplet data into data of a tree structure;
and determining a model structure corresponding to the data of the tree structure as the topological structure.
A topology map generation apparatus, the apparatus comprising:
the log acquisition module is used for acquiring a call log of the target call chain;
the log analysis module is used for determining the calling relation among different service methods and the operation data corresponding to each service method according to the calling log;
the topological structure determining module is used for determining the topological structure of the target call chain according to the call relationship, wherein the topological structure takes each service method as a node and represents the call relationship by connecting lines among the nodes;
the topology structure diagram generation module is used for generating a topology structure diagram of the target call chain according to the topology structure;
and the data sending module is used for sending the topological structure diagram and the operation data to a terminal for display, wherein the operation data is displayed in the topological structure diagram.
A topology construction diagram display system, the system comprising a server and a terminal, the terminal comprising a user interface;
the server is used for acquiring a call log of a target call chain, determining call relations among different service methods and operation data corresponding to the service methods according to the call log, determining a topological structure of the target call chain according to the call relations, wherein the topological structure takes the service methods as nodes, characterizes the call relations by connecting lines among the nodes, generates a topological structure diagram of the target call chain according to the topological structure, and sends the topological structure diagram and the operation data to a terminal;
The terminal is used for displaying the topological structure diagram in the user interface and displaying the operation data in the topological structure diagram.
A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps of:
acquiring a call log of a target call chain;
determining calling relations among different service methods and operation data corresponding to the service methods according to the calling logs;
determining a topological structure of the target call chain according to the call relationship, wherein the topological structure takes each service method as a node and represents the call relationship by connecting lines among the nodes;
generating a topological structure diagram of the target call chain according to the topological structure;
and sending the topological structure diagram and the operation data to a terminal for display, wherein the operation data is displayed in the topological structure diagram.
A computer readable storage medium having stored thereon a computer program which when executed by a processor performs the steps of:
acquiring a call log of a target call chain;
Determining calling relations among different service methods and operation data corresponding to the service methods according to the calling logs;
determining a topological structure of the target call chain according to the call relationship, wherein the topological structure takes each service method as a node and represents the call relationship by connecting lines among the nodes;
generating a topological structure diagram of the target call chain according to the topological structure;
and sending the topological structure diagram and the operation data to a terminal for display, wherein the operation data is displayed in the topological structure diagram.
According to the topology structure diagram generating method, the device, the computer equipment, the storage medium and the topology structure diagram display system, the call log is acquired through the computer, the call relation between different service methods can be automatically determined, so that the topology structure can be accurately and completely determined, meanwhile, the operation data for a user to know the operation conditions between the server or the service methods are also obtained, the topology structure diagram and the operation data are sent to the terminal, the terminal can completely and accurately display the topology structure to the user, the user can intuitively know the operation conditions through the operation data associated with the service methods, and the user experience is improved.
Drawings
FIG. 1 is an application environment diagram of a topology structure diagram generation method in one embodiment;
FIG. 2 is a flow diagram of a topology map generation method in one embodiment;
FIG. 3 is a schematic diagram of a user interface of a terminal in one embodiment;
FIG. 4 is a flow chart of an index data presentation step according to one embodiment;
FIG. 5 is a flow diagram that illustrates the dependency presentation steps involved in one embodiment;
FIG. 6 is a flow diagram that illustrates steps involved in updating a topology in one embodiment;
FIG. 7 is a flow diagram that illustrates the steps involved in target call log retrieval in one embodiment;
FIG. 8 is a block diagram showing a topology structure of an apparatus for generating a topology map in one embodiment;
fig. 9 is an internal structural diagram of a computer device in one embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application will be further described in detail with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the present application.
The topology structure diagram generation method provided by the application can be applied to an application environment shown in fig. 1. The method comprises the steps that a server 101 and a terminal 102 are communicated through a network, the server 101 processes a call log to obtain a topology structure diagram and operation data, and the terminal 102 obtains the topology structure diagram and displays the topology structure diagram and the operation data on a user interface; in addition, the terminal 102 may further obtain an input selection instruction, and display different operation data on the user interface according to the selection instruction. The server 101 may be implemented by a stand-alone server or a server cluster formed by a plurality of servers, and the terminal 102 may be, but is not limited to, various computers with user interfaces, notebook computers, smart phones, tablet computers or portable wearable devices.
Of course, fig. 1 is only one of the cases, and in other cases, some data processing steps involved in the topology structure diagram generating method of the present application may be partially or completely distributed in a server or a terminal according to actual needs, and the terminal performs at least the steps of displaying the topology structure diagram and displaying the operation data. However, for ease of explanation of the principles of the methods provided herein, the following description is primarily directed around the application environment of fig. 1.
In some embodiments, as shown in fig. 2, a topology structure diagram generating method is provided, and the method is applied to the server 101 in fig. 1 for illustration, and includes the following steps:
step S201, obtaining a call log of a target call chain;
step S202, determining calling relations among different service methods and operation data corresponding to the service methods according to the calling logs;
step S203, determining the topological structure of a target call chain according to the call relationship, wherein the topological structure takes each service method as a node and represents the call relationship by the connection line between the nodes;
step S204, generating a topological structure diagram of a target call chain according to the topological structure;
step S205, the topology structure diagram and the operation data are sent to the terminal 102 for display, wherein the operation data are displayed in the topology structure diagram.
The target call chain in step S201 refers to a call chain formed by calling corresponding service methods in the process of processing a specified service flow by a server. Because the number of call logs of the server related to the background system is huge, various call logs for internal services or external services may be related, it is necessary to determine the scope of the call log corresponding to the topology structure diagram to be generated at this time by means of an ID in the call log or an ID of the server, that is, determine the scope of the call chain to be analyzed in numerous call chains, that is, determine the target call chain. Further, the call log of the target call chain is generally a call log within a period of time (hereinafter referred to as "statistical period"), such as a call log within a past few days or a call log generated at a certain period of time of a certain day.
In some specific occasions, the service types can be preset, for example, for a background system of the shopping APP, different service types such as 'shopping', 'order', 'shopping cart' and the like can be set, different target call chains are determined through service flows corresponding to the different service types, and then related call logs are collected.
Since a large number of call logs in the statistics period are often obtained in the previous step, according to these call logs, by executing step S202, the call relationship between different service methods may be determined, and in addition, according to these call logs, data such as the call times between service methods in the statistics period, the query rate per second (QPS) corresponding to the service methods, the response time corresponding to the service methods, etc. may be obtained, and these data may represent the operation condition of the server or the operation condition of the service methods, and one or more of these data may be regarded as operation data.
In step S203, since one call chain may relate to call relationships among a plurality of service methods, a plurality of nodes may exist in the corresponding topology structure, each node represents a service method, and when a call relationship exists between two service methods, the node is characterized by a connection line between the nodes. In some cases, a corresponding topology structure can be determined for a preset service type, a corresponding topology structure can be determined for a certain service flow under a certain service type, and a corresponding topology structure of a call chain responding to a service request sent by a certain client to a server of a background system can be determined, so that the topology structure is firstly determined according to which call chain is used as a target call chain, and the selection of the target call chain and the final topology structure are influenced due to the construction purposes of different topology structures.
In step S204, a topology structure diagram may be generated according to the topology structure, where the topology structure diagram may include data of nodes of the topology structure and data of connection lines between the nodes; the data of the nodes correspond to the service method, and the data of the connecting lines between the nodes correspond to the connection relation.
In step S205, the topology structure diagram and the operation data are sent to the terminal 102 for the purpose of being presented by the terminal 102. When the terminal 102 has a user interface and the topology map and the operation data are displayed through the user interface, the operation data of the service method corresponding to the node can be displayed in the vicinity of the node in the topology map. Taking a part of the area shown in fig. 3 as an example, such operation data as 950, 950 and 900 can be respectively displayed at the positions near the first node 311, the second node 312 and the third node 313, so that a user (generally including related personnel of software development, maintenance and design) can more intuitively feel the operation condition of the whole calling link. Of course, FIG. 3 is merely one example, and in other examples, operational data may be presented in a list or other chart form.
Conventional call-related grooming is overly dependent on manual operations, statistics of the operational data are not refined to each service method, and the operational data are typically displayed in a separate table in another user interface, not associated with the topology. Different from the traditional mode, the topology structure diagram generating method provided by the application can automatically determine the calling relation between different service methods by acquiring the calling log of the target calling chain through the computer, thereby determining and obtaining the complete topology structure, simultaneously obtaining the operation data for a user to know the operation condition between the server or the service method, being beneficial to simultaneously displaying the topology structure and the operation data through the terminal 102, being capable of completely and accurately displaying the topology structure to the user, being convenient for the user to intuitively know the operation condition through the associated operation data, and improving the user experience.
In some embodiments, as shown in fig. 1, a topology structure diagram display system is provided, the system comprising a server 101 and a terminal 102, the terminal 102 comprising a user interface;
the server 101 is configured to obtain a call log of a target call chain, determine a call relationship between different service methods and operation data corresponding to each service method according to the call log, determine a topology structure of the target call chain according to the call relationship, and generate a topology structure diagram of the target call chain according to the topology structure by using each service method as a node and representing the call relationship by a connection line between the nodes, and send the topology structure diagram and the operation data to the terminal 102;
the terminal 102 is configured to present the topology map in a user interface and present the operating data in the topology map.
In some embodiments, as shown in fig. 3 and 4, the operational data includes a plurality of index data; the terminal 102 is configured to perform the following steps:
step S401, displaying a topology structure diagram in a preset user interface 300, where the user interface 300 includes a topology structure diagram display area 301 and an operation area 302, and the operation area 302 includes a plurality of selection controls 303 for index data;
in step S402, when a selection instruction of any one of the selection controls 303 of the plurality of index data is monitored, the currently selected index data is displayed in the topology structure diagram display area 301.
In fig. 3, there are a plurality of selection controls, three index data corresponding to the query rate per second, response time, and fanout ratio of each service method, respectively. Fig. 3 shows the situation when the selection control of the query rate per second is selected, and it can be seen that the query rate per second corresponding to the service method of the node is correspondingly displayed in the vicinity of each node. In fig. 3, when the user selects other selection controls through operation, corresponding index data is displayed on the topology structure chart.
In some embodiments, the plurality of metric data includes at least three metric data including a query per second, a response time, and a fan-out ratio corresponding to the service method. It should be noted that in more specific situations, there may be more specific definitions of the index data, for example, for a query rate per second, it may be specifically defined as a daily peak query rate per second or an average query rate per second over a specified period of time; similarly for response time, the specific physical meaning of the response time direction can be further defined according to specific requirements, for example, the response time can refer to the peak-of-day response time; the fan-out ratio is also the same and will not be described in detail.
In some embodiments, the operation area may further include a selection control of the service condition logic, and when a selection instruction of the selection control is monitored, a calling relationship or a calling sequence of the service method in different service flows is shown in the topology structure chart showing area 301.
In some embodiments, the computer room IP identifier corresponding to the service method may also be obtained according to the call log, and then displayed in the topology structure diagram. When a certain service method is judged to be unavailable, the machine room IP identification code can be displayed for prompting.
In some embodiments, as shown in fig. 5, the topology structure map generating method further includes:
step S501, determining a dependency relationship between a corresponding upstream service method and a corresponding downstream service method according to a calling relationship, wherein the dependency relationship is used for indicating that the upstream service method is available or unavailable when the downstream service method is unavailable;
step S502, generating dependency relationship data according to the dependency relationship;
step S503, the dependency data is sent to the terminal 102 for display, where the dependency data is displayed in the topology structure diagram.
Correspondingly, the operation area of the user interface of the terminal 102 further comprises a selection control of the dependency relationship; the terminal 102 is further configured to perform the following operations: when a selection instruction of a selection control of the dependency relationship is monitored, the dependency relationship is displayed in a topology structure diagram display area.
More specifically, the dependencies may include a first dependency and a second dependency, the first dependency being used to indicate that the upstream service method continues to be available when the downstream service method is unavailable; the second dependency is used to indicate that the upstream service method is not available when the downstream service method is not available. The corresponding dependency relationship between the nodes can be displayed by giving different colors to the connection lines between the nodes in the topology structure diagram display area. In general, determining whether a service method is available can be performed by detecting whether the call log has error reporting information, and if the downstream service method reports errors, the upstream service method also follows the same type of errors, which can be regarded as unavailable when the downstream service method is unavailable. Of course, the dependency relationship may be defined according to other set rules.
In some embodiments, step S202 includes: determining different calling relations generated between an upstream service method and a downstream service method in different service flows according to the calling logs; and determining operation data corresponding to the upstream service method and the downstream service method respectively in different calling relations. Considering that in different business processes, the same upstream service method may call different downstream service methods, i.e. different business processes may cause a certain upstream service method to generate different calling relations for its downstream service method. Therefore, the operation data of the service method in different calling relations can be determined based on different calling relations, so that richer data for decision analysis can be brought to users. In addition, the connection lines among different nodes can be set according to different calling relations, and the topological structure is displayed in different display modes (such as different calling relations are displayed by using connection lines with different colors and different shapes), so that a user can see the topological structure more clearly.
Further, since the operation data are included in different calling relations, the upstream service method and the downstream service method respectively correspond to the operation data; the server 101 may send these operation data to the terminal 102; the terminal 102 may be configured to display, in the topology structure diagram display area, service data corresponding to a currently selected calling relationship when a selection instruction of a selection control corresponding to a certain calling relationship is monitored in selection controls of different calling relationships.
In some embodiments, as shown in fig. 7 and fig. 7, the topology structure diagram generating method further includes:
step S601, after step S203, executing an update task according to the update instruction; step S602, when the topology is updated, correspondingly updating the topology structure diagram; step S603, the updated topology structure diagram or the updated operation data is sent to the terminal 102 for display. Wherein performing the update task comprises the steps of: step S701, determining a new call log of a target call chain; step S702, sampling and collecting a new call log to obtain a target call log; step S703, updating the topology or the operation data according to the target call log. Correspondingly, the terminal 102 is further configured to display the updated topology structure diagram or the updated operation data.
The update instruction may be issued periodically, or may be issued at a specific time selected according to the actual situation. The update task is executed in the meaning that after the topology is initially established and the operation data is initially obtained, a new call log is generated every day due to a server of the background system, and meanwhile, a user may develop a new service scene so that the actual operation data and the topology are changed. When the change of the calling relation among different service methods is determined through the target calling log or a new service method appears, the topology structure needs to be updated; when the topology is unchanged, but only the operation data is changed, only the operation data is updated. At this time, the topology structure and the operation data are updated by adopting a sampling and collecting mode, so that the data processing capacity of the server can be reduced, and the user can obtain the latest information of the topology structure and the operation data under the concerned business process. The sampling and collecting modes can be various, for example, a certain percentage of sampling rate can be set for a new call log generated in a new statistical period, and special collection can be performed for a new call log of a call chain related to a certain service method.
In some embodiments, prior to step S702, a target service method is first determined among the service methods; accordingly, step S702 includes: determining a calling identifier corresponding to the target service method; and collecting the new call log with the call identifier as a target call log. The method can set the entry flow identification for some concerned service methods (namely the target service method) according to different service flows set in practice, and can collect the new call log of the target call chain related to the target service method when sampling and collecting the new call log is needed, so that the topology structure corresponding to the concerned service flow can be updated in time with higher pertinence. For some service methods which are not concerned, the frequency of collecting the related call logs can be reduced, namely the frequency of updating the related topological structure can be reduced. The call identifier corresponding to the target service method may be an identifier such as an ID of a server corresponding to the target service method or an ID of a corresponding call chain, or may be other identifiers.
In some embodiments, step S203 includes: generating triple data for recording the calling relation according to the calling relation, wherein the triple data comprises a business flow identifier, an upstream service method identifier, a downstream service method identifier and a corresponding calling relation identifier; converting the triplet data into data of a tree structure; and determining a model structure corresponding to the data of the tree structure as a topological structure. In the foregoing triplet data, the service flow identifier is used to indicate that the call chain of a certain upstream service method and a certain downstream service method relates to a certain customized service flow service. The business process identification may be associated with the entry process identification in the previous embodiment. More specifically, in the triplet data, the identifier of the upstream service method identifier, the identifier of the domain name corresponding to the calling relationship, and the identifier of the target business process can be used as basic elements of the triplet data, and the calling relationship identifier is used as attribute information. By means of generating the triple data and converting the triple data into the data of the tree structure, the purpose of rapidly extracting the topological structure from the call log is achieved. By means of generating the triple data and converting the triple data into the data of the tree structure, the purpose of rapidly extracting the topological structure from the call log is achieved.
It should be understood that, although the steps in the flowcharts of fig. 2 and 4-7 are shown in order as indicated by the arrows, these steps are not necessarily performed in order as indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, at least some of the steps of fig. 2, 4-7 may include multiple sub-steps or stages that are not necessarily performed at the same time, but may be performed at different times, nor does the order in which the sub-steps or stages are performed necessarily occur in sequence, but may be performed alternately or alternately with other steps or at least a portion of the sub-steps or stages of other steps.
In one embodiment, as shown in fig. 8, there is provided a topology structure map generating apparatus 800, comprising: a log obtaining module 801, a log analyzing module 802, a topology structure determining module 803, a topology structure diagram generating module 804 and a data transmitting module 805, wherein:
a log obtaining module 801, configured to obtain a call log of a target call chain;
The log analysis module 802 is configured to determine, according to the call log, a call relationship between different service methods and operation data corresponding to each service method;
the topology structure determining module 803 is configured to determine a topology structure of a target call chain according to the call relationship, where the topology structure uses each service method as a node, and represents the call relationship by using a connection line between the nodes;
the topology structure diagram generating module 804 is configured to generate a topology structure diagram of the target call chain according to the topology structure;
and the data sending module 805 is configured to send the topology structure diagram and the operation data to the terminal for display, where the operation data is displayed in the topology structure diagram.
In one embodiment, the topology structure map generation apparatus 800 further includes: the dependency relationship determining module is used for determining the dependency relationship between the corresponding upstream service method and the corresponding downstream service method according to the calling relationship, wherein the dependency relationship is used for indicating that the upstream service method is available or unavailable when the downstream service method is unavailable; the dependency relationship data generation module is used for generating dependency relationship data according to the dependency relationship; correspondingly, the data sending module 805 is further configured to send the dependency data to a terminal for presentation, where the dependency data is presented in a topology structure diagram.
In one embodiment, log analysis module 802 includes: the relation determining unit is used for determining different calling relations generated between the upstream service method and the downstream service method in different service flows according to the calling logs; and the relation data determining unit is used for determining operation data corresponding to the upstream service method and the downstream service method respectively in different calling relations.
In one embodiment, the topology structure map generation apparatus 800 further includes: the updating task execution module is used for executing the updating task according to the updating instruction after determining the topological structure of the target call chain according to the call relation; the topological graph updating module is used for correspondingly updating the topological structure graph when the topological structure is updated; correspondingly, the data sending module 805 is further configured to send the updated puff graph or the updated operation data to the terminal for display. In this embodiment, the update task module further includes: the new call log determining unit is used for determining a new call log of the target call chain; the sampling unit is used for sampling and collecting the new call log to obtain a target call log; and the data updating unit is used for updating the topological structure or the operation data according to the target call log.
In one embodiment, the topology structure map generating apparatus 800 further includes a target method determining module for determining a target service method among the service methods before sampling the new call log; correspondingly, the sampling unit is specifically configured to: determining a calling identifier corresponding to the target service method; and collecting the new call log with the call identifier as a target call log.
In one embodiment, the topology determination module 803 includes: the system comprises a triplet generation unit, a call relation generation unit and a call relation generation unit, wherein the triplet generation unit is used for generating triplet data for recording the call relation according to the call relation, and the triplet data comprises a business flow identifier, an upstream service method identifier, a downstream service method identifier and a corresponding call relation identifier; the data structure conversion unit is used for converting the triplet data into data with a tree structure; and the structure determining unit is used for determining a model structure corresponding to the data of the tree structure as a topological structure.
For specific limitations of the topology structure map generating apparatus, reference may be made to the above limitation of the topology structure map generating method, and no further description is given here. The respective modules in the topology structure map generating apparatus described above may be implemented in whole or in part by software, hardware, or a combination thereof. The above modules may be embedded in hardware or may be independent of a processor in the computer device, or may be stored in software in a memory in the computer device, so that the processor may call and execute operations corresponding to the above modules.
In one embodiment, a computer device is provided, which may be a server, and the internal structure of which may be as shown in fig. 9. The computer device includes a processor, a memory, and a network interface connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a topology structure map generation method.
It will be appreciated by those skilled in the art that the structure shown in fig. 9 is merely a block diagram of a portion of the structure associated with the present application and is not limiting of the computer device to which the present application applies, and that a particular computer device may include more or fewer components than shown, or may combine some of the components, or have a different arrangement of components.
In one embodiment, a computer device is provided comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor implementing the steps of when executing the computer program: acquiring a call log of a target call chain; determining calling relations among different service methods and operation data corresponding to the service methods according to the calling logs; determining a topological structure of a target call chain according to the call relationship, wherein the topological structure takes each service method as a node and represents the call relationship by connecting lines among the nodes; generating a topological structure diagram of the target call chain according to the topological structure; and sending the topological structure diagram and the operation data to a terminal for display, wherein the operation data is displayed in the topological structure diagram.
In one embodiment, the processor when executing the computer program further performs the steps of: determining a dependency relationship between the corresponding upstream service method and the corresponding downstream service method according to the calling relationship, wherein the dependency relationship is used for indicating that the upstream service method is available or unavailable when the downstream service method is unavailable; generating dependency data according to the dependency; and sending the dependency relationship data to a terminal for display, wherein the dependency relationship data is displayed in a topological structure diagram.
In one embodiment, the step of determining the calling relation between different service methods and the operation data corresponding to each service method according to the calling log is implemented when the processor executes the computer program, and includes the following steps: determining different calling relations generated between an upstream service method and a downstream service method in different service flows according to the calling logs; and determining operation data corresponding to the upstream service method and the downstream service method respectively in different calling relations.
In one embodiment, the processor when executing the computer program further performs the steps of: after determining the topological structure of the target call chain according to the call relation, executing an update task according to the update instruction; when the topology is updated, correspondingly updating the topology structure diagram; and sending the updated flutter structure diagram or the updated operation data to the terminal for display. Further, the step of implementing the update task when the processor executes the computer program includes: determining a new call log of the target call chain; sampling and collecting the new call log to obtain a target call log; according to the target call log, updating the topological structure or the operation data;
In one embodiment, the processor when executing the computer program further performs the steps of: before sampling and collecting a new call log, determining a target service method among the service methods; further, the step of implementing sampling the new call log when the processor executes the computer program includes: determining a calling identifier corresponding to the target service method; and collecting the new call log with the call identifier as a target call log.
In one embodiment, the step of determining the topology of the target call chain based on the call relationship is implemented when the processor executes the computer program and comprises: generating triple data for recording the calling relation according to the calling relation, wherein the triple data comprises a business flow identifier, an upstream service method identifier, a downstream service method identifier and a corresponding calling relation identifier; converting the triplet data into data of a tree structure; and determining a model structure corresponding to the data of the tree structure as a topological structure.
In one embodiment, a computer readable storage medium is provided having a computer program stored thereon, which when executed by a processor, performs the steps of: acquiring a call log of a target call chain; determining calling relations among different service methods and operation data corresponding to the service methods according to the calling logs; determining a topological structure of a target call chain according to the call relationship, wherein the topological structure takes each service method as a node and represents the call relationship by connecting lines among the nodes; generating a topological structure diagram of the target call chain according to the topological structure; and sending the topological structure diagram and the operation data to a terminal for display, wherein the operation data is displayed in the topological structure diagram.
In one embodiment, the computer program when executed by the processor further performs the steps of: determining a dependency relationship between the corresponding upstream service method and the corresponding downstream service method according to the calling relationship, wherein the dependency relationship is used for indicating that the upstream service method is available or unavailable when the downstream service method is unavailable; generating dependency data according to the dependency; and sending the dependency relationship data to a terminal for display, wherein the dependency relationship data is displayed in a topological structure diagram.
In one embodiment, the step of determining the calling relation between different service methods and the operation data corresponding to each service method according to the calling log when the computer program is executed by the processor includes the following steps: determining different calling relations generated between an upstream service method and a downstream service method in different service flows according to the calling logs; and determining operation data corresponding to the upstream service method and the downstream service method respectively in different calling relations.
In one embodiment, the computer program when executed by the processor further performs the steps of: after determining the topological structure of the target call chain according to the call relation, executing an update task according to the update instruction; when the topology is updated, correspondingly updating the topology structure diagram; and sending the updated flutter structure diagram or the updated operation data to the terminal for display. Further, the step of performing the update task when the computer program is executed by the processor comprises: determining a new call log of the target call chain; sampling and collecting the new call log to obtain a target call log; according to the target call log, updating the topological structure or the operation data;
In one embodiment, the computer program when executed by the processor further performs the steps of: before sampling and collecting a new call log, determining a target service method among the service methods; further, the step of performing sample collection of the new call log when the computer program is executed by the processor comprises: determining a calling identifier corresponding to the target service method; and collecting the new call log with the call identifier as a target call log.
In one embodiment, the step of determining the topology of the target call chain based on the call relationships is implemented when the computer program is executed by the processor, comprising: generating triple data for recording the calling relation according to the calling relation, wherein the triple data comprises a business flow identifier, an upstream service method identifier, a downstream service method identifier and a corresponding calling relation identifier; converting the triplet data into data of a tree structure; and determining a model structure corresponding to the data of the tree structure as a topological structure.
Those skilled in the art will appreciate that implementing all or part of the above described methods may be accomplished by way of a computer program stored on a non-transitory computer readable storage medium, which when executed, may comprise the steps of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in the various embodiments provided herein may include non-volatile and/or volatile memory. The nonvolatile memory can include Read Only Memory (ROM), programmable ROM (PROM), electrically Programmable ROM (EPROM), electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), memory bus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), among others.
The technical features of the above embodiments may be arbitrarily combined, and all possible combinations of the technical features in the above embodiments are not described for brevity of description, however, as long as there is no contradiction between the combinations of the technical features, they should be considered as the scope of the description.
The above examples merely represent a few embodiments of the present application, which are described in more detail and are not to be construed as limiting the scope of the invention. It should be noted that it would be apparent to those skilled in the art that various modifications and improvements could be made without departing from the spirit of the present application, which would be within the scope of the present application. Accordingly, the scope of protection of the present application is to be determined by the claims appended hereto.
Claims (9)
1. A topology map generation method, the method comprising:
acquiring a call log of a target call chain;
determining calling relations among different service methods and operation data corresponding to the service methods according to the calling logs;
determining a topological structure of the target call chain according to the call relationship, wherein the topological structure takes each service method as a node and represents the call relationship by connecting lines among the nodes;
Generating a topological structure diagram of the target call chain according to the topological structure;
transmitting the topological structure diagram and the operation data to a terminal for display, wherein the operation data is displayed in the topological structure diagram;
determining a dependency relationship between a corresponding upstream service method and a corresponding downstream service method according to the calling relationship, wherein the dependency relationship is used for indicating that the upstream service method is available or unavailable when the downstream service method is unavailable;
generating dependency relationship data according to the dependency relationship;
sending the dependency relationship data to the terminal for display, wherein the dependency relationship data is displayed in the topological structure diagram;
the determining, according to the call log, a call relationship between different service methods and operation data corresponding to each service method includes: determining different calling relations generated between the upstream service method and the downstream service method in different service flows according to the calling logs; determining operation data corresponding to the upstream service method and the downstream service method respectively in the different calling relations;
the determining the topology structure of the target call chain according to the call relationship comprises the following steps: generating triple data for recording the calling relation according to the calling relation, wherein the triple data comprises a business flow identifier, an upstream service method identifier, a downstream service method identifier and a corresponding calling relation identifier; converting the triplet data into data of a tree structure; and determining a model structure corresponding to the data of the tree structure as the topological structure.
2. The method of claim 1, wherein the operational data comprises a plurality of metric data;
the terminal is used for displaying the topological structure diagram in a preset user interface, the user interface comprises a topological structure diagram display area and an operation area, and the operation area comprises selection controls of the plurality of index data;
the terminal is further used for displaying the currently selected index data in the topological structure diagram display area when any one of the selection controls of the plurality of index data is monitored.
3. The method of claim 2, wherein the plurality of metric data includes at least three metric data including a query per second rate, a response time, and a fan-out ratio corresponding to the service method.
4. The method according to claim 1, wherein the method further comprises:
after the topology structure of the target call chain is determined according to the call relation, executing an update task according to an update instruction, wherein the executing the update task comprises: determining a new call log of the target call chain; sampling and collecting the new call log to obtain a target call log; updating the topological structure or the operation data according to the target call log;
When the topology is updated, correspondingly updating the topology structure map;
and sending the updated flutter structure diagram or the updated operation data to the terminal for display.
5. The method according to claim 4, wherein the method further comprises:
before sampling and collecting the new call log, determining a target service method in the service methods;
the sampling and collecting the new call log comprises the following steps:
determining a calling identifier corresponding to the target service method;
and collecting the new call log with the call identifier as the target call log.
6. A topology map generation apparatus, the apparatus comprising:
the log acquisition module is used for acquiring a call log of the target call chain;
the log analysis module is used for determining the calling relation among different service methods and the operation data corresponding to each service method according to the calling log;
the topological structure determining module is used for determining the topological structure of the target call chain according to the call relationship, wherein the topological structure takes each service method as a node and represents the call relationship by connecting lines among the nodes;
The topology structure diagram generation module is used for generating a topology structure diagram of the target call chain according to the topology structure;
the data sending module is used for sending the topological structure diagram and the operation data to a terminal for display, wherein the operation data is displayed in the topological structure diagram;
the dependency relationship determining module is used for determining a dependency relationship between a corresponding upstream service method and a corresponding downstream service method according to the calling relationship, wherein the dependency relationship is used for indicating that the upstream service method is available or unavailable when the downstream service method is unavailable;
the dependency relationship data generation module is used for generating dependency relationship data according to the dependency relationship;
wherein, the log analysis module includes: the relation determining unit is used for determining different calling relations generated between the upstream service method and the downstream service method in different service flows according to the calling logs; a relationship data determining unit, configured to determine operation data corresponding to the upstream service method and the downstream service method respectively in the different call relationships;
the topology determination module includes: the triplet generation unit is used for generating triplet data for recording the calling relation according to the calling relation, wherein the triplet data comprises a business flow identifier, an upstream service method identifier, a downstream service method identifier and a corresponding calling relation identifier; a data structure conversion unit for converting the triplet data into data of a tree structure; a structure determining unit, configured to determine a model structure corresponding to the tree structure data as the topology structure;
The data sending module is further configured to send the dependency relationship data to the terminal for display, where the dependency relationship data is displayed in the topology structure diagram.
7. A topology construction diagram display system, characterized in that the system comprises a server and a terminal, the terminal comprising a user interface;
the server is used for acquiring a call log of a target call chain, determining call relations among different service methods and operation data corresponding to the service methods according to the call log, determining a topological structure of the target call chain according to the call relations, wherein the topological structure takes the service methods as nodes, characterizes the call relations by connecting lines among the nodes, generates a topological structure diagram of the target call chain according to the topological structure, and sends the topological structure diagram and the operation data to the terminal; determining a dependency relationship between a corresponding upstream service method and a corresponding downstream service method according to the calling relationship, wherein the dependency relationship is used for indicating that the upstream service method is available or unavailable when the downstream service method is unavailable; generating dependency relationship data according to the dependency relationship; sending the dependency data to the terminal;
The determining, according to the call log, a call relationship between different service methods and operation data corresponding to each service method includes: determining different calling relations generated between the upstream service method and the downstream service method in different service flows according to the calling logs; determining operation data corresponding to the upstream service method and the downstream service method respectively in the different calling relations;
the determining the topology structure of the target call chain according to the call relationship comprises the following steps: generating triple data for recording the calling relation according to the calling relation, wherein the triple data comprises a business flow identifier, an upstream service method identifier, a downstream service method identifier and a corresponding calling relation identifier; converting the triplet data into data of a tree structure; determining a model structure corresponding to the data of the tree structure as the topological structure;
the terminal is used for displaying the topological structure diagram in the user interface and displaying the operation data and the dependency relationship data in the topological structure diagram.
8. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the steps of the method according to any one of claims 1 to 5 when the computer program is executed by the processor.
9. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the steps of the method of any of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110006873.3A CN112783720B (en) | 2021-01-05 | 2021-01-05 | Topology structure diagram generation method, device, computer equipment and display system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110006873.3A CN112783720B (en) | 2021-01-05 | 2021-01-05 | Topology structure diagram generation method, device, computer equipment and display system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112783720A CN112783720A (en) | 2021-05-11 |
| CN112783720B true CN112783720B (en) | 2023-05-19 |
Family
ID=75755300
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110006873.3A Active CN112783720B (en) | 2021-01-05 | 2021-01-05 | Topology structure diagram generation method, device, computer equipment and display system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112783720B (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113590361A (en) * | 2021-08-04 | 2021-11-02 | 中科曙光国际信息产业有限公司 | Virtual process topology method, device, computer equipment and storage medium |
| CN114039860B (en) * | 2021-11-03 | 2023-10-31 | 厦门市美亚柏科信息股份有限公司 | Method and system for quickly constructing server network topology graph |
| CN114629768A (en) * | 2022-02-17 | 2022-06-14 | 亚信科技（南京）有限公司 | Application topology processing method and device, electronic equipment, storage medium and product |
| CN115333966B (en) * | 2022-08-11 | 2023-05-12 | 天翼数字生活科技有限公司 | Topology-based Nginx log analysis method, system and equipment |
| CN115473823A (en) * | 2022-08-11 | 2022-12-13 | 创业慧康科技股份有限公司 | Topological data set display method and device |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2013020591A (en) * | 2011-07-14 | 2013-01-31 | Kddi Corp | Dependency graph creation device, failure occurrence location diagnosis system, failure occurrence location diagnosis method and computer program |
| CN107704382A (en) * | 2017-09-07 | 2018-02-16 | 北京信息科技大学 | Towards Python function call path generating method and system |
| CN109992474A (en) * | 2019-03-08 | 2019-07-09 | 江苏达科云数据科技有限公司 | System topological detects generation method under a kind of cloud environment |
| CN110333898A (en) * | 2019-05-27 | 2019-10-15 | 北京达佳互联信息技术有限公司 | A kind of code relation generation method, device, electronic equipment and storage medium |
| CN111008022A (en) * | 2019-12-04 | 2020-04-14 | 浙江大搜车软件技术有限公司 | Relationship graph generation method and device, computer equipment and storage medium |
| CN111831548A (en) * | 2020-05-29 | 2020-10-27 | 微民保险代理有限公司 | Method and device for drawing dependency relationship topological graph |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106657192B (en) * | 2015-11-03 | 2020-06-30 | 阿里巴巴集团控股有限公司 | Method and equipment for presenting service calling information |
| CN108038145A (en) * | 2017-11-23 | 2018-05-15 | 携程旅游网络技术（上海）有限公司 | Distributed Services tracking, system, storage medium and electronic equipment |
| CN112115390A (en) * | 2019-06-20 | 2020-12-22 | 华为技术有限公司 | Method, device and equipment for displaying topology structure diagram and storage medium |
| CN110287081A (en) * | 2019-06-21 | 2019-09-27 | 腾讯科技(成都)有限公司 | A kind of service monitoring system and method |
| CN110515750B (en) * | 2019-09-05 | 2024-03-15 | 北京博睿宏远数据科技股份有限公司 | Application topology generation method, system and cluster |
| CN111913706B (en) * | 2020-07-07 | 2022-07-01 | 国电南瑞科技股份有限公司 | Topology construction method of dispatching automation system, storage medium and computing equipment |
-
2021
- 2021-01-05 CN CN202110006873.3A patent/CN112783720B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2013020591A (en) * | 2011-07-14 | 2013-01-31 | Kddi Corp | Dependency graph creation device, failure occurrence location diagnosis system, failure occurrence location diagnosis method and computer program |
| CN107704382A (en) * | 2017-09-07 | 2018-02-16 | 北京信息科技大学 | Towards Python function call path generating method and system |
| CN109992474A (en) * | 2019-03-08 | 2019-07-09 | 江苏达科云数据科技有限公司 | System topological detects generation method under a kind of cloud environment |
| CN110333898A (en) * | 2019-05-27 | 2019-10-15 | 北京达佳互联信息技术有限公司 | A kind of code relation generation method, device, electronic equipment and storage medium |
| CN111008022A (en) * | 2019-12-04 | 2020-04-14 | 浙江大搜车软件技术有限公司 | Relationship graph generation method and device, computer equipment and storage medium |
| CN111831548A (en) * | 2020-05-29 | 2020-10-27 | 微民保险代理有限公司 | Method and device for drawing dependency relationship topological graph |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112783720A (en) | 2021-05-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112783720B (en) | Topology structure diagram generation method, device, computer equipment and display system | |
| CN107992409B (en) | Test case generation method and device, computer equipment and storage medium | |
| CN112910945B (en) | Request link tracking method and service request processing method | |
| CN110688598B (en) | Service parameter acquisition method and device, computer equipment and storage medium | |
| EP4086771B1 (en) | Method and system for the on-demand generation of graph-like models out of multidimensional observation data | |
| CN109388791B (en) | Dynamic diagram display method and device, computer equipment and storage medium | |
| CN111400367B (en) | Service report generation method, device, computer equipment and storage medium | |
| US11144376B2 (en) | Veto-based model for measuring product health | |
| CN112202617B (en) | Resource management system monitoring method, device, computer equipment and storage medium | |
| CN113760641A (en) | Service monitoring method, device, computer system and computer readable storage medium | |
| CN112051771B (en) | Multi-cloud data acquisition method and device, computer equipment and storage medium | |
| CN111177481B (en) | User identifier mapping method and device | |
| CN113810234B (en) | Method and device for processing micro-service link topology and readable storage medium | |
| CN113821254A (en) | Interface data processing method, device, storage medium and equipment | |
| CN110780950A (en) | Interface metadata management method and device, computer equipment and storage medium | |
| CN112579705A (en) | Metadata acquisition method and device, computer equipment and storage medium | |
| CN113592114A (en) | User fault reporting research and judgment method and device in power grid, computer equipment and storage medium | |
| CN113377682A (en) | Service testing method and device | |
| CN113377789A (en) | Processing method and device for database change data, computer equipment and medium | |
| CN111259050A (en) | User operation track recording method and device, computer equipment and storage medium | |
| US10616306B2 (en) | System and method for large-scale capture and tracking of web-based application parameters | |
| CN111158979A (en) | Service dial testing method, system, device and storage medium | |
| CN112783739B (en) | Timeout time display method, device, system, computer equipment and storage medium | |
| CN110928750A (en) | Data processing method, device and equipment | |
| CN116089490A (en) | Data analysis method, device, terminal 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |