ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
gRPC deadlines and cancellation travel with the RPC via context propagation, letting servers abandon work the moment the caller stops waiting. Here's how to wire it up correctly — and where it silently fails.
Learn how to implement OpenTelemetry Context Propagation to stop trace fragmentation in microservices using W3C Trace Context and Java SDK examples.
Goal: Ensure that request‑scoped data such as the current security principal or MDC context is available inside a Hibernate Panache repository method when it is invoked from a reactive RESTEasy resource that returns a Uni or Multi. Current behavior: Quarkus automatically off‑loads the blocking Panache call to a worker thread, but it does not propagate @Reque
When a request context is cancelled while an OpenTelemetry span is still active, the SDK is expected to end the span, but the exact moment of span completion relative to the cancellation signal varies between language implementations. The OpenTelemetry Specification defines cancellation propagation but does not prescribe how instrumentation should record par
grpc
opentelemetry