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
The goal of the issue is to create a new module, opentelemetry-tracing-sync-backend, which will provide integration with blocking/direct-style OpenTelemetry tracing, as well as reference documentation showcasing how to use the module.
Moreover, a first step is to suggest a way of propagating the context (setting appropriate headers, including identifiers/correlation ids) that is compatible with virtual threads & scoped values, as used by Loom and Ox. Note that the the OT Java libraries often rely on ThreadLocals, which are not Loom-compatible.
Currently sttp-client only ships with OT+ZIO tracing integration.
The goal of the issue is to create a new module,
opentelemetry-tracing-sync-backend
, which will provide integration with blocking/direct-style OpenTelemetry tracing, as well as reference documentation showcasing how to use the module.Moreover, a first step is to suggest a way of propagating the context (setting appropriate headers, including identifiers/correlation ids) that is compatible with virtual threads & scoped values, as used by Loom and Ox. Note that the the OT Java libraries often rely on
ThreadLocal
s, which are not Loom-compatible.See also softwaremill/tapir#4103
The text was updated successfully, but these errors were encountered: