Java agent v8.15.0

New features and improvements

• Addition of AWS Lambda SDK instrumentation by @meiao in 1998
• Reporting of Flyway migration events by @jtduffy in 2021
• Add support for using an environment variable for config file location by @jtduffy in 2022
• Support AWS Kinesis V1 and V2 SDKs by @obenkenobi in 2031
• Addition of kafka-clients-node-metrics-3.7.0 Instrumentation module by @deleonenriqueta in 2039
• Add instrumentation for glassfish-jul-extension logging library by @jasonjkeller in 2049
• Java 23 support by @jasonjkeller in 2055
• Support reporting of ECS Fargate Docker ids by @jtduffy in 2050
• Actuator endpoint transaction naming for Spring Boot 3 by @jtduffy in 2077

Fixes

• Slick 3.5.0 instrumentation bug fix by @kanderson250 in 2025
• Protect against Http2Headers methods throwing exceptions in Netty instrumentation by @jasonjkeller in 2042
• Fix an issue where the Kinesis instrumentation is generating ERROR logs due to a NullPointerException by @obenkenobi in 2052

IAST

• CSEC version bump to 1.5 by @jtduffy in 2076
• Changelog: https://github.com/newrelic/csec-java-agent/releases/tag/1.5.0

Full Changelog: https://github.com/newrelic/newrelic-java-agent/compare/v8.14.0...v8.15.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.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.
>       include_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.