Support Otlp Tracing's GRPC port from service connections #41333
Conversation
Otlp Tracing's exporter is configured using `Transport`. Current support for service connections read the mapped port for HTTP transport `4318`. This commits adds support to read port for GRPC transport `4317`.
spring-projects-issues
added
the
status: waiting-for-triage
|
Thanks for the PR, @eddumelendez. I'm not sure what the answer is, but this doesn't feel quite right to me. I don't think the connection details should have a separate method for the GRPC endpoint. Ideally, the existing |
|
Hi @wilkinsona, yes, I agree. I think that's the only way I was able to achieve it. Looking forward for any hint to update the PR. |
wilkinsona
added
the
for: team-meeting
|
We discussed this today and we think we might be able to pass the |
philwebb
added
type: enhancement
Otlp Tracing's exporter is configured using `Transport`. Current support for service connections read the mapped port for HTTP transport `4318`. This commits adds support to read port for GRPC transport `4317`. See spring-projectsgh-41333
|
Placing on hold as we'd like to spend a bit of time thinking through our gRPC support across logs, metrics, and tracing. |
Otlp Tracing's exporter is configured using Transport. Current support for service connections read the mapped port for HTTP transport 4318. This commits adds support to read port for GRPC transport 4317. See gh-41333
|
Thanks! I've modified |
Otlp Tracing's exporter is configured using
Transport. Current support for service connections read the mapped port for HTTP transport4318. This commits adds support to read port for GRPC transport4317.