Java agent release notesRSS

New features and improvements

• Added support for Slick 3.4.0 on Scala 2.13
• Added support for Embedded Tomcat JMX
• Updated the Java agent's snakeyaml dependency to 1.33
• Added tracer debug logging, which will appear when -Dnewrelic.config.log_level=finest and -Dnewrelic.debug=true are set
• Improved logging when using the recordCustomEvent API now includes event type, key and value
• Added Log4j1 instrumentation to support auto log forwarding
• Added JBoss Logging instrumentation to support auto log forwarding
• Real-time profiling for Java using JFR metrics can now be dynamically enabled/disabled via agent configuration

Fixes

• Removed leading slash in JCache metric names
• Fixed a bug that was preventing Log4j2 metrics from getting disabled properly
• Added a missing delimiter in POSTGRES_DIALECT_PATTERN
• Fixed a ClassCastException in GraphQL 16/17
• Refactored HttpURLConnection instrumentation to fix several bugs that were affecting external calls and distributed traces
• Refactored grpc-1.40.0 instrumentation to ensure that tokens were properly being linked across threads
• Fixed a bug that was causing transactions to fail to link when the Spring Webclient would timeout and emit a ReadTimeoutException

Removals

The following previously deprecated instrumentation modules were removed:

• cassandra-datastax-2.1.2
• httpclient-3.0
• jdbc-embedded-derby-10.2.1.6
• jdbc-embedded-derby-10.10.1.1
• jetty-7
• jetty-7.6
• jetty-9
• jetty-9.0.4
• jetty-9.1
• mongodb-2.12
• mongodb-2.14
• mongodb-3.0
• okhttp-3.0.0
• okhttp-3.4.0
• okhttp-3.5.0

The previously deprecated httpResponseCode, response.status, and response.statusMessage transaction/span attributes were removed. These have been replaced by http.statusCode and http.statusText. If you've any custom dashboards or alerts that query the httpResponseCode, response.status, and response.statusMessage attributes then they will need to be updated to instead use http.statusCode and http.statusText.

Update to latest version

To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console.

Then, to update to the latest Java agent version:

1. Back up the entire Java agent root directory to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number.
2. Download the agent.
3. Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory.
4. Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed.
5. Restart your Java dispatcher.

If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory.

Update agent config differences

We add new settings to newrelic.yml as we release new versions of the agent. You can use diff or another diffing utility to see what's changed, and add the new config settings to your old file. Make sure not to overwrite any customizations you've made to the file, such as your license key, app name, or changes to default settings.

For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like:

➜ diff newrelic_7.10.0.yml newrelic_7.11.0.yml
...
107a108,119
>       # Whether the log events should include context from loggers with support for that.
>       context_data:
>
>         # When true, application logs will contain context data.
>         enabled: false
>
>         # A comma separated list of attribute keys whose values should be sent to New Relic.
>         #include:
>
>         # A comma separated list of attribute keys whose values should not be sent to New Relic.
>         #exclude:
>
125a138
>
128c141
<     enabled: false
---
>     enabled: true
...

In this example, these lines were added to the default newrelic.yml in Java agent version 7.11.0. If you're moving to 7.11.0 or higher, you should add these new lines to your original newrelic.yml.

New features and improvements

Fixes

• Fix bug with log4j2 metrics 1068
• Adds a previously missing delimiter in POSTGRES_DIALECT_PATTERN "|" 1050
• Update snakeyaml lib to v1.33 security patch 1077

Deprecation notice

The following instrumentation modules have been deprecated for removal:

• cassandra-datastax-2.1.2
• httpclient-3.0
• jdbc-embedded-derby-10.10.1.1
• jetty-7
• jetty-7.6
• jetty-9
• jetty-9.0.4
• jetty-9.1
• mongodb-2.12
• mongodb-2.14
• mongodb-3.0
• okhttp-3.0.0
• okhttp-3.4.0
• okhttp-3.5.0

The httpResponseCode, response.status and response.statusMessage transaction/span attributes are deprecated and will be removed in a future release. These have been replaced by http.statusCode and http.statusText.

Update to latest version

To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console.

Then, to update to the latest Java agent version:

1. Back up the entire Java agent root directory to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number.
2. Download the agent.
3. Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory.
4. Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed.
5. Restart your Java dispatcher.

If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory.

Update agent config differences

We add new settings to newrelic.yml as we release new versions of the agent. You can use diff or another diffing utility to see what's changed, and add the new config settings to your old file. Make sure not to overwrite any customizations you've made to the file, such as your license key, app name, or changes to default settings.

For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like:

➜ diff newrelic_7.10.0.yml newrelic_7.11.0.yml
...
107a108,119
>       # Whether the log events should include context from loggers with support for that.
>       context_data:
>
>         # When true, application logs will contain context data.
>         enabled: false
>
>         # A comma separated list of attribute keys whose values should be sent to New Relic.
>         #include:
>
>         # A comma separated list of attribute keys whose values should not be sent to New Relic.
>         #exclude:
>
125a138
>
128c141
<     enabled: false
---
>     enabled: true
...

In this example, these lines were added to the default newrelic.yml in Java agent version 7.11.0. If you are moving to 7.11.0 or higher, you should add these new lines to your original newrelic.yml.

新機能と改善点

• Java 19 1022をサポート

• Play 2.8.16+ 981をサポート

• ojdbc8 v21.1.0.0+ 1042をサポート

• Semeru/OpenJ9 JVM のサポート993

• java.util.logging のログ転送をサポート (JUL) 1049

• ログコンテキストデータの転送をサポート866

  エージェントは、ログ レコードを転送するときに、Mapped Diagnostic Context (MDC、logback/slf4j) および ThreadContext (log4j2) のデータを属性として転送できるようになりました。この機能を有効にすると、これらの属性はcontext.プレフィックス付きでログ レコードに追加されます。この機能を有効にする方法の詳細については、 context_dataのドキュメントを参照してください。

• カスタムイベント制限の増加1036

  このバージョンでは、カスタムイベントのデフォルトの制限が1分あたり10,000イベントから1分あたり30,000イベントに引き上げられます。カスタムイベントが制限されていたシナリオでは、この変更により、より多くのカスタムイベントをNew Relicに送信できるようになります。また、1分あたり100,000イベントという新しい設定可能な最大制限もあります。制限を変更するには、max_samples_storedのドキュメントをご覧ください。変更の詳細と、カスタムイベントがドロップされているかどうかを判断する方法については、Explorers Hubの投稿をご覧ください。

• コードレベルのメトリクスはデフォルトでオン1037

  エージェント 7.10 で導入されたコードレベル メトリクス機能がデフォルトで有効になるようになりました。 この機能により、データの消費量が増加します。金額はアプリケーションによって異なります。 コードレベル メトリクスを無効にするには、 コードレベル メトリクスのドキュメントの手順を参照してください。

修正

• Jedis 計装1011で例外がスローされるのを防ぐ
• Http4sトランザクション1006の改善
• 予想されたエラーかどうかをnoticeError APIが検証しない問題を修正1014
• クラスター1031に Lettuce クエリのコマンドを追加します
• クリーンなリポジトリ1048からエージェント jar をビルドする際の例外を修正しました
• コードレベルのメトリクスのエラー処理の改善1021 1051
• 例外1053で HttpUrlConnection スパンが終了しない問題を修正しました

廃止のお知らせ

次の計装モジュールは削除対象として非推奨となっています。

• cassandra-datastax-2.1.2
• httpクライアント-3.0
• jdbc-embedded-derby-10.10.1.1
• 桟橋-7
• 桟橋-7.6
• 桟橋-9
• 桟橋-9.0.4
• 桟橋-9.1
• mongodb-2.12
• mongodb-2.14
• mongodb-3.0
• okhttp-3.0.0
• okhttp-3.4.0
• okhttp-3.5.0

httpResponseCode 、 response.status 、およびresponse.statusMessageトランザクション/スパン属性は非推奨であり、将来のリリースで削除される予定です。これらはhttp.statusCodeとhttp.statusTextに置き換えられました。

サポートステートメント

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

最新バージョンへのアップデート

現在使用中のJavaエージェントのバージョンを特定するには、java -jar newrelic.jar -vを実行します。Javaエージェントのバージョンがコンソールに出力されます。

次に、最新バージョンのJavaエージェントにアップデートするには、以下の手順に従います。

1. すべてのJavaエージェントのルートディレクトリを別の場所にバックアップします。そのディレクトリの名前をNewRelic_Agent#.#.#に変更します。ここで、#.#.#はエージェントのバージョン番号です。
2. エージェントをダウンロードします。
3. 新しいエージェントのダウンロードファイルを解凍し、newrelic-api.jarとnewrelic.jarを元のJavaエージェントのルートディレクトリにコピーします。
4. 古いnewrelic.ymlとzipからダウンロードした新しいnewrelic.ymlを比較し、必要に応じてファイルを更新します。
5. Javaディスパッチャを再起動します。

Javaエージェントのアップデート後に問題が発生する場合は、バックアップしたNew Relicエージェントディレクトリから復元します。

エージェント設定の差分のアップデート

エージェントの新しいバージョンをリリースする際に、newrelic.ymlに新しい設定を追加します。diffまたは別の差分ユーティリティを使用して変更内容を確認してから、新しい設定を古いファイルに追加できます。ライセンスキー、アプリ名、デフォルト設定の変更など、ファイルに対して行ったカスタマイズを上書きしないようにしてください。

たとえば、 Javaバージョン 7.10.0 および 7.11.0 のデフォルトのnewrelic.ymlファイルをdiffすると、コンソールに表示される結果は次のようになります。

➜ diff newrelic_7.10.0.yml newrelic_7.11.0.yml
...
107a108,119
>       # Whether the log events should include context from loggers with support for that.
>       context_data:
>
>         # When true, application logs will contain context data.
>         enabled: false
>
>         # A comma separated list of attribute keys whose values should be sent to New Relic.
>         #include:
>
>         # A comma separated list of attribute keys whose values should not be sent to New Relic.
>         #exclude:
>
125a138
>
128c141
<     enabled: false
---
>     enabled: true
...

この例では、これらの行はJavaエージェント バージョン 7.11.0 のデフォルトのnewrelic.ymlに追加されました。 7.11.0 以降に移行する場合は、これらの新しい行を元のnewrelic.ymlに追加する必要があります。

New features and improvements

Added the following Jakarta EE 9/9.1 compatible instrumentation:

• Jetty 11
• Tomcat 10
• Enterprise Java Beans 4.0
• Jakarta RS/WS
• Jersey 3+
• Jersey Client 3
• JSP 3
• Servlet 5 & 6
• Jakarata.xml
• JMS 3
• Glassfish 6.0
• Open Liberty 21.0.0.12+

Code level metrics

For traced methods in automatic instrumentation or from @Trace annotations, the agent is now capable of reporting metrics with method-level granularity. When the new functionality is enabled, the agent will associate source-code-related metadata with some metrics. Then, when the corresponding Java class file that defines the methods is loaded up in a New Relic CodeStream-powered IDE, the four golden signals for each method will be presented to the developer directly.

Agent log forwarding now adds the following attributes to log events for the log4j2 and logback1.2 frameworks:

• thread.name
• thread.id
• logger.name
• logger.fqcn
• error.class
• error.stack
• error.message

Fixes

Fixed an issue with distributed tracing headers not being added on external requests made with the HttpUrlConnection client

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.

Full changelog: https://github.com/newrelic/newrelic-java-agent/compare/v7.9.0...v7.10.0

Update to latest version

To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console.

Then, to update to the latest Java agent version:

1. Back up the entire Java agent root directory to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number.
2. Download the agent.
3. Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory.
4. Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed.
5. Restart your Java dispatcher.

If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory.

Update agent config differences

We add new settings to newrelic.yml as we release new versions of the agent. You can use diff or another diffing utility to see what's changed, and add the new config settings to your old file. Make sure not to overwrite any customizations you've made to the file, such as your license key, app name, or changes to default settings.

For example, if you diff the default newrelic.yml files for Java agent versions 7.7.0 and 7.8.0, the results printed to the console will be:

➜ diff newrelic_7.7.0.yml newrelic_7.8.0.yml
98c98
<     #forwarding:
---
>     forwarding:
100,101c100,101
<       # When true, application logs will be forwarded to New Relic. The default is false.
<       #enabled: false
---
>       # When true, application logs will be forwarded to New Relic. The default is true.
>       enabled: true

In this example, these lines were added to the default newrelic.yml in Java agent version 7.8.0. If you are moving to 7.8.0 or higher, you should add these new lines to your original newrelic.yml.

New features and improvements

• Where applicable, existing instrumentation has been tested and verified as compatible with Jakarta EE 8. 900
• Add new instrumentation to support Jetty 10. 936
• Update to jfr-daemon 1.9.0 to address CVE-2020-29582 and improve CPU overhead. 937
• Add support to pass a boolean environment variable NEWRELIC_DEBUG where setting it to true activates the debug configuration. 890
• Improved performance by internally replacing regex replace with iterative char replace (thanks to @zowens for this contribution) 933

Fixes

• Update the httpurlconnection instrumentation to use newer distributed tracing APIs so that spans are correctly marked as external calls in distributed traces and contain the expected http.* attributes. 885
• Illegal Access Exception is no longer thrown from apps using NR agent with scala 2.12 and Java 11. 876

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.

Update to latest version

To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console.

Then, to update to the latest Java agent version:

1. Back up the entire Java agent root directory to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number.
2. Download the agent.
3. Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory.
4. Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed.
5. Restart your Java dispatcher.

If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory.

Update agent config differences

We add new settings to newrelic.yml as we release new versions of the agent. You can use diff or another diffing utility to see what's changed, and add the new config settings to your old file. Make sure not to overwrite any customizations you've made to the file, such as your license key, app name, or changes to default settings.

For example, if you diff the default newrelic.yml files for Java agent versions 7.7.0 and 7.8.0, the results printed to the console will be:

➜ diff newrelic_7.7.0.yml newrelic_7.8.0.yml
98c98
<     #forwarding:
---
>     forwarding:
100,101c100,101
<       # When true, application logs will be forwarded to New Relic. The default is false.
<       #enabled: false
---
>       # When true, application logs will be forwarded to New Relic. The default is true.
>       enabled: true

In this example, these lines were added to the default newrelic.yml in Java agent version 7.8.0. If you are moving to 7.8.0 or higher, you should add these new lines to your original newrelic.yml.

New features and improvements

• Updated the agent to use caffeine 2.9.3 832
• Refactored the log.level attribute name on LogEvents to instead be level 858
• Kafka instrumentation - supports metrics for kafka-clients versions 3.x. 860 and 865
• Update to jfr-daemon 1.8.0 869
• Lettuce instrumentation - supports lettuce-core 4.3 up to 6.x. Please remove any other (experimental/incubating) lettuce extensions or else Redis database metrics could be doubled. 872

Fixes

• Fixed CQLParser getOperationAndTableName exception handling. Exceptions are now handled within the CQLParser. 857
• Removed akka-http-core bindAndHandle instrumentation to resolve scenarios where duplicated transactions could result 850 (see Scala Akka HTTP core instrumentation for more details)

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.

New features and improvements

• Supports Java 18 813
• APM logs in context. Automatic application log forwarding is now enabled by default. This version of the agent will automatically send enriched application logs to New Relic. To learn more about this feature see Java: Configure logs in context, and additional configuration options are available Java agent configuration: Config file. To learn about how to toggle log ingestion on or off by account see Disable automatic logging 817
• Added instrumentation support for the Postgres, MySQL, Oracle & MSSQL R2DBC connectors 810, 816, 829, and 828

Fixes

• Patches a security issue related to an older version of jszip that is included in the Java agent API Javadoc jar 820

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.

New features and improvements

• APM logs in context: a quick way to view logs no matter where you are in the platform
  • Adds support for logging metrics which shows the rate of log message by severity in the Logs chart in the APM Summary view. This is enabled by default in this release.
  • Adds support for forwarding application logs to New Relic. This automatically sends application logs that have been enriched to power automatic logs in context. This is disabled by default in this release. This may be on by default in a future release.
  • Adds support for enriching application logs written to disk or standard out. This can be used with another log forwarder to power logs in context if in-agent log forwarding is not desired. We recommend enabling either log forwarding or local log decorating, but not both features. This is disabled by default in this release.
  • To learn more about APM logs in context and the configuration options, please see the documentation here. 718
• Added instrumentation support for the MariaDB & H2 R2DBC connectors 799 724
• Updated agent support for Jedis 4.0.0+ 698
• Updated agent support for Cassandra dataStax 4+ 690

Fixes

• Guard against intermittent null pointer exceptions 707
• Support CSP nonce parameter for RUM header and footer 591
• Fixed an issue with auto app naming and distributed tracing transactions 566
• Increased maximum TransactionError message size 581
• The httpResponseCode, response.status and response.statusMessage transaction/span attributes are deprecated and will be removed in a future release. These have been replaced by http.statusCode and http.statusText 513:

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.