Description
With Spring Boot 3.x the HTTP client used can be selected based on what is present on the classpath. Some applications may use Jetty Client (org.eclipse.jetty:jetty-client) as the HTTP client implementation In this scenario, outbound HTTP calls occur but the java agent doesn't currently report External service calls for Jetty client requests. This can cause some customers using Jetty Client to lose external service visibility.
Add instrumentation so outbound HTTP calls made through Jetty Client are captured as external services.
https://mvnrepository.com/artifact/org.eclipse.jetty/jetty-client
Context
This behavior was observed while troubleshooting a Spring Boot 3.x upgrade where Reactor Netty was automatically selected as the HTTP client. NR-527170
Description
With Spring Boot 3.x the HTTP client used can be selected based on what is present on the classpath. Some applications may use Jetty Client (org.eclipse.jetty:jetty-client) as the HTTP client implementation In this scenario, outbound HTTP calls occur but the java agent doesn't currently report External service calls for Jetty client requests. This can cause some customers using Jetty Client to lose external service visibility.
Add instrumentation so outbound HTTP calls made through Jetty Client are captured as external services.
https://mvnrepository.com/artifact/org.eclipse.jetty/jetty-client
Context
This behavior was observed while troubleshooting a Spring Boot 3.x upgrade where Reactor Netty was automatically selected as the HTTP client. NR-527170