...
...
| Excerpt |
|---|
The eHealth infrastructure makes it possible to trace all actions across different services and components. This is implemented using Istio and OpenTracing with Jaeger. The Call Tracing applies to both Telemedicine Solutions (3rd party) and eHealth Services (Infrastructure Provider) |
| Table of Contents |
|---|
The figure below show the trace flow from initial traffic to a Istio enabled pod, through the jaeger system all the way to the jaeger web interface and the FUT background service "SLA-metrics" (a part of the SLA calculating system).
| Gliffy | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Header Propagation
For all containers deployed on the infrastructure, an Istio-sidecar proxy is deployed in the same pod. The Istio proxy are able to automatically send spans (the time spend in a single service) to Jaeger.
...
The headers that must be propagated from the incoming request to all outgoing requests are the following:
x-request-idx-b3-traceidx-b3-spanidx-b3-parentspanidx-b3-sampledx-b3-flagsx-ot-span-contextb3 (for forward compatibility)
All headers may not be present for all requests, but if they are, then they must be propagated.
...
This allows the infrastructure to:
Pinpoint potentially slow external dependencies
Calculate how much time is spend waiting for external dependencies for each end-user request
Create audit trails for all requests
More Info
Java client library and great explanation of the different B3 headers: https://github.com/openzipkin/b3-propagation
...
Various alternatives related to server and client instrumentation: https://github.com/opentracing-contrib
E.g. use https://github.com/opentracing-contrib/java-spring-web if using Spring Boot + servlets + Spring RestTemplate clients (other clients also available, e.g. Apache HttpClient: https://github.com/opentracing-contrib/java-apache-httpclient)
Example
| Gliffy | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
...
Tracing on requests to external services
...
Jaeger traces should be sent to the Jaeger collector at: http://jaeger-operator-jaeger-collector.jaeger.svc.cluster.local:14268/api/traces