Java agent release notesRSS

New features and improvements:

• Real-time profiling for Java using JFR metrics is now fully integrated into the Java agent. See the JFR core README for additional details.

This feature requires a supported version of Java 8 (specifically version 8u262 or higher) or Java 11 or higher and is currently disabled by default. To enable it set the following in your yaml (indented 2 spaces under the common section).

jfr:
  enabled: true

Notice: If you were previously using the jfr-daemon jar as an agent extension or standalone process you should remove that option to avoid potential conflicts with the JFR service that is now built into the agent.

• Not compatible with Java 7. In order to continue to innovate and efficiently provide new capabilities to our customers who run on the JVM, this and future agent versions aren't compatible with Java 7. If you're running Java 7, you may continue to use Java agent 6.5.0 or lower. For details, see this topic on the Explorers Hub.
• Adds support for akka http with Scala 2.13. #271
• Class annotation to trace lambda methods. #274
• Class annotation to trace methods by return type. #275

Fixes:

• Fixes an issue that could cause multiple versions of akka-http-core instrumentation to apply at the same time. #208
• The agent will now log dropped events at FINE instead of WARN to decrease verbosity. #296
• Fixes Javadoc comments that incorrectly stated that, when calling the noticeError API multiple times, the first error would be reported when in fact it's the last error that is reported. #313

Support statement:

• New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life.

Known Issues

• OkHttp

This release contains a bug that breaks OkHttp versions 3.X and below. All affected users should upgrade to 7.0.1.

新機能と改善点：

• エージェントにはSSL証明書がバンドルされなくなり、以前にバンドルされていた証明書を使用するようにエージェントを設定していたuse_private_sslオプションは削除されました。デフォルトでは、ca_bundle_pathオプションを使用して別のトラストストアを使用するように明示的に設定されていない限り、エージェントはJVMによって提供されるSSLトラストストアを使用します。詳細については、SSL証明書の設定をご覧ください。

修正：

• JAX-RSサブリソースを使用する際に、不正確なトランザクションのネーミングを引き起こす可能性のある問題を修正しました。
• Reactor Nettyの計装の改善および修正。

廃止のお知らせ

• Java 7互換性の非推奨化

JVMで実行している顧客に革新をもたらし続け、新しい機能を効率的に提供するために、Java 7のサポートは非推奨となり、これがJava 7と互換性のある最後のエージェントのバージョンとなります。

Java 7を実行している場合は、引き続きJavaエージェント6.5.0以前を使用できます。

詳しくは、Explorers Hubの投稿をご覧ください。

サポートステートメント:

• New Relic では、最新の機能とパフォーマンス上のメリットを確実に得られるよう、エージェントを定期的にアップグレードすることをお勧めします。さらに、古いリリースはサポート終了になるとサポートされなくなります。

Fixes

Fixes an issue that could cause some instrumentation modules (e.g. jax-rs-1.0) to have a WeaveViolation and not apply properly.

Fixes

Fixes an issue in 6.4.0 where spans would not get sent to Infinite Tracing.

Note:

• There is an issue with this agent release that could lead to spans not being sent to Infinite Tracing. Please use 6.4.1 instead.

New Features and Improvements:

• Spring Webflux/Netty Reactor instrumentation improvements for enhanced tracing across asynchronous thread hops.
• The agent will now utilize a backoff sequence on connection retries to Infinite Tracing.
• New distributed tracing APIs have been added to better support general use cases for propagating distributed tracing headers. In particular the new APIs provide enhanced support for W3C Trace Context but are flexible enough to support other header protocols that may be supported by the agent in the future. Previous distributed tracing APIs have been deprecated and are subject to removal in a future agent release. See documentation here.
  • Transaction.insertDistributedTraceHeaders(Headers) is used to create and insert distributed tracing headers (both newrelic and W3C Trace Context) into a Headers data structure.
  • Transaction.acceptDistributedTraceHeaders(TransportType, Headers) is used to accept the distributed tracing headers sent from the calling service and link these services together in a distributed trace.

Fixes:

• Updated the Java agent’s snakeyaml dependency to 1.27.
• In some environments the jar collector service could lead to high CPU utilization at application startup. The agent now provides a configurable rate limiter, with a reasonable default, for processing jars detected in the application’s environment. See documentation here.

Support statement:

• New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life.

Improvements

• Spring Webflux
  • The Java agent now supports Spring Webflux versions 5.3+
  • Added reactor-netty.errors.enabled configuration to allow disabling error reporting in Subscriber::onError.
• Scala 2.13
  • The Java agent now provides support for Scala 2.13 and frameworks compiled with 2.13 Akka-http, Play

Fixes

• The netty-4.0.8 instrumentation would sometimes not start a Transaction on channelRead, potentially affecting instrumentation dependent on it including: Spring, Akka and Play
• Updated the Java agent’s Apache HttpClient dependency to 5.13
• Spring Webclient could report the wrong URL when multiple HTTP calls to several URLs occurred in parallel

Fixes

• Fixes an issue where Spring-Webflux applications with endpoints returning Flux or empty content could become unresponsive

New features

• Adds support for Akka Http Core 10.2.0. Thank you jobicarter for reporting this issue.
• Adds support for gRPC 1.30.0. Thank you jef for submitting this request and trying it out.
• Adds support for map and flatmap async external calls in spring webflux framework. Previously the agent didn’t support client calls that occurred within the map or flatmap methods within the spring webflux framework. External calls such as serviceB and serviceC in the example below would not get reported to New Relic:

return serviceA.getData()
                .map(service -> Response.builder().service(service).build())
                .flatMap(serviceB::getData)
                .flatMap(serviceC::getData)
                .doOnNext(this::saveResponse);

• Adds support for Play 2.16.3. Many thanks to junder31 for this contribution.

Improvements

• The agent now supports parsing cgroup ids that do not contain docker-. Previously, the agent only supported docker cgroup ids that contained docker- in them, such as 1:cpu:/system.slice/docker-12345abcde.scope. The agent now supports parsing cgroup ids such as 1:cpu:/system.slice/crio-12345abcde.scope.

Fixes

• Prevents the agent from logging a timeout exception when using New Relic Edge with Infinite Tracing but the agent hasn’t sent spans in a while.
• Prevents the agent from logging a socket exception when trying to retrieve cloud provider information in a non-cloud environment.
• Adds New Relic EU certifications if ca_bundle_path is specified. This fix also came with the reintroduction of the use_private_ssl config, which can be set to add our agent certs to the truststore.

Support statement:

• New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life.