Replies: 4 comments 2 replies
-
@jpkrohling @bogdandrutu Can you please review and comment on this ? |
Beta Was this translation helpful? Give feedback.
-
That document seems to be auto-generated. The Server Settings might indeed allow receivers to listen on UDP, but there's no UDP support for gRPC at all, and no support on the OTLP receiver to accept batches via UDP. I believe we should:
|
Beta Was this translation helpful? Give feedback.
-
I don't think there is a specific reason, it just wasn't implemented. Are you up to opening a PR with a concrete proposal? |
Beta Was this translation helpful? Give feedback.
-
UDP does not work with gRPC, and seems to not work with HTTP, the two L7 layers that we use. But we do support unixsockets if you are on the same machine. |
Beta Was this translation helpful? Give feedback.
-
Use case : I want to use OtelCollector as agent, and would want to configure OTLP receiver to listen on UDP port to avoid buffering on the app side.
I tried using below OTLP receiver config and ran into this issue. After going through the code i don't see any implementation for UDP in specific. Am i missing anything here ? Please suggest?
ISSUE
Error: cannot start pipelines: listen udp 127.0.0.1:4317: address localhost:4317: unexpected address type
2022/09/02 14:15:05 collector server run finished with error: cannot start pipelines: listen udp 127.0.0.1:4317: address localhost:4317: unexpected address type
Exiting.
**Config based on https://github.com/open-telemetry/opentelemetry-collector/blob/main/receiver/otlpreceiver/config.md#:~:text=in%20RFC%204007.-,transport,-string **
Above documentation seems to be misleading.
Beta Was this translation helpful? Give feedback.
All reactions