| 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) |
...
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).
The “SLA-metrics” services extracts response times from Jaeger/Elasticsearch and imports those to Splunk.
| Gliffy | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
For all containers deployed on the infrastructure, an Istio-sidecar proxy is deployed in the same pod. This is configured using the eHealth Helm Charts (see Helm Charts).
The Istio proxy are able to automatically send spans (the time spend in a single service) to Jaeger.
...
Jaeger traces should be sent to the Jaeger collector at: http://jaeger-operator-jaeger-collector.jaeger.svc.cluster.local:14268/api/traces