topic Transaction stitching issue within the OpenShift namespaces in Container platforms

Transaction stitching issue within the OpenShift namespaces

Babar_Qayyum — Mon, 11 Dec 2023 16:47:14 GMT

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?

Regards,

Babar

Re: Transaction stitching issue within the OpenShift namespaces

paolo_fumanelli — Tue, 12 Dec 2023 10:41:56 GMT

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.

Re: Transaction stitching issue within the OpenShift namespaces

IzabelaRokita — Thu, 05 Jun 2025 13:42:01 GMT

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 😊

Re: Transaction stitching issue within the OpenShift namespaces

Babar_Qayyum — Thu, 05 Jun 2025 17:00:27 GMT

Hello @IzabelaRokita

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.

Regards,

Babar