adutra commented on code in PR #2757:
URL: https://github.com/apache/polaris/pull/2757#discussion_r2447689109
##########
helm/polaris/values.yaml:
##########
@@ -518,6 +516,16 @@ realmContext:
realms:
- POLARIS
+# -- Configuration for correlation IDs.
+correlationId:
Review Comment:
We already support that :-) In Quarkus, W3C Trace Context propagation is
enabled by default:
https://quarkus.io/guides/opentelemetry-tracing#propagators
IOW, Polaris correlation ID can be considered a simplified alternative to
OTel context propagation; but the former doesn't preclude the latter. You can
perfectly combine both techniques together.
Polaris correlation ID has one small advantage though: it is included in
Polaris events, while OTel context is not. So the only way to crrelate a
Polaris event with an OTel trace is to first locate the trace using the
correlation ID from the event.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
