Expected behavior

I'm working with @dhaval24 on an approach to set correlation between message queue consumers / producers as discussed in issue #764. My approach is based on this sample application.

Telemetry correlation works 100% locally on my laptop and also locally when running in Docker. My expectation is this would work the same in Kubernetes.

Actual behavior

The call for TraceContextCorrelation.generateChildDependencyTraceparent() returns null when running in Kubernetes.

To Reproduce

Deploy workload to AKS (version 1.12.5).

Sample Application

Full source code is here

System information

Please provide the following information:

• SDK Version: 2.3.1
• OS type and version: Debian 9
• Application Server type and version (if applicable): Tomcat
• Using spring-boot? Yes
• Additional relevant libraries (with version, if applicable): OpenJDK 8

My Kubernetes environment is Azure Kubernetes Service (AKS) version 1.12.5.

Logs

N/A

Screenshots

Example of the application running locally in Docker:

Example of ThreadContext in Kubernetes and the null value returned for generateChildDependencyTraceparent(). I handle this null condition in my code.