The

Question

The <https github com open telemetry opentelemetry specification blob main specification sdk environment variables md|OpenTelemetry spec> accepts a list of propagators `OTEL PROPAGATORS` AFAIK it chooses the first valid propagator for incoming requests Would that be feasible to implement in Cerbos Right now I have to choose between tracecontext and b3 I prefer tracecontext but some of the 3rd party services we use only support b3 so it d be super cool if Cerbos had an `auto` option to detect the propagation headers from an incoming request

Charith (Cerbos) · Answer

We can certainly look into that

Charith (Cerbos) · Answer

When we first started working on Cerbos Otel was still not production ready So we went with OpenCensus That s still there because the Otel Go libraries still have some unresolved issues like nil pointer derefs in the gRPC interceptors

Charith (Cerbos) · Answer

So the opencensus otel bridge might not be fully compatible with the spec yet We ll see if there s a way to support `auto` though

Rasmus Dencker · Answer

Oh alright No worries though For now it works I actually thought otel was just a rename merge of opencensus

Rasmus Dencker · Answer

but I see that they added several new stuff too smile

Charith (Cerbos) · Answer

They merged OpenCensus and OpenTracing projects to become Otel and pretty much rewrote everything from scratch to end up with something that IMHO is worse than the original projects slightly smiling face There are lots of bugs missing features and a really weird Go module setup for the library

Rasmus Dencker · Answer

Oh damn

Charith (Cerbos) · Answer

Looks like this is possible to do I have raised a PR for it <https github com cerbos cerbos pull 980> Hoping to get it out in the next release which is not too far away

Rasmus Dencker · Answer

Awesome Thanks