Component
Instrumentation: otelgrpc
Problem Statement
We observe in the OTel Demo traces, screenshot below, that otelgrpc sets server.address to the IP address (e.g. 172.18.0.19) rather than the hostname provided to the gRPC client (e.g. payment).
This makes troubleshooting harder and seems misaligned with the OTel semantic conventions, which state that server.address should use the server domain name when available (without reverse DNS), falling back to the IP otherwise (see reference).
Proposed Solution
Use the hostname provided in the gRPC client configuration instead of the IP address resolved from that hostname.
Alternatives
No response
Prior Art
No response
Additional Context
No response
Component
Instrumentation: otelgrpc
Problem Statement
We observe in the OTel Demo traces, screenshot below, that
otelgrpcsets server.address to the IP address (e.g.172.18.0.19) rather than the hostname provided to the gRPC client (e.g.payment).This makes troubleshooting harder and seems misaligned with the OTel semantic conventions, which state that
server.addressshould use the server domain name when available (without reverse DNS), falling back to the IP otherwise (see reference).Proposed Solution
Use the hostname provided in the gRPC client configuration instead of the IP address resolved from that hostname.
Alternatives
No response
Prior Art
No response
Additional Context
No response