Is the traceId the same for all messages of a GRPC streaming response?

[otbe]

Hi,

I have more like a theoretical question. Let's say I have a server and client application. The server provides a GRPC service which has a method that uses a streaming response. The response can go one for many days or weeks in our case, its like a push communication for changes. Both services are instrumented via the latest Otel Java Agent.

What we see is that from the start of the application onwards the traceId on the client when receiving stream messages is the same for all messages. Doesn't matter if it's 1 minute after boot or 2 days. There is no custom instrumentation in place (in both client&server).

Two questions:

• is this expected?
• Is there a way to change this behaviour? Right now this leads to extremely large traces that cannot be handled by our system (tempo).

Used versions:

• Spring Boot 3.5.3
• Otel Java Agent 2.18.1