Missing Service Correlation in Dynatrace (OpenShift)

[Salma_berechid]

Hello guys,

We have the Dynatrace Operator installed on an OpenShift cluster.

We are able to detect the application and all related services; however, we’ve noticed that there is no service-to-service correlation between Backend BFF and Backend API, even though they communicate with each other in our architecture.

Do you have any suggestions on what could be causing this or how we can troubleshoot the missing correlation?

Salma

[AntonPineiro]

Hi,

I would check if technologies involved are supported in Technology support.

Best regards

[Salma_berechid]

Hello Anton,
I’ve checked it, and all the technologies are supported.
Salma

[AntonPineiro]

Hi,

You can raise a support ticket about it.

Best regards

[PacoPorro]

@Salma_berechid

It looks like the X-dynaTrace header is missing somewhere between the components. Try creating a request attribute based on this header and check whether the values changed for the same request. If it does, something in the chain is stripping the header

[Salma_berechid]

Hello,
After analyzing the issue, we noticed that the x-dynatrace header is present, but the other headers such as traceparent and tracestate are missing.

We also observed that Dynatrace creates a new trace at each step instead of a single end-to-end trace.
Salma