topic Re: Missing Service Correlation in Dynatrace (OpenShift) in Dynatrace Managed Q&A

Missing Service Correlation in Dynatrace (OpenShift)

Salma_berechid — Mon, 26 Jan 2026 08:29:23 GMT

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

Re: Missing Service Correlation in Dynatrace (OpenShift)

AntonPineiro — Fri, 23 Jan 2026 13:46:59 GMT

Hi,

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

Best regards

Re: Missing Service Correlation in Dynatrace (OpenShift)

Salma_berechid — Fri, 23 Jan 2026 14:20:49 GMT

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

Re: Missing Service Correlation in Dynatrace (OpenShift)

AntonPineiro — Mon, 26 Jan 2026 08:07:07 GMT

Hi,

You can raise a support ticket about it.

Best regards

Re: Missing Service Correlation in Dynatrace (OpenShift)

PacoPorro — Mon, 26 Jan 2026 08:18:14 GMT

@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

Re: Missing Service Correlation in Dynatrace (OpenShift)

Salma_berechid — Tue, 27 Jan 2026 09:35:18 GMT

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

Re: Missing Service Correlation in Dynatrace (OpenShift)

Salma_berechid — Wed, 04 Feb 2026 10:10:23 GMT

Hello folks,
For anyone encountering the same issue, please check whether the Java HTTP Client feature is enabled.
Salma