Lauri Tulmin
|
a2d4148067
|
Remove http stable semconv tests (#10087)
|
2023-12-21 08:30:26 -08:00 |
|
Lauri Tulmin
|
b9e459da07
|
Test http client stable semconv (#9178)
|
2023-08-13 10:22:04 -07: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 |
Trask Stalnaker
|
20c72f3e98
|
Format kotlin gradle files (#3942)
* Add ktlint for kotlinGradle
* ktlint fails on wildcard imports
* Auto-format kotlin gradle files
|
2021-08-25 13:43:57 +09:00 |
Anuraag Agrawal
|
761b9c280b
|
Migrate instrumentation gradle files to kotlin (#3414)
* Migrate instrumentation gradle files to kotlin
* Convert
* Muzzle
|
2021-06-28 17:27:12 +09:00 |