Some demo services (frontend, featureflag, quoteservice) appear as two differently named instances inside the Instana dependency map (for example "frontend" and "my-otel-demo-frontend"). It is because the actual service name (as defined via OTEL_SERVICE_NAME or INSTANA_SERVICE_NAME environment variables) does not match the Kubernetes service name.
The second service shows up when Instana tries to infer the downstream service (by looking at the caller's exit span attributes) by the DNS hostname.
To remove the duplicities one of the following is possible:
modify the Helm chart to name the created Kubernetes services without prepending the release name
prepend the Helm release name to the internal service names (defined in the env. variables) and container names
use instrumentation hacks to change the hostname attributes (a bad idea as it disrupts tag semantics)
a better yet unknown idea someone suggests in the comments
Some demo services (frontend, featureflag, quoteservice) appear as two differently named instances inside the Instana dependency map (for example "frontend" and "my-otel-demo-frontend"). It is because the actual service name (as defined via OTEL_SERVICE_NAME or INSTANA_SERVICE_NAME environment variables) does not match the Kubernetes service name. The second service shows up when Instana tries to infer the downstream service (by looking at the caller's exit span attributes) by the DNS hostname.
To remove the duplicities one of the following is possible: