open-telemetry
/
opentelemetry-java-instrumentation
mirror of https://github.com/open-telemetry/opentelemetry-java-instrumentation.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
opentelemetry-java-instrume.../instrumentation/lettuce
History
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
..
lettuce-4.0/javaagent Extract `net.peer.{name,port}` on start for CLIENT spans (#6828) 2022-10-10 16:00:19 -07:00
lettuce-5.0/javaagent Extract `net.peer.{name,port}` on start for CLIENT spans (#6828) 2022-10-10 16:00:19 -07:00
lettuce-5.1 Extract `net.peer.{name,port}` on start for CLIENT spans (#6828) 2022-10-10 16:00:19 -07:00
lettuce-common/library Type annotation placement (#4406) 2021-10-17 17:38:43 -07:00
README.md Add settings docs for instrumentations (#4981) 2022-01-03 10:24:48 -08:00

README.md

Settings for the Lettuce instrumentation

System property Type Default Description
otel.instrumentation.lettuce.experimental-span-attributes Boolean false Enable the capture of experimental span attributes.