CN110543401A - hierarchical application topology generation method, system and cluster - Google Patents
hierarchical application topology generation method, system and cluster Download PDFInfo
- Publication number
- CN110543401A CN110543401A CN201910837343.6A CN201910837343A CN110543401A CN 110543401 A CN110543401 A CN 110543401A CN 201910837343 A CN201910837343 A CN 201910837343A CN 110543401 A CN110543401 A CN 110543401A
- Authority
- CN
- China
- Prior art keywords
- data
- application
- calling
- service
- cluster
- 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
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/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
-
- 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/3065—Monitoring arrangements determined by the means or processing involved in reporting the monitored data
- G06F11/3072—Monitoring arrangements determined by the means or processing involved in reporting the monitored data where the reporting involves data filtering, e.g. pattern matching, time or event triggered, adaptive or policy-based reporting
- G06F11/3082—Monitoring arrangements determined by the means or processing involved in reporting the monitored data where the reporting involves data filtering, e.g. pattern matching, time or event triggered, adaptive or policy-based reporting the data filtering being achieved by aggregating or compressing the monitored data
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Quality & Reliability (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Mathematical Physics (AREA)
- Computer Vision & Pattern Recognition (AREA)
- Debugging And Monitoring (AREA)
Abstract
The embodiment of the invention provides a hierarchical application topology generation method, a system and a cluster, wherein the method comprises the following steps: when an instance in the application is called, recording back-end calling data at a position where a corresponding class method is called at the back end through a probe configured by the instance; the back-end calling data comprises calling relation data, calling evaluation index data, application identifiers, service identifiers, cluster identifiers and probe identifiers corresponding to the instances; reporting the back-end calling data to a data processing server through a probe, obtaining aggregated data of the back-end calling data through the data processing server based on an application identifier, a service identifier and a cluster identifier corresponding to an example, and storing the aggregated data and the back-end calling data to a database; the service analysis system queries the back-end calling data and the aggregated data, and generates a hierarchical application topology based on the back-end calling data and the aggregated data, so that the application topology can be simplified, the checking information can be conveniently positioned step by step, and the checking efficiency is improved.
Description
Technical Field
the embodiment of the invention relates to the technical field of computers, in particular to a hierarchical application topology generation method, a hierarchical application topology generation system and a hierarchical application topology generation cluster.
Background
the application topology reflects the call relationships between multiple instances within the application (which may be the system or functional modules of the system). The application topology reflects the circulation of service flows among a plurality of nodes, and comprises an end-to-end execution process of reflecting services, not only the calling relation between ends, but also calling evaluation index data.
with the development of internet big data technology, distributed application is more and more complex, an application topology combed by using a traditional method is inconvenient to look up due to more nodes and no good level of the application topology, and the information to be looked up can be found only by spending more time, so that the looking-up efficiency is low.
Disclosure of Invention
The embodiment of the invention provides a hierarchical application topology generation method, which can simplify application topology, is convenient for positioning checked information step by step and improves checking efficiency.
In a first aspect, an embodiment of the present invention provides a hierarchical application topology generating method, including:
When an instance in the application is called, recording back-end calling data at a position where a corresponding class method is called at the back end through a probe configured by the instance;
the back-end calling data comprise calling relation data, calling evaluation index data, application identifiers, service identifiers, cluster identifiers and probe identifiers corresponding to the instances; the application is a service system or a functional module of the service system;
reporting the back-end calling data to a data processing server through the probe, obtaining aggregated data of the back-end calling data through the data processing server based on the application identifier, the service identifier and the cluster identifier corresponding to the instance, and storing the aggregated data and the back-end calling data to a database;
And accessing the database through a service analysis system, inquiring the back-end calling data and the aggregation data, and generating a hierarchical application topology based on the back-end calling data and the aggregation data.
In a second aspect, an embodiment of the present invention further provides a data determining method, including:
When an instance in the application is called, recording back-end calling data at a position where a corresponding class method is called at the back end through a probe configured by the instance;
The back-end calling data comprise calling relation data, calling evaluation index data, application identifiers, service identifiers, cluster identifiers and probe identifiers corresponding to the instances; the application is a service system or a functional module of the service system;
and reporting the back-end calling data to a data processing server through the probe, obtaining aggregated data of the back-end calling data through the data processing server based on the application identifier, the service identifier and the cluster identifier corresponding to the instance, and storing the aggregated data and the back-end calling data to a database.
in a third aspect, an embodiment of the present invention provides a hierarchical application topology generating method, including:
querying back-end call data and aggregated data in a database;
the back-end calling data comprise calling relation data, calling evaluation index data, application identifiers, service identifiers, cluster identifiers and probe identifiers corresponding to the instances; the application is a service system or a functional module of the service system; acquiring aggregated data of post-call data based on application identifiers, service identifiers and cluster identifiers corresponding to the instances;
generating a hierarchical application topology based on the back-end invocation data and the aggregated data.
In a fourth aspect, an embodiment of the present invention provides a hierarchical application topology system, including: the system comprises a business system, a probe, a data processing server and an analysis system;
The service system is used for recording back-end calling data at a back-end calling corresponding class method through a probe configured by an instance when the instance in the application is called, and reporting the back-end calling data to the data processing server through the probe;
the back-end calling data comprise calling relation data, calling evaluation index data, application identifiers, service identifiers, cluster identifiers and probe identifiers corresponding to the instances; the application is a service system or a functional module of the service system;
the data processing server is used for obtaining aggregated data of post-calling data based on the application identifier, the service identifier and the cluster identifier corresponding to the instance, and storing the aggregated data and the post-calling data to a database;
And the service analysis system is used for accessing the database, inquiring the back-end calling data and the aggregation data, and generating a hierarchical application topology based on the back-end calling data and the aggregation data.
In a fifth aspect, an embodiment of the present invention provides a cluster, which includes the hierarchical application topology generation system provided in the embodiment of the present invention.
according to the technical scheme provided by the embodiment of the invention, when an instance in application is called, the back-end calling data is recorded at the position of a back-end calling corresponding class method by configuring a probe in the instance, wherein the back-end calling data comprises calling relation data, calling evaluation index data, an application identifier, a service identifier, a cluster identifier and a probe identifier corresponding to the instance, aggregated data of the back-end calling data is obtained based on the application identifier, the service identifier, the cluster identifier and the probe identifier corresponding to the instance through a data processing server, and a hierarchical application topology is obtained based on the back-end calling data and the aggregated data through an analysis system, so that the application topology can be simplified, the checking information can be conveniently positioned stage by stage, a user can check the calling relation among the instances in a hierarchical manner and the performance data called by the instances, the user searching time is saved, and the checking efficiency is improved, and calling evaluation index data can be recorded at the position where the probe calls the corresponding class method at the back end, so that a user can check the calling evaluation index data through the application topology, and the user can know more about calling conditions among the instances in the application.
drawings
Fig. 1 is a flowchart of a hierarchical application topology generation method according to an embodiment of the present invention;
FIG. 2 is a flow chart of a data determination method according to an embodiment of the present invention;
fig. 3 is a flowchart of a hierarchical application topology generation method according to an embodiment of the present invention;
Fig. 4a is a block diagram of a hierarchical application topology generation system according to an embodiment of the present invention;
fig. 4b is a block diagram of a hierarchical application topology generation system according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram of a cluster according to an embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be further noted that, for the convenience of description, only some of the structures related to the present invention are shown in the drawings, not all of the structures.
fig. 1 is a flowchart of a hierarchical application topology generation method provided in an embodiment of the present invention, where the method is performed by a hierarchical application topology generation system, and the system may be applied in a cluster. As shown in fig. 1, the method provided by the embodiment of the present invention includes:
S110: when an instance in the application is called, recording back-end calling data at a position where a corresponding class method is called at the back end through a probe configured by the instance; the back-end calling data comprise calling relation data, calling evaluation index data, application identifiers, service identifiers, cluster identifiers and probe identifiers corresponding to the instances; the application is a service system or a functional module of the service system.
in the embodiment of the present invention, the service system may be a system that processes various services. In an implementation manner of the embodiment of the present invention, optionally, when an instance in an application is called, before recording back-end call data at a place where a back-end calls a corresponding class method by using a probe configured by the instance, the method may further include: and configuring a probe for each instance in the application, so that each instance invokes a corresponding class method at a back end when running, and configuring an application identifier, a service identifier, a cluster identifier and a probe identifier for each instance. The back-end call may be a call between instances, a call of a database, a call of nosql, or a call of rpc, and the like, and requires a client of the business system to access a service provided by a remote host through a network.
in the embodiment of the present invention, when configuring the application identifier, the service identifier, the cluster identifier, and the probe identifier for each instance, if the application identifiers of each instance are the same in the same application, and the instances are operated in the same cluster, the identifiers of the clusters may also be the same, and if each instance belongs to the same service, the service identifiers may be the same, for example, if a login service in a business system may operate multiple instances, the service identifiers of the multiple instances are the same. For example, if 4 instances need to be configured in an application, the configuration information of instance 1 may be: application 1, service 1, cluster 1 and probe 1; the configuration information for instance 2 may be application 1, service 1, cluster 2, and probe 2; the configuration information for instance 3 may be application 1, service 2, cluster 3, and probe 3. The configuration information for instance 4 may be application 1, service 2, cluster 4, and probe 4. It can be seen that examples 1-4 have the same application identification; instance 1 and instance 2 have the same service identification and instance 3 and instance 4 have the same service identification. Thus, by configuring application identification, service identification, cluster identification, and probe identification for each instance, calls that occur during instance runtime can be ranked, thereby generating a ranked application topology.
When the instance runs, the probe configured by the instance can automatically bury the point at the position where the back end calls the corresponding class method, namely, the probe configured by the instance is used for monitoring at the position where the back end calls the corresponding class method. A class method may be a method that can be called directly without declaring an object (instance), and may generally have a return value that is used to return some instances specific to the class. In one implementation of the embodiment of the present invention, the error information of instance invocation may be determined by probe monitoring exception information, class method return value information, or invoked response information of the instance configuration. Optionally, when a class method is called once, it may be determined to be a back-end call. The time consumed to invoke a class method can be taken as the response time for a back-end call.
in the embodiment of the present invention, optionally, the back-end call data includes call relation data, call evaluation index data, and an application identifier, a service identifier, a cluster identifier, and a probe identifier corresponding to an instance. Optionally, the call relation data may include an IP address of the caller, an IP address of the callee, a monitoring port of the caller, a monitoring port of the callee, a call mode, and the like. The calling evaluation index data can comprise calling response time, calling times, error information and the like; the calling relation data comprises calling relation data among services, calling relation data among clusters, relation data among probes and the like.
s120: and reporting the back-end calling data to a data processing server through the probe, obtaining aggregated data of the back-end calling data through the data processing server based on the application identifier, the service identifier and the cluster identifier corresponding to the instance, and storing the aggregated data and the back-end calling data to a database.
In the embodiment of the present invention, the database may be a local database or a cloud database, and the type of the database is not limited.
in an implementation manner of the embodiment of the present invention, optionally, obtaining, by the data processing server, aggregated data of the post-call data based on the application identifier, the service identifier, and the cluster identifier corresponding to the instance may include: and aggregating the call evaluation index data with the same application identifier, the same cluster identifier and the same service identifier through the data processing server to obtain aggregated data. Specifically, the evaluation index data is called among services corresponding to instances with the same application identifier through the data processing server for aggregation, so that aggregated data of each application is obtained; aggregating the call evaluation index data among the clusters corresponding to the instances with the same service identification through the data processing server to obtain aggregated data of each service; and aggregating the call evaluation index data among the probes corresponding to the instances with the same cluster identification through the data processing server to obtain the aggregated data of each cluster. The calling evaluation index data comprises calling times, response time and error information.
by way of example; if the application identifier, the service identifier, the cluster identifier and the probe identifier corresponding to the example 1 are respectively the application 1, the service 1, the cluster 1 and the probe 1;
The application identifier, the service identifier, the cluster identifier and the probe identifier corresponding to the example 2 are respectively the application 1, the service 1, the cluster 2 and the probe 2;
The application identifier, the service identifier, the cluster identifier and the probe identifier corresponding to example 3 are respectively: application 1, service 2, cluster 3, and probe 3;
the application identifier, service identifier, cluster identifier and probe identifier corresponding to example 4 are application 1, service 2, cluster 3 and probe 4, respectively.
It can be seen that instances 1-4 have the same application identification, instances 1 and 2 have the same service identification, and instances 3 and 4 have the same service identification. The evaluation index data may be aggregated for calls between services corresponding to examples 1-4. For example, the number of calls, the number of call errors, and the like between services corresponding to instance 1, instance 2, instance 3, and instance 4 may be added to obtain the aggregated data of application 1. Since the example 1 and the example 2 have the same service identifier, the call evaluation index data between the clusters corresponding to the example 1 and the example 2 can be aggregated to obtain the aggregated data of the service 1. The instances 3 and 4 also have the same service identifier, and the call evaluation index data between the clusters corresponding to the instances 3 and 4 can be aggregated to obtain the aggregated data of the service 2.
s130: and accessing the database through a service analysis system, inquiring the back-end calling data and the aggregation data, and generating a hierarchical application topology based on the back-end calling data and the aggregation data.
In the embodiment of the present invention, optionally, the analysis system and the service system may be independent systems, or may be integrated into one system.
in an implementation manner of the embodiment of the present invention, optionally, the generating the hierarchical application topology based on the back-end invocation data and the aggregation data may include: generating a calling evaluation index display page in the application based on the aggregation data of the services corresponding to the instances with the same application identification; generating an application display page based on the aggregation data of the applications corresponding to the instances with the same application identification; generating a service topology based on call relation data between services corresponding to instances with the same application identification and aggregated data of each service; generating a cluster topology based on call relation data between clusters corresponding to instances with the same service identification and aggregated data of each cluster; and generating probe topology based on the calling relationship data among the probes with the same cluster identification and the calling evaluation index data of the probes.
The application topology, the service topology, the cluster topology and the probe topology form a hierarchical application topology, the hierarchical application topology can be checked through an analysis system, the service topology can be checked under each application, the cluster topology can be checked under each service, the probe topology can be checked under each cluster, and the calling evaluation index data of the probe can be checked under each probe. Therefore, by generating the hierarchical application topology, the application topology can be simplified, the checking information can be conveniently positioned step by step, a user can check the calling relation among the instances and the performance data called by the instances in a hierarchical manner, the user searching time is saved, and the checking efficiency is improved.
On the basis of the above embodiment, the technical solution provided by the embodiment of the present invention may further include: displaying the calling evaluation index data in each application according to the application identification through an analysis system; when the operation of triggering the target application is detected through an analysis system, displaying the service topology in the target application; when an operation of triggering a target service is detected in the service topology through an analysis system, showing a cluster topology in the target service; when receiving an operation of triggering a target cluster in the cluster topology through an analysis system, displaying the probe topology in the target cluster; and when receiving an operation of triggering a target probe in the probe topology through an analysis system, displaying calling evaluation index data in the target probe. The analysis system can display the hierarchical topology through the Web component, and can display the calling evaluation index data of all applications according to application names. In the application data, if the topological relation under a certain application needs to be viewed, the corresponding application can be clicked, and the corresponding service topology is skipped to be viewed. In the service topology, if the topological relation under a certain service is to be viewed, the corresponding service can be clicked, and the corresponding cluster topology is skipped to view. In the cluster topology, if the topological relation under a certain cluster needs to be viewed, the corresponding cluster can be clicked, and the corresponding probe topology is skipped to view. In the probe topology, if the data of a certain probe is to be viewed, the corresponding probe can be clicked, and the corresponding probe data is skipped to be viewed.
Therefore, the application topology can be simplified by displaying the application topology in a grading way, the checking information can be conveniently positioned step by step, the user can check the calling relation among the instances in a grading way and the performance data called by the instances, the user searching time is saved, and the checking efficiency is improved.
according to the technical scheme provided by the embodiment of the invention, when an instance in application is called, the back-end calling data is recorded at the position of a back-end calling corresponding class method by configuring a probe in the instance, wherein the back-end calling data comprises calling relation data, calling evaluation index data, an application identifier, a service identifier, a cluster identifier and a probe identifier corresponding to the instance, aggregated data of the back-end calling data is obtained based on the application identifier, the service identifier, the cluster identifier and the probe identifier corresponding to the instance through a data processing server, and a hierarchical application topology is obtained based on the back-end calling data and the aggregated data through an analysis system, so that the application topology can be simplified, the checking information can be conveniently positioned stage by stage, a user can check the calling relation among the instances in a hierarchical manner and the performance data called by the instances, the user searching time is saved, and the checking efficiency is improved, and calling evaluation index data can be recorded at the position where the probe calls the corresponding class method at the back end, so that a user can check the calling evaluation index data through the application topology, and the user can know more about calling conditions among the instances in the application.
Fig. 2 is a flowchart of a data determination method according to an embodiment of the present invention, where the method may be executed by a business system, and the business system may be deployed in a cluster. The service system of the embodiment of the invention is suitable for the condition that the service system and the analysis system are mutually independent. As shown in fig. 2, the technical solution provided by the embodiment of the present invention includes:
s210: when an instance in the application is called, recording back-end calling data at a position where a corresponding class method is called at the back end through a probe configured by the instance; the back-end calling data comprise calling relation data, calling evaluation index data, application identifiers, service identifiers, cluster identifiers and probe identifiers corresponding to the instances; the application is a service system or a functional module of the service system.
s220: and reporting the back-end calling data to a data processing server through the probe, obtaining aggregated data of the back-end calling data through the data processing server based on the application identifier, the service identifier and the cluster identifier corresponding to the instance, and storing the aggregated data and the back-end calling data to a database.
the descriptions of S210 and S220 can be referred to in the above embodiments as descriptions of S110 and S120.
According to the technical scheme provided by the embodiment of the invention, when an instance in application is called, the back-end calling data is recorded at the position of a back-end calling corresponding class method by configuring a probe in the instance, wherein the back-end calling data comprises calling relation data, calling evaluation index data, an application identifier, a service identifier, a cluster identifier and a probe identifier corresponding to the instance, and aggregated data of the back-end calling data is obtained based on the application identifier, the service identifier, the cluster identifier and the probe identifier corresponding to the instance through a data processing server, so that a hierarchical application topology is obtained through an analysis system based on the back-end calling data and the aggregated data, the application topology is simplified, the checking information is conveniently positioned stage by stage, a user can check the calling relation among the instances in a hierarchical manner and the performance data called by the instances, the user searching time is saved, the checking efficiency is improved, and calling evaluation index data can be recorded at the position where the probe calls the corresponding class method at the back end, so that a user can check the calling evaluation index data through the application topology, and the user can know more about the instance calling condition in the application.
fig. 3 is a flowchart of a hierarchical application topology generation method according to an embodiment of the present invention, where the method may be executed by an analysis system, and the analysis system may be deployed in a cluster. The analysis system of the embodiment of the invention is suitable for the situation that the analysis system is mutually independent from the service system of the embodiment.
S310: querying back-end call data and aggregated data in a database; the back-end calling data comprise calling relation data, calling evaluation index data, application identifiers, service identifiers, cluster identifiers and probe identifiers corresponding to the instances; the application is a service system or a functional module of the service system; and obtaining the aggregated data of the post-call data based on the application identifier, the service identifier and the cluster identifier corresponding to the instance.
S320: generating a hierarchical application topology based on the back-end invocation data and the aggregated data.
The descriptions of S310 and S320 may refer to the descriptions of the above embodiments, and the descriptions of the backend call data and the aggregated data may refer to the descriptions of the above embodiments.
According to the technical scheme provided by the embodiment of the invention, the hierarchical application topology is generated by calling data and aggregated data at the back end, the application topology can be simplified, the checking information can be conveniently positioned stage by stage, a user can check the calling relation among the examples and the performance data called by the examples in a hierarchical manner, the user searching time is saved, the checking efficiency is improved, and the user can check more calling information so as to know the calling condition in detail.
Fig. 4a is a block diagram of a hierarchical application topology generation system according to an embodiment of the present invention, and as shown in fig. 4a, the hierarchical application topology generation system includes: a business system 410, a probe 420, a data processing server 430, and an analysis system 440.
the service system 410 is used for recording back-end calling data at a back-end calling corresponding class method through a probe configured by an instance when the instance in the application is called, and reporting the back-end calling data to the data processing server through the probe;
The back-end calling data comprise calling relation data, calling evaluation index data, application identifiers, service identifiers, cluster identifiers and probe identifiers corresponding to the instances; the application is a service system or a functional module of the service system;
The data processing server 420 is configured to obtain aggregated data of post-call data based on the application identifier, the service identifier, and the cluster identifier corresponding to the instance, and store the aggregated data and the post-call data in the database 450;
and the service analysis system 430 is configured to access the database, query the back-end call data and the aggregated data, and generate a hierarchical application topology based on the back-end call data and the aggregated data.
optionally, the invoking evaluation index data includes: number of calls, response time, and error information.
Optionally, the data processing service, 430, is configured to:
Calling evaluation index data among services corresponding to the instances with the same application identification for aggregation to obtain aggregated data of each application;
aggregating the call evaluation index data among clusters corresponding to the instances with the same service identification to obtain aggregated data of each service;
and aggregating the calling evaluation index data among the probes corresponding to the instances with the same cluster identification to obtain the aggregated data of each cluster.
optionally, the analysis system 440 is configured to:
generating a calling evaluation index display page in the application based on the aggregated data of each application corresponding to the instances with the same application identification;
Generating a service topology based on call relation data between services corresponding to instances with the same application identification and aggregated data of each service;
generating a cluster topology based on call relation data between clusters corresponding to instances with the same service identification and aggregated data of each cluster;
And generating probe topology based on the calling relationship data among the probes with the same cluster identification and the calling evaluation index data of the probes.
optionally, the analysis system 440 is further configured to:
displaying the calling evaluation index data in each application according to the application identification;
when the operation of triggering a target application is detected, showing the service topology in the target application;
when an operation of triggering a target service is detected in the service topology, showing a cluster topology in the target service;
When receiving an operation of triggering a target cluster in the cluster topology, displaying the probe topology in the target cluster;
and when receiving an operation of triggering a target probe in the probe topology, displaying calling evaluation index data in the target probe.
wherein, the frame diagram of the hierarchical application topology generation system can refer to fig. 4 b.
Fig. 5 is a structural block diagram of a cluster according to an embodiment of the present invention, and as shown in fig. 5, the cluster 2 includes the application topology system 1 according to the above embodiment of the present invention.
it is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.
Claims (10)
1. a hierarchical application topology generation method is characterized by comprising the following steps:
When an instance in the application is called, recording back-end calling data at a position where a corresponding class method is called at the back end through a probe configured by the instance;
the back-end calling data comprise calling relation data, calling evaluation index data, application identifiers, service identifiers, cluster identifiers and probe identifiers corresponding to the instances; the application is a service system or a functional module of the service system;
Reporting the back-end calling data to a data processing server through the probe, obtaining aggregated data of the back-end calling data through the data processing server based on the application identifier, the service identifier and the cluster identifier corresponding to the instance, and storing the aggregated data and the back-end calling data to a database;
And accessing the database through a service analysis system, inquiring the back-end calling data and the aggregation data, and generating a hierarchical application topology based on the back-end calling data and the aggregation data.
2. The method of claim 1, further comprising:
and configuring a probe at each instance so that each instance can call a corresponding class method at a back end during operation, and configuring an application identifier, a service identifier, a cluster identifier and a probe identifier at each instance.
3. the method of claim 1, wherein said invoking evaluation metric data comprises: number of calls, response time, and error information.
4. The method of claim 1,
The obtaining, by the data processing server, aggregated data of post-call data based on the application identifier, the service identifier, and the cluster identifier corresponding to the service instance includes:
Calling evaluation index data among services corresponding to the instances with the same application identification through the data processing server for aggregation to obtain aggregated data of each application;
Aggregating the call evaluation index data among the clusters corresponding to the instances with the same service identification through the data processing server to obtain aggregated data of each service;
And aggregating the call evaluation index data among the probes corresponding to the instances with the same cluster identification through the data processing server to obtain the aggregated data of each cluster.
5. The method of claim 4, wherein generating a hierarchical application topology based on the back-end invocation data and the aggregated data comprises:
Generating a calling evaluation index display page in the application based on the aggregated data of each application corresponding to the instances with the same application identification;
generating a service topology based on call relation data between services corresponding to instances with the same application identification and aggregated data of each service;
generating a cluster topology based on call relation data between clusters corresponding to instances with the same service identification and aggregated data of each cluster;
And generating probe topology based on the calling relationship data between the probes corresponding to the instances with the same cluster identification and the calling evaluation index data of the probes.
6. the method of claim 1, further comprising:
displaying the calling evaluation index data in each application according to the application identification through an analysis system;
When the operation of triggering the target application is detected through an analysis system, displaying the service topology in the target application;
when an operation of triggering a target service is detected in the service topology through an analysis system, showing a cluster topology in the target service;
when receiving an operation of triggering a target cluster in the cluster topology through an analysis system, displaying the probe topology in the target cluster;
And when receiving an operation of triggering a target probe in the probe topology through an analysis system, displaying calling evaluation index data in the target probe.
7. A method for determining data, comprising:
when an instance in the application is called, recording back-end calling data at a position where a corresponding class method is called at the back end through a probe configured by the instance;
The back-end calling data comprise calling relation data, calling evaluation index data, application identifiers, service identifiers, cluster identifiers and probe identifiers corresponding to the instances; the application is a service system or a functional module of the service system;
and reporting the back-end calling data to a data processing server through the probe, obtaining aggregated data of the back-end calling data through the data processing server based on the application identifier, the service identifier and the cluster identifier corresponding to the instance, and storing the aggregated data and the back-end calling data to a database.
8. A hierarchical application topology generation method is characterized by comprising the following steps:
querying back-end call data and aggregated data in a database;
The back-end calling data comprise calling relation data, calling evaluation index data, application identifiers, service identifiers, cluster identifiers and probe identifiers corresponding to the instances; the application is a service system or a functional module of the service system; acquiring aggregated data of post-call data based on application identifiers, service identifiers and cluster identifiers corresponding to the instances;
generating a hierarchical application topology based on the back-end invocation data and the aggregated data.
9. A hierarchical application topology generation system, comprising: the system comprises a business system, a probe, a data processing server and an analysis system;
The service system is used for recording back-end calling data at a back-end calling corresponding class method through a probe configured by an instance when the instance in the application is called, and reporting the back-end calling data to the data processing server through the probe;
The back-end calling data comprise calling relation data, calling evaluation index data, application identifiers, service identifiers, cluster identifiers and probe identifiers corresponding to the instances; the application is a service system or a functional module of the service system;
The data processing server is used for obtaining aggregated data of post-calling data based on the application identifier, the service identifier and the cluster identifier corresponding to the instance, and storing the aggregated data and the post-calling data to a database;
and the service analysis system is used for accessing the database, inquiring the back-end calling data and the aggregation data, and generating a hierarchical application topology based on the back-end calling data and the aggregation data.
10. a cluster comprising the hierarchical application topology generation system of claim 9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910837343.6A CN110543401B (en) | 2019-09-05 | 2019-09-05 | Hierarchical application topology generation method, hierarchical application topology generation system and hierarchical application topology cluster |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910837343.6A CN110543401B (en) | 2019-09-05 | 2019-09-05 | Hierarchical application topology generation method, hierarchical application topology generation system and hierarchical application topology cluster |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110543401A true CN110543401A (en) | 2019-12-06 |
| CN110543401B CN110543401B (en) | 2023-08-01 |
Family
ID=68712666
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910837343.6A Active CN110543401B (en) | 2019-09-05 | 2019-09-05 | Hierarchical application topology generation method, hierarchical application topology generation system and hierarchical application topology cluster |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110543401B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111880989A (en) * | 2020-07-14 | 2020-11-03 | 中国银联股份有限公司 | Configuration item management method and device |
| CN113746763A (en) * | 2020-05-29 | 2021-12-03 | 华为技术有限公司 | Data processing method, device and equipment |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107104832A (en) * | 2017-04-20 | 2017-08-29 | 上海欣诺通信技术有限公司 | The automatic method and apparatus for finding cross-node service topology on transoceanic multiplex section looped network |
| US20170272326A1 (en) * | 2016-03-21 | 2017-09-21 | Futurewei Technologies, Inc. | Determining service group based network topologies |
| CN108234168A (en) * | 2016-12-15 | 2018-06-29 | 腾讯科技（深圳）有限公司 | A kind of method for exhibiting data and system based on service topology |
| CN108509566A (en) * | 2018-03-26 | 2018-09-07 | 国家电网公司客户服务中心 | One kind is based on 95598 data publication service operation system network topology method for visualizing on cloud |
-
2019
- 2019-09-05 CN CN201910837343.6A patent/CN110543401B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20170272326A1 (en) * | 2016-03-21 | 2017-09-21 | Futurewei Technologies, Inc. | Determining service group based network topologies |
| CN108234168A (en) * | 2016-12-15 | 2018-06-29 | 腾讯科技（深圳）有限公司 | A kind of method for exhibiting data and system based on service topology |
| CN107104832A (en) * | 2017-04-20 | 2017-08-29 | 上海欣诺通信技术有限公司 | The automatic method and apparatus for finding cross-node service topology on transoceanic multiplex section looped network |
| CN108509566A (en) * | 2018-03-26 | 2018-09-07 | 国家电网公司客户服务中心 | One kind is based on 95598 data publication service operation system network topology method for visualizing on cloud |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113746763A (en) * | 2020-05-29 | 2021-12-03 | 华为技术有限公司 | Data processing method, device and equipment |
| CN113746763B (en) * | 2020-05-29 | 2022-11-11 | 华为技术有限公司 | Data processing method, device and equipment |
| CN111880989A (en) * | 2020-07-14 | 2020-11-03 | 中国银联股份有限公司 | Configuration item management method and device |
| CN111880989B (en) * | 2020-07-14 | 2024-05-17 | 中国银联股份有限公司 | Configuration item management method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110543401B (en) | 2023-08-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112910945B (en) | Request link tracking method and service request processing method | |
| US7979245B1 (en) | Model-based systems and methods for monitoring computing resource performance | |
| US8286036B2 (en) | Objective assessment of application crashes from a customer environment | |
| US8285800B2 (en) | Service model creation using monitored data of the performance management tool | |
| US8041683B1 (en) | Methods and apparatus for locating network logs | |
| WO2020173080A1 (en) | Method and apparatus for querying call chain information | |
| US11689536B1 (en) | Server-based restricted access storage | |
| CN110515750B (en) | Application topology generation method, system and cluster | |
| CN114745295B (en) | Data acquisition method, device, equipment and readable storage medium | |
| CN111562889B (en) | Data processing method, device, system and storage medium | |
| CN114490268A (en) | Full link monitoring method, device, equipment, storage medium and program product | |
| US7783743B1 (en) | Methods and apparatus for processing electronic mail-related data | |
| CN110543401B (en) | Hierarchical application topology generation method, hierarchical application topology generation system and hierarchical application topology cluster | |
| CN113596078B (en) | Service problem positioning method and device | |
| US20230044850A1 (en) | Tracing and exposing data used for generating analytics | |
| CN111708611B (en) | Lightweight Kubernetes monitoring system and method | |
| CN111984849A (en) | Information query method, device, equipment and medium | |
| CN116708266A (en) | Cloud service topological graph real-time updating method, device, equipment and medium | |
| US7500144B2 (en) | Resolving problems in a business process utilizing a situational representation of component status | |
| CN114201314B (en) | Contract-based routing method for realizing service dependency discovery and service access | |
| CN112104480B (en) | Method and system for improving alarm quality | |
| US11403157B1 (en) | Identifying a root cause of an error | |
| CN109587223B (en) | Data aggregation method, device and system | |
| CN115918116A (en) | Information processing method, device and storage medium | |
| CN111913789A (en) | Program tracking method, device and medium supporting micro-service architecture |
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 |