Known Issues
- AWS SQS via the JMS integration is broken by #2145. Do not use this version if you are an SQS user. Fixed in 0.76.1
- High CPU usage when paired with trace agent < 7.26.0 - recommended to upgrade to 0.76.1 immediately
Breaking Changes
- JMS producers use
$
as replacement for-
#2145- To avoid propagation problems producers >= 0.76.0 require consumers >= 0.59.0
Improvements
- Enable tracer metrics #2513
- Log injection enabled by default #2440
- [Profiling] Add support for Oracle proprietary JFR implementation #2466
- Axway API integration #1724
- Base Mule 4 instrumentation with HTTP Server Test #2438
- Add support for redshift JDBC #2511
- [CIAPP] Support Test assumptions as skipped tests in JUnit4 and JUnit5 #2437
Changes
- Prefer methods that avoid duplicate header values #2527
- [Mongo] Better mongo scrubbing #2525
- [Dependencies] Upgrade bytebuddy to 1.10.22 #2483
- [Dependencies] Bump JCTools dependency #2465
- [Dependencies] Drop hdrhistogram #2179
- [Grpc] [Integrations] Allow gRPC users to ignore specific outbound RPC calls #2482
- [Context-propagation] [Integrations] [Rabbitmq] [Spring] Propagate context to Spring MessageListenerAdapter #2478
- [Integrations] JAX-WS WebService and WebServiceProvider instrumentation #2473
- Prioritize remote address from
X-Forwarded-For
header when possible #2468 - [Context-propagation] [Reactor] disable reactor hooks instrumentation #2460
- [Reactor] Various reactor instrumentation cleanups #2451
- [CIAPP] Collect git information from local git folder. #2405
- Try reducing allocation in stream processing #2209
Performance
- cache some strings and misc cleanup in webflux-server #2462
- various performance optimizations #2518 #2517 #2508 #2464