Replies: 2 comments 2 replies
-
/cc @brunobat (opentelemetry), @radcortez (opentelemetry) |
Beta Was this translation helpful? Give feedback.
-
I took the Otel example and added rest client. Without using org.eclipse.microprofile.rest.client.propagateHeaders=traceparent,tracestate ============================================================= import jakarta.ws.rs.GET; import org.eclipse.microprofile.rest.client.RestClientBuilder; import io.smallrye.mutiny.Uni; @path("/")
} ================================================================ package org.acme.opentelemetry; import org.eclipse.microprofile.rest.client.annotation.RegisterClientHeaders; import io.smallrye.mutiny.Uni; @path("")
} =========================================================== quarkus.application.name=myservice ##org.eclipse.microprofile.rest.client.propagateHeaders=traceparent,tracestate quarkus.rest-client.countries.url=https://restcountries.com/v3.1/ quarkus.log.min-level=ALL quarkus.http.access-log.enabled=true quarkus.http.access-log.log-to-file=true quarkus.rest-client.logging.scope=all ===========================================================
================================================================== |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Is there not a way to auto propagate the parentId and traceId in the RestEasy reactive client headers? We can make it work using ClientRequestFilter or org.eclipse.microprofile.rest.client.propagateHeaders=traceparent,tracestate
but I would rather not have to add any of these to propagate the W3C Trace Context headers.
Beta Was this translation helpful? Give feedback.
All reactions