Traces are not correctly ccorrelated when using an API Gateway

Kibana version:

Elasticsearch version:

APM Server version:
Unknown/ most likely 8.11.1

APM Agent language and version:
No APM Agent.
.NET OpenTelemetry sending data directly to the APm server using OTLP protocol.

Browser version:

Original install method (e.g. download page, yum, deb, from source, etc.) and version:

Fresh install or upgraded from other version?

Is there anything special in your setup? For example, are you using the Logstash or Kafka outputs? Are you using a load balancer in front of the APM Servers? Have you changed index pattern, generated custom templates, changed agent configuration etc.

Description of the problem including expected versus actual behavior. Please include screenshots (if relevant):
Transactions are not correctly correlated across services when they communicate via an API gateway.

Given a setup where two services communicate via an API gateway, in this case Azure API Management. dependencies are not correctly correlated in the trace viewer in Kibana.

When Service A makes a call to Service B the result is that Service B is not shown as a dependency for Service A and the transaction from Service B is not correctly shown within the transaction from Service A. The following image shows the transactions and the details:

As you can see the trace id in Service B is the same as the trace id in Service A but it is not correctly shown.

Is this a problem with OpenTelemetry, API Gateways or perhaps a combination of both?

The expected result is something as shown in the Kibana demo page where looking at the trace from Service A shows that the transaction goes to Service B

Errors in browser console (if relevant):

Provide logs and/or server output (if relevant):

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.