Mateusz Rzeszutek
|
280c1ea4c1
|
Enable stable HTTP semconv by default (#9925)
|
2023-11-28 10:43:51 -08:00 |
Trask Stalnaker
|
3b77cc4b2d
|
Semconv 1.21 (#9408)
Co-authored-by: Lauri Tulmin <ltulmin@splunk.com>
|
2023-09-13 19:20:23 +00:00 |
|
Trask Stalnaker
|
cc4e1bf1ae
|
Update semconv to 1.21.0, PART 2 - HTTP (#9372)
|
2023-09-07 08:25:23 -07:00 |
|
Mateusz Rzeszutek
|
6e573289ae
|
Replace NetAttributes with SemanticAttributes (#8992)
|
2023-07-21 11:27:54 +02:00 |
|
Mateusz Rzeszutek
|
c10108bbe0
|
Enable HTTP client read timeout tests by default (#8530)
|
2023-05-19 10:24:49 -07:00 |
|
Mateusz Rzeszutek
|
f501569106
|
Switch from http.flavor to net.protocol.* in HTTP client instrumentat… (#8131)
|
2023-04-07 13:39:42 +02:00 |
Lauri Tulmin
|
08236a710f
|
Add library instrumentation for java http client (#8138)
Resolves
https://github.com/open-telemetry/opentelemetry-java-instrumentation/issues/8069
The javaagent instrumentation also supports propagating context into
[BodyHandler](https://docs.oracle.com/en/java/javase/11/docs/api/java.net.http/java/net/http/HttpResponse.BodyHandler.html)
implemented in
https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/main/instrumentation/java-http-client/javaagent/src/main/java/io/opentelemetry/javaagent/instrumentation/httpclient/BodyHandlerWrapper.java
I think the initial idea behind it was that this allowed propagating
context into callbacks. Because this didn't work for
`connectionErrorUnopenedPortWithCallback` test later we also added
wrapping completable future to take care of propagating context into
callbacks. Should I also implement context propagation for `BodyHandler`
in library instrumentation or should I just delete it? I guess it could
come handy if someone builds a custom `BodyHandler` and wants to emit
spans from there, though this doesn't feel too likely. I'd like deleting
it more.
---------
Co-authored-by: Trask Stalnaker <trask.stalnaker@gmail.com>
|
2023-04-03 13:08:29 -07:00 |