Traces for specific services are not properly connected while calling internal services through Spring Cloud Gateway (Root Span Missing)

[kworkbee]

Describe the bug

Traces for specific services are not properly connected while calling internal services through Spring Cloud Gateway

As a result, Root Span is missing.

Steps to reproduce

Inject OpenTelemetry JavaAgent into Gateway and each services

Expected behavior

A normal connection of the trace along the route through the service

Actual behavior

Determine what happens when certain applications are separated into two traces

Javaagent or library instrumentation version

2.10.0

Environment

JDK: Adoptium Temurin 17
OS: AL2023 (Amazon Linux, Kubernetes)

Gateway : Spring Cloud Gateway (Boot 3.1.5 / Cloud 2023.0.4)
Services:

• For service that work as intended : Boot 3.3.4
• For service that do not work as intended : Boot 2.6.7

Additional context

No response

[laurit]

For service that work as intended : Boot 3.3.4
For service that do not work as intended : Boot 2.6.7

Does this mean that some services work as expected while others don't?
Could you provide a minimal application that reproduces your issue.

[kworkbee]

For service that work as intended : Boot 3.3.4
For service that do not work as intended : Boot 2.6.7

Does this mean that some services work as expected while others don't? Could you provide a minimal application that reproduces your issue.

Hi @laurit, Sorry for late response.

As you mentioned, it is a phenomenon in which traces are created individually for some services in requests from the same gateway to other services.

As it is a business application, there are parts where it is impossible to share source code directly due to security risks, so we tried to reproduce it in the same environment, but now it is not going as intended.

Originally, it was an application that delivers trace directly to Zipkin via B3 Propagation internally, but it seems to be reproduced even though we removed the current dependency.

[laurit]

As it is a business application, there are parts where it is impossible to share source code directly due to security risks, so we tried to reproduce it in the same environment, but now it is not going as intended.

We do not want the source code of your application. We are asking for a minimal sample application that reproduces the issue. To fix the issue ideally we need some way to reproduce it so we could get a better understanding what causes the problem.

Originally, it was an application that delivers trace directly to Zipkin via B3 Propagation internally, but it seems to be reproduced even though we removed the current dependency.

I don't follow this.

[github-actions]

This has been automatically marked as stale because it has been marked as needing author feedback and has not had any activity for 7 days. It will be closed automatically if there is no response from the author within 7 additional days from this comment.