CN111917844A - Distributed service tracking method and device - Google Patents
Distributed service tracking method and device Download PDFInfo
- Publication number
- CN111917844A CN111917844A CN202010694164.4A CN202010694164A CN111917844A CN 111917844 A CN111917844 A CN 111917844A CN 202010694164 A CN202010694164 A CN 202010694164A CN 111917844 A CN111917844 A CN 111917844A
- Authority
- CN
- China
- Prior art keywords
- service
- tracking
- configuration information
- sidecar
- information
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 48
- 230000006854 communication Effects 0.000 claims abstract description 66
- 238000004891 communication Methods 0.000 claims abstract description 45
- 230000004044 response Effects 0.000 claims description 12
- 238000011144 upstream manufacturing Methods 0.000 claims description 10
- 238000010586 diagram Methods 0.000 description 6
- 238000011161 development Methods 0.000 description 5
- 230000006870 function Effects 0.000 description 5
- 241000529895 Stercorarius Species 0.000 description 4
- 239000012141 concentrate Substances 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 3
- 238000012545 processing Methods 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 230000006978 adaptation Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000001364 causal effect Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 230000008447 perception Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The disclosure provides a method and a device for tracking distributed services, relates to the technical field of network communication, and can realize distributed service tracking based on a Sidecar mode. The method for tracking the distributed service provided by the embodiment of the disclosure comprises the following steps: the method comprises the steps that a Sidecar network agent obtains service tracking configuration information of corresponding application services, and a tracking task is established according to the service tracking configuration information; and the Sidecar network agent receives the communication process message of the application service and reports the tracking information of the communication process message to a service tracking system server according to the created tracking task.
Description
Technical Field
The present disclosure relates to the field of network communication technologies, and in particular, to a method and an apparatus for distributed service tracking.
Background
In a distributed service architecture, the distributed service needs to be managed, and a call chain of each request is recorded; the time at which each service is called on the call chain; topological relationships between individual services, etc., this behavior is referred to as "distributed service tracking.
With the development of cloud native technology, a Service Mesh (Service Mesh) architecture is already a TCP protocol in the microservice era and becomes a key link for the native landing of the cloud of an enterprise. The Service Mesh is used as a network infrastructure layer, and communication among applications in the Service Mesh can pass through a Sidecar (Sidecar) network proxy so as to realize the functions of light-weight network proxy, no perception of application programs, retry/timeout of decoupling application programs, monitoring, tracking, Service discovery and the like; this mode is also referred to as the Sidecar mode. However, the Service Mesh based on the Sidecar mode provides a method in the related art for performing Service tracking on the managed application.
Disclosure of Invention
The embodiment of the disclosure provides a method and a device for distributed Service tracking, which can solve the problem of Service Mesh Service tracking based on a Sidecar mode. The technical scheme is as follows:
according to a first aspect of embodiments of the present disclosure, there is provided a method for distributed service tracking, the method including: the method comprises the steps that a Sidecar network agent obtains service tracking configuration information of corresponding application services, and a tracking task is established according to the service tracking configuration information; and the Sidecar network agent receives the communication process message of the application service and reports the tracking information of the communication process message to a service tracking system server according to the created tracking task. The distributed service tracking mode realizes the distributed service tracking of the application service only through the Sidecar network agent; the flexibility is strong.
In some embodiments, the step of obtaining the service tracking configuration information of the corresponding application service by the Sidecar network agent may include: and receiving Service tracking configuration information sent by a Service grid Mesh control plane, or receiving Service tracking configuration information input by a user.
In some implementations, the service tracking configuration information may include at least one of: the system comprises information of a distributed tracking system, communication protocol information, a network traffic transparent interception rule, upstream and downstream service addresses of Sidecar connection and a network traffic forwarding rule.
In some embodiments, creating a tracking task may include embedding a service tracking call record.
In some embodiments, the communication process messages of the application service may include request messages and response messages.
In some embodiments, the tracking information of the communication process message includes one or more of: service name, request method, request path, request parameters, response time, request status.
By the distributed service tracking method provided by the embodiment, the distributed tracking of the application service realized by various development languages can be realized by relying on the calling chain tracking of the Sidecar mode communication protocol layer. In some embodiments, the application is imperceptible, that is, the application itself may not invoke chain tracing, and developers need not pay much attention to application distributed tracing and concentrate on program development, thereby providing more creativity for developers. In some embodiments, heterogeneous programming language applications may be supported, and pluggable extension capabilities may be provided, i.e., distributed tracking system engines within the Sidecar based on different extensions to the enterprise distributed tracking system.
According to a second aspect of the embodiments of the present disclosure, there is provided an apparatus for distributed service tracking, including: the device comprises an acquisition module, a creation module, a communication module and a reporting module; the acquisition module is used for acquiring service tracking configuration information of the corresponding application service; the creating module is used for creating a tracking task according to the service tracking configuration information; the communication module is used for receiving a communication process message of the application service; and the reporting module is used for reporting the tracking information of the communication process message to a service tracking system server according to the created tracking task.
In some embodiments, the obtaining module obtains the service tracking configuration information of the corresponding application service, and may include: and receiving Service tracking configuration information sent by a Service grid Mesh control plane, or receiving Service tracking configuration information input by a user.
In some embodiments, the service tracking configuration information comprises at least one of: the system comprises information of a distributed tracking system, communication protocol information, a network traffic transparent interception rule, upstream and downstream service addresses of Sidecar connection and a network traffic forwarding rule.
In some embodiments, creating the tracking task includes embedding a service tracking call record.
In some embodiments, the communication process messages of the application service may include request messages and response messages; the trace information of the communication process message includes one or more of the following: service name, request method, request path, request parameters, response time, request status.
Through the distributed service tracking method or device provided by the embodiment, the distributed service tracking of various distributed tracking system engines can be realized by relying on the call chain tracking of the Sidecar mode communication protocol layer, is irrelevant to development languages, is completely transparent when used up correspondingly, and supports various network communication protocols. The developer does not need to pay much attention to the distributed tracking of the application program and concentrates on the program development, so that the developer is more creative. In some embodiments, a pluggable extension capability may also be provided, i.e., a distributed tracking system engine that is internal to the Sidecar, depending on the different extensions of the enterprise distributed tracking system.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and together with the description, serve to explain the principles of the disclosure.
Fig. 1 is a schematic diagram of Service Mesh-based Sidecar mode distributed Service tracing provided by an embodiment of the present disclosure;
FIG. 2 is a flow chart of a distributed service tracking method provided by an embodiment of the present disclosure;
fig. 3 is a schematic flow chart illustrating the processing of an application service communication message at the Sidecar according to the embodiment of the present disclosure;
fig. 4 is a schematic diagram of a sdecar creating service tracking embedded point and reporting tracking information according to the embodiment of the present disclosure;
fig. 5 is a structural diagram of a distributed service tracking apparatus according to an embodiment of the present disclosure.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the exemplary embodiments below are not intended to represent all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.
The tracking unit of the service tracking is a process from the time when a Request (Request) initiated by a client arrives at the boundary of a tracked system to the time when the tracked system returns a Response (Response) to the client, and is called tracking (Trace). Each Trace calls a plurality of services, and in order to record which services are called and information such as time consumption of each call, a call record is embedded every time a service is called, which is called a "Span". Briefly, the Trace represents a track of primary data or an execution path in a system, and can be simply regarded as a directed acyclic graph with multiple spans, the spans represent a primary logic operation running unit in the system, the spans are nested or sequentially arranged to establish a logic causal relationship, and the multiple spans form a primary Trace record. Where SpanContext represents the state of crossing a process boundary and passing to a lower Span. In some embodiments, SpanContext may contain information such as < Trace _ id, Span _ id, sampled > tuple, etc. In the process that the system provides services to the outside, requests and responses occur continuously, Trace is generated continuously, and the Trace with Span is recorded, so that a service topological graph of the system can be drawn. By adding information such as response time in the span, success or failure of the request and the like, abnormal service can be found when problems occur; according to historical data, the system can analyze the overall level to find out the performance difference and locate the target of performance optimization.
In the Service Mesh architecture based on the Sidecar mode, the Service Mesh is responsible for reliably passing requests, such as the isio, in a complex Service topology of application services. The Service Mesh comprises a control plane and a data plane, wherein the control plane is responsible for realizing Service registration and Service discovery and sending network flow, safety control and communication encryption configuration files among services to the data plane. A data plane, i.e., Sidecar (also called a Sidecar container or a Sidecar network agent), which can be implemented together with application code without awareness of the application itself; the functions of network flow control, load balancing, security policy control and the like can be realized through the configuration issued by the control plane. In some embodiments, the Sidecar is started in a separate process, and each host may share the same Sidecar process or each application may have a Sidecar process exclusive. All the service control functions are taken over by the Sidecar, the communication between the services needs to pass through the Sidecar network proxy, and the external access of the application only needs to access the Sidecar.
Distributed tracing in the practice of the present disclosure may be implemented based on the Sidecar model. Fig. 1 is a schematic diagram of Service Mesh based Sidecar mode distributed Service tracing. As shown in fig. 1, the Service Mesh100 includes a server 101 and a server 102, wherein an application Service (also referred to as Service) a and a Sidecar103 are deployed in the server 101, and a ServiceB and a Sidecar104 are deployed in the server 102. Functions such as network communication requests of ServiceA are managed by the Sidecar103, and functions such as network communication requests of ServiceB are managed by the Sidecar 104. The control plane of Service Mesh100 is used to manage and configure the Sidecar103 and Sidecar104 to enforce policies and collect telemetry. The distributed service tracking system server 105 is configured to receive tracking information reported by the Sidecar103 and the Sidecar 104. In some embodiments, the distributed service tracking system may be a Jaeger system, a SkyWalking system, a Zipkin system, etc., and the communication information used may be of various types, such as HTTP/1.x protocol, HTTP/2.0 protocol, Dubbo protocol, RPC protocol, etc. In some embodiments, there may be more servers in the Service Mesh to deploy multiple different services and sidecars, not limited to the number shown in fig. 1.
In some embodiments, Service may be deployed in a container environment, or may be deployed in a non-container link, such as a physical machine, a virtual machine, or the like. In some embodiments, the Sidecar may also be deployed separately. The required configuration file can be modified in a manual configuration mode without depending on a Service Mesh control surface to send the configuration file. Network traffic for all services is managed entirely by the Sidecar network proxy.
In some embodiments, the Sidecar may include a distributed tracking system engine. The distributed tracking system engine can be implemented by writing functional code and can be in a plug-in form. The distributed tracking system engine can realize the reporting of the call chain tracking data of various existing distributed tracking systems (such as a Jaeger system, a Skywalk system, a Zipkin system and the like), is suitable for the existing distributed tracking technology system of an enterprise, and has flexible expansion capability.
In some embodiments, the Sidecar may include a communication protocol engine. The communication protocol engine can be realized by writing functional codes and can identify a plurality of communication protocols (such as HTTP/1.x protocol, HTTP/2.0 protocol, Dubbo protocol, RPC protocol and the like). The communication protocol engine adds calling chain tracking embedded point information in the coding and decoding process by identifying the protocol adopted by mutual calling between application services, completes the calling chain information acquisition process and further realizes the distributed service tracking of the communication protocol level.
Fig. 2 is a flowchart of a distributed service tracking method provided by an embodiment of the present disclosure. As shown in fig. 2, the method comprises the steps of:
201: the method comprises the steps that a Sidecar network agent obtains service tracking configuration information of corresponding application services;
202: the Sidecar network agent creates a tracking task according to the service tracking configuration information;
203: the Sidecar network agent receives a communication process message of the application service;
204: and the Sidecar network agent reports the tracking information of the communication process message to the service tracking system server according to the created tracking task.
In some embodiments, the Service tracing configuration information obtained by the Sidecar may be Service tracing configuration information received from a Service Mesh control plane; or may be service tracking configuration information that receives user input. That is, the Service tracking configuration information may issue the configuration file to the Sidecar configuration directory through the Service Mesh control plane, or the user may directly write the configuration file manually and copy the configuration file to the Sidecar configuration directory. In some embodiments, the service tracking configuration information may also be preset or default. In some embodiments, the configuration file may be in a YAML file format, which primarily exposes service tracking and communication protocol related configurations, such as the following code:
in some embodiments, the Sidecar acquisition service tracking configuration information may include information for a distributed tracking system, such as a Jaeger system, a SkyWalking system, a Zipkin system, etc.; in some embodiments, the Sidecar acquisition service tracking configuration information may also include inter-service network communication protocol information, such as HTTP/1.x protocol, HTTP/2.0 protocol, Dubbo protocol, RPC protocol, and the like.
In some embodiments, the service tracking configuration information may also include network traffic transparent interception rules, upstream and downstream service addresses of the Sidecar connection, and other traffic forwarding rules, among others.
In some embodiments, the sdecar creates the service trace task according to the service trace configuration information, and may create a service trace Span, detect whether a service trace context (spncontext) is included in the data frame before creating the Span, extract (extract) the service trace information into the current Span if the service trace context (spncontext) is included in the data frame, or directly create the Span, and Inject (Inject) the current Span information into the data frame to transfer the service trace information. After the data frame is processed, the data frame is forwarded to other upstream applications through the route, and the data frame is encoded into byte codes and forwarded according to the network communication protocol of the upstream applications.
In some embodiments, the communication process information in step 202 may include a request message or may be a response message.
In some embodiments, the tracking information in step 203 may include one or more of: service name, request method, request path, request parameters, response time, request status. Wherein, the request method can be GET (GET), transfer (POST), PUT (PUT), DELETE (DELETE), etc.; the request path may be the URL of the request; the request parameters can be configured according to the needs; the request status may be success or failure.
By the distributed service tracking method provided by the embodiment, the distributed tracking of the application service realized by various development languages can be realized by relying on the calling chain tracking of the Sidecar mode communication protocol layer. In some embodiments, the application is imperceptible, that is, the application itself may not invoke chain tracing, and developers need not pay much attention to application distributed tracing and concentrate on program development, thereby providing more creativity for developers. In some embodiments, heterogeneous programming language applications may be supported, and pluggable extension capabilities may be provided, i.e., distributed tracking system engines within the Sidecar based on different extensions to the enterprise distributed tracking system.
In some embodiments, in conjunction with fig. 1 and 2, the distributed tracking system information is a SkyWalking system and the communication protocol information may be an HTTP protocol. The Sidecar creates the tracing information of the communication process message according to the service tracing configuration information and reports the tracing information to the service tracing system server, and the method can be realized by the following modes: when the server 101 sends a request of ServiceA to the server 102, the Sidecar103 of ServiceA first receives the request, the Sidecar103 parses the request byte stream into an HTTP data structure object, a distributed trace system engine inside the Sidecar adds trace information according to service trace configuration information in a configuration file in a skywalk system trace manner, and reports the trace information to a back-end skywalk system server before the request is forwarded to the Sidecar104 of ServiceB deployed by the server 102, such as 127.0.0.1:11800 addresses in the configuration. After receiving the request, the Sidecar104 of the ServiceB also parses the request byte stream into an HTTP data structure object, adds the trace information, and reports to the skywalk back end, so that the entire service trace process is completed. The user can realize distributed call chain tracking without changing the original application code.
Through the distributed service tracking method provided by the embodiment, based on the Sidecar mode, complex systems of various RPC frames, micro-services, cloud computing, big data and the like and call chain information collection of applications spanning multiple modules/services/containers can be realized, service call topological graphs, call times, total application request duration, duration spent by each component and the like among applications are known, and meanwhile, by combining embedded point information of the application service, the purpose of positioning application performance bottleneck in real time/quasi-real time and optimizing performance is realized.
Fig. 3 is a flow diagram of application service communication message processing at the Sidecar. As shown in fig. 3, the network traffic of the application service ServiceA is managed by the Sidecar301, the Sidecar301 receives the request message from the application service ServiceA, when the byte stream of the request message enters the Sidecar301, the Sidecar301 reads the byte stream at the network communication layer, sends the read byte stream to the network communication protocol engine for decoding operation, and the decoded data is created and encapsulated into a structured data frame object according to different communication protocols, for example, an HTTP request protocol, and is decoded into a data structure object conforming to the HTTP protocol, including a request line, a request header, and request data. The service trace information is reported to the distributed trace system server 303 before the data frame is routed to the Sidecar301 of the application service ServiceA.
Fig. 4 is a schematic diagram of the sdue creating service tracking embedded point and reporting tracking information. The distributed tracking system engine 402 in the Sidecar401 determines the backend distributed tracking system based on the service tracking configuration information. The distributed tracking system may be a Jaeger system, a SkyWalking system, a Zipkin system, etc., among others. The figure only illustrates the SkyWalking system as an example. As shown, the communication protocol engine 403 in the Sidecar determines the communication protocol, such as HTTP/1.x protocol, used for inter-invoking between application services according to the service tracking configuration information. After determining the distributed Trace system and the communication protocol used, the Sidecar can embed a call record, also called a "Span," according to the create service Trace. In some embodiments, as shown in fig. 4, before creating Span, it is necessary to detect whether a service trace context (Span context) is included in the data frame, if so, extract the service trace information to the current Span, otherwise, create Span directly, and then Inject (Inject) the current Span information into the (Inject) data frame, and pass the service trace information on. After the data frame is processed, the data frame is forwarded to other upstream applications through the route, and the data frame is encoded into byte codes and forwarded according to the network communication protocol of the upstream applications. And adding calling chain tracking embedded point information in the encoding and decoding process to complete the calling chain information acquisition process, thereby realizing the distributed service tracking of the communication protocol level.
The embodiment of the present disclosure provides a distributed service tracking apparatus, as shown in fig. 5, the data transmission apparatus 500 includes: an acquisition module 501, a creation module 502, a communication module 503 and a reporting module 504. The obtaining module 501 is configured to obtain service tracking configuration information of a corresponding application service; the creating module 502 is configured to create a tracking task according to the service tracking configuration information; the communication module 503 is configured to receive a communication process message of the application service; the reporting module 504 is configured to report the tracking information of the communication process message to the service tracking system server according to the created tracking task.
In some embodiments, the obtaining module 501 obtains the service tracking configuration information of the corresponding application service, including: and receiving Service tracking configuration information sent by a Service grid Mesh control plane, or receiving Service tracking configuration information input by a user.
In some embodiments, the service tracking configuration information may include at least one of: the system comprises information of a distributed tracking system, communication protocol information, a network traffic transparent interception rule, upstream and downstream service addresses of Sidecar connection and a network traffic forwarding rule.
In some embodiments, creating the tracking task includes creating a service tracking Span.
Through the distributed service tracking device provided by the embodiment, the distributed service tracking device can be tracked by depending on the calling chain of the Sidecar mode communication protocol layer, is independent of development language, is completely transparent when used up correspondingly, supports various network communication protocols, and supports the distributed service tracking of various distributed tracking system engines. The developer does not need to pay much attention to the distributed tracking of the application program and concentrates on the program development, so that the developer is more creative. In some embodiments, a pluggable extension capability may also be provided, i.e., a distributed tracking system engine that is internal to the Sidecar, depending on the different extensions of the enterprise distributed tracking system.
Based on the distributed service tracking method described in the embodiments of the present disclosure, a computer-readable storage medium is also provided in the embodiments of the present disclosure, for example, the non-transitory computer-readable storage medium may be a Read Only Memory (ROM), a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like. The storage medium stores computer instructions for executing the distributed service tracking method described in the embodiments of the present disclosure, and details thereof are not described herein.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It will be understood that the present disclosure is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
Claims (10)
1. A method of distributed service tracking, the method comprising: the method comprises the steps that a Sidecar Sidecar network agent obtains service tracking configuration information corresponding to application services, and a tracking task is established according to the service tracking configuration information; and the Sidecar network agent receives the communication process message of the application service and reports the tracking information of the communication process message to a service tracking system server according to the created tracking task.
2. The method of claim 1, wherein the Sidecar network agent obtains service tracking configuration information of the corresponding application service, comprising: and receiving the Service tracking configuration information sent by a Service grid Mesh control plane, or receiving the Service tracking configuration information input by a user.
3. The method of claim 1, wherein the service tracking configuration information comprises at least one of: the system comprises information of a distributed tracking system, communication protocol information, a network traffic transparent interception rule, upstream and downstream service addresses of Sidecar connection and a network traffic forwarding rule.
4. The method of claim 1, wherein creating a trace task comprises embedding a service trace call record.
5. The method of claim 1, wherein the communication procedure messages of the application service comprise a request message and a response message.
6. The method of any of claims 1-5, wherein the tracking information of the communication process message comprises one or more of: service name, request method, request path, request parameters, response time, request status.
7. An apparatus for distributed service tracking, comprising: the device comprises an acquisition module, a creation module, a communication module and a reporting module; the acquisition module is used for acquiring service tracking configuration information of the corresponding application service; the creating module is used for creating a tracking task according to the service tracking configuration information; the communication module is used for receiving a communication process message of the application service; and the reporting module is used for reporting the tracking information of the communication process message to a service tracking system server according to the created tracking task.
8. The apparatus of claim 7, wherein the obtaining module obtains service tracking configuration information of the corresponding application service, including: and receiving the Service tracking configuration information sent by a Service grid Mesh control plane, or receiving the Service tracking configuration information input by a user.
9. The apparatus of claim 7, wherein the service tracking configuration information comprises at least one of: the system comprises information of a distributed tracking system, communication protocol information, a network traffic transparent interception rule, upstream and downstream service addresses of Sidecar connection and a network traffic forwarding rule.
10. The apparatus according to any of claims 7-9, wherein the creating a trace task comprises embedding a call record.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010694164.4A CN111917844A (en) | 2020-07-17 | 2020-07-17 | Distributed service tracking method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010694164.4A CN111917844A (en) | 2020-07-17 | 2020-07-17 | Distributed service tracking method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111917844A true CN111917844A (en) | 2020-11-10 |
Family
ID=73281018
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010694164.4A Pending CN111917844A (en) | 2020-07-17 | 2020-07-17 | Distributed service tracking method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111917844A (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112363809A (en) * | 2020-11-27 | 2021-02-12 | 成都精灵云科技有限公司 | System and method for realizing micro-service link collection based on kubernets |
| CN112491634A (en) * | 2020-12-21 | 2021-03-12 | 北京云思畅想科技有限公司 | Full-link intelligent fault simulation and assessment defense method in micro-service scene |
| CN112511560A (en) * | 2020-12-21 | 2021-03-16 | 北京云思畅想科技有限公司 | Data security guarantee method in hybrid cloud environment based on service grid |
| CN112689013A (en) * | 2020-12-24 | 2021-04-20 | 中国农业银行股份有限公司 | System, method and device for service discovery |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109067597A (en) * | 2018-09-21 | 2018-12-21 | 杭州安恒信息技术股份有限公司 | A kind of distributed system dynamic and intelligent service administering method |
| CN110618067A (en) * | 2019-09-20 | 2019-12-27 | 谢国宇 | Pollution tracking and tracing system and method based on monitoring service grid |
| CN111078504A (en) * | 2019-12-25 | 2020-04-28 | 深圳前海环融联易信息科技服务有限公司 | Distributed call chain tracking method and device, computer equipment and storage medium |
| CN111163150A (en) * | 2019-12-25 | 2020-05-15 | 上海精鲲计算机科技有限公司 | Distributed calling tracking system |
| US20200228433A1 (en) * | 2019-01-15 | 2020-07-16 | Fujitsu Limited | Computer-readable recording medium including monitoring program, programmable device, and monitoring method |
-
2020
- 2020-07-17 CN CN202010694164.4A patent/CN111917844A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109067597A (en) * | 2018-09-21 | 2018-12-21 | 杭州安恒信息技术股份有限公司 | A kind of distributed system dynamic and intelligent service administering method |
| US20200228433A1 (en) * | 2019-01-15 | 2020-07-16 | Fujitsu Limited | Computer-readable recording medium including monitoring program, programmable device, and monitoring method |
| CN110618067A (en) * | 2019-09-20 | 2019-12-27 | 谢国宇 | Pollution tracking and tracing system and method based on monitoring service grid |
| CN111078504A (en) * | 2019-12-25 | 2020-04-28 | 深圳前海环融联易信息科技服务有限公司 | Distributed call chain tracking method and device, computer equipment and storage medium |
| CN111163150A (en) * | 2019-12-25 | 2020-05-15 | 上海精鲲计算机科技有限公司 | Distributed calling tracking system |
Non-Patent Citations (2)
| Title |
|---|
| WEIXIN_34087307: ""使用Envoy 作Sidecar Proxy的微服务模式-3.分布式追踪"", 《HTTPS://BLOG.CSDN.NET/WEIXIN_34087307/ARTICLE/DETAILS/88573189》 * |
| 佚名: ""Kubernetes上的服务网格Istio-分布式追踪篇"", 《HTTPS://KALEDL.COM/ARTICLE/233278.HTML》 * |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112363809A (en) * | 2020-11-27 | 2021-02-12 | 成都精灵云科技有限公司 | System and method for realizing micro-service link collection based on kubernets |
| CN112491634A (en) * | 2020-12-21 | 2021-03-12 | 北京云思畅想科技有限公司 | Full-link intelligent fault simulation and assessment defense method in micro-service scene |
| CN112511560A (en) * | 2020-12-21 | 2021-03-16 | 北京云思畅想科技有限公司 | Data security guarantee method in hybrid cloud environment based on service grid |
| CN112491634B (en) * | 2020-12-21 | 2021-09-24 | 北京云思畅想科技有限公司 | Full-link intelligent fault simulation and assessment defense method in micro-service scene |
| CN112689013A (en) * | 2020-12-24 | 2021-04-20 | 中国农业银行股份有限公司 | System, method and device for service discovery |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111917844A (en) | Distributed service tracking method and device | |
| US11184459B2 (en) | Method and system for a network presence platform with intelligent routing | |
| CN110784527A (en) | Information management system and method | |
| US20040001514A1 (en) | Remote services system communication module | |
| US20030212738A1 (en) | Remote services system message system to support redundancy of data flow | |
| US10931479B2 (en) | Inband data gathering with dynamic intermediary route selections | |
| CN113835836B (en) | System, method, computer device and medium for dynamic publishing container service | |
| CN105052076A (en) | Interface management service entity, functional service entity and network element management method | |
| CN111901308B (en) | Information interaction method | |
| CN105183470A (en) | Natural language processing systematic service platform | |
| CN113556359A (en) | Communication protocol conversion method, device, system and gateway device | |
| CN113472719A (en) | Method, device and storage medium for protocol analysis of gatekeeper based on data ferry | |
| US11552868B1 (en) | Collect and forward | |
| CN106330994A (en) | User message publishing method and system | |
| CN114301988A (en) | Distributed calling method and device, storage medium and electronic equipment | |
| EP4415323A1 (en) | Application traffic comprehensive management method, apparatus, and electronic device | |
| CN116684468B (en) | Data processing method, device, equipment and storage medium | |
| US12088347B2 (en) | Intelligent monitoring and repair of network services using log feeds provided over Li-Fi networks | |
| CN110011850B (en) | Management method and device for services in cloud computing system | |
| JPH10320362A (en) | Method for transmitting communication in network including communication service and network for using the same | |
| KR101771658B1 (en) | Apparatus and method for blocking internet advertisement | |
| US20190387075A1 (en) | Methods for exposing mainframe data as a web service and devices thereof | |
| US20230342270A1 (en) | Intelligent Coordination of Log Analysis and Repair Processes in a Multi-Cloud System | |
| CN115208956B (en) | Implementation method of block chain gateway | |
| CN116795651B (en) | Feedback geospatial data service quality log consistency maintenance 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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20201110 |