Enable Shift tracing capabilities
The implementation for the KOBIL Shift services tracing functionality is part of the default KOBIL Shift functionality and makes use of Jaeger and ZipKin services. The parameter to enable is part of the KOBIL Shift metaconfiguration section"common". There is no specific setting per specific KOBIL service but for groups.
Enable the Shift tracing:
The Kobil Service Charts are designed to handle the common configurations down to the KOBIL Shift services grouped by "idp", "ast", "smartsceen" and "scp" plus "payment" services. When enable i.e. the "ast" tracing-flag - then all "ast"-service will make use of the tracing endpoints per common.tracing.
When changing the metaconfiguration to cover updated parameter the KOBIL Shift deployment needs to be updated by helm update <shift> ...."
common:
...
..
tracing:
# -- Enable / Disable tracing for service groups.
enable:
idp: false ### enable by "true"
ast: false ### enable by "true"
smartscreen: false
scp: false
payment: false
# -- hostname of tracing sink used by idp, ast and smartscreen services.
# Must support model.proto protocol on port 14250 (gRPC).
# For example a jaeger-collector:
# https://www.jaegertracing.io/docs/next-release/deployment/#agent
jaegerGrpcHost: "http://jaeger-collector.tracing.svc.cluster.local:14250/api/v2/spans"
# -- hostname of tracing sink used by scp and payment services.
# Must support zipkin protocol on port 9411 (HTTP).
# For example a jaeger-collector:
# https://www.jaegertracing.io/docs/next-release/deployment/#collector
zipkinUrl: "http://jaeger-collector.tracing.svc.cluster.local:9411/api/v2/spans"
Notes:
It is required to have "Jaeger"-Services availabe and running (jaegerGrpcHost service - per gcommon.tracing.jaegerGrpsHost: "<hostname:port/path>
/ zipKinUrl per gcommon.tracing.jaegerGrpsHost: "<hostname:port/path>
.
Using the stored "tracing"-data is then done using a frontend-Tool - ie. the Jaeger UI service.