CN109922123B - Display method and display device for call relation between servers - Google Patents
Display method and display device for call relation between servers Download PDFInfo
- Publication number
- CN109922123B CN109922123B CN201811609736.3A CN201811609736A CN109922123B CN 109922123 B CN109922123 B CN 109922123B CN 201811609736 A CN201811609736 A CN 201811609736A CN 109922123 B CN109922123 B CN 109922123B
- Authority
- CN
- China
- Prior art keywords
- server
- tracking information
- information
- identifier
- tracking
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Abstract
The embodiment of the application discloses a display method and a display device of call relations between servers, wherein the display method comprises the following steps: receiving tracking information sent by a server; wherein each tracking information comprises: a request information identifier, a tracking information identifier, and a parent tracking information identifier of the tracking information; determining a first server for processing the first request information based on the corresponding relation between the first request information identification and the first request information; the request information identification comprises a first request information identification; determining a calling relationship between the first servers according to a tracking information identifier in the tracking information sent by each first server and a parent tracking information identifier of the tracking information; and displaying the first request information and the calling relation between the first servers. According to the display method of the call relation between the servers, when the first server processes the first request information, the call relation between the first servers can be known, and the first server is convenient to manage.
Description
Technical Field
The embodiment of the application relates to a display technology, in particular to a display method and a display device for call relations between servers.
Background
At present, with the innovative progress of computer technology and network technology, particularly the continuous development and application of a micro-service architecture, the system development brings the change of covering the ground, and frequent calling among servers brings the difficulty for managing the servers.
Disclosure of Invention
The embodiment of the application provides a display method and a display device for call relations between servers to solve the problems in the prior art.
The technical scheme of the embodiment of the application is realized as follows:
the embodiment of the application provides a method for displaying call relations between servers, which comprises the following steps:
receiving tracking information sent by a server; wherein each tracking information comprises: a request information identifier, a tracking information identifier, and a parent tracking information identifier of the tracking information;
determining a first server for processing the first request information based on the corresponding relation between the first request information identification and the first request information; wherein the request information identification comprises the first request information identification;
determining a calling relationship between the first servers according to a tracking information identifier in the tracking information sent by each first server and a parent tracking information identifier of the tracking information;
and displaying the first request information and the calling relation between the first servers.
The embodiment of the present application further provides a display device for call relations between servers, where the display device includes:
the receiving unit is configured to receive the tracking information sent by the server; wherein each tracking information comprises: a request information identifier, a tracking information identifier, and a parent tracking information identifier of the tracking information;
the processing unit is configured to determine that the receiving unit receives the tracking information sent by the server, and determine a first server for processing the first request information based on the corresponding relation between the first request information identifier and the first request information; wherein the request information identification comprises the first request information identification; determining a calling relationship between the first servers according to a tracking information identifier in the tracking information sent by each first server and a parent tracking information identifier of the tracking information, and exciting a display unit to display the first request information and the calling relationship between the first servers;
the display unit is configured to display the first request information and the call relationship between the first servers.
In the embodiment of the application, tracking information sent by a server is received; wherein each tracking information comprises: a request information identifier, a tracking information identifier, and a parent tracking information identifier of the tracking information; determining a first server for processing the first request information based on the corresponding relation between the first request information identification and the first request information; wherein the request information identification comprises the first request information identification; determining a calling relationship between the first servers according to a tracking information identifier in the tracking information sent by each first server and a parent tracking information identifier of the tracking information; displaying the first request information and the calling relation between the first servers; when the first server processes the first request information, the calling relationship among the first services can be known, and the first server is convenient to manage.
Drawings
FIG. 1 is a flowchart of an embodiment of a method for displaying call relations between servers according to the present application;
FIG. 2 is a flowchart of an embodiment of a method for displaying call relations between servers according to the present application;
FIG. 3 is a diagram of an application scenario of a method for displaying call relationships between servers according to the present application;
FIG. 4 is a diagram of an application scenario of a method for displaying call relationships between servers according to the present application;
FIG. 5 is a diagram of an application scenario of a method for displaying call relations between servers according to the present application;
FIG. 6 is a schematic structural diagram of an embodiment of a device for displaying call relations between servers.
Detailed Description
The present application will be described in further detail with reference to the following drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the relevant invention and not restrictive of the invention. It should be noted that, for convenience of description, only the portions related to the related invention are shown in the drawings.
It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict. The present application will be described in detail below with reference to the embodiments with reference to the attached drawings.
Example one
As shown in fig. 1, an embodiment of the present application describes a method for displaying a call relationship between servers: the method comprises the following steps:
step 101, receiving tracking information sent by a server; wherein each tracking information comprises: a request information identifier, a tracking information identifier, and a parent tracking information identifier of the tracking information.
In the embodiment of the present application, the education system interacts with each server through the network to receive or transmit messages and the like. Here, when the education system receives the request information, the request information is transmitted to the server through the network, and the request information is processed by the server.
Here, the method for displaying the call relationship between the servers may be executed by a device for displaying the call relationship between the servers; when the server processes the request information, the tracking information is sent to the display device of the call relation between the servers through the network, and the display device of the call relation between the servers receives the tracking information sent by the server. The display device of the call relation between the servers can call the monitoring system for the distributed link. For example, as shown in fig. 3, the display device of the call relationship between servers calls the monitoring system for the Zipkin distributed link, and S represents the server that sends the trace information.
It should be understood by those skilled in the art that the server is a generic term, and the server may be a Database (DB), a server, or a memory (Cache).
Here, the network may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.
Here, the implementation manner of causing the server to transmit the trace information when processing the request information is not limited. For example, the presentation device of call relationship between servers may be implemented by establishing a collection element, implanting the collection element in the educational system, collecting the element tracking request information when the educational system sends the request information to the servers, and sending the tracking information to the presentation device of call relationship between servers when the servers process the request information. Here, the education system further transmits the correspondence between the identification of the request information and the request information to the presentation apparatus of the call relationship between the servers.
Each trace information includes: a request information identifier, a tracking information identifier, and a parent tracking information identifier of the tracking information.
The request information identification is used for identifying the request information, the request information identification and the request information have a corresponding relation, and each request information has a unique corresponding request information identification so as to be convenient for identifying the request information.
Here, the request information identifier and the request information may be associated with each other through a table, or may be associated with each other through a key-value pair.
Here, the trace information identifier is used to identify the trace information, there is a correspondence between the trace information identifier and the trace information, and each trace information in one request information has a unique corresponding trace information identifier so as to identify the trace information.
Here, the parent tracking information identifier of the tracking information is used for identifying the parent tracking information of the tracking information, the parent tracking information identifier of the tracking information and the parent tracking information of the tracking information have a corresponding relationship, and the parent tracking information of each tracking information has the parent tracking information identifier of the tracking information uniquely corresponding to the parent tracking information, so as to identify the parent tracking information of the tracking information; thereby determining the parent server of the server.
In some optional implementations, the tracking information further includes: creating a timestamp of the tracking information and a time duration for completing acquisition of the tracking information.
Here, the time stamp is a time stamp when the trace information is created, and is used to record the acquisition time.
Here, the time period for completing the acquisition of the trace information is the time elapsed from the creation of the trace information to the completion of the final acquisition of the trace information.
Step 102, determining a first server for processing the first request information based on the corresponding relation between the first request information identification and the first request information; wherein the request information identification comprises the first request information identification.
In this embodiment of the application, the number of the received request information identifiers may be one, or may be at least two. Here, the first request information identifier is one of the received request information identifiers.
Here, the correspondence between the first request information identifier and the first request information may be stored in a presentation device of the call relationship between the servers. Of course, the acquisition element can be embedded into the education system by establishing the acquisition element, when the education system sends the request information to the server, the acquisition unit tracks the request information, generates the request information identifier corresponding to the request information, and the education system sends the request information identifier corresponding to the request information to the display device of the call relation between the servers.
Here, the first server for processing the first request information is determined based on the corresponding relationship between the first request information identifier and the first request information, and the server containing the first request information identifier in the to-be-sent tracking information is screened out as the first server.
Step 103, determining the calling relationship between the first servers according to the tracking information identifier in the tracking information sent by each first server and the parent tracking information identifier of the tracking information.
In the embodiment of the present application, the parent tracking information of the tracking information may be directly found through the parent tracking information identifier of the tracking information, so as to determine the calling relationship of the calling relationship between the first servers.
Here, when the parent tracking information identifier of the tracking information is empty, the first server is correspondingly a primary server, that is, a root server.
In some optional implementations of the embodiment of the present application, when the trace information sent by each first server only includes: when one of the client tracking information and the server tracking information is selected, determining a call relationship between the first servers according to a tracking information identifier in the tracking information sent by each first server and a parent tracking information identifier of the tracking information comprises:
determining a first server sending the client tracking information as a primary server;
determining a first server sending the tracking information of the server side as a last-stage server;
and determining the calling relationship between the last-stage server and the primary server according to the tracking information identifier in the client tracking information sent by the primary server and the parent tracking information identifier of the tracking information in the server tracking information sent by the last-stage server. Of course, since there are only the primary server and the last server, where the primary server is the parent server of the last server, the call relation can be directly determined.
In some optional implementations of the embodiment of the present application, when part of the trace information sent by the first server includes: when the client side tracks information and the server side tracks information, determining the calling relationship between the first servers according to the tracking information identifier in the tracking information sent by each first server and the parent tracking information identifier of the tracking information comprises the following steps:
determining a first server sending the client tracking information as a primary server;
determining a first server sending the tracking information of the server side as a last-stage server;
determining a first server sending client tracking information and server tracking information as an intermediate server;
determining a calling relationship between the primary server and the intermediate-level server according to a tracking information identifier in the client tracking information sent by the primary server and a parent tracking information identifier in the server tracking information sent by the intermediate-level server;
determining a calling relationship between the intermediate-level servers according to a parent tracking information identifier in the server tracking information and a tracking information identifier in the client tracking information sent by the intermediate-level servers;
and determining the calling relationship between the last-stage server and the middle-stage server according to a parent tracking information identifier in the server tracking information sent by the last-stage server and a tracking information identifier in the client tracking information sent by the middle-stage server.
Here, each of the trace information may further include: annotating; wherein the annotation characterizes a type of the each tracking information; the annotation comprises: a first type of annotation and a second type of annotation; wherein the first type of annotation characterizes the tracking information as client tracking information; and the second annotation represents that the tracking information is the tracking information of the server. Determining the type of the trace information sent by each first server based on the annotation in the trace information sent by each first server; and determining the calling relationship among the first servers according to the type of the tracking information sent by each first server, the tracking information identification in the tracking information sent by each first server and the parent tracking information identification of the tracking information.
In an application scenario, the determination of the call relationship among server 0, server 1, server 2, and server 3 by the above method is shown in fig. 4. As shown in fig. 5, server 0 is the primary server, and annotation c indicates that server 0 sends client tracking information; the server 1 is a middle-level server, and notes c and s indicate that the server 1 sends client tracking information and server tracking information; the server 2 and the server 3 are final servers, and the annotation s indicates that the server 2 and the server 3 transmit server tracking information. Here, span is tracking information.
And 104, displaying the first request information and the calling relationship between the first servers.
The display device for the call relation between the servers can directly display the first request information and the call relation between the first servers through a chart and a graph, can quickly locate a server fault point and know the call condition between the servers in a service.
In some optional implementations of embodiments of the present application, when the tracking information further includes: creating a timestamp of the tracking information and finishing the time for acquiring the tracking information;
the display method can also comprise the following steps: displaying a timestamp of the first server for creating the tracking information and a time length for finishing acquiring the tracking information; so that the time spent by the first server in processing the request information can be known, and the first server with low processing speed can be improved to improve the working efficiency.
In some optional implementation manners of the embodiment of the present application, the display method may further include:
storing the first request information and the call relation between the first servers corresponding to the first request information; therefore, the first server is analyzed to know the calling relationship among the first services.
In the embodiment of the application, tracking information sent by a server is received; wherein each tracking information comprises: a request information identifier, a tracking information identifier, and a parent tracking information identifier of the tracking information; determining a first server for processing the first request information based on the corresponding relation between the first request information identification and the first request information; wherein the request information identification comprises the first request information identification; determining a calling relationship between the first servers according to a tracking information identifier in the tracking information sent by each first server and a parent tracking information identifier of the tracking information; displaying the first request information and the calling relation between the first servers; when the first server processes the first request information, the calling relationship among the first services can be known, and the first server is convenient to manage.
Example two
As shown in fig. 2, an embodiment of the present application further describes a method for displaying a call relationship between servers: the method comprises the following steps:
step 201, receiving tracking information sent by a server; wherein each tracking information comprises: a request information identifier, a tracking information identifier, and a parent tracking information identifier of the tracking information.
Step 202, receiving the corresponding relation between the request information identification and the request information.
Here, the exhibiting apparatus of call relation between servers may implant the collecting element in the education system by establishing the collecting element, collect the element trace request information when the education system transmits the request information to the server, and transmit the trace information to the exhibiting apparatus of call relation between servers when the server processes the request information. Here, the education system also sends the corresponding relation between the request information identification and the request information to the display device of the call relation between the servers; in order to determine the server that processes the requested information.
Step 203, determining a first server for processing the first request information based on the corresponding relationship between the first request information identifier and the first request information; wherein the request information identification comprises the first request information identification.
Here, the first server for processing the first request information is determined based on the corresponding relationship between the first request information identifier and the first request information, and the server containing the first request information identifier in the to-be-sent tracking information is screened out as the first server.
And step 204, determining the calling relationship between the first servers according to the tracking information identifier in the tracking information sent by each first server and the parent tracking information identifier of the tracking information.
And step 205, displaying the first request information and the call relationship between the first servers.
The display device for the call relation between the servers can directly display the first request information and the call relation between the first servers through a chart and a graph, can quickly locate a server fault point and know the call condition between the servers in a service.
In the embodiment of the present application, step 201, step 203, step 204, and step 205 correspond to step 101, step 102, step 103, and step 104 in the first embodiment, and the description related to step 101, step 102, step 103, and step 104 in the first embodiment is also applicable to step 201, step 203, step 204, and step 205 here, and is not described herein again.
Here, the order of step 201 and step 202 is not limited.
EXAMPLE III
As shown in fig. 6, the present application further describes an apparatus for displaying call relations between servers, and the embodiment of the apparatus for displaying call relations between servers corresponds to the above embodiment of the method for displaying call relations between servers shown in fig. 1 and fig. 2, so that the operations and features described in the above embodiment of the method for displaying call relations between servers shown in fig. 1 and fig. 2 are also applicable to the embodiment of the apparatus for displaying call relations between servers, and a detailed description thereof is omitted here.
The display device for the call relation between the servers comprises:
a receiving unit 601 configured to receive tracking information sent by a server; wherein each tracking information comprises: a request information identifier, a tracking information identifier, and a parent tracking information identifier of the tracking information;
a processing unit 603 configured to determine that the receiving unit 601 receives the tracking information sent by the server, and determine a first server for processing the first request information based on a corresponding relationship between the first request information identifier and the first request information; wherein the request information identification comprises the first request information identification; determining a calling relationship between the first servers according to a tracking information identifier in the tracking information sent by each first server and a parent tracking information identifier of the tracking information, and triggering a display unit 602 to display the first request information and the calling relationship between the first servers;
the displaying unit 602 is configured to display the first request information and the call relationship between the first servers.
In some optional implementations of embodiments of the application, each piece of tracking information further includes: annotating; wherein the annotation characterizes a type of the each tracking information; the annotation comprises: a first type of annotation and a second type of annotation; wherein the first type of annotation characterizes the tracking information as client tracking information; the second annotation represents that the tracking information is tracking information of a server;
the processing unit 603 is further configured to determine the type of the trace information sent by each first server based on the annotation in the trace information sent by each first server.
In some optional implementations of the application embodiment, when the trace information sent by each first server only includes: when one of the client tracking information and the server tracking information is used, the processing unit 603 is configured to determine, according to a tracking information identifier in the tracking information sent by each first server and a parent tracking information identifier of the tracking information, a call relationship between the first servers, including:
the processing unit 603 is configured to determine that the first server sending the client tracking information is the primary server; determining a first server sending the tracking information of the server side as a last-stage server; and determining the calling relationship between the last-stage server and the primary server according to the tracking information identifier in the client tracking information sent by the primary server and the parent tracking information identifier of the tracking information in the server tracking information sent by the last-stage server.
In some optional implementations of the embodiment of the application, when the part of the trace information sent by the first server includes: when the client trace information and the server trace information are obtained, the processing unit 603 is configured to determine, according to a trace information identifier in the trace information sent by each first server and a parent trace information identifier of the trace information, a call relationship between the first servers, including:
the processing unit 603 is configured to determine that the first server sending the client tracking information is the primary server; determining a first server sending the tracking information of the server side as a last-stage server; determining a first server sending client tracking information and server tracking information as an intermediate server; determining a calling relationship between the primary server and the intermediate-level server according to a tracking information identifier in the client tracking information sent by the primary server and a parent tracking information identifier in the server tracking information sent by the intermediate-level server; determining a calling relationship between the intermediate-level servers according to a parent tracking information identifier in the server tracking information and a tracking information identifier in the client tracking information sent by the intermediate-level servers; and determining the calling relationship between the last-stage server and the middle-stage server according to a parent tracking information identifier in the server tracking information sent by the last-stage server and a tracking information identifier in the client tracking information sent by the middle-stage server.
In some optional implementations of the embodiments of the application, the tracking information further includes: creating a timestamp of the tracking information and a time length for completing acquisition of the tracking information;
the presentation unit 602 is further configured to present a timestamp of the first server creating the tracking information and a time duration of completing the acquisition of the tracking information;
the processing unit 603 is further configured to trigger the presentation unit 602 to present a timestamp of the creation of the trace information by the first server and a time duration of the completion of the acquisition of the trace information.
Here, the presentation unit 602 can know the time taken by the first server when processing the request information, which facilitates to improve the first server with a slow processing speed to improve the work efficiency.
In some optional implementation manners of the application embodiment, the receiving unit 601 is further configured to receive a correspondence between the request information identifier and the request information.
In some optional implementations of the embodiments of the application, the display and demonstration device further includes:
the storage unit is configured to store the first request information and a call relation between first servers corresponding to the first request information;
the processor is further configured to trigger the storage unit to store the first request information and a call relationship between first servers corresponding to the first request information.
Here, the storage unit stores the first request information and the call relationship between the first servers corresponding to the first request information, so as to analyze the first servers to know the call relationship between the first services.
In the embodiment of the present application, the receiving unit 601 is configured to receive tracking information sent by a server; wherein each tracking information comprises: a request information identifier, a tracking information identifier, and a parent tracking information identifier of the tracking information; a processing unit 603 configured to determine that the receiving unit 601 receives the tracking information sent by the server, and determine a first server for processing the first request information based on a corresponding relationship between the first request information identifier and the first request information; wherein the request information identification comprises the first request information identification; determining a calling relationship between the first servers according to a tracking information identifier in the tracking information sent by each first server and a parent tracking information identifier of the tracking information, and triggering a display unit 602 to display the first request information and the calling relationship between the first servers; the display unit 602 is configured to display the first request information and the call relationship between the first servers; when the first server processes the first request information, the calling relationship among the first services can be known, and the first server is convenient to manage.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (6)
1. A display method for call relations between servers is characterized in that the display method comprises the following steps:
receiving tracking information sent by a server; wherein each tracking information comprises: a request information identifier, a tracking information identifier, and a parent tracking information identifier of the tracking information;
determining a first server for processing the first request information based on the corresponding relation between the first request information identification and the first request information; wherein the request information identification comprises the first request information identification;
determining a calling relationship between the first servers according to a tracking information identifier in the tracking information sent by each first server and a parent tracking information identifier of the tracking information;
displaying the first request information and the calling relation between the first servers;
wherein each piece of tracking information further comprises: annotating; wherein the annotation characterizes a type of the each tracking information; the annotation comprises: a first type of annotation and a second type of annotation; wherein the first type of annotation characterizes the tracking information as client tracking information; the second annotation represents that the tracking information is tracking information of a server;
determining the type of the trace information sent by each first server based on the annotation in the trace information sent by each first server;
when part of the first server sends the trace information, the trace information comprises: when the client side tracks information and the server side tracks information, determining the calling relationship between the first servers according to the tracking information identifier in the tracking information sent by each first server and the parent tracking information identifier of the tracking information comprises the following steps:
determining a first server sending the client tracking information as a primary server;
determining a first server sending the tracking information of the server side as a last-stage server;
determining a first server sending client tracking information and server tracking information as an intermediate server;
determining a calling relationship between the primary server and the intermediate-level server according to a tracking information identifier in the client tracking information sent by the primary server and a parent tracking information identifier in the server tracking information sent by the intermediate-level server;
determining a calling relationship between the intermediate-level servers according to a parent tracking information identifier in the server tracking information and a tracking information identifier in the client tracking information sent by the intermediate-level servers;
and determining the calling relationship between the last-stage server and the middle-stage server according to a parent tracking information identifier in the server tracking information sent by the last-stage server and a tracking information identifier in the client tracking information sent by the middle-stage server.
2. The method of claim 1, wherein the tracking information further comprises: creating a timestamp of the tracking information and a time length for completing acquisition of the tracking information;
the display method further comprises the following steps: and displaying a timestamp of the first server for creating the tracking information and the time length for finishing acquiring the tracking information.
3. The presentation method according to claim 1, wherein before said determining a first server to process the first request information based on the correspondence between the first request information identification and the first request information, the presentation method further comprises:
and receiving the corresponding relation between the request information identification and the request information.
4. The utility model provides a display device of relation of transferring between cloud education server which characterized in that, display device includes:
the receiving unit is configured to receive the tracking information sent by the server; wherein each tracking information comprises: a request information identifier, a tracking information identifier, and a parent tracking information identifier of the tracking information;
the processing unit is configured to determine that the receiving unit receives the tracking information sent by the server, and determine a first server for processing the first request information based on the corresponding relation between the first request information identifier and the first request information; wherein the request information identification comprises the first request information identification; determining a calling relationship between the first servers according to a tracking information identifier in the tracking information sent by each first server and a parent tracking information identifier of the tracking information, and exciting a display unit to display the first request information and the calling relationship between the first servers;
the display unit is configured to display the first request information and the call relationship between the first servers;
wherein each piece of tracking information further comprises: annotating; wherein the annotation characterizes a type of the each tracking information; the annotation comprises: a first type of annotation and a second type of annotation; wherein the first type of annotation characterizes the tracking information as client tracking information; the second annotation represents that the tracking information is tracking information of a server;
the processing unit is further configured to determine the type of the trace information sent by each first server based on the annotation in the trace information sent by each first server;
when part of the first server sends the trace information, the trace information comprises: when the client side trace information and the server side trace information are obtained, the processing unit is configured to determine a call relationship between the first servers according to a trace information identifier in the trace information sent by each first server and a parent trace information identifier of the trace information, and the determination includes:
the processing unit is configured to determine that a first server that sends client tracking information is a primary server; determining a first server sending the tracking information of the server side as a last-stage server; determining a first server sending client tracking information and server tracking information as an intermediate server; determining a calling relationship between the primary server and the intermediate-level server according to a tracking information identifier in the client tracking information sent by the primary server and a parent tracking information identifier in the server tracking information sent by the intermediate-level server; determining a calling relationship between the intermediate-level servers according to a parent tracking information identifier in the server tracking information and a tracking information identifier in the client tracking information sent by the intermediate-level servers; and determining the calling relationship between the last-stage server and the middle-stage server according to a parent tracking information identifier in the server tracking information sent by the last-stage server and a tracking information identifier in the client tracking information sent by the middle-stage server.
5. The display apparatus as claimed in claim 4, wherein the tracking information further comprises: creating a timestamp of the tracking information and a time length for completing acquisition of the tracking information;
the display unit is also configured to display a timestamp for the first server to create the tracking information and a time length for completing acquisition of the tracking information;
the processing unit is further configured to trigger the presentation unit to present a timestamp of the creation of the trace information by the first server and a duration of completion of the acquisition of the trace information.
6. The apparatus according to claim 4, wherein the receiving unit is further configured to receive a corresponding relationship between the request information identifier and the request information.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811609736.3A CN109922123B (en) | 2018-12-27 | 2018-12-27 | Display method and display device for call relation between servers |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811609736.3A CN109922123B (en) | 2018-12-27 | 2018-12-27 | Display method and display device for call relation between servers |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109922123A CN109922123A (en) | 2019-06-21 |
| CN109922123B true CN109922123B (en) | 2022-01-11 |
Family
ID=66960046
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811609736.3A Active CN109922123B (en) | 2018-12-27 | 2018-12-27 | Display method and display device for call relation between servers |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109922123B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112527410A (en) * | 2020-12-17 | 2021-03-19 | 深圳市欢太科技有限公司 | Full link tracking method, device, equipment and storage medium |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102088472A (en) * | 2010-11-12 | 2011-06-08 | 中国传媒大学 | Wide area network-oriented decomposition support method for animation rendering task and implementation method |
| CN103108005A (en) * | 2011-11-11 | 2013-05-15 | 上海聚力传媒技术有限公司 | Method, device and system for achieving data sharing in distributed storage system |
| CN103533006A (en) * | 2012-07-06 | 2014-01-22 | 中兴通讯股份有限公司 | United cloud disk client, server, system and united cloud disk service method |
| CN107483419A (en) * | 2017-07-28 | 2017-12-15 | 深圳市优克联新技术有限公司 | Method, apparatus, system, server and the computer-readable recording medium of server authentication access terminal |
| CN107688520A (en) * | 2017-07-18 | 2018-02-13 | 北京奥鹏远程教育中心有限公司 | distributed service tracking system and method |
| CN108173915A (en) * | 2017-12-21 | 2018-06-15 | 中国联合网络通信集团有限公司 | Call chain processing method and processing device |
| CN108462750A (en) * | 2018-03-22 | 2018-08-28 | 平安好房（上海）电子商务有限公司 | Distribution calls method for tracing, operation system, monitoring system and storage medium |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8473956B2 (en) * | 2008-01-15 | 2013-06-25 | Microsoft Corporation | Priority based scheduling system for server |
| US8392312B2 (en) * | 2008-09-24 | 2013-03-05 | Netapp, Inc. | Adaptive scheduling of storage operations based on utilization of a multiple client and server resources in a distributed network storage system |
| US20140258022A1 (en) * | 2013-03-08 | 2014-09-11 | Kamal Zamer | Inferred Budget |
-
2018
- 2018-12-27 CN CN201811609736.3A patent/CN109922123B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102088472A (en) * | 2010-11-12 | 2011-06-08 | 中国传媒大学 | Wide area network-oriented decomposition support method for animation rendering task and implementation method |
| CN103108005A (en) * | 2011-11-11 | 2013-05-15 | 上海聚力传媒技术有限公司 | Method, device and system for achieving data sharing in distributed storage system |
| CN103533006A (en) * | 2012-07-06 | 2014-01-22 | 中兴通讯股份有限公司 | United cloud disk client, server, system and united cloud disk service method |
| CN107688520A (en) * | 2017-07-18 | 2018-02-13 | 北京奥鹏远程教育中心有限公司 | distributed service tracking system and method |
| CN107483419A (en) * | 2017-07-28 | 2017-12-15 | 深圳市优克联新技术有限公司 | Method, apparatus, system, server and the computer-readable recording medium of server authentication access terminal |
| CN108173915A (en) * | 2017-12-21 | 2018-06-15 | 中国联合网络通信集团有限公司 | Call chain processing method and processing device |
| CN108462750A (en) * | 2018-03-22 | 2018-08-28 | 平安好房（上海）电子商务有限公司 | Distribution calls method for tracing, operation system, monitoring system and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109922123A (en) | 2019-06-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104301203B (en) | A kind of information push method and equipment | |
| CN106815254B (en) | Data processing method and device | |
| CN110275992B (en) | Emergency processing method, device, server and computer readable storage medium | |
| CN109656797B (en) | Log data association method and device | |
| CN109753432A (en) | A kind of interface performance test method, apparatus, server and system | |
| CN113242159A (en) | Application access relation determining method and device | |
| CN109922123B (en) | Display method and display device for call relation between servers | |
| CN112398797B (en) | Data transmission method, receiving device, transmitting device, medium, equipment and system | |
| CN109409948B (en) | Transaction abnormity detection method, device, equipment and computer readable storage medium | |
| CN105467907A (en) | Automatic inspection system and method | |
| CN104298671B (en) | data statistical analysis method and device | |
| CN113067802B (en) | User identification method, device, equipment and computer readable storage medium | |
| CN110737655B (en) | Method and device for reporting data | |
| CN110007940B (en) | Gray scale release verification method, system, server and readable storage medium | |
| CN109086185B (en) | Fault detection method, device and equipment of storage cluster and storage medium | |
| CN110070379B (en) | Message transmission method, device and server | |
| CN107566216B (en) | Monitoring method, device and service system | |
| CN113079070B (en) | Method and device for monitoring response performance of domain name system | |
| CN112435063A (en) | Resource processing method and device, electronic equipment and storage medium | |
| CN111159988B (en) | Model processing method, device, computer equipment and storage medium | |
| CN110825466B (en) | Program jamming processing method and jamming processing device | |
| CN112231185A (en) | Knowledge acquisition method and device based on alarm information of application system | |
| CN110633182B (en) | System, method and device for monitoring server stability | |
| CN207802396U (en) | End-to-end signaling analysis platform based on client perception | |
| CN110837454A (en) | Interface monitoring processing method and server |
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 |