...
...
| 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 figure below show the trace flow from initial traffic to a istio Istio enabled pod, through the jaeger system all the way to the jaeger web interface and the fut FUT background service "SLA-metrics" (a part of the SLA calculating system).
...
For all containers deployed on the infrastructure, an istioIstio-sidecar proxy is deployed in the same pod. The istio Istio proxy are able to automatically send spans (the time spend in a single service) to Jaeger.
...
If an application deployed on the ehealtheHealth-platform infrastructure makes a call to an external dependency, this call should also have the tracing headers on.
...
Jaeger traces should be sent to the Jaeger collector at: http://jaeger-operator-jaeger-collector.jaeger.svc.cluster.local:14268/api/traces