opentelemetry-java-instrume.../instrumentation/couchbase/couchbase-2.0/javaagent/src
Mateusz Rzeszutek 77035fc88c
Extract `net.peer.{name,port}` on start for CLIENT spans (#6828)
The [HTTP
spec](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/semantic_conventions/http.md#http-client)
says these two attributes must be provided at span creation time - I
think it makes sense to extend it over to all `net`-related
instrumentations, cause these are supposed to be the logical peer
name/port, which are supposed to be known before the connection is
started/exchange is made.
2022-10-10 16:00:19 -07:00
..
main/java/io/opentelemetry/javaagent/instrumentation/couchbase/v2_0 Extract `net.peer.{name,port}` on start for CLIENT spans (#6828) 2022-10-10 16:00:19 -07:00
test/groovy Use low cardinality span names in Couchbase instrumentation (#2449) 2021-03-02 10:25:01 -08:00