Hello! I wonder if it is possible to have distributed tracing from the mobile application to the backend part (for example, a mobile application that calls a series of microservices deployed in a Kubernetes).
If possible, is that traceability based on the W3C Trace Context standard?
Solved! Go to Solution.
Hello @luis_mpa ,
when you instrument your mobile application with Dynatrace, then those linking works. If you use auto-instrumentation and a supported library (typically the common case), then Dynatrace will automatically inject HTTP request header (X-Dynatrace) into the requests made from the mobile app and those headers will be picked up by the OneAgent monitoring the backend. If you don't use auto instrumentation you must add those headers by yourself.
So W3C context is not used, but the Dynatrace headers. There is no option to use w3c headers as of now for this.
Thank you very much for your quick reply, @Julius_Loman ! 🙂
What happens if we have Dynatrace configured to use the W3C Trace Context headers? Is there mobile-->backend traceability even if the mobile SDK uses X-Dynatrace or is it broken?
Has Dynatrace planned to upgrade mobile traceability by adopting the W3C Trace Context? If so, is there a date?
@luis_mpa , Dynatrace uses both on the backend side. If you have W3C tracing headers enabled (that's enabled by default now in new environments), it does not interfere in any way, nothing is broken, Dynatrace picks up both headers.
But for mobile app -> mobile backend, the x-dynatrace is used. I'm not aware of any plans to use W3C headers for Dynatrace Mobile SDKs.