New features and improvements
- Instrumentation for Spring Webclient 5/6 now captures http status code and http status message 1658
- Add status code to
grpc-1.40.0client instrumentation 1673 - Add config to set the size limit of attributes on custom events (i.e.
newrelic.config.custom_insights_events.max_attribute_value). Default size is255characters and the max is4095. 1683 - Add Spring instrumentation modules to support proper transaction naming (route + HTTP method) of traditional annotated spring controllers as well as controllers that inherit annotations from interfaces, super classes or custom annotations. Note that because the new instrumentation can change transaction names, enabling this "enhanced transaction naming" is gated by the
newrelic.config.class_transformer.enhanced_spring_transaction_namingagent configuration option, which isfalseby default. Thanks to @mgr32 for their help with validating the naming changes. 1675 - Add instrumentation for Vert.x 4.5.x web client and futures 1704
Fixes
- Remove erroneous printing of stack trace in
SlowTransactionManager1684 - Convert the
ProcessPointCutover to a weaver instrumentation module to better handle cases where it is used in a multi-threaded environment. 1685
Removals
- Remove support for setting agent config with rarely used lower-case, dotted environment variable names (e.g.
newrelic.config.labels). Customers relying on lower-case, dotted environment variables should switch to the standard upper-case, underscore names (e.g.NEW_RELIC_CONFIG_LABELS). There are no changes to documented system property behavior (vianewrelic.config., server-side config, YAML, or standard environment variable (viaNEW_RELIC_). 1598
Deprecations
- The browser footer injection APIs have been deprecated and will be removed in a future agent release. The header injection API now adds both the header and footer scripts. 1679
The following instrumentation modules are deprecated and will be removed in the next major release:
aws-wrap-0.7.0java.completable-future-jdk8play-2.3spring-3.0.0netty-3.4Struts v1
IAST
- Update Security Agent to Public Release version
1.1.01710 - Changelog: https://github.com/newrelic/csec-java-agent/releases/tag/1.1.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:
- 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 are 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.