A note for the community
- Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
- If you are interested in working on this issue or have submitted a pull request, please leave a comment
Use Cases
Many OpenTelemetry collectors and backends (e.g., Jaeger, Tempo, Grafana Cloud) expect gRPC as the primary transport protocol on port 4317. Users wanting to send data to these systems currently cannot use Vector's OpenTelemetry sink directly.
Attempted Solutions
No response
Proposal
Perhaps we can reuse code from the Vector sink which already supports gRPC. But this is not a must.
References
Version
No response
A note for the community
Use Cases
Many OpenTelemetry collectors and backends (e.g., Jaeger, Tempo, Grafana Cloud) expect gRPC as the primary transport protocol on port 4317. Users wanting to send data to these systems currently cannot use Vector's OpenTelemetry sink directly.
Attempted Solutions
No response
Proposal
Perhaps we can reuse code from the Vector sink which already supports gRPC. But this is not a must.
References
Version
No response