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.

Nouvelle fonctionnalité et améliorations

• Prise en charge de Java 19 1022

• Prise en charge de Play 2.8.16+ 981

• Prise en charge de ojdbc8 v21.1.0.0+ 1042

• Prise en charge des JVM Semeru/OpenJ9 993

• Prise en charge du transfert de logs pour java.util.logging (JUL) 1049

• Prise en charge du transfert des données de contexte de log 866

  L'Agent peut désormais transmettre les données du Mapped Diagnostic Context (MDC, logback/slf4j) et du ThreadContext (log4j2) sous forme d'attributs lors du transfert des enregistrements de logs. Lorsque la fonctionnalité est activée, ces attributs seront ajoutés aux enregistrements de log avec un préfixe context.. Pour plus de détails sur l'activation de cette fonctionnalité, consultez la documentation relative à context_data.

• Augmentation de la limite des événements personnalisés 1036

  Cette version augmente la limite par défaut des événements personnalisés de 10 000 événements par minute à 30 000 événements par minute. Dans le cas où les événements personnalisés étaient limités, ce changement permettra d’envoyer davantage d’événements personnalisés à New Relic. Il existe également une nouvelle limite maximale configurable de 100 000 événements par minute. Pour modifier les limites, consultez la documentation de max_samples_stored. Pour en savoir plus sur ce changement et comment déterminer si des événements personnalisés sont rejetés, consultez notre publication sur l’Explorers Hub.

• Métriques au niveau du code activées par défaut 1037

  La fonctionnalité de métriques au niveau du code introduite avec l'Agent 7.10 est désormais activée par défaut. Cette fonctionnalité entraînera une augmentation de la consommation de données. La quantité dépend de l'application. Pour désactiver les métriques au niveau du code, consultez les instructions de notre documentation sur les métriques au niveau du code.

Corrections

• Empêcher la levée d'une exception dans l'instrumentation Jedis 1011
• Amélioration des transactions Http4s 1006
• Correction de l'API noticeError qui ne vérifiait pas si les erreurs étaient attendues 1014
• Ajoute une commande pour les requêtes Lettuce vers les clusters 1031
• Correction d'une exception lors de la construction du JAR de l'agent à partir d'un dépôt propre 1048
• Meilleure gestion des erreurs pour les métriques au niveau du code 1021 1051
• Correction des spans HttpUrlConnection ne se terminant pas lors d'une exception 1053

Avis de dépréciation

Les modules d'instrumentation suivants sont dépréciés en vue de leur suppression :

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

Les attributs de transaction/span httpResponseCode, response.status et response.statusMessage sont obsolètes et seront supprimés dans une future version. Ceux-ci ont été remplacés par http.statusCode et http.statusText.

Déclaration de soutien

New Relic recommande de mettre à jour l'agent régulièrement pour vous assurer de bénéficier des dernières fonctionnalités et améliorations de performances. De plus, les anciennes versions ne seront plus prises en charge lorsqu'elles atteindront la fin de vie.

Mise à jour vers la dernière version

Pour identifier la version de l’agent Java que vous utilisez actuellement, exécutez java -jar newrelic.jar -v. Votre version d'agent Java sera imprimée sur votre console.

Ensuite, pour mettre à jour vers la dernière version de l'agent Java :

1. Sauvegardez l’ intégralité du répertoire racine de l’agent Java vers un autre emplacement. Renommez ce répertoire en NewRelic_Agent#.#.#, où #.#.# est le numéro de version de l'agent.
2. Téléchargez l'agent.
3. Décompressez le nouveau fichier de téléchargement de l'agent, puis copiez newrelic-api.jar et newrelic.jar dans le répertoire racine de l'agent Java d'origine.
4. Comparez votre ancien newrelic.yml avec le newrelic.yml nouvellement téléchargé à partir du zip et mettez à jour le fichier si nécessaire.
5. Redémarrez votre répartiteur Java.

Si vous rencontrez des problèmes après la mise à jour de l'agent Java, effectuez la restauration à partir du répertoire de l'agent New Relic sauvegardé.

Différences de configuration de l'agent de mise à jour

Nous ajoutons de nouveaux paramètres à newrelic.yml à mesure que nous sortons de nouvelles versions de l'agent. Vous pouvez utiliser diff ou un autre utilitaire de comparaison pour voir ce qui a changé et ajouter les nouveaux paramètres de configuration à votre ancien fichier. Assurez-vous de ne pas écraser les personnalisations que vous avez apportées au fichier, telles que votre clé de licence, le nom de l'application ou les modifications apportées aux paramètres par défaut.

Par exemple, si vous diff les fichiers par défaut newrelic.yml pour les versions 7.10.0 et 7.11.0 de l'agent Java, les résultats imprimés sur la console seront comme suit :

➜ 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
...

Dans cet exemple, ces lignes ont été ajoutées au newrelic.yml par défaut dans la version 7.11.0 de l'agent Java. Si vous passez à la version 7.11.0 ou supérieure, vous devez ajouter ces nouvelles lignes à votre newrelic.yml d'origine.

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.