You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I should be able to use opentelemetry SDK to propagate trace headers from the actor client to server.
Actual Behavior
Today, providing a traceparent header in the actor client doesn't propagate to the actor server while using the latest version of Dapr (1.14.4) and the Java SDK. Additionally following the example here still causes the actor client and actor server traces to show up with two separate trace IDs.
Steps to Reproduce the Problem
Run actor client and actor server apps, and use the open telemetry SDK to propagate the trace header through from client -> server. Print the headers out on each side to see that they are different.
Release Note
RELEASE NOTE: FIX Propagate traces in actors
The text was updated successfully, but these errors were encountered:
Expected Behavior
I should be able to use opentelemetry SDK to propagate trace headers from the actor client to server.
Actual Behavior
Today, providing a
traceparent
header in the actor client doesn't propagate to the actor server while using the latest version of Dapr (1.14.4) and the Java SDK. Additionally following the example here still causes the actor client and actor server traces to show up with two separate trace IDs.Steps to Reproduce the Problem
Run actor client and actor server apps, and use the open telemetry SDK to propagate the trace header through from client -> server. Print the headers out on each side to see that they are different.
Release Note
RELEASE NOTE: FIX Propagate traces in actors
The text was updated successfully, but these errors were encountered: