cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Transaction stitching issue within the OpenShift namespaces

Babar_Qayyum
DynaMight Guru
DynaMight Guru

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

1 REPLY 1

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.

Featured Posts