Java agent v9.3.0

New features and improvements

• Add log_level_denylist config to default yaml 2830

• Solr 9 JMX module 2821

• New centralized token counting strategy for capturing token counts from LLM Responses. 2837

• Support for capturing JDBC batch operations; specifically the addBatch() and executeBatch() methods. 2840

• XML RPC instrumentation module to replace legacy point cut 2841

• Add a new JFR specific config jfr.use_display_name. If set to true, the agent will set the JFR host name to the value in the process_host.display_name configuration. The default is false to preserve old behavior.

If jfr.use_display_name is true but the display_name config is empty, the JfrService will fallback to the old behavior for the host name.

common: &default_settings
  jfr:
    use_display_name: true

2847

• Remove unneeded segment creation in java.xmlrpc module 2853

• Update aws-bedrock-runtime-2.20 Module with a new token counting strategy for each of the models. 2845

• New license key obfuscation algorithm 2864

• Support for Micronaut Http Clients versions 3.5.0+ 2834

• Support for Apache Camel 3.9.0 and up 2896 2901

• Support for Kafka Clients 4.0.0 and up 2896

• Internal dependency Log4j Core Upgrade from 2.17.1 to 2.25.4 2833

• AWS DAX Support starting from 2.0.0 to latest 2873

• Add instrumentation for Spring AI completion and embedding clients for versions 1.0.0 and up. This adds new instrumentation modules:

spring-ai-client-chat-1.0.0
spring-ai-model-1.0.0

2842

• Core Tracing - Drop SpanEvents and Re-Parent dropped SpanLinks 2881

• Pointcut replacements

  • Remove SpringDispatcherPointCut and SpringExceptionHandlerPointCut and instead move the functionality into our Spring instrumentation modules.
  • Replace HandlerInterceptorPointCut 28712886

• Support Micronaut’s BlockingHttpClient 2860

• Add support for AI Model Context Protocol 1.0.0 to latest. 2880

Fixes

• Fix coroutines instrumentation. Fixes include:

  • Better tracking of asynchronous behavior by instrumenting gaps that were found where execution can jump to another thread.
  • Better naming on Coroutines and Continuations. Existing naming was too generic. New naming identifies according to whether it is started via runBlocking, async, withContext or launch.
  • Removed some utility methods that were no longer used 2802

• Fixes excessive number of unexpired async tokens when instrumenting Micronaut. 2792

• Resolution of Mule 4.9 IllegalAccessError 2859

• Fix a mis-recording of the Instrumented and Kept metrics for Core Tracing, as they were originally being recorded as a time metric. 2881

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.

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.