CN110515750B - Application topology generation method, system and cluster - Google Patents
Application topology generation method, system and cluster Download PDFInfo
- Publication number
- CN110515750B CN110515750B CN201910837331.3A CN201910837331A CN110515750B CN 110515750 B CN110515750 B CN 110515750B CN 201910837331 A CN201910837331 A CN 201910837331A CN 110515750 B CN110515750 B CN 110515750B
- Authority
- CN
- China
- Prior art keywords
- data
- end call
- service
- call
- application
- 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
- 238000000034 method Methods 0.000 title claims abstract description 82
- 239000000523 sample Substances 0.000 claims abstract description 52
- 238000011156 evaluation Methods 0.000 claims abstract description 45
- 238000012545 processing Methods 0.000 claims abstract description 31
- 238000012544 monitoring process Methods 0.000 claims description 5
- 238000010586 diagram Methods 0.000 description 8
- 241001178520 Stomatepia mongo Species 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000008707 rearrangement Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/547—Remote procedure calls [RPC]; Web services
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0639—Performance analysis of employees; Performance analysis of enterprise or organisation operations
- G06Q10/06393—Score-carding, benchmarking or key performance indicator [KPI] analysis
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Development Economics (AREA)
- Strategic Management (AREA)
- Databases & Information Systems (AREA)
- Educational Administration (AREA)
- Economics (AREA)
- Entrepreneurship & Innovation (AREA)
- Game Theory and Decision Science (AREA)
- Data Mining & Analysis (AREA)
- Marketing (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- General Business, Economics & Management (AREA)
- Debugging And Monitoring (AREA)
Abstract
The embodiment of the invention discloses an application topology generation method, an application topology generation system and a cluster, wherein the method comprises the following steps: when the service in the application is called, recording back-end call data at a class method corresponding to the back-end call through a probe of service configuration; the back-end call data comprise call relation data among services and call evaluation index data of the services; the application is a service system or a functional module of the service system; reporting the back-end call data to the data processing server through the probe so that the data processing server stores the back-end call data to the database; and querying back-end call data by the analysis system, and generating an application topology based on the back-end call data. According to the technical scheme provided by the embodiment of the invention, for a new service system, the code of the service system is not required to be changed, the service system is transparent and non-invasive, and the user can check the call evaluation index data of the service through the application topology, so that the user can know the call condition of the service more.
Description
Technical Field
The embodiment of the invention relates to the technical field of computers, in particular to an application topology generation method, an application topology generation system and an application topology generation cluster.
Background
The application topology reflects the call relationships between multiple services within an application (which may be a system or a functional module of a system). The application topology represents the circulation of the service flow among a plurality of nodes, including the execution process of representing the service from end to end, not only the call relation between end to end, but also the call evaluation index data.
With the development of internet big data technology, distributed application is more and more complex, and it takes a great deal of effort to use the traditional method to comb out the complete application topology, when new nodes are added, the topology needs to be combed again, in addition, the application topology combed out by the traditional method only shows the end-to-end calling relationship in service, and can not show the evaluation index data of the calling, so that the user can not know the calling condition between services well.
Disclosure of Invention
The embodiment of the invention provides an application topology generation method, an application topology generation system and an application topology generation cluster, which can be used for a new service system with added nodes without changing codes of the service system, is transparent to the service and is non-invasive, so that a user can check call evaluation index data of a service through the application topology, and the user can know the call condition of the service more.
In a first aspect, an embodiment of the present invention provides an application topology generating method, including:
when the service in the application is called, recording back-end call data at a class method corresponding to the back-end call through a probe of service configuration;
the back-end call data comprise call relation data among services and call evaluation index data of the services; the application is a service system or a functional module of the service system;
reporting the back-end call data to a data processing server through the probe so that the data processing server stores the back-end call data to a database;
and accessing the database through an analysis system, inquiring the back-end call data, and generating an application topology based on the back-end call data.
In a second aspect, an embodiment of the present invention further provides a method for determining back-end call data, including:
when the service in the application is called, recording back-end call data at a class method corresponding to the back-end call through a probe of service configuration;
the back-end call data comprise call relation data among services and call evaluation index data of the services; the application is a service system or a functional module of the service system;
and reporting the back-end call data to a data processing server through the probe so that the data processing server stores the back-end call data to a database.
In a third aspect, an embodiment of the present invention provides an application topology generating method, including:
querying back-end call data in a database; the back-end call data comprise call relation data among services in the application and call evaluation index data of the services; the application is a service system or a functional module of the service system;
and generating an application topology based on the back-end call data.
In a fourth aspect, an embodiment of the present invention provides an application topology generating 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 call data at a class method corresponding to back-end call through a probe of service configuration when service in an application is called, and reporting the back-end call data to the data processing server through the probe;
the back-end call data comprise call relation data among services and call evaluation index data of the services; the application is a service system or a functional module of the service system;
the data processing server is used for storing the back-end call data into a database;
the analysis system is used for accessing the database, inquiring the back-end call data and generating application topology based on the back-end call data.
In a fifth aspect, an embodiment of the present invention provides a cluster, where the cluster includes an application topology generating system provided by the embodiment of the present invention.
According to the technical scheme provided by the embodiment of the invention, when the service in the application is called, the probe configured in the service is used for recording the back-end call data at the class method corresponding to the back-end call, wherein the back-end call data comprises call data between the services and call evaluation index data, and an analysis system is used for generating an application topology based on the back-end call data; for a new service system with added nodes, the back-end call data can be recorded only by configuring probes for each service, the codes of the service system are not required to be changed, the service is transparent and non-invasive, and call evaluation index data can be recorded at the class method corresponding to the back-end call through the probes, so that a user can check the call evaluation index data of the service through application topology, and the user can know the call condition among the services in the application.
Drawings
FIG. 1a is a flowchart of an application topology generation method according to an embodiment of the present invention;
FIG. 1b is a schematic diagram of an application topology according to an embodiment of the present invention;
FIG. 2 is a flowchart of a method for determining back-end call data according to an embodiment of the present invention;
FIG. 3 is a flowchart of an application topology generation method provided in an embodiment of the present invention;
FIG. 4a is a block diagram of an application topology generation system according to an embodiment of the present invention;
FIG. 4b is a block diagram of an application topology generation system provided by an embodiment of the present invention;
fig. 5 is a block diagram of a cluster according to an embodiment of the present invention.
Detailed Description
The invention is described in further detail below with reference to the drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting thereof. It should be further noted that, for convenience of description, only some, but not all of the structures related to the present invention are shown in the drawings.
Fig. 1a is a flowchart of an application topology generation method according to an embodiment of the present invention, where the method may be performed by an application topology generation system, and the system may be applied to a cluster. As shown in fig. 1a, the method provided by the embodiment of the invention includes:
s110: when the service in the application is called, recording back-end call data at a class method corresponding to back-end call through a probe of service configuration, wherein the back-end call data comprises call relation data among the services and call evaluation index data of the services; the application is a service system or a functional module of the service system.
In the embodiment of the invention, the service system can be a system for processing various services. In one implementation manner of the embodiment of the present invention, optionally, when a service in an application is invoked, before the record of the back-end invocation data at the back-end invocation corresponding class method, the probe configured by the service may further include: each service in the application configures probes so that each service runs with a point buried at the back-end calling the corresponding class method. The back-end call may include a call between services, a call of a database, a call of nosql, or a rpc call, etc., and a client of the service system needs to access a service provided by a remote host through a network.
When the service runs, the probes of the service configuration can be automatically buried at the positions of the class methods corresponding to the back-end calls, namely, the probes of the service configuration are monitored at the positions of the class methods corresponding to the back-end calls. A class method can be all methods of a class, including directly callable methods and instantiating callable methods, and can generally have a return value, which acts to return some specific instances of the class. In one implementation of the embodiment of the invention, the error information of the service call can be determined by monitoring the exception information, the class method return value information or the called response information by the probe of the service configuration. Alternatively, when a class method is called, it may be determined as a back-end call. The time consuming invocation of the class method may be referred to as the response time of a back-end invocation.
In the embodiment of the invention, optionally, the back-end call data includes call relationship data between services and call evaluation index data of the services. Optionally, the call relationship data between the services may include an IP address of the caller, an IP address of the callee, a listening port of the caller, a listening port of the callee, a calling manner, and the like. The call evaluation index data may include response time of call, number of calls, error information, and the like.
S120: and reporting the back-end call data to a data processing server through the probe so that the data processing server stores the back-end call data to a database.
In the embodiment of the invention, the probe reports the back-end call data to the data processing server, and the data processing server stores the back-end call data in the database. The database may be a local database or a cloud database, and the type of the database is not limited.
S130: and accessing the database through an analysis system, inquiring the back-end call data, and generating an application topology based on the back-end call data.
In the embodiment of the invention, the analysis system and the service system can be independent systems or integrated in one system.
In one implementation manner of the embodiment of the present invention, optionally, accessing the database through an analysis system, querying the back-end call data includes: and acquiring keywords input by a user through an analysis system, and inquiring back-end call data matched with the keywords in the database. The keyword may be an application identifier, for example, when a user needs to view an application topology of an application, the application identifier may be input through an analysis system, back-end call data of a service matching the application identifier may be queried, and the application topology may be generated based on the back-end call data. In one implementation manner of the embodiment of the present invention, optionally, the generating an application topology based on the back-end call data includes: and generating an application topology based on the back-end call data through a Web component. Thus, through the application topology, the user can view the calling relation among the services, performance data of service calling and the like so as to know the service processing condition.
On the basis of the above embodiment, the technical solution provided by the embodiment of the present invention may further include: and displaying the application topology, wherein the call evaluation index data is displayed between a calling party and a called party. When the application topology is displayed, the call evaluation index data can be displayed between the call method and the called party, so that a user can clearly view the called evaluation index. The application topology can also display the calling relation between the services and the identification of the calling party and the called party.
In the embodiment of the invention, the method for generating the application topology is illustrated by calling the services in the application, and taking the calling relation of 3 services in the back-end call as an example:
service 1 invokes service 2 and service 3;
service 2 invokes mysql and redis;
service 3 calls mysql and mongo;
the back-end call data recorded by the probe may be as shown in table 1. As shown in table 1, the response times, and error times when the service 1 calls the service 2 and the service 3 are recorded in the back-end call data, the response times, and error times when the service 2 calls mysql and redis, and the response times, and error times when the service 3 calls mysql and mongo, and information such as the ip of the calling party, the ip of the called party, and the call mode when the service calls are recorded.
TABLE 1
FIG. 1b is an application topology diagram of the web component in the analytics system generated based on the back-end call data recorded in Table 1, as shown in FIG. 1b, between the call evaluation index data display and the caller and callee, which may be convenient for a clear view of the service call situation.
According to the technical scheme provided by the embodiment of the invention, when the service in the application is called, the probe configured in the service is used for recording the back-end call data at the class method corresponding to the back-end call, wherein the back-end call data comprises call data between the services and call evaluation index data, and an analysis system is used for generating an application topology based on the back-end call data; for a new service system with added nodes, the back-end call data can be recorded only by configuring probes for each service, the codes of the service system are not required to be changed, the service is transparent and non-invasive, and call evaluation index data can be recorded at the class method corresponding to the back-end call through the probes, so that a user can check the call evaluation index data of the service through application topology, and the user can know the call condition among the services in the application.
Fig. 2 is a flowchart of a method for determining back-end call data according to an embodiment of the present invention, where the method may be performed by a service system, and the service system may be deployed in a cluster. The business system of the embodiment of the invention is suitable for the situation that the business 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 the service in the application is called, recording back-end call data at a class method corresponding to back-end call through a probe of service configuration, wherein the back-end call data comprises call relation data among the services and call evaluation index data of the services; the application is a service system or a functional module of the service system.
In the embodiment of the invention, the service system can be a system for processing various services. In one implementation manner of the embodiment of the present invention, optionally, when a service in an application is invoked, before the record of the back-end invocation data at the back-end invocation corresponding class method, the probe configured by the service may further include: each service in the application configures probes so that each service runs with a point buried at the back-end calling the corresponding class method. The back-end call may include a call between services, a call of a database, a call of nosql, or a rpc call, etc., and a client of the service system needs to access a service provided by a remote host through a network.
When the service runs, the probes of the service configuration can be buried at the positions of the class methods corresponding to the back-end calls, namely, the probes of the service configuration can be used for monitoring at the positions of the class methods corresponding to the back-end calls. Where a class method may be a method that can be invoked directly without declaring an object (instance), it may typically have a return value that acts to return some instances specific to that class. In one implementation of the embodiment of the invention, the error information of the service call can be determined by monitoring the exception information, the class method return value information or the called response information by the probe of the service configuration. Alternatively, when a class method is called, it may be determined as a back-end call. The time consuming invocation of the class method may be referred to as the response time of a back-end invocation.
In the embodiment of the invention, optionally, the back-end call data includes call relationship data between services and call evaluation index data of the services. Optionally, the call relationship data between the services may include an IP address of the caller, an IP address of the callee, a listening port of the caller, a listening port of the callee, a calling manner, and the like. The call evaluation index data may include response time of call, number of calls, error information, and the like.
S220: and reporting the back-end call data to a data processing server through the probe so that the data processing server stores the back-end call data to a database.
In the embodiment of the invention, the probe reports the back-end call data to the data processing server, and the data processing server stores the back-end call data in the database. The database may be a local database or a cloud database, and the type of the database is not limited.
According to the technical scheme provided by the embodiment of the invention, when the service in the application is called, the probe in the service is configured to record the back-end call data at the class method corresponding to the back-end call, wherein the back-end call data comprises call data and call evaluation index data between the services, for a new business system with a node added, the back-end call data can be recorded only by configuring the probe for each service without changing codes of the business system, the business is transparent and non-invasive, and the call evaluation index data can be recorded at the class method corresponding to the back-end call through the probe, so that a user can check the call evaluation index data of the service through application topology, and the call condition between the services in the application is more known.
Fig. 3 is a flowchart of an application topology generation method provided by an embodiment of the present invention, which may be performed by an analysis system, which 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 with the business system of the embodiment.
As shown in fig. 3, the technical solution provided by the embodiment of the present invention includes:
s310: and querying back-end call data in the database, wherein the back-end call data comprises call relation data among services in the application and call evaluation index data of the services.
In one implementation manner of the embodiment of the present invention, optionally, querying the back-end call data in the data may include: and acquiring keywords input by a user through an analysis system, and inquiring back-end call data matched with the keywords in a database. The keyword may be an application identifier, for example, when a user needs to view an application topology of an application, the application identifier may be input through an analysis system, back-end call data of a service matching the application identifier may be queried, and the application topology may be generated based on the back-end call data.
S320: and generating an application topology based on the back-end call data.
In one implementation manner of the embodiment of the present invention, optionally, the generating an application topology based on the back-end call data includes: and generating an application topology based on the back-end call data through a Web component. Thus, through the application topology, the user can view the calling relation among the services, performance data of service calling and the like so as to know the service processing condition.
On the basis of the above embodiment, the technical solution provided by the embodiment of the present invention may further include: and displaying the application topology, and displaying the call evaluation index data between the calling party and the called party. When the application topology is displayed, the call evaluation index data can be displayed between the calling party and the called party, so that a user can clearly view the called evaluation index. The application topology can also display the calling relation between the services and the identification of the calling party and the called party.
According to the technical scheme provided by the embodiment of the invention, the analysis system generates the application topology based on the call relation data among the services and the call evaluation index data, so that a user can view more service call information, and the user can know the service call condition in detail.
Fig. 4a is a block diagram of an application topology generating system according to an embodiment of the present invention, as shown in fig. 4a, including: business system 410, probe 420, data processing server 430, and analysis system 440.
The service system 410 is configured to record back-end call data at a class method corresponding to back-end call by the probe 420 when a service in an application is called, and report the back-end call data to a data processing server by the probe 420, where the back-end call data includes call relationship data between services and call evaluation index data of the service; the application is a service system or a functional module of the service system;
a data processing server 430 for storing the back-end call data in a database 450;
and the analysis system 440 is configured to access the database, query the back-end call data, and generate an application topology based on the back-end call data.
Optionally, the service system 410 is configured to configure probes for each service in the application, so that each service runs while calling a corresponding class method at the back end to embed a point.
Optionally, the call evaluation index data includes call times, response time and error information.
And monitoring abnormal information, class method return value information or called response information through a probe of service configuration to determine error information of service call.
Optionally, the analysis system 440 is further configured to expose the application topology, and the call evaluation index data is exposed between the caller and the callee.
Optionally, the analysis system 440 is configured to obtain a keyword input by a user, and query the database for back-end call data matching the keyword.
Wherein a framework diagram of the application topology generation system can be referred to fig. 4b.
Fig. 5 is a block diagram of a cluster according to an embodiment of the present invention, and as shown in fig. 5, the cluster 2 includes an application topology generating system 1 according to the foregoing embodiment of the present invention.
Note that the above is only a preferred embodiment of the present invention and the technical principle applied. 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, while the invention has been described in connection with the above embodiments, the invention is not limited to the embodiments, but may be embodied in many other equivalent forms without departing from the spirit or scope of the invention, which is set forth in the following claims.
Claims (7)
1. An application topology generation method, comprising:
when the service in the application is called, recording back-end call data at a class method corresponding to the back-end call through a probe of service configuration;
the back-end call data comprise call relation data among services and call evaluation index data of the services; the application is a service system or a functional module of the service system;
reporting the back-end call data to a data processing server through the probe so that the data processing server stores the back-end call data to a database;
acquiring keywords input by a user through an analysis system, inquiring back-end call data matched with the keywords in the database, and generating an application topology based on the back-end call data through a Web component;
displaying the application topology, wherein the call evaluation index data is displayed between a calling party and a called party; the application topology is also used for showing the calling relation between services and the identification of a calling party and a called party;
the method further comprises the steps of:
and configuring probes for each service in the application, so that each service is buried at a class method position corresponding to the back-end call when running, wherein when the class method is called once, the back-end call is determined once, and the time consumption for calling the class method is taken as the response time of the back-end call once.
2. The method of claim 1, wherein the call evaluation index data includes call times, response times, and error information.
3. The method of claim 2, wherein the probe monitoring through the service configuration determines error information for service invocation, such as exception information, class method return value information, or invoked response information.
4. A method for determining back-end call data, comprising:
when the service in the application is called, recording back-end call data at a class method corresponding to the back-end call through a probe of service configuration;
the back-end call data comprise call relation data among services and call evaluation index data of the services; the application is a service system or a functional module of the service system;
reporting the back-end call data to a data processing server through the probe so that the data processing server stores the back-end call data to a database;
acquiring keywords input by a user through an analysis system, inquiring back-end call data matched with the keywords in the database, and generating an application topology based on the back-end call data through a Web component;
displaying the application topology, wherein the call evaluation index data is displayed between a calling party and a called party; the application topology is also used for showing the calling relation between services and the identification of a calling party and a called party;
the method further comprises the steps of:
and configuring probes for each service in the application, so that each service is buried at a class method position corresponding to the back-end call when running, wherein when the class method is called once, the back-end call is determined once, and the time consumption for calling the class method is taken as the response time of the back-end call once.
5. An application topology generation method, comprising:
querying back-end call data in a database; the back-end call data comprise call relation data among services in the application and call evaluation index data of the services; the application is a service system or a functional module of the service system;
acquiring keywords input by a user through an analysis system, inquiring back-end call data matched with the keywords in the database, and generating an application topology based on the back-end call data through a Web component; displaying the application topology, wherein the call evaluation index data is displayed between a calling party and a called party; the application topology is also used for showing the calling relation between services and the identification of a calling party and a called party;
the method further comprises the steps of:
and configuring probes for each service in the application, so that each service is buried at a class method position corresponding to the back-end call when running, wherein when the class method is called once, the back-end call is determined once, and the time consumption for calling the class method is taken as the response time of the back-end call once.
6. An 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 call data at a class method corresponding to back-end call through a probe of service configuration when service in an application is called, and reporting the back-end call data to the data processing server through the probe;
the back-end call data comprise call relation data among services and call evaluation index data of the services; the application is a service system or a functional module of the service system;
the data processing server is used for storing the back-end call data into a database;
the analysis system is used for acquiring keywords input by a user, inquiring back-end call data matched with the keywords in the database, and generating an application topology based on the back-end call data through a Web component; displaying the application topology, wherein the call evaluation index data is displayed between a calling party and a called party; the application topology is also used for showing the calling relation between services and the identification of a calling party and a called party;
the service system is further configured with probes for each service in the application, so that each service is buried in a class method corresponding to the back-end call when running, wherein when the class method is called once, the back-end call is determined once, and the time consumption for calling the class method is taken as the response time of the back-end call once.
7. A cluster comprising the application topology generation system of claim 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910837331.3A CN110515750B (en) | 2019-09-05 | 2019-09-05 | Application topology generation method, system and cluster |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910837331.3A CN110515750B (en) | 2019-09-05 | 2019-09-05 | Application topology generation method, system and cluster |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110515750A CN110515750A (en) | 2019-11-29 |
| CN110515750B true CN110515750B (en) | 2024-03-15 |
Family
ID=68631095
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910837331.3A Active CN110515750B (en) | 2019-09-05 | 2019-09-05 | Application topology generation method, system and cluster |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110515750B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112492021B (en) * | 2020-11-25 | 2023-12-01 | 北京宝兰德软件股份有限公司 | Service calling relation path detection method based on network data |
| CN112527620B (en) * | 2020-12-24 | 2024-08-13 | 北京百度网讯科技有限公司 | Database performance analysis method and device, electronic equipment, medium and product |
| CN112783720B (en) * | 2021-01-05 | 2023-05-19 | 广州品唯软件有限公司 | Topology structure diagram generation method, device, computer equipment and display system |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107766205A (en) * | 2017-10-10 | 2018-03-06 | 武汉大学 | A kind of monitoring system and method towards the tracking of micro services invoked procedure |
| CN109254901A (en) * | 2018-09-30 | 2019-01-22 | 北京九章云极科技有限公司 | A kind of Monitoring Indexes method and system |
| CN109286191A (en) * | 2018-11-22 | 2019-01-29 | 国网江苏省电力有限公司 | The cruising inspection system and method for J2EE power business application system based on ASM |
| CN109802842A (en) * | 2017-11-16 | 2019-05-24 | 华为软件技术有限公司 | The generation method and relevant device of applied topology |
-
2019
- 2019-09-05 CN CN201910837331.3A patent/CN110515750B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107766205A (en) * | 2017-10-10 | 2018-03-06 | 武汉大学 | A kind of monitoring system and method towards the tracking of micro services invoked procedure |
| CN109802842A (en) * | 2017-11-16 | 2019-05-24 | 华为软件技术有限公司 | The generation method and relevant device of applied topology |
| CN109254901A (en) * | 2018-09-30 | 2019-01-22 | 北京九章云极科技有限公司 | A kind of Monitoring Indexes method and system |
| CN109286191A (en) * | 2018-11-22 | 2019-01-29 | 国网江苏省电力有限公司 | The cruising inspection system and method for J2EE power business application system based on ASM |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110515750A (en) | 2019-11-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11736378B1 (en) | Collaborative incident management for networked computing systems | |
| US11366686B1 (en) | Managing user data in a multitenant deployment | |
| US10985970B1 (en) | Automatic actionable event responder for operational clusters | |
| US11232125B1 (en) | Conversion of cloud computing platform data for ingestion by data intake and query system | |
| US11836148B1 (en) | Data source correlation user interface | |
| US11829330B2 (en) | Log data extraction from data chunks of an isolated execution environment | |
| CN110515750B (en) | Application topology generation method, system and cluster | |
| US11145123B1 (en) | Generating extended reality overlays in an industrial environment | |
| US6212676B1 (en) | Event architecture for system management in an operating system | |
| US11755577B1 (en) | Skewing of scheduled search queries | |
| US20190095599A1 (en) | Customizing a user behavior analytics deployment | |
| CN106375458B (en) | Service calling system, method and device | |
| US20190098068A1 (en) | Customizable load balancing in a user behavior analytics deployment | |
| CN108520037A (en) | Data query method, apparatus and data visualisation system | |
| CN114745295B (en) | Data acquisition method, device, equipment and readable storage medium | |
| US12047450B1 (en) | Management of connected sensor devices | |
| CN109871289A (en) | A kind of remote procedure call service creation method and device | |
| CN114490268A (en) | Full link monitoring method, device, equipment, storage medium and program product | |
| US20230044850A1 (en) | Tracing and exposing data used for generating analytics | |
| US11853330B1 (en) | Data structure navigator | |
| CN113792008A (en) | Method and device for acquiring network topology structure, electronic equipment and storage medium | |
| CN110543401B (en) | Hierarchical application topology generation method, hierarchical application topology generation system and hierarchical application topology cluster | |
| CN116820874A (en) | Enterprise-level big data component and method for monitoring and alarming application | |
| US20190182312A1 (en) | System and method for large-scale capture and tracking of web-based application parameters | |
| CN111782428A (en) | Data calling system and method |
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 |