Move net.peer.name from common http attributes section to just client http attributes section #2366
Labels
area:semantic-conventions
Related to semantic conventions
semconv:HTTP
spec:trace
Related to the specification/trace directory
What are you trying to achieve?
Help instrumenters avoid the problem we've run into in the opentelemetry-java-instrumentation project with triggering reverse name lookups (open-telemetry/opentelemetry-java-instrumentation#5297, open-telemetry/opentelemetry-java-instrumentation#5305, open-telemetry/opentelemetry-java-instrumentation#5393).
Given the problems this causes, I think it's worth moving
net.peer.name
from common http attributes section to just the client http attributes section (and add an explanation why it's not recommended for http server spans).The text was updated successfully, but these errors were encountered: