This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Dear All, We are facing a situation where a transaction is not stitching between two different namespaces hosted on the same OpenShift cluster. The flow is Mobile App > F5 > Webserver > HAProxy/router (installed as Pods) > Service A (namespace A) > Service B (namespace B) > backends. The service flow is working up to the following: Mobile App > F5 > Webserver > HAProxy/router (installed as Pods) > Service A (namespace A). What could be the reasons behind this situation?
Hi, if you take one transaction, and currently it ends on service A, can you find the missing part of the trace as a trace of service B? If so, the reason behind could be that somehow x-dynatrace header is dropped by service B.
Hey @Babar_Qayyum, did you manage to find the solution to your problem? If so, it would be amazing if you've shared it with the rest of the Community! If not, let me know, and I'll look for some further assistance 😊
The described issue was due to the non supported technology on the second part of the transaction and lately I heard from my collogues that they were asked by the Dynatrace support to use the OpenTelemetry to stitch the transaction as a workaround/or visibility.
