Java agent release notesRSS

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.

Novos recursos e melhorias

• Suporte ao Java 19 1022

• Suporte ao Play 2.8.16+ 981

• Suporte ao ojdbc8 v21.1.0.0+ 1042

• Suporte a JVMs Semeru/OpenJ9 993

• Suporte ao encaminhamento de logs para java.util.logging (JUL) 1049

• Suporte ao encaminhamento de dados de contexto de log 866

  O agente agora pode encaminhar dados no Mapped Diagnostic Context (MDC, logback/slf4j) e ThreadContext (log4j2) como atributos ao encaminhar registros de log. Quando o recurso estiver habilitado, esses atributos serão adicionados aos registros de log com um prefixo context.. Para obter detalhes sobre como habilitar este recurso, consulte a documentação do context_data.

• Aumento do limite de eventos personalizados 1036

  Esta versão aumenta o limite padrão de eventos personalizados de 10.000 eventos por minuto para 30.000 eventos por minuto. No cenário em que os eventos personalizados estavam sendo limitados, essa alteração permitirá que mais eventos personalizados sejam enviados para a New Relic. Há também um novo limite máximo configurável de 100.000 eventos por minuto. Para alterar os limites, consulte a documentação para max_samples_stored. Para saber mais sobre a mudança e como determinar se eventos personalizados estão sendo descartados, consulte nossa postagem no Explorers Hub.

• Métricas em nível de código ativadas por padrão 1037

  A funcionalidade de métricas de nível de código introduzida com o agente 7.10 agora está habilitada por padrão. Este recurso causará um aumento no consumo de dados. A quantidade depende da aplicação. Para desativar as métricas de nível de código, consulte as instruções em nossa documentação de métricas de nível de código.

Correções

• Evita que uma exceção seja lançada na instrumentação do Jedis 1011
• Melhoria nas transações Http4s 1006
• Correção da API noticeError que não verificava se os erros eram esperados 1014
• Adiciona comando para consultas do Lettuce a clusters 1031
• Correção de exceção ao gerar o jar do agente a partir de um repositório limpo 1048
• Melhor tratamento de erros para métricas em nível de código 1021 1051
• Correção de spans do HttpUrlConnection que não encerravam em exceção 1053

Aviso de descontinuação

Os seguintes módulos de instrumentação estão sendo descontinuados para remoção:

• 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

Os atributos de transação/span httpResponseCode, response.status e response.statusMessage estão descontinuados e serão removidos em uma versão futura. Estes foram substituídos por http.statusCode e http.statusText.

Declaração de apoio

A New Relic recomenda que você atualize o agente regularmente para garantir que obtenha os recursos e benefícios de desempenho mais recentes. Além disso, versões mais antigas não serão mais suportadas quando atingirem o fim da vida útil.

Atualizar para a versão mais recente

Para identificar qual versão do agente Java você está usando atualmente, execute java -jar newrelic.jar -v. A versão do seu agente Java será impressa em seu console.

Em seguida, para atualizar para a versão mais recente do agente Java:

1. Faça backup de todo o diretório raiz do agente Java em outro local. Renomeie esse diretório para NewRelic_Agent#.#.#, onde #.#.# é o número da versão do agente.
2. Baixe o agente.
3. Descompacte o novo arquivo de download do agente e copie newrelic-api.jar e newrelic.jar no diretório raiz original do agente Java.
4. Compare seu newrelic.yml antigo com o newrelic.yml recém-baixado do zip e atualize o arquivo, se necessário.
5. Reinicie seu despachante Java.

Se você tiver problemas após a atualização do agente Java, restaure a partir do diretório do agente New Relic do qual foi feito backup.

Atualizar diferenças de configuração do agente

Adicionamos novas configurações a newrelic.yml à medida que lançamos novas versões do agente. Você pode usar diff ou outro utilitário de comparação para ver o que mudou e adicionar as novas configurações ao seu arquivo antigo. Certifique-se de não substituir nenhuma personalização feita no arquivo, como chave de licença, nome do aplicativo ou alterações nas configurações padrão.

Por exemplo, se você diff os arquivos newrelic.yml padrão para as versões 7.10.0 e 7.11.0 do agente Java, os resultados impressos no console serão como:

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

Neste exemplo, essas linhas foram adicionadas ao newrelic.yml padrão na versão 7.11.0 do agente Java. Se você estiver migrando para a 7.11.0 ou superior, você deve adicionar estas novas linhas ao seu newrelic.yml original.

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.

Fixes

• Changed log4j version to 2.12.4 to mitigate the security vulnerability CVE-2021-44832. 766

Mitigation for Java 7

• This release is compatible with Java 7.

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.