New features and improvements
- Obfuscate JVM properties 2114
 The Java agent will now obfuscate values passed to JVM properties. For example:-Dprop=12345will now be sent as-Dprop=obfuscated. The documentation has information on how to disable obfuscation and how to add exceptions.
- Cloud API 2081
 The Cloud API allows cloud provider account information to be provided to the agent. This will allow the agent to populate thecloud.resource_idattribute in calls to select cloud services.
 The API documentation has information on how to use it programmatically.
 This information can also be provided using a configuration option.
- Support distributed tracing for Kafka Stream 3.7.x 2095 
- Report if agent was installed via Azure site extension 2094 
- Lazy initialization of GUIDs on DefaultTracers 2088 
- Java HttpClient: Addition of status code to reported externals 2089 
- AWS Lambda: populate - cloud.resource_idusing data from Cloud API 2115
- Kinesis Data Streams: populate - cloud.resource_id2112
- DynamoDB: populate - cloud.resource_id2113
Fixes
- Use recordResponseTimeMetric instead of recordMetric 2128 
- Use WeakReference HttpUrlConnection instrumentation 2082 
- Fix a bug where Jetty 12 would not properly link distributed traces 2140 
- Update to JFR daemon 1.13.0 2129 
 This update changes the HTTP client used, which caused problems with some proxies.
IAST
- CSEC version bump to 1.5.1 2076 
- Changelog: https://github.com/newrelic/csec-java-agent/releases/tag/1.5.1 
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:
- Back up the entire Java agent root directory to another location. Rename that directory to NewRelic_Agent#.#.#, where#.#.#is the agent version number.
- Download the agent..
- Unzip the new agent download file, then copy newrelic-api.jarandnewrelic.jarinto the original Java agent root directory.
- Compare your old newrelic.ymlwith the newly downloadednewrelic.ymlfrom the zip, and update the file if needed.
- 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.