-
## Expected Behavior
ParentID should be propagated correctly, so full trace can be visualized in Jaeger.
## Actual Behavior
TraceID is preserved but ParentID is lost which leads to flat span tree…
-
### Description
Context propagation does not work correctly between http client and server as context
is not read from header on server side. Always new context is created.
-
### Description
The MP Context Propagation specification includes a `SECURITY` context (see `org.eclipse.microprofile.context.ThreadContext#SECURITY`), but Quarkus does not directly "implement" this …
-
### Issue description
I expect there to be information about how Tracing context is passed to coroutines and in the micronaut core docs there is a section https://docs.micronaut.io/latest/guide/ind…
-
Async-listener will propagate contexts through Promise.all, which is different behavior from similar functionality in the domain module.
It's not 100% clear to me that this is a bug, though it is une…
-
Context Propagation is used more and more but its cost is noticeable.
We need to improve it in the short to medium term.
-
Span context isn't propagated automatically when using OpenTelemetry manual instrumentation. It needs to be propagated whenever thread context switch happens (as they are stored in ThreadLocal) to avo…
-
Provide documentation around Context propagation
- I want to propagate user credential/token across multiple calls
- I want to propagate trace ID of some sort across multiple calls
- Does it only…
-
It appears GRPC has support for manual context propagation, by providing a storage mechanism. It's not entirely clear to me if it's pluggable or not, but it looks similar in use-case to what we do her…
-
## Problem
Currently query logs can not relate to requests or a parent context from which they were invoked from. This means solutions like https://github.com/iamolegga/nestjs-pino or as well datad…
tak1n updated
9 months ago