John Watson

> So if I put Sleuth aside and just use OTel exporter alone, this means that the exporter is not usable out of the box, you need to go the...

> fyi: [open-telemetry/opentelemetry-java#3123](https://github.com/open-telemetry/opentelemetry-java/issues/3123) FYI, I chatted with @anuraaga about this last week and we both agree that this is something for distributions (like spring-cloud-sleuth-otel) to manage, rather than have the...

> @jkwatson I understand that you don't want to include the client. What I don't understand is why? > From the client perspective, this is not a good experience, users...

> There not being a default client and that being a bad user experience aside, why is it the responsibility of Sleuth to know what version of grpc etc work...

We had discussed during the SIG meeting that perhaps what we need is a `scope` object we can set on the builder, rather than having to do it piecemeal.

> > We had discussed during the SIG meeting that perhaps what we need is a scope object we can set on the builder, rather than having to do it...

I'm not sure that PR is a full replacement. I'm using the PrometheusServlet to serve up prometheus data. That uses the default registry, and the bridge lets me just let...

> > I'm using the PrometheusServlet to serve up prometheus data. > > You should be able to do this via `PrometheusHttpServerBuilder#setPrometheusRegistry(PrometheusRegistry.defaultRegistry)`, no? The code registers an OTEL implementation of...

Oh! 🤔 I'd be happy to try that out, once it's merged and released; if it works, then I'm 👍🏽 on this proposal.

Support hasn't been implemented yet...simple as that.