Tim Peeters
Tim Peeters
> Just an idea I had, but I'm not sure if this is common: we could use the URL to determine the kind of transport to use. `http://` or `https://`...
> I haven't seen people use grpc:// or grpcs:// so far. But I'll do some research ... Indeed, `grpc://` or `grpcs://` does not really seem to be a thing. How...
> A bit aside of these changes: why do you want to use gRPC? gRPC is already enabled for the ingestion of traces coming from the OpenTelemetry integration in ingress-nginx....
I fiddled around a bit but I'm not yet convinced I'm on the right track for an integration tests for the `OtlpGrpcSpanExporter`. The following code: ``` private final Server s...
I added a new commit with a first attempt for an integration test. Looking forward to some feedback. Initially I tried to use the existing `MockWebServer` but it is unable...
I've replaced the solution that relied on the gRPC server with a simple Jetty server. I'm no longer parsing the request to gRPC classes. I believe this matches more closely...
> Thank you very much and congratulations on your first contribution 🎉! Big thanks to all of you for the excellent guidance.
I've provided an initial proposal to support `OtlpGrpcSpanExporter`. See https://github.com/spring-projects/spring-boot/pull/41213 Looking forward to any feedback.
We already upgraded to v2.321.0 a few days ago but still run into this issue from time to time.